diff --git a/de_DE.ISO8859-1/articles/Makefile.inc b/de_DE.ISO8859-1/articles/Makefile.inc index cf192d078c..06e8d21cb6 100644 --- a/de_DE.ISO8859-1/articles/Makefile.inc +++ b/de_DE.ISO8859-1/articles/Makefile.inc @@ -1,11 +1,10 @@ # # The FreeBSD Documentation Project # The FreeBSD German Documentation Project # # $FreeBSD$ # $FreeBSDde: de-docproj/articles/Makefile.inc,v 1.1 2004/11/28 21:13:46 jkois Exp $ # basiert auf: 1.4 # DESTDIR?= ${DOCDIR}/de_DE.ISO8859-1/articles/${.CURDIR:T} -COLLATEINDEX+=-s Symbole diff --git a/de_DE.ISO8859-1/articles/contributing-ports/article.xml b/de_DE.ISO8859-1/articles/contributing-ports/article.xml index 585df8c56a..4882931849 100644 --- a/de_DE.ISO8859-1/articles/contributing-ports/article.xml +++ b/de_DE.ISO8859-1/articles/contributing-ports/article.xml @@ -1,934 +1,936 @@
Zur FreeBSD Ports-Sammlung beitragen Dieser Artikel beschreibt, wie man zur FreeBSD Ports-Sammlung beitragen kann. Übersetzt von Martin Wilke. Sam Lawrance Mark Linimon &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Ports, beitragen Einleitung Die Ports-Sammlung ist ständig in Bearbeitung. Wir wollen unseren Benutzern eine einfach zu verwendende, aktuelle und qualitativ hochwertige Quelle für Software von Drittanbietern bereitstellen. Deshalb suchen wir immer Personen, die etwas von ihrer Zeit aufwenden können, um uns dabei zu helfen. An der Ports-Sammlung zu arbeiten ist ein hervorragender Weg, um zu helfen und dem Projekt etwas zurück zu geben. Egal, ob Sie eine dauerhafte Funktion oder eine kleine Aufgabe für einen regnerischen Tag suchen - wir würden uns über Ihre Hilfe freuen! Als Freiwillige/r setzen Sie sich selbst Grenzen. Sie sollten sich aber immer bewusst sein, dass andere Mitglieder der &os; Community möglicherweise auch etwas von Ihnen erwarten. Sie sollten dies auf jeden Fall in Ihre Entscheidung mit einbeziehen. Was Sie tun können, um uns zu helfen Um die Ports-Sammlung aktuell und in einem sauberen Zustand zu halten, sind viele Dinge zu erledigen: Finden Sie eine begehrte oder nützliche Software und erstellen Sie einen Port. Es gibt eine große Anzahl von Ports, die keinen Maintainer haben. Werden Sie Maintainer und betreuen Sie einen Port. Wenn Sie einen Port erstellt haben oder betreuen, vergessen Sie nicht, welche Aufgaben ein Maintainer hat. Wenn Sie nur eine kleine Aufgabe suchen, könnten Sie beispielsweise einen Bug oder defekten Port fixen. Erstellen Sie einen neuen Port Es gibt ein eigenes Handbuch, das beim Erstellen (und Aktualisieren) von Ports hilft. Es heißt Porter-Handbuch. Das Porter-Handbuch ist die beste Referenz, um mit dem Ports-System zu arbeiten. Es enthält Details darüber, wie das Ports-System funktioniert und wie man mit/an den Ports arbeitet. Übernahme eines nicht betreuten Ports Einen nicht betreuten Port aussuchen Die Betreuung eines Ports ist ein guter Weg zu helfen. Nicht betreute Ports bleiben nur aktuell und stabil, wenn ein Freiwilliger dafür sorgt. Es gibt eine grosse Anzahl nicht betreuter Ports, daher ist es eine gute Idee für den Einstieg, einen verwaisten Port zu übernehmen, den Sie auch regelmässig selbst verwenden. Nicht betreute Ports haben als MAINTAINER den Wert ports@FreeBSD.org. Eine Liste der derzeit nicht betreuten Ports sowie Informationen zu deren aktuellen Fehlern und Problemen können Sie unter &os; Ports Monitoring System einsehen. Einige Ports beeinflussen durch Abhängigkeiten und Slave-Port-Beziehungen eine grosse Anzahl anderer Ports. Generell ist es ratsam, dass Maintainer über ein Mindestmaß an Erfahrung verfügen, bevor Sie derartige Ports betreuen. Um herauszufinden, ob ein Port Abhängigkeiten oder Slave-Ports hat, können Sie im Master-Port-Index /usr/ports/INDEX nachsehen. (Der Name der Datei kann bei den einzelnen Releases von FreeBSD variieren, z.B. INDEX-8). Einige Ports haben bedingte Abhängigkeiten, die nicht im Standard-Index INDEX zu finden sind. Wir erwarten, dass Sie in der Lage sind, solche Ports zu erkennen, indem Sie sich die Makefiles anderer Ports ansehen. Wie man einen Port übernimmt Bitte vergewissern Sie sich, dass Sie die Aufgaben eines Maintainers verstanden haben. Lesen Sie bitte auch das Porter-Handbuch. Übernehmen Sie nicht mehr Aufgaben, als Sie bewältigen können. Sie können einen nicht reservierten Port jederzeit übernehmen, die Entscheidung liegt bei Ihnen. Wenn Sie dazu bereit sind, setzen Sie MAINTAINER auf Ihre E-Mail-Adresse und reichen einen Problembericht (PR) mit den von Ihnen vorgenommenen Änderungen ein. Wenn beim Kompilieren des Ports Fehler auftreten oder eine Aktualisierung notwendig ist, können Sie derartige Änderungen dem selben PR beifügen. Das ist sehr hilfreich, weil sich viele Committer weigern, die Wartung eines Ports zu übergeben, wenn jemand nicht die nötige Erfahrung mit &os; vorweisen kann. Das Einreichen von PRs, die Kompilierfehler beheben oder Ports aktualisieren, ist der beste Weg, um Erfahrung zu sammeln. Erstellen Sie Ihren PR mit der category ports und der class change-request. Ein Committer wird Ihren PR analysieren, die Änderungen committen und danach den PR abschließen. Manchmal kann dieser Prozess eine Weile dauern (auch Committer sind "nur" freiwillige Helfer!). Die Herausforderung als Ports-Maintainer Dieser Abschnitt erklärt, warum Ports betreut werden müssen, und beschreibt die Pflichten eines Ports-Maintainers. Warum müssen Ports betreut werden? Einen Port zu erstellen ist eine einmalige Sache. Sicherzustellen, dass ein Port aktuell ist und auch in Zukunft funktioniert, erfordert hingegen eine laufende Betreuung und einen nicht zu unterschätzenden Arbeitsaufwand. Maintainer sind Personen, die einen Teil ihrer Zeit dazu verwenden, einen Port für andere FreeBSD-Anwender aktuell und einfach installierbar zu halten. Der wichtigste Grund für die Betreuung von Ports ist der Wunsch, der &os;-Community die neueste und beste Drittanbieter-Software zur Verfügung zu stellen. Eine zusätzliche Herausforderung ist die Aufrechterhaltung der Funktionalität einzelner Ports innerhalb der sich verändernden Ports-Sammlung. Als Ports-Maintainer werden Sie folgende Herausforderungen meistern: Neue Software-Versionen und Aktualisierungen Neue Versionen und Aktualisierung von bereits portierter Software werden kontinuierlich veröffentlicht und müssen in die Ports-Sammlung integriert werden, um aktuelle Software ausliefern zu können. Änderungen an Abhängigkeiten ihres Ports Wenn bedeutende Änderungen an den Abhängigkeiten Ihres Ports gemacht wurden, kann es vonnöten sein, diesen zu aktualisieren, damit er weiterhin korrekt funktioniert. Änderungen an abhängigen Ports Wenn andere Ports von einem Ihrer betreuten Ports abhängig sind, müssen Änderungen eventuell mit anderen Maintainern abgesprochen werden. Zusammenwirken von anderen Benutzern, Maintainern und Entwicklern Ein Teil der Aufgabe eines Maintainers ist es, Support zu leisten. Damit ist kein Hauptsupport für die Software gemeint (wir haben allerdings nichts dagegen, wenn Sie sich dennoch entscheiden, dies zu tun). Ihre Aufgabe ist aber, sich um &os;-spezifische Fragen zu Ihren Ports zu kümmern. Bugs finden Eine Portierung könnte vielleicht von &os;-spezifischen Bugs beeinflusst werden. In einem solchen Fall ist es Ihre Aufgabe, den Fehler zu finden und zu beheben. Daher sollten Sie Ihren Port umfassend testen, um derartige Probleme zu entdecken, bevor Sie einen Port in die Ports-Sammlung aufnehmen. Änderungen an Ports, Infrastruktur und Lizenzen Gelegentlich werden die Werkzeuge für das Bauen von Ports erneuert oder es wird ein neuer Vorschlag zur Infrastruktur der Ports-Sammlung gemacht. Sie sollten von diesen Änderungen wissen, falls Ihre Ports betroffen sind und aktualisiert werden müssen. Änderungen am Basissystem &os; ist in ständiger Entwicklung. Änderungen an Software, Bibliotheken, dem Kernel oder sogar Lizenzänderungen können Änderungsbedarf an den Ports auslösen. Aufgaben eines Maintainers Halten Sie Ihre Ports aktuell Dieser Abschnitt bietet einen kurzen Überblick zu diesem Thema. Ausführliche Informationen zur Aktualisierung von Ports finden Sie im Porter-Handbuch. Achten Sie auf Aktualisierungen Überwachen Sie Ihr Programm auf neue Versionen der Software, Aktualisierungen und Security-Fixes. Ankündigungen in Mailinglisten oder auf Nachrichtenseiten im Internet sind dabei sehr hilfreich. Manchmal werden Sie von Benutzern gefragt werden, wann Ihr Port eine Aktualisierung bekommt. Wenn Sie mit anderen Dingen beschäftigt sind oder aus sonstigen Gründen keine Aktualisierung bereitstellen können, fragen Sie den Benutzer doch einfach, ob er Ihnen bei der Aktualisierung helfen möchte. Es kann auch vorkommen, dass Sie eine automatisch generierte E-Mail vom &os; Ports Version Check bekommen, die Sie darüber informiert, dass eine aktuellere Version des Distfiles Ihres Ports verfügbar ist. Weitere Informationen über dieses System (inklusive einer Erklärung, wie Sie derartige E-Mails in Zukunft vermeiden können) finden Sie ebenfalls in einer solchen Nachricht. Aufnehmen von Änderungen Wenn verfügbar, integrieren Sie die Veränderungen in den Port. Sie müssen in der Lage sein, einen Patch zwischen dem alten und dem neuen Port zu generieren. Nachprüfung und Test Überprüfen und testen Sie ihre Änderungen gründlich: Kompilieren, installieren und testen Sie ihren Port auf so vielen Plattformen und Architekturen, wie Sie können. Es kommt sehr häufig vor, dass ein Port auf einem Entwicklungszweig oder einer Plattform funktioniert, auf einer anderen Plattform aber Fehler erzeugt. Stellen Sie sicher, dass die Abhängigkeiten ihres Ports vollständig sind. Die empfohlene Vorgehensweise dafür ist, dass Sie ihre eigenen Ports in einer Tinderbox kompilieren. Weitere Informationen zu diesem Thema finden Sie im Abschnitt Ressourcen dieses Artikels. Stellen Sie sicher, dass die Liste der zu installierenden Dateien und Verzeichnisse aktuell ist. Überprüfen Sie ihren Port mit &man.portlint.1;. Sehen Sie sich dazu den Abschnitt Ressourcen an. Dieser enthält wichtige Informationen zum Einsatz von portlint. Achten Sie darauf, dass Änderungen an Ihrem Port nicht den Bau eines anderen Ports verhindern. Ist dies der Fall, besprechen Sie die von Ihnen durchgeführten Änderungen mit den Maintainern der betroffenen Ports. Dies ist besonders dann wichtig, wenn Ihre Aktualisierung die Shared Library-Version ändert; in diesem Fall werden Sie für die abhängigen Ports einen PORTREVISION-Bump benötigen, damit diese von automatisierten Werkzeugen wie portmaster oder &man.portupgrade.1; auf dem neuesten Stand gehalten werden. Änderungen einreichen Reichen Sie ihre Aktualisierungen mit einem PR ein, welcher die Änderungen erklärt und einen Patch enthält, der die Änderungen zwischen dem Original und Ihrer aktualisierten Version umfasst. Lesen Sie bitte zuerst den Artikel Writing FreeBSD Problem Reports, der das korrekte Einreichen von Problemberichten beschreibt. Bitte schicken Sie kein &man.shar.1;-Archiv des gesamten Ports. Benutzen Sie stattdessen &man.diff.1; -ruN. Auf diese Art und Weise können Committer viel einfacher erkennen, welche Änderungen vorgenommen wurden. Das Porter-Handbuch enthält viele nützliche Informationen zum Upgrading eines Ports. Warten Es kann nur sehr wenig Zeit vergehen, bis sich ein Committer mit Ihrem PR befasst. Es kann aber auch mehrere Wochen dauern, bis eine Reaktion erfolgt - haben Sie bitte Geduld. Feedback geben Wenn ein Committer Probleme in Ihren Änderungen entdeckt, wird er Sie darüber informieren. Eine schnelle Reaktion Ihrerseits ist hilfreich, um Ihren PR rasch bearbeiten zu können. Außerdem hilft es Ihnen, den Faden nicht zu verlieren, wenn Sie versuchen, aufgetretene Probleme zu lösen. Und zuletzt... Ihre Änderungen werden übermittelt und im Anschluss daran wird Ihr Port aktualisiert. Der betreffende PR wird danach vom Committer geschlossen. Herzlichen Glückwunsch, Sie haben es geschafft! Stellen Sie sicher, dass Ihre Ports den Buildprozess weiterhin erfolgreich durchlaufen Dieser Abschnitt beschreibt, wie Sie Probleme entdecken und beheben, die ihre Ports daran hindern, den Buildprozess erfolgreich zu durchlaufen. &os; garantiert nur für die -STABLE-Zweige, dass die Ports-Sammlung korrekt funktioniert. Sie sollten 7-STABLE oder 8-STABLE benutzen, wobei der letztere Zweig bevorzugt wird. Theoretisch sollte es ausreichen, das aktuelle Stable Release des jeweiligen STABLE-Zweigs einzusetzen (da die ABIs in der Regel nicht geändert werden), es empfiehlt sich aber, dem jeweiligen STABLE-Zweig zu folgen. Seit die Mehrheit von &os;-Installationen auf PC-kompatiblen Maschinen arbeitet (i386-Architektur) erwarten wir, dass Ihr Port auf dieser Architektur funktioniert. Ebenfalls bevorzugen wir es, wenn Ports nativ auf der amd64-Architektur funktionieren. Es ist durchaus in Ordnung, um Hilfe zu fragen, wenn Sie keine solche Maschine besitzen. Häufige Fehler beim Umgang mit nicht-i386 Maschinen entstehen, weil Programmierer ür Instanzen und Pointer ints verwendeten, oder weil der relativ simple gcc-Compiler genutzt wird. Immer mehr Programmautoren überarbeiten ihren Code, um diese Fehler zu beseitigen — wenn der Programmautor seinen Code allerdings nicht aktiv betreut, müssen Sie dies eventuell selbst in die Hand nehmen. Sie sollten die folgende Liste durchgehen, um sicherzustellen, dass Ihr Port gebaut werden kann: Achten Sie auf Build-Fehler Überprüfen Sie regelmäßig den Ports Building Cluster pointyhat und den Distfiles-Scanner, um festzustellen, ob einer Ihrer Ports nicht gebaut oder die Distfiles nicht geladen werden können (lesen Sie den Abschnitt Ressourcen dieses Artikels für weitere Informationen zu diesen Systemen). Fehlerberichte kommen eventuell auch von anderen Benutzern oder als automatisierte Meldungen per E-Mail. Sammeln Sie Informationen Wenn Sie ein Problem entdecken, benötigen Sie als Erstes Informationen, die Ihnen dabei helfen, dieses Problem zu beheben. Build-Fehler, die von pointyhat gemeinsam mit Logdateien verschickt werden, zeigen Ihnen, an welcher Stelle der Fehler auftritt. Wenn Ihnen ein Fehler von einem anderen Benutzer mitgeteilt wird, fragen Sie nach, ob er bereit ist, ihnen Informationen zukommen zu lassen, die eventuell bei der Diagnose des Problems helfen können, wie z.B.: Build-Logs. Die Werkzeuge und Optionen, mit denen ein Port gebaut wurde (inklusive der Optionen in /etc/make.conf). Eine Liste installierter Pakete auf dem System kann mit &man.pkg.info.1; erstellt werden. Die &os;-Version, welche benutzt wird, kann mit &man.uname.1; -a ermittelt werden. Wann die Ports-Sammlung das letzte Mal aktualisiert wurde. Wann die INDEX-Datei zuletzt aktualisiert wurde. Suchen und finden Sie eine Lösung Leider gibt es keinen allgemein gültigen Weg, dies zu tun. Denken Sie daran: Wenn Probleme auftauchen bitten Sie einfach jemanden um Hilfe! Ein guter Anfang ist die Mailingliste &a.ports;. Auch die Entwickler der Software selbst sind oft sehr hilfreich. Änderungen übermitteln Genau wie beim Aktualisieren eines Ports sollten Änderungen integriert, geprüft und getestet werden. Reichen Sie Ihre Arbeit als PR ein und geben Sie Feedback, falls dies notwendig ist. Patches an Programmautoren senden Manchmal müssen Sie Patches erstellen, um einen Port unter FreeBSD zum Laufen zu bekommen. Einige (aber nicht alle) Programmautoren nehmen diese Patches in Ihren Code für das nächste Release auf. Dies kann den Benutzern anderer BSD-Systeme helfen und einiges an unnötiger Mehrarbeit ersparen. Bitte betrachten Sie das Versenden von verwertbaren Patches an die Autoren als ein Gebot der Höflichkeit. Ermitteln Sie Bug-Reports und PRs, die Ihre Ports betreffen &os;-spezifische Bugs werden meistens durch falsche Annahmen über Build- und Laufzeitumgebungen, die nicht zu &os; passen, verursacht. Derartige Probleme zu entdecken ist oft sehr schwierig, glücklicherweise sind derartige Probleme aber nicht sehr häufig. Folgende Schritte sind notwendig, um sicherzustellen, dass ihr Port weiterhin wie gewünscht funktioniert: Antworten Sie auf Bug-Reports Bugs können Ihnen als E-Mail durch die GNATS Problem Report database zugestellt werden, Sie können Ihnen aber auch direkt von Benutzern gemeldet werden. Sie sollten innerhalb von 14 Tagen auf PRs und andere Berichte antworten. Versuchen Sie schnellstmöglich zu antworten, selbst wenn Sie nur mitteilen können, dass Sie noch etwas Zeit brauchen, bevor Sie den PR bearbeiten können. Sollten Sie nicht innerhalb von 14 Tagen geantwortet haben, darf jeder Committer via maintainer-timeout auf einen PR, den Sie nicht beantwortet haben, reagieren. Sammeln Sie Informationen Wenn mit dem Bug-Report nicht auch gleichzeitig eine Lösung übermittelt wird, müssen Sie zuerst die zum Beheben des Problems nötigen Informationen sammeln. Wenn der Fehler reproduzierbar ist, können Sie die meisten Informationen selbst sammeln. Wenn nicht, bitten Sie die Person, die den Fehler gefunden hat, diese Informationen für Sie zu sammeln: Eine genaue Beschreibung dessen, was Er/Sie getan hat, den erwarteten Programmverlauf und den tatsächlichen Ablauf. Eine Kopie der Eingabedaten, die den Fehler auslösen. Informationen über das System, auf dem der Port gebaut und ausgeführt wird, etwa die Liste der installierten Pakete sowie die Ausgabe von &man.env.1;. Core dumps. Stack traces. Schließen Sie falsche Reports aus Einige Fehlerberichte sind eventuell falsch. Es kommt vor, dass ein Programm falsch benutzt wird. Weiterhin können installierten Pakete veraltet sein und müssten einfach nur aktualisiert werden. Manchmal ist ein gemeldeter Fehler auch nicht &os;-spezifisch. In diesem Fall melden Sie den Fehler den derzeitigen Entwicklern der Software. Wenn Sie in der Lage sind, den Fehler zu beheben, können Sie dies natürlich trotzdem tun und den Entwicklern Ihren Patch zukommen lassen. Lösungen finden Bei Build-Fehlern werden Sie eine Lösung finden müssen. Denken Sie daran zu fragen, wenn Sie nicht weiterkommen! Änderungen einreichen oder annehmen Genau so wie bei der Aktualisierung eines Ports sollten Sie alle Änderungen zuvor analysieren und testen, um Sie danach als neuen PR (oder als Folgebericht (follow-up), falls ein PR zu diesem Problem bereits existiert) einzureichen. Falls ein anderer Anwender Änderungen für einen PR eingereicht hat, können Sie einen Folgebericht erstellen, mit dem Sie die vorgeschlagenen Änderungen akzeptieren oder (mit einer Begründung) ablehnen. Support leisten Teilaufgabe eines Maintainers ist es, Support zu leisten — nicht den Hauptsupport für die Software — aber für seine Ports und &os;-spezifische Schlampereien und Probleme. Benutzer kontaktieren Sie vielleicht wegen Fragen, Anregungen, Problemen und Patches. Die meiste Zeit werden sich derartige Mitteilungen spezifisch auf &os; beziehen. Manchmal müssen Sie eventuell ihre diplomatischen Fähigkeiten auffrischen und Benutzer freundlich an die korrekten Anlaufstellen für den Hauptsupport verweisen. Nur selten werden Sie auf eine Person treffen, die Sie fragt, warum die RPMs nicht aktuell sind oder wie Sie die Software unter Foo Linux zum Laufen bringen. Ergreifen Sie die Gelegenheit und berichten Sie, dass Ihr Port aktuell ist (natürlich nur, wenn er es auch tatsächlich ist) und schlagen Sie vor, einmal &os; auszuprobieren. Wenn Sie Glück haben, werden Benutzer und Entwickler gelegentlich daran denken, dass Sie eine sehr beschäftigte Person sind, deren Zeit nicht unerschöpflich, sondern kostbar ist, und werden vielleicht ein Teil Ihrer Arbeit für Sie übernehmen. Beispielsweise könnten sie: Einen PR einreichen oder Ihnen Patches schicken. Einen vorhandenen PR untersuchen und eventuell einen Patch dazu erstellen. Ihnen Änderungen für Ihre Ports zusenden. In diesem Fall ist ihre Hauptaufgabe zeitnahes Antworten. Der Timeout für nicht ansprechbare Maintainer beträgt auch hier wieder 14 Tage. Nach dieser Periode können Änderungen ohne ihre Prüfung eingereicht werden. Diese Personen haben sich die Arbeit gemacht, etwas für Sie zu übernehmen, versuchen Sie daher, möglichst rasch zu antworten. Danach überprüfen, akzeptieren, verändern oder diskutieren Sie diese Änderungen mit den betroffenen Personen so schnell wie möglich. Wenn Sie vermitteln können, dass Sie deren Arbeit zu schätzen wissen (und das sollten Sie), dann werden Sie eine bessere Chance haben, dass diese Personen ihnen auch in Zukunft etwas Arbeit abnehmen. :-) Defekte Ports finden und reparieren Es gibt zwei wirklich gute Anlaufstellen, um Ports zu finden, die ihre Aufmerksamkeit benötigen. Sie können das Web Interface der Problem Reports-Datenbank nutzen, um nach ungelösten Problemen zu suchen. Die Mehrheit der PRs, die zu Ports eingereicht werden, betreffen Aktualisierungsprobleme, aber mit ein bißchen Recherche in den Übersichten und Zusammenfassungen sollten Sie das eine oder andere Interessante finden. (Die Kategorie sw-bug ist ein guter Platz, um mit der Arbeit zu beginnen). Die zweite Anlaufstelle ist das &os; Ports Monitoring System. Hier können Sie nicht betreute Ports mit Build-Fehlern und Ports, die als BROKEN gekennzeichnet sind, finden. Natürlich ist es auch in Ordnung, Änderungen an betreuten Ports zu machen. Denken Sie aber bitte daran, den Maintainer zuvor davon zu informieren, da dieser möglicherweise bereits an diesem Problem arbeitet. Sobald Sie einen Fehler oder ein Problem gefunden haben, sammeln Sie dazu Informationen und versuchen Sie, den Fehler zu analysieren und zu beheben! Wenn sich bereits ein PR mit diesem Problem befasst, knüpfen Sie dort an. Ansonsten reichen Sie einen neuen PR ein. Die von Ihnen vorgeschlagenen Änderungen werden danach geprüft. Sind diese in Ordnung, werden Sie danach committed. Sagen Sie Bescheid, wenn Sie einen Port nicht mehr betreuen möchten So wie Ihre Interessen sich ändern, haben Sie vielleicht irgendwann auch nicht mehr die Zeit, weiterhin einige (oder alle) Ihrer Ports zu betreuen. Das ist verständlich. Bitte lassen Sie es uns wissen, wenn Sie keine Zeit oder kein Interesse mehr daran haben, Maintainer zu sein oder einen Port selbst nicht mehr benutzen und deshalb gerne abgeben wollen. Nur auf diese Art und Weise können wir vorankommen und anderen anbieten, an diesen Ports zu arbeiten, ohne dass diese auf Ihre Antworten warten müssen. Denken Sie daran: &os; ist ein Freiwilligen-Projekt. Wenn Ihnen eine Aufgabe keinen Spaß mehr macht, ist es wahrscheinlich an der Zeit, jemand anderen an Ihre Ports zu lassen. In jedem Fall behält sich das Ports Management Team (portmgr) das Recht vor, Ihnen den Maintainer-Status abzuerkennen, wenn Sie für längere Zeit nicht aktiv sind (derzeit liegt diese Grenze bei drei Monaten). Damit ist gemeint, dass ungelöste Probleme oder ausstehende Aktualisierungen in diesem Zeitraum nicht bearbeitet wurden. Ressourcen für Ports-Maintainer und Committer Das Porter-Handbuch ist Ihr Ratgeber zum Ports-System und sollte stets in Ihrer Reichweite sein! Der Artikel Writing FreeBSD Problem Reports beschreibt, wie PRs formuliert und eingereicht werden sollen. Allein im Jahr 2005 wurden mehr als 11.000 PRs zu verschiedenen Ports eingereicht! Wenn Sie die Anweisungen dieses Artikels befolgen, werden wir weniger Zeit benötigen, um Ihre PRs zu bearbeiten. Die Problem Report Database. Pointyhat ist der Ports Build Cluster. Sie können Pointyhat nutzen, um nach Port-Buildlogs über alle Architekturen und Haupt-Releases zu suchen. Das FreeBSD Ports Monitoring System kann verschiedene Informationen über Ports enthalten, beispielsweise Build-Fehler und Problemberichte. Als Ports-Maintainer können Sie hier den Buildstatus Ihres Ports in Erfahrung bringen. Als Committer können Sie dort defekte und unbetreute Ports finden, die gefixt werden müssten. Der &os; Ports Distfile-Scanner kann Ihnen die Ports anzeigen, deren Distfiles nicht erreichbar sind. Sie können damit Ihre eigenen Ports prüfen oder auch herauszufinden, ob die MASTER_SITES-Einträge bestimmter Ports nicht mehr aktuell sind. Der tinderbox-Port ist die gründlichste Lösung, um den Port während des ganzen Prozesses der Installation, Paketerstellung und Deinstallation zu testen. Das Programm bietet sowohl eine Kommandozeilen- als auch eine Web-Schnittstelle. Weitere Informationen zu diesem Port finden Sie im Verzeichnis ports/ports-mgmt/tinderbox sowie auf der Tinderbox Homepage. Mit &man.portlint.1; können Sie einen Port auf die Einhaltung von stilistischen und funktionellen Richtlinien hin überprüfen. Da es sich bei portlint um eine heuristische Anwendung handelt, sollten Sie dessen Ausgaben nur als einen Ratgeber verwenden. Wenn portlint zu umfangreiche Änderungen vorschlägt, lesen Sie nochmal das Porter-Handbuch oder bitten Sie jemanden um Rat. Die Mailingliste &a.ports; ist für allgemeine Diskussionen über Ports vorgesehen. Wenn Sie Hilfe benötigen können Sie dort nachfragen. Sie können einzelne Mailinglisten auch abonnieren oder in deren Archiven suchen und lesen. Die Mailinglisten &a.ports-bugs; und &a.cvs-ports; könnten für Sie ebenfalls von Interesse sein. + +
diff --git a/de_DE.ISO8859-1/articles/contributing/article.xml b/de_DE.ISO8859-1/articles/contributing/article.xml index 6993c696dd..3e21b6b8eb 100644 --- a/de_DE.ISO8859-1/articles/contributing/article.xml +++ b/de_DE.ISO8859-1/articles/contributing/article.xml @@ -1,622 +1,624 @@
&os; unterstützen Dieser Artikel beschreibt, wie Einzelpersonen oder Unternehmen das &os;-Projekt unterstützen können. Übersetzt von Johann Kois. Jordan Hubbard Beigetragen von &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Unterstützung Sie wollen &os; unterstützen? Das ist großartig! &os; ist auf die Unterstützung seiner Anwender angewiesen, um zu überleben. Ihre Beiträge werden nicht nur begrüßt, sie sind für die Weiterentwicklung von &os; von elementarer Bedeutung. Im Gegensatz zu dem, was einige Leute Ihnen einreden wollen, müssen Sie kein Spitzenprogrammierer oder persönlicher Freund eines Mitglieds des FreeBSD-Core-Teams sein, damit Ihre Beiträge akzeptiert werden. Ein große und wachsende Anzahl von internationalen Unterstützern verschiedenen Alters und mit verschiedenen technischen Fähigkeiten entwickelt FreeBSD weiter. Es gibt immer mehr zu tun, als von den beteiligten Personen bewältigt werden kann, daher freuen wir uns über jede Hilfe. Das FreeBSD-Projekt ist für ein komplettes Betriebssytem verantwortlich, nicht nur für einen Kernel oder ein paar verstreute Werkzeuge. Daher umfasst unsere TODO-Liste viele verschiedene Aufgabenbereiche: Angefangen von der Dokumentation, über Betatests und Präsentationen bis zu Systeminstallationen und speziellen Weiterentwicklungen des Kernels. Da Fähigkeiten in den verschiedensten Bereichen benötigt werden, kann fast jeder etwas zu diesem Projekt beitragen. Personen, die im kommerziellen Umfeld mit FreeBSD zu tun haben, sind ebenfalls aufgefordert, sich bei uns zu melden. Brauchen Sie eine spezielle Erweiterung, damit Ihr Produkt funktioniert? Wir kommen Ihren Wünschen gerne entgegen, vorausgesetzt, sie sind nicht zu speziell. Arbeiten Sie an einem Mehrwertprodukt? Dann informieren Sie uns bitte! Wir könnten in der Lage sein, an einem Teil davon mitzuarbeiten. Die Welt der freien Software fordert viele bestehenden Annahmen über die Entwicklung, den Verkauf und die Wartung von Software heraus, und wir bitten Sie, ernsthaft darüber nachzudenken. Was wird gebraucht? Die folgende Liste von Aufgaben und Unterprojekten repräsentiert eine Zusammenfassung von verschiedenen TODO-Listen und Benutzerwünschen. Aufgaben für Nicht-Programmierer Viele Menschen, die an FreeBSD beteiligt sind, sind keine Programmierer. Es sind Leute, die an der Dokumentation arbeiten, Internetseiten erstellen oder einfach Hilfe anbieten. Alles, was diese Leute mitbringen müssen, sind Zeit und die Bereitschaft, etwas zu lernen. Lesen Sie die häufig gestellten Fragen (FAQ) und das Handbuch gelegentlich. Wenn etwas schlecht erklärt wird, veraltet oder einfach falsch ist, teilen Sie es uns mit. Oder noch besser, korrigieren Sie es (SGML ist nicht schwer zu erlernen, wir akzeptieren aber auch Vorschläge im ASCII-Format.). Helfen Sie dabei, die Dokumentation in Ihre Muttersprache zu übersetzen. Wenn an der Übersetzung in Ihre Sprache bereits gearbeitet wird, helfen Sie, indem Sie weitere Dokumente übersetzen, oder sorgen Sie dafür, dass die Übersetzungen aktuell sind. Lesen Sie zuerst die Übersetzungs-FAQ der Fibel für neue Mitarbeiter des FreeBSD-Dokumentations-Projekts. Sie verpflichten sich dabei nicht dazu, jede einzelne Seite zu übersetzen — als Freiwilliger übersetzen Sie genau so viel, wie Sie wollen. Wenn jemand mit der Übersetzung beginnt, beteiligen sich fast immer auch andere Personen daran. Wenn Sie nur Zeit und Energie für einen Teil der Dokumentation haben, dann übersetzen Sie bitte die Installationsanleitung. Lesen Sie &a.questions; sowie die &ng.misc; gelegentlich (oder sogar regelmäßig). Es kann sehr befriedigend sein, wenn Sie Ihr Wissen teilen und anderen Leuten dabei helfen können, deren Probleme zu lösen; vielleicht lernen Sie sogar noch etwas Neues! Diese Foren können auch eine Quelle für Ideen sein, an denen man arbeiten könnte. Aufgaben für Programmierer Die meisten der hier aufgeführten Aufgaben erfordern entweder einen bedeutenden Zeitaufwand oder eine sehr gute Kenntnis des FreeBSD-Kernels, oder beides. Es gibt jedoch genug Aufgaben, die auch für Wochenendprogrammierer geeignet sind. Wenn Sie FreeBSD-CURRENT installiert haben und über eine schnelle Internetanbindung verfügen, können Sie von current.FreeBSD.org ein täglich neu erzeugtes Release herunterladen — versuchen Sie dann hin und wieder, das neueste Release zu installieren und melden Sie dabei eventuell auftretende Fehler. Lesen Sie &a.bugs;. Es könnte ein Problem geben, an dem Sie konstruktiv mitarbeiten könnten, oder für das es Patches gibt, die Sie testen könnten. Oder Sie könnten sogar versuchen, eines dieser Probleme selbst zu beheben. Wenn Sie von Fehlerbehebungen wissen, die zwar erfolgreich auf -CURRENT angewendet wurden, die aber nach einem bestimmten Zeitraum nicht in -STABLE eingebracht wurden (normalerweise innerhalb einiger Wochen), erinnern Sie den Committer höflich daran. Verschieben Sie beigetragene Software im Quellcodebaum nach src/contrib. Stellen Sie sicher, dass der Code in src/contrib aktuell ist. Bauen Sie den Quellcodebaum (oder einen Teil des Baumes) mit aktivierten Compilerwarnungen und beheben Sie auftretende Fehlermeldungen. Beheben Sie Fehlermeldungen bei der Installation von Ports, die auf unsauberen Code hinweisen (etwa die Verwendung von gets() oder die Einbindung von malloc.h). Wenn Sie einen Port beigetragen und dabei irgendwelche &os;-spezifischen Änderungen getätigt haben, senden Sie Ihre Patches an die ursprünglichen Autoren (das wird ihr Leben einfacher machen, wenn die nächste Version des Ports erscheint). Besorgen Sie sich Kopien von wichtigen Standards wie &posix;. Als Ausgangspunkt für Ihre Suche können Sie die Seite des FreeBSD C99 & POSIX Standards Conformance Project verwenden. Vergleichen Sie das Verhalten von FreeBSD mit dem von dem jeweiligen Standard geforderten Verhalten. Verhält sich FreeBSD in einem Bereich unterschiedlich, sollten Sie einen Problembericht (PR) einsenden. Wenn Sie dazu in der Lage sind, können Sie sich auch eine Lösung des Problems überlegen und Ihrem PR einen Patch anfügen. Wenn Sie der Meinung sind, dass der Standard nicht korrekt ist, können Sie auch das jeweilige Standardgremium um weitere Informationen bitten. Schlagen Sie weitere Aufgaben für diese Liste vor! Die PR-Datenbank durchsehen problem reports database Die FreeBSD PR-Datenbank enthält alle derzeit offenen Problemberichte und Verbesserungswüsche, die von Anwendern eingereicht wurden. Die PR-Datenbank enthält sowohl Aufgaben für Programmierer als auch für Nichtprogrammierer. Gehen Sie die Liste der offenen PRs durch, um festzustellen, ob Sie ein Problem interessiert. Bei manchen Berichten geht es nur darum, zu überprüfen, ob der bereitgestellte Patch korrekt funktioniert. Andere Problemberichte sind hingegen komplexer, oder beinhalten überhaupt keinen Lösungsvorschlag. Beginnen Sie mit den PRs, die niemandem zugewiesen sind. Ist ein PR, für den Sie eine Lösung hätten, bereits jemandem zugewiesen, nehmen Sie mit dem dafür Zuständigen Kontakt auf und fragen Sie ihn, ob Sie an der Lösung mitarbeiten können — es könnte etwa bereits ein Patch existieren, der nur noch getestet werden muss, oder Sie könnten weitere Ideen mit ihm diskutieren. Wählen Sie einen der Einträge auf der <quote>Ideen</quote>-Seite aus Die Liste von Projekten und Ideen für &os; ist auch für Freiwillige interessant, die etwas zum &os; Projekt beitragen möchten. Diese Liste wird regelmäßig aktualisiert und enthält Einträge für Programmierer und Nicht-Programmierer sowie Informationen zu jedem Projekt. Was Sie tun können Mögliche Beiträge lassen sich in fünf Kategorien einteilen: Fehlerberichte und allgemeine Vorschläge Eine Idee oder ein Vorschlag von allgemeinem technischen Interesse sollte an &a.hackers; geschickt werden. Personen, die an solchen Fragen interessiert sind (und kein Problem mit einem hohen Mailaufkommen haben!) können die Mailingliste &a.hackers; auch abonnieren. Informationen zu dieser und anderen Mailinglisten finden Sie im FreeBSD Handbuch. Wenn Sie einen Fehler gefunden oder eine Verbesserung entwickelt haben, vergessen Sie nicht, einen Bericht über &man.send-pr.1; oder dessen Internetschnittstelle zu erstellen. Versuchen Sie bitte, jedes Feld auszufüllen. Ist Ihr Patch kleiner als 65 KB, sollten Sie ihn direkt in den Bericht einbauen. Kann der Patch direkt auf den Quellcodebaum angewendet werden, fügen Sie [PATCH] im Synopsis-Feld ein. Wenn Sie einen Patch einfügen, verwenden Sie bitte kein copy-and-paste, weil dadurch Tabulatoren in Leerzeichen umgewandelt werden, was den Patch unbrauchbar macht. Sind die Patches viel größer als 20 KB, sollten Sie sie komprimieren (z.B. mit &man.gzip.1; oder &man.bzip2.1;) und &man.uuencode.1; verwenden, um diese in ihren Problembericht einzufügen. Nachdem Sie einen Bericht versandt haben, erhalten Sie eine E-Mail, die eine Bestätigung sowie eine Identifikationsnummer enthält. Geben Sie diese Nummer im Betreff der Nachricht an ("Re: kern/3377"), wenn Sie neue Informationen zu diesem Problem an &a.bugfollowup; senden. Zusätzliche Informationen zu Problemberichten sollten immer auf diese Art und Weise verschickt werden. Sollten Sie innerhalb einer Woche keine Bestätigung erhalten, oder &man.send-pr.1; nicht verwenden können, können Sie über &a.bugs; jemanden bitten, dies für Sie zu erledigen. Weitere Informationen zum Verfassen von guten Problemberichten finden Sie im entsprechenden Artikel. Änderungen der Dokumentation documentation submissions Änderungen der Dokumentation werden vom &a.doc; überwacht. Lesen Sie bitte die Fibel für neue Mitarbeiter des FreeBSD-Dokumentationsprojekts für weitere Informationen. Korrekturen und Ergänzungen (selbst kleine Änderungen sind willkommen!) werden mit &man.send-pr.1; übermittelt. Lesen Sie dazu den Abschnitt Fehlerberichte und allgemeine Vorschläge. Änderungen am vorhandenen Quellcode FreeBSD-CURRENT Änderungen des existierenden Quellcodes sind etwas komplizierter. Entscheidend ist hier, wie vertraut Sie mit dem aktuellen Entwicklungsstand von FreeBSD sind. Es existiert eine spezielle, ständig aktualisierte Version von FreeBSD, die als FreeBSD-CURRENT bekannt ist. Diese ist auf verschiedenen Wegen erhältlich und stellt den aktuellen Stand der Entwicklung dar. Lesen Sie den Abschnitt FreeBSD-CURRENT vs. FreeBSD-STABLE des Handbuchs für weitere Informationen zur Installation und Verwendung von FreeBSD-CURRENT. Arbeiten Sie mit älteren Quellcodeversionen, kann dies leider bedeuten, das Ihre Änderungen obsolet sind, oder sich nicht mehr in FreeBSD reintegrieren lassen. Dieses Risiko lässt sich verringern, wenn Sie die Mailinglisten &a.announce; und &a.current; abonnieren, auf denen aktuelle Systemänderungen diskutiert werden. Wenn Ihre Änderungen auf ausreichend aktuellen Quellen beruhen, erstellen Sie als Nächstes einen Differenzensatz, den Sie an die FreeBSD-Entwickler schicken. Eine solche Differenz erstellen Sie mit &man.diff.1;. Das bevorzugte &man.diff.1;-Format für das Versenden von Patches ist das sogenannte unified output-Format, das Sie mit diff -u erstellen. Für größere Änderungen kann allerdings das context output-Format (erzeugt mit diff -c) die bessere Wahl sein. diff Dazu ein Beispiel: &prompt.user; diff -c oldfile newfile oder &prompt.user; diff -c -r olddir newdir würde einen solchen Satz von Differenzen für die angegebene Verzeichnishierarchie erzeugen. Genauso hätte &prompt.user; diff -u oldfile newfile oder &prompt.user; diff -u -r olddir newdir den gleichen Effekt, allerdings erfolgt die Ausgabe im unified diff-Format. Lesen Sie dazu auch &man.diff.1;. Nachdem Sie den Differenzensatz erstellt und mit &man.patch.1; getestet haben, sollten Sie ihn an das FreeBSD-Projekt senden. Verwenden Sie dazu &man.send-pr.1; (wie im Abschnitt Fehlerberichte und allgemeine Vorschläge beschrieben). Senden Sie die Differenzen nicht nur an &a.hackers;, da diese sonst verloren gehen. Wir freuen uns über Ihren Beitrag (schließlich ist FreeBSD ein Freiwilligenprojekt); wir sind aber manchmal nicht in der Lage, das Problem sofort anzugehen. Es verbleibt aber in der PR-Datenbank, bis wir dafür Zeit finden. Verwenden Sie den Begriff [PATCH] im Synopsis-Feld des Berichts. uuencode Sie können auch ein tar-Archiv erzeugen (was vor allem dann sinnvoll ist, wenn Sie Dateien hinzugefügt, gelöscht oder umbenannt haben) und &man.uuencode.1; auf das Archiv anwenden. Mit &man.shar.1; erzeugte Archive sind ebenfalls willkommen. Wenn Ihre Änderungen potentielle Probleme aufweisen, wie Unklarheiten im Hinblick auf das Copyright, oder Sie einfach eine genaue Überprüfung Ihrer Änderungen möchten, sollten Sie die Änderungen an das &a.core; schicken, statt sie mit &man.send-pr.1; zu versenden. Die Mailingliste &a.core; erreicht nur eine kleine Gruppe von Leuten, die sich um die tägliche Arbeit an &os; kümmern. Beachten Sie aber, dass diese Gruppe sehr beschäftigt ist. Daher sollten Sie nur dann eine E-Mail an sie schicken, wenn es absolut notwendig ist. &man.intro.9; und &man.style.9; beschreiben den zu verwendenden Programmierstil. Bevor Sie also Code versenden, sollten Sie diese Informationen gelesen haben. Neuer Code oder große Mehrwertpakete Handelt es sich um einen bedeutenden Beitrag oder um das Hinzufügen von neuen wichtigen Fähigkeiten zu FreeBSD, ist es fast immer notwendig, die Änderungen als uuencoded tar-Dateien zu versenden, oder diese auf einer Internetseite oder einem FTP-Server bereitzustellen. Haben Sie keinen eigenen Speicherplatz im Internet, sollten Sie auf einer entsprechenden Mailinglisten nachfragen, ob jemand diese Aufgabe für Sie übernehmen kann. Arbeitet man mit großen Codebeständen, kommt man unweigerlich mit den unterschiedlichen Lizenzen in Berührung. Code, der in FreeBSD enthalten ist, kann unter den folgenden Lizenzen stehen: BSD-Lizenz Der BSD-Lizenz. Diese Lizenz wird von uns bevorzugt, weil sie an keine Bedingungen geknüpft ist und daher für kommerzielle Unternehmen sehr attraktiv ist. Das FreeBSD-Projekt unterstützt diese kommerzielle Verwendung, die manchmal sogar in eine Förderung des FreeBSD-Projekts mündet. GPLGNU General Public License GNU General Public License Der GNU General Public License, oder GPL. Diese Lizenz ist nicht ganz so beliebt bei uns, da sie die kommerzielle Nutzung des Quellcodes einschränkt. In Anbetracht der schieren Menge an GPL-Quellcode, den wir derzeit benötigen (wie Compiler, Assembler oder Textformatierer) wären wir aber schlecht beraten, Beiträge, die unter dieser Lizenz stehen, abzulehnen. Code, der unter der GPL steht, befindet sich in einem gesonderten Bereich des Quellcodebaums, und zwar unter /sys/gnu oder /usr/src/gnu, und ist daher für jeden, für den die GPL ein Problem darstellt, sofort erkennbar. Beiträge, die unter einer dieser Lizenzen stehen, müssen sorgfältig geprüft werden, bevor ihre Aufnahme in FreeBSD in Betracht gezogen wird. Beiträge, für die besonders restriktive Lizenzen gelten, werden generell abgelehnt, obwohl die Autoren ermutigt werden, ihre Veränderungen über ihre eigenen Kanäle verfügbar zu machen. Um Ihre Arbeit unter die BSD-Lizenz zu stellen, fügen Sie den folgenden Text am Beginn jeder von Ihnen erstellten Quellcodedatei ein, wobei Sie den Text zwischen den %%-Zeichen durch die entsprechenden Informationen ersetzt: Copyright (c) %%Jahr der Veröffentlichung%% %%Ihr Name%%, %%Ihr Land%% %%Ihre Postleitzahl%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%Ihr Name%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%Ihr Name%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ Eine Kopie dieses Textes finden Sie unter /usr/share/examples/etc/bsd-style-copyright. Geld, Hardware oder Internetzugang Wir freuen uns immer, wenn jemand das FreeBSD-Projekt durch Spenden unterstützen will. Auch kleine Spenden können eine große Wirkung haben. Hardwarespenden sind ebenfalls sehr wichtig, um die Liste der von FreeBSD unterstützten Hardware erweitern zu können, da uns die Mittel zum Erwerb dieser Hardware fehlen. <anchor id="donations"/>Geldspenden Die FreeBSD Foundation ist eine gemeinnützige Gesellschaft, die zur Unterstützung des FreeBSD-Projekts geschaffen wurde. Sie ist nach dem Paragraphen 501(c)3 sowohl von der amerikanischen Einkommenssteuer als auch von der des Staates Colorado befreit. Spenden an solche steuerbefreiten Gesellschaften können unter gewissen Umständen steuermindernd geltend gemacht werden. Sie können Spenden in Scheckform an folgende Adresse senden:
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
Die FreeBSD Foundation ist nun auch in der Lage, Spenden durch das PayPal-System entgegenzunehmen. Solche Spenden können über die Homepage der Foundation erfolgen. Für weitere Informationen zur FreeBSD Foundation sollten Sie den Artikel The FreeBSD Foundation -- an Introduction lesen. Sie erreichen die FreeBSD Foundation über die E-Mail-Adresse bod@FreeBSDFoundation.org. Hardwarespenden donations Das FreeBSD-Projekt freut sich, wenn jemand benötigte Hardware spenden will. Sind Sie daran interessiert, setzen Sie sich bitte mit dem Donations Liaison Office in Verbindung. Internetzugang zur Verfügung stellen Wir sind ständig auf der Suche nach neuen FTP-, WWW- oder cvsup-Spiegeln. Wenn Sie einen solchen Spiegel einrichten wollen, lesen Sie bitte den Artikel Mirroring FreeBSD, der weitere Informationen enthält. + +
diff --git a/de_DE.ISO8859-1/articles/nanobsd/article.xml b/de_DE.ISO8859-1/articles/nanobsd/article.xml index 875d6c7214..02c0d32a81 100644 --- a/de_DE.ISO8859-1/articles/nanobsd/article.xml +++ b/de_DE.ISO8859-1/articles/nanobsd/article.xml @@ -1,548 +1,550 @@
Einführung in NanoBSD Daniel Gerzo $FreeBSD$ 2006 The FreeBSD Documentation Project &tm-attrib.freebsd; &tm-attrib.general; Dieses Dokument stellt Informationen zu den NanoBSD Werkzeugen bereit, die dazu verwendet werden können ein &os; Abbild für eingebettete Systeme zu erstellen, welche auf eine Compact Flash Karte passen (oder andere Massenspeicher). Übersetzt von Björn Heidotting. Einführung in NanoBSD NanoBSD NanoBSD ist ein Werkzeug welches derzeit von &a.phk; entwickelt wird. Es erstellt ein &os; Systemabbild für eingebettete Systeme, die auf eine Compact Flash Karte passen (oder andere Massenspeicher). Es kann dazu benutzt werden um spezialisierte Installationsabbilder zu bauen, entworfen für die einfache Installation und Wartung von Systemen die als "Computer Appliances" bekannt sind. Computer Appliances haben ihre Hard- und Software fest verbaut, dass bedeutet alle Anwendungen sind vorinstalliert. Die Appliance wird an ein bestehendes Netzwerk angeschlossen und kann mit der Arbeit (fast) sofort beginnen. Zu den Eigenschaften von NanoBSD gehören: Ports und Pakete funktionieren wie in &os; — Jede einzelne Anwendung kann auf dem NanoBSD Abbild installiert und benutzt werden, auf die gleiche Weise wie Sie es aus &os; gewohnt sind. Keine fehlende Funktionalität — Wenn es möglich ist, etwas mit &os; zu tun, ist es auch möglich, die gleiche Sache mit NanoBSD zu tun, es sei denn, eine oder mehrere Funktionen wurden ausdrücklich vor dem Bau des NanoBSD Abbilds entfernt. Zur Laufzeit ist alles read-only — Es ist sicher den Stromstecker zu ziehen. Es besteht dann keine Notwendigkeit, einen &man.fsck.8; nach einem nicht ordnungsgemäßem Herunterfahren des Systems auszuführen. Einfach zu bauen und anzupassen — Unter Verwendung von nur einem Shell-Skript und einer Konfigurationsdatei ist es möglich, ein reduziertes und angepasstes Abbild zu bauen, welches jegliche Reihe von Anforderungen erfüllt. NanoBSD Anleitung Das Design von NanoBSD Sobald das Abbild auf dem Medium verfügbar ist, kann NanoBSD gebootet werden. Der Massenspeicher ist standardmäßig in drei Teile unterteilt: Zwei Abbild Partitionen: code#1 und code#2. Die Partition der Konfigurationsdatei, welche zur Laufzeit unter dem /cfg Verzeichnis gemountet werden kann. Diese Partitionen sind im Allgemeinen read-only. Die /etc und /var Verzeichnisse sind &man.md.4; (malloc) Speicher. Die Partition der Konfigurationsdatei besteht unter dem /cfg Verzeichnis. Sie enthält Dateien für das /etc Verzeichnis und wird direkt nach dem Botten read-only eingehangen, weshalb es erforderlich ist geänderte Dateien von /etc zurück nach /cfg zu kopieren falls die Änderungen nach einem Neustart bestehen bleiben sollen. Dauerhafte Änderungen in <filename>/etc/resolv.conf</filename> vornehmen &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg Die /cfg Partition sollte nur während des Bootvorgangs und zu Änderungen an den Konfigurationsdateien gemountet werden. Die /cfg Partition jederzeit gemountet zu haben ist keine gute Idee, besonders wenn das NanoBSD System auf einem Massenspeicher betrieben wird, der eventuell druch eine große Anzahl von Schreiboperationen nachteilig beeinträchtigt wird (z. B. wenn der Dateisystem-Syncer den Speicher mit Daten überflutet). Ein NanoBSD Abbild erstellen Ein NanoBSD Abbild wird über ein einfaches nanobsd.sh Shell-Skript gebaut, das sich unter /usr/src/tools/tools/nanobsd befindet. Das Skript erstellt ein Abbild, welches dann mittels &man.dd.1; auf einen Massenspeicher kopiert werden kann. Die folgenden Kommandos sind notwendig um ein NanoBSD Abbild zu erstellen: &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k Wechsel in das Basisverzeichnis des NanoBSD Skripts. Den Bauprozess starten. Wechsel in das Verzeichnis, in dem das gebaute Abbild liegt. NanoBSD auf einem Massenspeicher installieren. Ein NanoBSD Abbild anpassen Dies ist wahrscheinlich das wichtigste und interessanteste Merkmal von NanoBSD. Hierbei werden Sie auch die meiste Zeit mit der Entwicklung von NanoBSD verbringen. Der Aufruf des folgenden Kommandos wird nanobsd.sh dazu zwingen, seine Konfiguration aus myconf.nano aus dem aktuellen Verzeichnis zu lesen: &prompt.root; sh nanobsd.sh -c myconf.nano Die Anpassung wird auf zwei Arten geschehen: Konfigurations-Optionen Benutzerdefinierte Funktionen Konfigurations-Optionen Durch Konfigurationseinstellungen ist es möglich Optionen zu übergeben, die sowohl die buildworld und installworld Phasen des NanoBSD Bauprozesses betreffen, sowie interne Optionen, die den Haupt-Bauprozess von NanoBSD beeinflussen. Durch diese Optionen ist es möglich, das System so zu reduzieren, dass es mit wenig Platz, etwa 64 MB auskommt. Sie können die Konfigurationsdateien dazu nutzten &os; noch weiter zu trimmen, bis es nur noch aus dem Kernel und zwei oder drei Dateien im Userland besteht. Die Konfigurationsdatei besteht aus Konfigurations-Optionen, welche die Standardwerte überschreiben. NANO_NAME — Name des Build (wird verwendet, um die workdir Namen zu konstruieren). NANO_SRC — Pfad zum Quelltextverzeichnis, das für den Bau des Abbilds verwendet wird. NANO_KERNEL — Name der Kernelkonfigurationsdatei, die für den Bau des Kernels verwendet wird. CONF_BUILD — Optionen für die buildworld Phase des Bauprozesses. CONF_INSTALL — Optionen für die installworld Phase des Bauprozesses. CONF_WORLD — Optionen für die buildworld und installworld Phasen des Bauprozesses. FlashDevice — Definiert den zu benutzenden Medientyp. Überprüfen Sie die Datei FlashDevice.sub für weitere Informationen. Benutzerdefinierte Funktionen Mit Hilfe von Shell-Funktionen in der Konfigurationsdatei besteht die Möglichkeit zur Feinabstimmung von NanoBSD. Das folgende Beispiel illustriert das Grundmodell von benutzerdefinierten Funktionen: cust_foo () ( echo "bar=baz" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo Ein besseres Beispiel für eine Anpassung ist folgende, welche die Standardgröße des /etc Verzeichnisses von 5 MB auf 30 MB ändert: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size Es gibt ein paar vordefinierte Standardfunktionen die Sie nutzen können: cust_comconsole — Deaktiviert &man.getty.8; auf den VGA Geräten (den /dev/ttyv* Gerätedateien) und ermöglicht die Nutzung der seriellen Schnittstelle COM1 als Systemkonsole. cust_allow_ssh_root — Erlaubt es root sich über &man.sshd.8; anzumelden. cust_install_files — Installiert Dateien aus dem nanobsd/Files Verzeichnis, das einige nützliche Skripte für die Systemverwaltung enthält. Pakete hinzufügen Durch benutzerdefinierte Funktionen können Pakete zum NanoBSD Abbild hinzugefügt werden. Die nachfolgende Funktion installiert alle Pakete aus /usr/src/tools/tools/nanobsd/packages: install_packages () ( mkdir -p ${NANO_WORLDDIR}/packages cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;' rm -rf ${NANO_WORLDDIR}/packages ) customize_cmd install_packages Beispiel einer Konfigurationsdatei Ein komplettes Beispiel für eine Konfigurationsdatei zum Erstellen eines benutzerdefinierten NanoBSD Abbilds könnte folgende sein: NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie NanoBSD aktualisieren The Update-Prozess von NanoBSD ist relativ einfach: Erstellen Sie ein neues NanoBSD Abbild. Laden Sie das neue Abbild in eine unbenutzte Partition eines laufenden NanoBSD Systems. Der wichtigste Unterschied dieses Schrittes zur ersten NanoBSD Installation besteht darin, das jetzt anstatt der Datei _.disk.full (enthält ein Abbild der gesamten Platte) die Datei _.disk.image (enthält ein Abbild einer einzelnen System-Partition) installiert wird. Neustart, um das System von der neu installierten Partition zu starten. Wenn alles gut geht, ist die Aktualisierung abgeschlossen. Wenn etwas schief läuft, starten Sie wieder in die vorherige Partition (die das alte, funktionierende Abbild enthält) um die System-Funktionalität so schnell wie möglich wieder herzustellen. Beheben Sie alle Probleme des neu gebauten Abbilds, und wiederholen Sie den Vorgang. Um das neue Abbild auf das laufende NanoBSD System zu installieren, ist es möglich, entweder das updatep1 oder updatep2 Skript im /root Verzeichnis zu verwenden, je nachdem, von welcher Partition das aktuelle System läuft. In Abhängigkeit davon welche Dienste der Host, der das NanoBSD Abbild anbietet, und welche Art von Transfer bevorzugt wird, bestehen eine von drei zu prüfenden Möglichkeiten: Verwendung von &man.ftp.1; Wenn die Übertragungsgeschwindigkeit an erster Stelle steht, verwenden Sie dieses Beispiel: &prompt.root; ftp myhost get _.disk.image "| sh updatep1" Verwendung von &man.ssh.1; Wenn eine sichere Übertragung bevorzugt wird, sollten Sie die Verwendung dieses Beispiels in Betracht ziehen: &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 Verwendung von &man.nc.1; Verwenden Sie dieses Beispiel, wenn auf dem Remote-Host kein &man.ftpd.8; oder &man.sshd.8; Dienst läuft: Zunächst öffnen Sie eine TCP-Listener auf dem Host der das Abbild bereitstellt und zum Client sendet: myhost&prompt.root; nc -l 2222 < _.disk.image Stellen Sie sicher das der benutzte Port nicht blockiert wird, um eingehende Verbindungen, vom NanoBSD Host durch die Firewall, zu ermöglichen. Verbinden Sie sich zum Host der das Abbild bereitstellt und führen Sie das updatep1 Skript aus: &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/de_DE.ISO8859-1/books/Makefile.inc b/de_DE.ISO8859-1/books/Makefile.inc index f6f6151093..1238ecb6b5 100644 --- a/de_DE.ISO8859-1/books/Makefile.inc +++ b/de_DE.ISO8859-1/books/Makefile.inc @@ -1,11 +1,10 @@ # # The FreeBSD Documentation Project # The FreeBSD German Documentation Project # # $FreeBSD$ # $FreeBSDde: de-docproj/books/Makefile.inc,v 1.8 2002/04/12 05:57:24 mheinen Exp $ # basiert auf: 1.4 # DESTDIR?= ${DOCDIR}/de_DE.ISO8859-1/books/${.CURDIR:T} -COLLATEINDEX+=-s Symbole diff --git a/de_DE.ISO8859-1/books/developers-handbook/Makefile b/de_DE.ISO8859-1/books/developers-handbook/Makefile index 375e408711..dd85528e0f 100644 --- a/de_DE.ISO8859-1/books/developers-handbook/Makefile +++ b/de_DE.ISO8859-1/books/developers-handbook/Makefile @@ -1,49 +1,47 @@ # The FreeBSD Documentation Project # The FreeBSD German Documentation Project # # $FreeBSD$ # $FreeBSDde: de-docproj/books/developers-handbook/Makefile,v 1.3 2009/02/21 19:12:23 jkois Exp $ # basiert auf: 1.24 # # Build the FreeBSD Developers' Handbook. # MAINTAINER=doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # Images IMAGES_EN= sockets/layers.eps sockets/sain.eps sockets/sainfill.eps sockets/sainlsb.eps sockets/sainmsb.eps sockets/sainserv.eps sockets/serv.eps sockets/serv2.eps sockets/slayers.eps # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= introduction/chapter.xml SRCS+= ipv6/chapter.xml SRCS+= kernelbuild/chapter.xml SRCS+= kerneldebug/chapter.xml SRCS+= l10n/chapter.xml SRCS+= policies/chapter.xml SRCS+= secure/chapter.xml SRCS+= sockets/chapter.xml SRCS+= testing/chapter.xml SRCS+= tools/chapter.xml SRCS+= x86/chapter.xml # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/de_DE.ISO8859-1/books/developers-handbook/chapters.ent b/de_DE.ISO8859-1/books/developers-handbook/chapters.ent index 7b1ed4db4c..d38cfa1154 100644 --- a/de_DE.ISO8859-1/books/developers-handbook/chapters.ent +++ b/de_DE.ISO8859-1/books/developers-handbook/chapters.ent @@ -1,43 +1,38 @@ - - - -]]> - +"> diff --git a/de_DE.ISO8859-1/books/fdp-primer/book.xml b/de_DE.ISO8859-1/books/fdp-primer/book.xml index 4dd715903b..31eb5fee81 100644 --- a/de_DE.ISO8859-1/books/fdp-primer/book.xml +++ b/de_DE.ISO8859-1/books/fdp-primer/book.xml @@ -1,273 +1,271 @@ %chapters; ]> Die Fibel für neue Mitarbeiter des FreeBSD-Dokumentationsprojekts 1998-2012 The FreeBSD Documentation Project 1998-2012 The FreeBSD German Documentation Project $FreeBSD$ $FreeBSD$ &legalnotice; Vielen Dank für Ihr Interesse und Ihre Mitarbeit an der FreeBSD-Dokumentation. Jeder Beitrag ist für uns sehr wichtig. In dieser Fibel wird von der eingesetzten Software bis hin zu den Vorstellungen des FreeBSD-Dokumentationsprojekts alles behandelt, was Sie wissen müssen, wenn Sie sich am FreeBSD-Dokumentationsprojekt beteiligen wollen. Bitte beachten Sie, dass diese Fibel jederzeit unter Bearbeitung und noch nicht vollständig ist. Benutzungshinweise Die Eingabeaufforderungen Die folgende Tabelle zeigt die normale Eingabeaufforderung des Systems und die Eingabeaufforderung des Superusers. Die in diesem Buch vorkommenden Beispiele benutzen die jeweilige Eingabeaufforderung, um zu zeigen, unter welchem Benutzer die Beispiele ausgeführt werden sollten. Benutzer Eingabeaufforderung Normaler Benutzer &prompt.user; Superuser &prompt.root; Typographische Festlegungen Um die Lesbarkeit zu erhöhen, werden in diesem Dokument die im folgenden genannten typographischen Festlegungen verwendet: Bedeutung Beispiel Kommandonamen Geben Sie ls -a ein, um alle Dateien anzuzeigen. Datei- und Verzeichnisnamen Bearbeiten Sie .login. Bildschirmein- und ausgaben You have mail. Referenzen auf Hilfeseiten Mit &man.su.1; können Sie sich als ein anderer Benutzer anmelden. Benutzer- und Gruppennamen Ich bin root, ich darf das. Hervorhebungen Hier müssen Sie vorsichtig sein. Argumente auf der Kommandozeile, die durch existierende Namen, Dateien oder Variablen ersetzt werden müssen Dateien können Sie mit dem Befehl rm Dateiname löschen. Umgebungsvariablen $HOME ist Ihr Benutzerverzeichnis. Anmerkungen, Tipps, wichtige Hinweise, Warnungen und Beispiel An einigen Stellen innerhalb dieses Buchs werden wichtige oder nützliche Hinweise gegeben, die besonders hervorgehoben sind. Hier ein kurzer Überblick über die verwendeten Darstellungen. Anmerkungen werden so dargestellt. Sie enthalten Informationen die Sie nur zu lesen brauchen, wenn Sie direkt davon betroffen sind. Tipps sind Informationen, die vielleicht hilfreich sein könnten oder aufzeigen, wie bestimmte Dinge einfacher zu bewerkstelligen sind. Besonders wichtige Punkte werden so hervorgehoben. Meist enthalten sie Hinweise auf vielleicht zusätzlich auszuführende Schritte oder Dinge, die besonders zu beachten sind. Warnungen werden wie dieser Abschnitt dargestellt und weisen auf mögliche Schäden hin, die entstehen können, falls die beschriebenen Schritte nicht genau befolgt oder Hinweise nicht beachtet werden. Die Palette der möglichen Schäden reicht von Hardwareschäden bis hin zu Datendatenverlust durch ein versehentliches Löschen von wichtigen Dateien oder ganzen Verzeichnissen. Ein Beispiel Beispiele, die so wie hier dargestellt werden, enthalten meist kleine Übungen, die nachvollzogen werden sollten, um das vorher beschriebene besser zu verinnerlichen oder mit den erzeugten Ausgaben vertraut zu werden. Danksagungen Ich möchte mich bei Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn und Christopher Maden bedanken, die sich die Zeit genommen haben, die frühen Entwürfe dieses Dokuments zu lesen und viele hilfreiche Hinweise und Ratschläge gegeben haben. &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/de_DE.ISO8859-1/books/handbook/Makefile b/de_DE.ISO8859-1/books/handbook/Makefile index d3775164db..1f46588470 100644 --- a/de_DE.ISO8859-1/books/handbook/Makefile +++ b/de_DE.ISO8859-1/books/handbook/Makefile @@ -1,328 +1,326 @@ # # $FreeBSD$ # $FreeBSDde: de-docproj/books/handbook/Makefile,v 1.67 2011/12/31 12:27:25 bcr Exp $ # basiert auf: 1.119 # # Build the FreeBSD Handbook in its German translation. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER=de-bsd-translators@de.FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= dtrace/chapter.xml SRCS+= eresources/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent # alle Kapitel bauen CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/de_DE.ISO8859-1/books/handbook/chapters.ent b/de_DE.ISO8859-1/books/handbook/chapters.ent index a933a8d86e..ba4f855d3f 100644 --- a/de_DE.ISO8859-1/books/handbook/chapters.ent +++ b/de_DE.ISO8859-1/books/handbook/chapters.ent @@ -1,77 +1,77 @@ %pgpkeys; - + "> diff --git a/el_GR.ISO8859-7/articles/contributing/article.xml b/el_GR.ISO8859-7/articles/contributing/article.xml index 8417de73ad..8709fb6070 100644 --- a/el_GR.ISO8859-7/articles/contributing/article.xml +++ b/el_GR.ISO8859-7/articles/contributing/article.xml @@ -1,619 +1,621 @@
ÓõíåéóöÝñïíôáò óôï &os; Áõôü ôï Üñèñï ðåñéãñÜöåé äéÜöïñïõò ôñüðïõò ìå ôïõò ïðïßïõò ìðïñåß Ýíá Üôïìï Þ ìéá ïñãÜíùóç íá óõíåéóöÝñåé óôï &os;. Jordan Hubbard ÃñÜöôçêå áðü ôïí ÊõñéÜêïò ÊåíôñùôÞò ÌåôáöñÜóôçêå áðü ôïí &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ contributing ÈÝëåôå íá óõìâÜëëåôå óôï &os; ëïéðüí; Áõôü åßíáé õðÝñï÷ï! Ôï &os; âáóßæåôáé óôç óõíåéóöïñÜ ôùí ÷ñçóôþí ãéá íá åðéâéþóåé ùò Ýñãï. Ïé óõíåéóöïñÝò óáò äåí åßíáé áðëþò êáëïäå÷ïýìåíåò, áëëÜ åßíáé ïõóéáóôéêÝò ðñïêåéìÝíïõ ôï &os; íá óõíå÷ßóåé íá áíáðôýóóåôáé. Äåí åßíáé áíÜãêç íá åßóôå ðñïãñáììáôéóôÞò Þ ößëïò ìå ôçí êåíôñéêÞ ïìÜäá ôïõ &os; ãéá íá ãßíåé ç óõíåéóöïñÜ óáò áðïäåêôÞ. Ôï &os; áíáðôýóóåôáé áðü Ýíá ìåãÜëï áñéèìü áíèñþðùí áðü üëï ôïí êüóìï. Óôçí ïìÜäá áíÜðôõîçò õðÜñ÷ïõí Üôïìá äéáöüñùí çëéêéþí Þ ãíùóôéêþí áíôéêåéìÝíùí. Ïé åñãáóßåò ïé ïðïßåò ðñÝðåé íá ãßíïõí åßíáé áñêåôÝò üìùò. ÐïëëÝò öïñÝò åßíáé ðåñéóóüôåñåò áðü üôé ìðïñïýí íá êÜíïõí ïé Üíèñùðïé ðïõ åßíáé äéáèÝóéìïé óôçí ïìÜäá ôïõ &os;. Ãé áõôü åßíáé ðÜíôïôå êáëïäå÷ïýìåíç êÜèå âïÞèåéá. Ôï &os; åßíáé õðåýèõíï ãéá Ýíá ïëüêëçñï ëåéôïõñãéêü ðåñéâÜëëïí, êé ü÷é ìüíï ãéá Ýíá ðõñÞíá Þ ìåñéêÜ äéÜóðáñôá åñãáëåßá. ¸ôóé, ç ëßóôá ôùí åñãáóéþí ðïõ ðñÝðåé íá ãßíïõí êáëýðôåé Ýíá áñêåôÜ ìåãÜëï åýñïò: áðü ôçí ôåêìçñßùóç, ôç äïêéìÞ êáé ôçí ðáñïõóßáóç, ìÝ÷ñé ôï ðñüãñáììá åãêáôÜóôáóçò ôïõ óõóôÞìáôïò êáé ôá ðïëý åîåéäéêåõìÝíá èÝìáôá ôçò áíÜðôõîçò ôïõ ðõñÞíá. ¸ôóé åßíáé ó÷åäüí óßãïõñï üôé üëïé ìðïñïýí íá óõíåéóöÝñïõí ìå åðïéêïäïìçôéêü ôñüðï óôï Ýñãï áíÜðôõîçò ôïõ &os;, üðïéåò ãíþóåéò êáé íá Ý÷ïõí. Ìáò åíäéáöÝñåé åðßóçò êáé êÜèå åðéêïéíùíßá ìå åìðïñéêïýò ïñãáíéóìïýò, åöüóïí äñáóôçñéïðïéïýíôáé óå êÜðïéï ÷þñï ó÷åôéêü ìå ôï &os;. ×ñåéÜæåóôå ìéá åéäéêÞ åðÝêôáóç ãéá íá äïõëÝøåé ôï ðñïúüí óáò; Èá ìáò âñåßôå äåêôéêïýò óôá áéôÞìáôá óáò· åéäéêÜ üôáí åßíáé ñåáëéóôéêÜ. Äïõëåýåôå ðÜíù óå Ýíá ðñïúüí âáóéóìÝíï óôï &os;; Ðáñáêáëïýìå åíçìåñþóôå ìáò. Ìðïñåß íá óõíåñãáóôïýìå ìå êÜðïéï ôñüðï ÷ñÞóéìï êáé óôéò äýï ðëåõñÝò. Ï êüóìïò ôïõ åëåýèåñïõ ëïãéóìéêïý Ý÷åé åíäéáöÝñïõóåò åðéðôþóåéò óå ðïëëÝò õðÜñ÷ïõóåò èåùñßåò ó÷åôéêÜ ìå ôçí áíÜðôõîç, ôçí ðþëçóç êáé ôç óõíôÞñçóç ôïõ ëïãéóìéêïý. Áîßæåé, áí ü÷é íá áó÷ïëçèåßôå ìáæß ôïõ, ôïõëÜ÷éóôïí íá Ý÷åôå õðüøç óáò ðùò ëåéôïõñãåß. Ôé ÷ñåéÜæåôáé Ç ëßóôá åñãáóéþí êáé ìéêñüôåñùí Ýñãùí ðïõ áêïëïõèåß åßíáé ìéá åíäåéêôéêÞ óõëëïãÞ áðü éäÝåò ãéá õëïðïßçóç êáé áéôÞìáôá ôùí ÷ñçóôþí ôïõ &os;. Åñãáóßåò ðïõ äå ÷ñåéÜæïíôáé ðñïãñáììáôéóôÝò Áñêåôïß Üíèñùðïé ðïõ ó÷åôßæïíôáé ìå ôï &os; äåí åßíáé ðñïãñáììáôéóôÝò. Ôï Ýñãï ðåñéëáìâÜíåé óõããñáöåßò ôåêìçñßùóçò, ó÷åäéáóôÝò éóôïóåëßäùí êáé áíèñþðïõò ðïõ ôï õðïóôçñßæïõí. Ôï ìüíï ðïõ ÷ñåéÜæåôáé ãéá íá óõíåéóöÝñåé êÜðïéïò óôï Ýñãï áõôÞò ôçò ïìÜäáò åßíáé ç äéÜèåóç íá åðåíäýóåé ëßãï ÷ñüíï êáé ç èÝëçóç ãéá ãíþóç. ÄéáâÜóôå ôç ëßóôá óõ÷íþí åñùôÞóåùí (FAQ) êáé ôï Åã÷åéñßäéï ôïõ &os;. Áí êÜôé äåí åîçãåßôáé óùóôÜ, ðåñéÝ÷åé îåðåñáóìÝíåò ðëçñïöïñßåò Þ åßíáé åíôåëþò ëÜèïò, åéäïðïéÞóôå ìáò. Áêüìá êáëýôåñá, óôåßëôå ìáò ìéá äéüñèùóç (ç SGML äåí åßíáé äýóêïëç óôçí åêìÜèçóç, áëëÜ ðÜíôá äå÷üìáóôå êáé äéïñèþóåéò óå ìïñöÞ áðëïý êåéìÝíïõ ASCII). ÂïçèÞóôå óôç ìåôÜöñáóç ôçò ôåêìçñßùóçò ôïõ &os; óôç ìçôñéêÞ óáò ãëþóóá. Áí õðÜñ÷åé Þäç ôåêìçñßùóç óôç ãëþóóá óáò, ìðïñåßôå íá âïçèÞóåôå óôç ìåôÜöñáóç åðéðñüóèåôùí êåéìÝíùí Þ íá åðéâåâáéþíåôå üôé ç ìåôÜöñáóç åßíáé åíçìåñùìÝíç. Ðñþôá, êïéôÜîôå óôéò áðáíôçìÝíåò åñùôÞóåéò ó÷åôéêÜ ìå ôéò ìåôáöñÜóåéò óôï Âáóéêü Ïäçãü ãéá ôçí Ôåêìçñßùóç ôïõ &os;. Ôï íá óôåßëåôå ìßá ìåôÜöñáóç äåí óáò êáèéóôÜ õðåýèõíï íá ìåôáöñÜóåôå üëç ôçí ôåêìçñßùóç ôïõ &os;. Ùò åèåëïíôÞò ìðïñåßôå íá ìåôáöñÜóåôå üóá êåßìåíá èÝëåôå Þ ìðïñåßôå· üóï ðïëëÜ, ìåãÜëá, ìéêñÜ Þ ëßãá åßíáé áõôÜ. Ìüëéò áñ÷ßóåé êÜðïéïò ôç ìåôÜöñáóç ôçò ôåêìçñßùóçò ôïõ &os; óå ìéá ãëþóóá, ó÷åäüí áìÝóùò áñ÷ßóïõí íá óõíåéóöÝñïõí êé Üëëïé óôçí ðñïóðÜèåéá. Áí Ý÷åôå ôï ÷ñüíï Þ ôçí åíÝñãåéá íá ìåôáöñÜóåôå ìüíï Ýíá ìÝñïò ôçò ôåêìçñßùóçò, ðáñáêáëïýìå ìåôáöñÜóôå ôéò ïäçãßåò åãêáôÜóôáóçò. Íá äéáâÜæåôå ðåñéóôáóéáêÜ (Þ êáèçìåñéíÜ) ôéò &a.questions; êáé &ng.misc;. Ôï íá ìïéñÜæåóôå ôçí åìðåéñßá óáò êáé íá âïçèÜôå áíèñþðïõò íá ëýóïõí ôá ðñïâëÞìáôÜ ôïõò ìðïñåß íá åßíáé éäéáßôåñá éêáíïðïéçôéêü. ÌåñéêÝò öïñÝò ìðïñåß íá ìÜèåôå êáé êÜôé íÝï ìÝóá áðü áõôÞ ôç äéáäéêáóßá! Åðßóçò áõôÝò ïé óõæçôÞóåéò ìðïñåß íá óáò äþóïõí éäÝåò ãéá êáéíïýñéá åíäéáöÝñïíôá ðñÜãìáôá ìå ôá ïðïßá ìðïñåßôå íá áó÷ïëçèåßôå. Åñãáóßåò ãéá ðñïãñáììáôéóôÝò Óôéò ðåñéóóüôåñåò áðü ôéò åñãáóßåò ðïõ áíáöÝñïíôáé åäþ ÷ñåéÜæåôáé åßôå óçìáíôéêÞ åðÝíäõóç ÷ñüíïõ Þ ìßá óå âÜèïò ãíþóç ôïõ ðõñÞíá ôïõ &os; Þ êáé ôá äýï. ÕðÜñ÷ïõí åðßóçò ðïëëÝò åñãáóßåò ïé ïðïßåò åßíáé ôáõôü÷ñïíá ÷ñÞóéìåò êáé áñêåôÜ åýêïëåò áêüìç êáé ãéá êÜðïéïí hacker ôïõ óáââáôïêýñéáêïõ. Áí ôñÝ÷åôå &os;-CURRENT êáé Ý÷åôå ãñÞãïñç óýíäåóç óôï Internet, õðÜñ÷åé Ýíáò åîõðçñåôçôÞò óôï current.FreeBSD.org ðïõ ÷ôßæåé ìéá ðëÞñç Ýêäïóç êÜèå ìÝñá. ÐñïóðáèÞóôå íá åãêáôáóôÞóåôå ôçí ôåëåõôáßá Ýêäïóç áðü åêåß êáé êÜíôå áíáöïñÜ ãéá ïðïéïäÞðïôå ðñüâëçìá óõíáíôÞóåôå êáôÜ ôç äéÜñêåéá ôçò åãêáôÜóôáóçò Þ ìåôÜ áðü áõôÞí. ÄéáâÜóôå ôç &a.bugs;. Ðéèáíüí íá õðÜñ÷åé êÜðïéï ðñüâëçìá ôï ïðïßï ìðïñåßôå íá ó÷ïëéÜóåôå åðïéêïäïìçôéêÜ Þ êÜðïéï patch ôï ïðïßï ìðïñåßôå íá äïêéìÜóåôå. Áêüìá êáëýôåñá, ìðïñåß íá âñåßôå êÜðïéï ðñüâëçìá ôï ïðïßï óáò öáßíåôáé åíäéáöÝñïí êáé ìðïñåß íá ôï äéïñèþóåôå ïé ßäéïé. Áí ãíùñßæåôå ïðïéåóäÞðïôå äéïñèþóåéò ðñïâëÞìáôïò ïé ïðïßåò Ý÷ïõí åöáñìïóôåß åðéôõ÷çìÝíá óôïí êëÜäï áíÜðôõîçò -CURRENT áëëÜ äåí Ý÷ïõí óõã÷ùíåõôåß ìå ôïí êëÜäï -STABLE ìåôÜ áðü êÜðïéï ëïãéêü äéÜóôçìá (óõíÞèùò ìåñéêÝò âäïìÜäåò), óôåßëôå óôïí committer ìéá åõãåíéêÞ õðåíèýìéóç. ÂïçèÞóôå ìáò íá îå÷ùñßóïõìå ôï ëïãéóìéêü áðü åîùôåñéêÝò ïìÜäåò êáé íá ìåôáêéíÞóïõìå ôÝôïéá ðñïãñÜììáôá óôïí êáôÜëïãï src/contrib ôïõ ðçãáßïõ êþäéêá. Óéãïõñåõôåßôå üôé ôá ðñïãñÜììáôá ôïõ src/contrib Ý÷ïõí åíçìåñùèåß óôéò ôåëåõôáßåò äéáèÝóéìåò åêäüóåéò. Ìåôáãëùôôßóôå ôïí ðçãáßï êþäéêá (Þ Ýíá ìÝñïò ôïõ êþäéêá) ìå åðéðëÝïí åéäïðïéÞóåéò ðéèáíþí ëáèþí (compiler warnings) êáé äéïñèþóôå üôé ëÜèç âñåßôå. Äéïñèþóôå ôéò ðñïåéäïðïéÞóåéò ëÜèïõò (warnings) ãéá ôá ports ôá ïðïßá ÷ñçóéìïðïéïýí ìç áðïäåêôÝò êëÞóåéò, üðùò ç óõíÜñôçóç gets(), Þ óõìðåñéëáìâÜíïõí ðáëéÜ áñ÷åßá include, üðùò ôï malloc.h. Áí Ý÷åôå óõíåéóöÝñåé áëëáãÝò ãéá êÜðïéá ports êáé ÷ñåéÜóôçêáí áëëáãÝò ãéá íá äïõëÝøåé ôï áíôßóôïé÷ï ëïãéóìéêü óùóôÜ óå &os;, óôåßëôå ôéò áëëáãÝò óáò óôïõò áñ÷éêïýò äçìéïõñãïýò ôïõ ëïãéóìéêïý (áõôü èá êÜíåé ôç æùÞ óáò åõêïëüôåñç üôáí èá êõêëïöïñÞóïõí ôç íÝá Ýêäïóç). Ðñïóðáèåßóôå íá âñåßôå áíôßãñáöá áðü åðßóçìá ðñüôõðá üðùò ôï &posix;. Ìðïñåßôå íá âñåßôå óõíäÝóìïõò ó÷åôéêÜ ìå áõôÜ ôá ðñüôõðá óôçí éóôïóåëßäá &os; C99 & POSIX Standards Conformance Project. Óõãêñßíåôå ôçí óõìðåñéöïñÜ ôïõ &os; ìå ôçí áðáéôïýìåíç áðü ôá ðñüôõðá. Áí ç óõìðåñéöïñÜ äéáöÝñåé, éäéáßôåñá óå ëåðôÜ Þ äõóäéÜêñéôá óçìåßá ôùí ðñïäéáãñáöþí, óôåßëôå ìéá áíáöïñÜ ðñïâëÞìáôïò ó÷åôéêÜ ìå áõôü. Áí åßíáé äõíáôüí óêåöôåßôå Ýíá ôñüðï íá äéïñèþóåôå ôï ðñüâëçìá êáé óõìðåñéëÜâåôå ôï patch óôçí áíáöïñÜ óáò. Áí èåùñåßôáé üôé ôá ðñüôõðá åßíáé ëáíèáóìÝíá, èÝóôå åñþôçìá óôïí ïñãáíéóìü ôïõ ðñïôýðïõ íá åîåôÜóåé ôï èÝìá. Ìðïñåßôå áêüìç íá ðñïôåßíåôå åðéðëÝïí åñãáóßåò ãéá áõôÞ ôç ëßóôá! Åñãáóßá ÌÝóù ôçò ÂÜóçò Áíáöïñþí ÐñïâëçìÜôùí (PR database) problem reports database âÜóç áíáöïñþí ðñïâëçìÜôùí Ç ëßóôá áíáöïñþí ðñïâëçìÜôùí ôïõ &os; ðåñéÝ÷åé üëåò ôéò ãíùóôÝò áíáöïñÝò ðñïâëçìÜôùí êáé ôá áéôÞìáôá áíáâÜèìéóçò ôá ïðïßá Ý÷ïõí õðïâÜëëåé óå áõôÞ ïé ÷ñÞóôåò ôïõ &os;. Óå áõôÞ õðÜñ÷ïõí åñãáóßåò ôüóï ãéá ðñïãñáììáôéóôÝò üóï êáé ãéá ìç ðñïãñáììáôéóôÝò. ¸íáò ôñüðïò íá âïçèÞóåôå ôçí áíÜðôõîç ôïõ &os; åßíáé íá äéáôñÝîåôå (ìßá ç ðåñéóóüôåñåò öïñÝò) ôç ëßóôá ðñïâëçìÜôùí, øÜ÷íïíôáò ãéá êÜôé ðïõ óáò åíäéáöÝñåé. ÌåñéêÝò áðü áõôÝò ôéò áíáöïñÝò ðñïâëçìÜôùí ó÷åôßæïíôáé ìå ðïëý áðëÝò åñãáóßåò. ÐïëëÝò öïñÝò áñêåß ìßá óýíôïìç ìáôéÜ ãéá íá åðéâåâáéùèåß üôé ç ðñïôåéíüìåíç äéüñèùóç êÜðïéïõ ðñïâëÞìáôïò åßíáé óùóôÞ. ¶ëëåò öïñÝò ïé áëëáãÝò ðïõ ÷ñåéÜæïíôáé åßíáé ðéï äýóêïëåò Þ äåí Ý÷åé âñåèåß êÜðïéá ëýóç áêüìá. Áñ÷ßóôå ìå ôéò áíáöïñÝò ðñïâëçìÜôùí ðïõ äåí Ý÷ïõí åê÷ùñçèåß óå êÜðïéïí Üëëïí. Áí ç áíáöïñÜ åßíáé êáôá÷ùñçìÝíç óå êÜðïéïí, áëëÜ âëÝðåôå üôé åßíáé êÜôé ðïõ ìðïñåßôå íá ÷åéñéóôåßôå, åéäïðïéÞóôå ìå email ôïí õðåýèõíï ôçò áíáöïñÜò êáé ñùôÞóôå áí ìðïñåßôå íá äïõëÝøåôå ðÜíù ó' áõôÞí. ºóùò ï õðåýèõíïò Ý÷åé Þäç îåêéíÞóåé êÜðïéåò äéïñèþóåéò êáé óáò äþóåé êÜôé ãéá äïêéìÞ Þ Ý÷åé Þäç êÜðïéåò éäÝåò ðïõ ìðïñåßôå íá óõæçôÞóåôå ìáæß ôïõ. ÄéáëÝîôå êÜðïéï áíôéêåßìåíï áðü ôçí óåëßäá ìå ôéò <quote>éäÝåò</quote>. Ç ëßóôá &os; ôùí Ýñãùí êáé ôùí éäåþí ãéá åèåëïíôÝò åßíáé åðßóçò äéáèÝóéìç ãéá áíèñþðïõò ìå äéÜèåóç íá óõíåéóöÝñïõí óôï Ýñãï ôïõ &os;. Ç ëßóôá áíáíåþíåôáé ôáêôéêÜ êáé ðåñéëáìâÜíåé áíôéêåßìåíá ãéá åíáó÷üëçóç ôüóï ãéá ðñïãñáììáôéóôÝò üóï êáé ãéá ìç ðñïãñáììáôéóôÝò êáé ðáñÝ÷åé ðëçñïöïñßåò ãéá êÜèå Ýñãï. Ðùò ìðïñåßôå íá óõíåéóöÝñåôå Ïé óõíåéóöïñÝò óôï óýóôçìá êáôáôÜóóïíôáé ãåíéêÜ óå ìéá áðü ôéò áêüëïõèåò 5 êáôçãïñßåò: ÁíáöïñÝò ðñïâëÞìáôïò êáé ãåíéêÝò åðåîçãçìáôéêÝò ðáñáôçñÞóåéò-ó÷üëéá Ìéá éäÝá Þ ðñüôáóç ãåíéêïý ôå÷íéêïý åíäéáöÝñïíôïò èá ðñÝðåé íá áðïóôáëåß óôç ëßóôá &a.hackers;. ÅðéðëÝïí, Üíèñùðïé ìå åíäéáöÝñïí ãéá ôÝôïéá èÝìáôá (áëëÜ êáé áíåêôéêüôçôá óå ìåãÜëï áñéèìü åéóåñ÷üìåíùí ìçíõìÜôùí!) ìðïñïýí íá ãñáöôïýí óôç ëßóôá &a.hackers;. Äåßôå ôï Åã÷åéñßäéï ôïõ &os; ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå áõôÞí áëëÜ êáé Üëëåò ëßóôåò. Áí âñåßôå êÜðïéï bug Þ áí Ý÷åôå êÜíåé êÜðïéá óõãêåêñéìÝíç áëëáãÞ, ðáñáêáëïýìå êÜíôå áíáöïñÜ ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá &man.send-pr.1; Þ ôçí áíôßóôïé÷ç éóôïóåëßäá. ÐñïóðáèÞóôå íá óõìðëçñþóåôå üëá ôá ðåäßá ôçò áíáöïñÜò. Áí ïé áëëáãÝò ðïõ êÜíáôå äåí îåðåñíïýí ôá 65KB óå ìÝãåèïò, óõìðåñéëÜâåôå ôéò áëëáãÝò óáò áðåõèåßáò óôçí áíáöïñÜ. Áí ïé áëëáãÝò åßíáé êáôÜëëçëåò ãéá åöáñìïãÞ óôïí ðçãáßï êþäéêá, ðñïóèÝóôå ôçí åôéêÝôá [PATCH] óôçí ðåñßëçøç ôçò áíáöïñÜò. ¼ôáí óõìðåñéëáìâÜíåôå patches, ìç ÷ñçóéìïðïéåßôå áíôéãñáöÞ-êáé-åðéêüëëçóç, äéüôé ç áíôéãñáöÞ êáé åðéêüëëçóç ìåôáôñÝðåé óõ÷íÜ ôïõò óôçëïèÝôåò (TAB) óå êåíÜ êáé á÷ñçóôåýåé ôï patch. Áí ôá patches åßíáé ðïëý ìåãáëýôåñá áðü 20KB, äïêéìÜóôå íá ôá óõìðéÝóåôå (ð.÷. ìå ôï &man.gzip.1; Þ ôï &man.bzip2.1;) êáé ÷ñçóéìïðïéÞóôå ôï åñãáëåßï &man.uuencode.1; ãéá íá åéóÜãåôå ôç óõìðéåóìÝíç ìïñöÞ óôçí áíáöïñÜ óáò. ÌåôÜ ôçò õðïâïëÞ ìéáò áíáöïñÜò èá ëÜâåôå åðéâåâáßùóç ðáñÜëëçëá ìå Ýíáí áñéèìü áíáöïñÜò. ÊñáôÞóôå ôïí áñéèìü þóôå íá ìðïñåßôå íá ìáò åíçìåñþíåôå ìå ðëçñïöïñßåò ó÷åôéêÜ ìå ôï ðñüâëçìá óôÝëíïíôáò mail óôï &a.bugfollowup;. ×ñçóéìïðïéÞóôå ôïí áñéèìü ôçò áíáöïñÜò óáò óôï èÝìá ôïõ ìçíýìáôïò, ð.÷. "Re: kern/3377". Åðéðñüóèåôåò ðëçñïöïñßåò ãéá ïðïéïäÞðïôå áíáöïñÜ ðñïâëÞìáôïò èá ðñÝðåé íá õðïâÜëëïíôáé ìå ôïí ðáñáðÜíù ôñüðï. ÅÜí äå ëÜâåôå åðéâåâáßùóç åãêáßñùò (3 ìÝñåò ùò ìéá âäïìÜäá, áíÜëïãá ìå ôç áîéïðéóôßá ôïõ email) Þ ãéá êÜðïéï ëüãï áäõíáôåßôå íá ÷ñçóéìïðïéÞóåôå ôçí åíôïëÞ &man.send-pr.1;, ìðïñåßôå íá áðåõèõíèåßôå óå êÜðïéïí ðñïêåéìÝíïõ íá ôçí áñ÷åéïèåôÞóåé ãéá åóÜò óôÝëíïíôáò mail óôç &a.bugs;. Äåßôå åðßóçò áõôü ôï Üñèñï ó÷åôéêÜ ìå ôï ðþò íá ãñÜöåôå êáëÝò áíáöïñÝò ðñïâëçìÜôùí. ÁëëáãÝò óôçí ôåêìçñßùóç documentation submissions óõíåéóöïñÝò ôåêìçñßùóçò Ïé áëëáãÝò óôçí ôåêìçñßùóç åðéâëÝðïíôáé áðü ôçí &a.doc;. Ãéá ðëÞñåéò ïäçãßåò ó÷åôéêÜ ìå ôïí ôñüðï ðïõ ìðïñåßôå íá óõíåéóöÝñåôå óôçí ôåêìçñßùóç ôïõ &os;, äåßôå ôïí Ïäçãü ôåêìçñßùóçò ôïõ &os;. Óôåßëôå ôá êáéíïýñéá óáò êåßìåíá Þ ôéò áëëáãÝò óáò (áêüìç êáé ìéêñïäéïñèþóåéò åßíáé ðÜíôá êáëïäå÷ïýìåíåò) ÷ñçóéìïðïéþíôáò ôçí åíôïëÞ &man.send-pr.1; üðùò ðåñéãñÜöåôå óôï ÁíáöïñÜ bugs êáé ãåíéêÜ ó÷üëéá - ðáñáôçñÞóåéò. ÁëëáãÝò óôïí Ðçãáßï Êþäéêá &os;-CURRENT Ìßá ðñïóèÞêç Þ áëëáãÞ óôïí õðÜñ÷ïíôá êþäéêá åßíáé êáôÜ êÜðïéï ôñüðï ðåñßôå÷íç õðüèåóç êáé åîáñôÜôáé áñêåôÜ áðü ôïí âáèìü ôçò åíçìÝñùóçò ðïõ Ý÷åôå ìå ôçí ôñÝ÷ïõóá êáôÜóôáóç ôçò áíÜðôõîçò ôïõ &os;. ÕðÜñ÷åé ìéá åéäéêÞ óõíå÷þò áíáðôõóóüìåíç Ýêäïóç ôïõ &os; ãíùóôÞ ùò &os;-CURRENT ç ïðïßá åßíáé äéáèÝóéìç ìå äéÜöïñïõò ôñüðïõò ãéá ôçí åõêïëßá ôùí ðñïãñáììáôéóôþí ðïõ äñáóôçñéïðïéïýíôáé åíåñãÜ óôçí áíÜðôõîç ôïõ óõóôÞìáôïò. Äåßôå ôï Åã÷åéñßäéï ôïõ &os; ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôï ðïõ èá âñåßôå êáé ðþò ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôï &os;-CURRENT. Äïõëåýïíôáò áðü ðáëéüôåñï êþäéêá äõóôõ÷þò óçìáßíåé üôé ïé áëëáãÝò óáò ìðïñåß ìåñéêÝò öïñÝò íá åßíáé áñêåôÜ îåðåñáóìÝíåò Þ íá áðïêëßíïõí ðïëý, ïðüôå íá äõóêïëåýåé êÜðùò ç åíóùìÜôùóÞ ôïõò óôï &os;. Ñßóêá óáí ãé' áõôÜ ìðïñïýí íá åëá÷éóôïðïéçèïýí êÜðùò ìå ôçí óõììåôï÷Þ óôéò ëßóôåò &a.announce; êáé &a.current;, óôéò ïðïßåò äéåîÜãïíôáé óõæçôÞóåéò ãéá ôçí ôñÝ÷ïõóá êáôÜóôáóç ôïõ óõóôÞìáôïò. Áöïý åîáóöáëßóåôå êÜðùò Ýíá ó÷åôéêÜ åíçìåñùìÝíï áíôßãñáöï ôïõ ðçãáßïõ êþäéêá ùò âÜóç ãéá ôéò áëëáãÝò óáò, ôï åðüìåíï âÞìá åßíáé íá äçìéïõñãÞóåôå diffs ãéá áðïóôïëÞ óôçí ïìÜäá áíÜðôõîçò ôïõ &os;. Áõôü ãßíåôáé ìå ôçí åíôïëÞ &man.diff.1;. Ôï ðñïôéìþìåíï format ôïõ &man.diff.1; ãéá ôçí õðïâïëÞ patches åßíáé ç åíïðïéçìÝíç ìïñöÞ åîüäïõ (unified diff), ðïõ äçìéïõñãåßôáé áðü ôçí åíôïëÞ diff -u. Ìéá ìéêñÞ åîáßñåóç åßíáé ôá ôá patches ðïõ áëëÜæïõí ìåãÜëá êïììÜôéá êþäéêá, ïõóéáóôéêÜ áíôéêáèéóôþíôáò ôá ó÷åäüí ìå ìéá êáéíïýñéá Ýêäïóç. Ãéá ôÝôïéåò áëëáãÝò ìðïñåß íá åßíáé ðéï åõáíÜãíùóôç ç ìïñöÞ åîüäïõ ðïõ äçìéïõñãåßôáé áðü ôçí åíôïëÞ diff -c. diff Ãéá ðáñÜäåéãìá ôï: &prompt.user; diff -c ðáëéü_áñ÷åßï íÝï_áñ÷åßï Þ ôï &prompt.user; diff -c -r ðáëéüò_êáôÜëïãïò íÝïò_êáôÜëïãïò èá äçìéïõñãÞóåé Ýíá óåô áðü context diffs ãéá ôïí êþäéêá ôïõ óõãêåêñéìÝíïõ áñ÷åßïõ Þ ôçò éåñáñ÷ßáò êáôáëüãùí. Ïìïßùò ôï, &prompt.user; diff -u ðáëéü_áñ÷åßï íÝï_áñ÷åßï Þ ôï &prompt.user; diff -u -r ðáëéüò_êáôÜëïãïò íÝïò_êáôÜëïãïò èá êÜíåé ôï ßäéï, áëëÜ èá ðáñÜãåé diff åíïðïéçìÝíç ìïñöÞ. Äåßôå ôç âïÞèåéá ôïõ åñãáëåßïõ &man.diff.1; ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò. Áðü ôç óôéãìÞ ðïõ Ý÷åôå êÜðïéá diffs, (ôá ïðïßá ìðïñåßôå íá åëÝãîåôå ìå ôçí åíôïëÞ &man.patch.1;), èá ðñÝðåé íá ôá õðïâÜëëåôå ãéá åíóùìÜôùóç óôï &os;. ×ñçóéìïðïéÞóôå ôï ðñüãñáììá &man.send-pr.1;, üðùò ðåñéãñÜöåôå óôï êåßìåíï ÁíáöïñÜ Bugs êáé ãåíéêüò ó÷ïëéáóìüò - ðáñáôçñÞóåéò. Ìç óôÝëíåôå ìüíï Ýíá ìÞíõìá ìå ôá patches óôç &a.hackers; áëëéþò èá ÷áèïýí! Óáò åõ÷áñéóôïýìå ðñïêáôáâïëéêÜ ãéá ïðïéáäÞðïôå ðñïóöïñÜ êþäéêá (ôï Ýñãï áíÜðôõîçò ôïõ &os; åßíáé åèåëïíôéêÞ ðñïóðÜèåéá ðïõ âáóßæåôáé áêñéâþò óå ôÝôïéåò ðñïóöïñÝò!). ÅðåéäÞ åßìáóôå áðáó÷ïëçìÝíïé, ìðïñåß íá ìç ÷åéñéóôïýìå ôçí áßôçóç ãéá áëëáãÞ áìÝóùò, ùóôüóï ìÝ÷ñé íá ôï êÜíïõìå áõôü, èá ðáñáìåßíåé óôçí âÜóç áíáöïñþí. Èõìçèåßôå íá åðéóçìÜíåôå ôçí õðïâïëÞ óáò ìå ôçí åôéêÝôá [PATCH] óôçí ðåñßëçøç ôçò áíáöïñÜò. uuencode Áí íïìßæåôå üôé ÷ñåéÜæåôáé (ð.÷. Ý÷åôå ðñïóèÝôåé, áöáéñÝóåé Þ ìåôïíïìÜóåé êÜðïéá áñ÷åßá), ÷ñçóéìïðïéåßóôå ôï åñãáëåßï tar ãéá íá ðáêåôÜñåôå ôéò áëëáãÝò óáò, êáé ôï åñãáëåßï &man.uuencode.1; ãéá íá ôéò åíóùìáôþóåôå óôçí áíáöïñÜ ðïõ èá óôåßëåôå. ÅíáëëáêôéêÜ, ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôï åñãáëåßï &man.shar.1; áíôß ãéá ôï &man.tar.1;. Áí ç öýóç ôùí áëëáãþí ðïõ èÝëåôå íá êÜíåôå åßíáé êÜðùò åõáßóèçôç, ð.÷. áí äåí åßóôå óßãïõñïé ãéá ôá ðíåõìáôéêÜ äéêáéþìáôá êáé ôç äéáíïìÞ ôùí áëëáãþí Þ áí áðëÜ äåí åßóôå Ýôïéìïé íá äþóåôå óôç äçìïóéüôçôá êÜðïéåò áëëáãÝò ÷ùñßò Ýíá review áêüìá, ôüôå åßíáé êáëýôåñá íá óôåßëåôå ôéò áëëáãÝò óáò áðåõèåßáò óôçí &a.core; áíôß íá ôéò ðñïùèÞóåôå ìÝóù ôïõ &man.send-pr.1;. Ç &a.core; áðïôåëåßôáé áðü Ýíá ðïëý ìéêñüôåñï áñéèìü áôüìùí. ¸÷åôå õðüøéí üìùò üôé áõôÞ ç ïìÜäá åßíáé ðïëý áðáó÷ïëçìÝíç, ïðüôå êáëü åßíáé íá ôïõò óôÝëíåôå ìçíýìáôá ìüíï üôáí åßóôå áñêåôÜ óßãïõñïé üôé åßíáé áðáñáßôçôï. ÊÜôé ôåëåõôáßï ó÷åôéêÜ ìå ôïí ðçãáßï êþäéêá ôïõ &os;. Ïé óåëßäåò ôåêìçñßùóçò &man.intro.9; êáé &man.style.9; ðåñéÝ÷ïõí ðëçñïöïñßåò ó÷åôéêÜ ìå ôï óôõë êþäéêá ðïõ ðñïôéìïýìå ãéá ôï &os;. Ðñéí óôåßëåôå óçìáíôéêÝò áëëáãÝò óôçí ïìÜäá áíÜðôõîçò åßíáé óçìáíôéêü íá Ý÷åôå åîïéêåéùèåß ìå ôï óôõë ðïõ ãñÜöïõìå êáé, üôáí åßíáé äõíáôüí, íá ôï áêïëïõèÞóåôå óôï ãñÜøéìï ôïõ êþäéêá ðïõ èá ìáò óôåßëåôå. ÍÝïò Êþäéêáò êáé ÌåãÜëá ÐáêÝôá Ðñüóèåôùí ×áñáêôçñéóôéêþí Óôçí ðåñßðôùóç ìéáò ó÷åôéêÜ ìåãÜëçò óõíåéóöïñÜò ëïãéóìéêïý óôï &os; êáé êÜèå öïñÜ ðïõ ðñïóôßèåôáé Ýíá óçìáíôéêü êáéíïýñéï ÷áñáêôçñéóôéêü óôï óýóôçìá, åßíáé ó÷åäüí ðÜíôá áðáñáßôçôï íá åßíáé äéáèÝóéìåò ïé áëëáãÝò ìå ôç ìïñöÞ åíüò ðáêÝôïõ tar Þ íá åßíáé äéáèÝóéìåò ìÝóù åíüò åîõðçñåôçôÞ web Þ FTP. Áí äåí Ý÷åôå ðñüóâáóç ãéá íá áíåâÜóåôå ôá áñ÷åßá óå êÜðïéïn åîõðçñåôçôÞ web Þ FTP, ñùôÞóôå óôçí êáôÜëëçëç ëßóôá çëåêôñïíéêïý ôá÷õäñïìåßïõ ôïõ &os; êáé êÜðïéïò Üëëïò ìðïñåß íá öéëïîåíÞóåé ôá áñ÷åßá ãéá óáò. Ôï åõáßóèçôï èÝìá ôùí ðíåõìáôéêþí äéêáéùìÜôùí êáé ôùí áäåéþí ÷ñÞóçò åßíáé ôï åðüìåíï ðñÜãìá ðïõ ðáßæåé ìåãÜëï ñüëï, éäéáßôåñá ãéá ìåãÜëá Ýñãá ëïãéóìéêïý. Ïé Üäåéåò ÷ñÞóçò ðïõ åßíáé áðïäåêôÝò ãéá êþäéêá ðïõ åíóùìáôþíåôáé óôï &os; åßíáé ïé ðáñáêÜôù: ¶äåéá BSD Ç Üäåéá ÷ñÞóçò BSD. ÁõôÞ ç Üäåéá åßíáé ç ðñïôéìüôåñç, ëüãù ôçò éäéáßôåñçò ÷ùñßò ðåñéïñéóìïýò öýóçò ðïõ Ý÷åé êáé ôçò äõíáôüôçôáò ÷ñÞóçò ôïõ êþäéêá áêüìç êáé ãéá åìðïñéêïýò óêïðïýò. Ç ÏìÜäá ôïõ &os; äåí áðïèáññýíåé ôÝôïéïõ åßäïõò ÷ñÞóç ôïõ ðçãáßïõ êþäéêá. Ôï áíôßèåôï ìÜëéóôá, åíèáññýíåé ôç ÷ñÞóç ôïõ êþäéêá, áöïý Ýôóé õðÜñ÷åé ðéèáíüôçôá ïñéóìÝíïé åìðïñéêïß íá óõíåéóöÝñïõí ìå ôç óåéñÜ ôïõò óôçí áíÜðôõîç ôïõ &os;. GPLGNU General Public License GNU General Public License Ç Üäåéá GNU General Public License, Þ GPL. áõôÞ ç Üäåéá äåí åßíáé ôüóï äçìïöéëÞò åðåéäÞ ÷ñåéÜæåôáé Ýîôñá ðñïóðÜèåéá áðü ïðïéïíäÞðïôå ÷ñçóéìïðïéåß ôïí êþäéêá ãéá åìðïñéêïýò óêïðïýò, áëëÜ åðåéäÞ õðÜñ÷åé Ýíá ìåãÜëï óþìá ðçãáßïõ êþäéêá, ôï ïðïßï äéáíÝìåôáé ìå áõôÞ ôçí Üäåéá êé áðü ôï ïðïßï åîáñôéüìáóôå (ìåôáãëùôôéóôÞò, assembler, ðñïãñÜììáôá ìïñöïðïßçóçò êåéìÝíïõ, êëð.), èá Þôáí êÜðùò ÷áæü íá ìç äå÷üìáóôå êáìßá áëëáãÞ óå ôÝôïéï êþäéêá. Ï êþäéêáò ìå Üäåéá GPL äéáíÝìåôáé üìùò óå äéêü ôïõ, îå÷ùñéóôü ìÝñïò ôïõ ðçãáßïõ êþäéêá ôïõ &os;, êÜôù áðü ôïõò êáôáëüãïõò /sys/gnu êáé /usr/src/gnu. ¸ôóé åßíáé åýêïëï íá îå÷ùñßóåé êáíåßò áðü ôïí êþäéêá ôïõ &os; üëá ôá ìÝñç ìå Üäåéá GPL, üôáí õðÜñ÷åé ëüãïò íá ãßíåé ôÝôïéïò äéá÷ùñéóìüò. Ïé óõíåéóöïñÝò êþäéêá ìå ïðïéáäÞðïôå Üëëç Üäåéá ðñÝðåé íá ðåñÜóïõí áðü ðïëý ðñïóåêôéêü Ýëåã÷ï ðñéí áðïöáóßóïõìå áí õðÜñ÷åé ëüãïò íá åíóùìáôùèïýí ìå ôï &os;. Ïé óõíåéóöïñÝò ìå éäéáßôåñá áõóôçñïýò åìðïñéêïýò ðåñéïñéóìïýò áðïññßðôïíôáé óõíÞèùò ÷ùñßò ðïëý óêÝøç, áëëÜ ïé äçìéïõñãïß ôùí áëëáãþí Þ ôïõ óõãêåêñéìÝíïõ êþäéêá ìðïñïýí ðÜíôá íá äéáíÝìïõí ôéò áëëáãÝò ôïõò ìÝóá áðü ôá äéêÜ ôïõò êáíÜëéá äéáíïìÞò êáé åðéêïéíùíßáò. Ãéá íá ïñßóåôå üôé êÜðïéï äéêü óáò Ýñãï ðçãáßïõ êþäéêá äéáíÝìåôáé ìå ôïõò üñïõò ìéÜò Üäåéáò ôýðïõ BSD ìðïñåßôå íá óõìðåñéëÜâåôå óôçí áñ÷Þ ôùí áñ÷åßùí ðçãáßïõ êþäéêá ôï ðáñáêÜôù êåßìåíï, áíôéêáèéóôþíôáò ôï êåßìåíï ìåôáîý ôùí %% ìå ôéò êáôÜëëçëåò ðëçñïöïñßåò: Copyright (c) %%÷ñïíéÜ_Þ_÷ñïíéÝò_áëëáãþí%% %%ôï_üíïìÜ_óáò%%, %%ç_äéåýèõíóÞ_óáò%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%ôï_üíïìÜ_óáò%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%ôï_üíïìÜ_óáò%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ ¸íá áíôßãñáöï áõôïý ôïõ êåéìÝíïõ õðÜñ÷åé óôï áñ÷åßï /usr/share/examples/etc/bsd-style-copyright, ïðüôå ìðïñåßôå íá ôï áíôéãñÜöåôå áðü åêåß êÜèå öïñÜ ðïõ ÷ñåéÜæåôáé. ×ñÞìáôá, Õëéêü Þ Ðñüóâáóç óôï Äéáäßêôõï ÊÜèå äùñåÜ ðïõ ìðïñåßôå íá êÜíåôå óôï Ýñãï ôïõ &os; åßíáé åõðñüóäåêôç. Áêüìá êáé ç ðéï ìéêñÞ ðñïóöïñÜ ìðïñåß íá Ý÷åé ìåãÜëç óçìáóßá ãéá Ýíá Ýñãï ôï ïðïßï âáóßæåôáé óôçí åèåëïíôéêÞ åñãáóßá, üðùò ôï äéêü ìáò. ÅéäéêÜ ïé ðñïóöïñÝò óå õëéêü åßíáé ðïëý óçìáíôéêÝò, áöïý Ýôóé ìáò äßíåôáé ç äõíáôüôçôá íá åðåêôåßíïõìå ôçí õðïóôÞñéîç ôïõ &os; ãéá ôï õëéêü áõôü — êÜôé ðïõ ìðïñåß íá ìçí åßíáé åýêïëï áí ðñÝðåé íá áãïñÜóïõìå êÜèå êïììÜôé õëéêïý ìüíïé ìáò. <anchor id="donations"/>×ñçìáôéêÝò ÄùñåÝò Ç ïñãÜíùóç &os; Foundation åßíáé Ýíáò ìç êåñäïóêïðéêüò óýëëïãïò, ï ïðïßïò Ý÷åé éäñõèåß ãéá íá ðñïùèÞóåé ôï Ýñãï ôçò ÏìÜäáò ôïõ &os;. Ëüãù ôçò íïìéêÞò öýóçò ôïõ óõëëüãïõ, ç ïñãÜíùóç ðáñÝ÷åé ìåñéêÝò öïñïëïãéêÝò åëáöñýíóåéò óôéò ÇíùìÝíåò Ðïëéôåßåò êáé ðéï óõãêåêñéìÝíá óôçí ðïëéôåßá ôïõ Colorado. Ïé äùñåÝò óôçí ïñãÜíùóç åêðßðôïõí áðü ôïõò öüñïõò ðïõ ðñÝðåé íá ðëçñþóåé êÜðïéïò óôéò ÇíùìÝíåò Ðïëéôåßåò· ðéèáíüí êáé óå Üëëá ìÝñç. Ïé äùñÝåò óáò ìðïñïýí íá óôáëïýí óå ìïñöÞ åìâÜóìáôïò, óôç äéåýèõíóç:
The &os; Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
Ç ïñãÜíùóç ìðïñåß ðëÝïí íá äå÷ôåß êáé äùñåÝò ìÝóù äéêôýïõ áðü ôï óýóôçìá PayPal. Áí åíäéáöÝñåóôå íá êÜíåôå êÜðïéá äùñåÜ, ðáñáêáëïýìå îåêéíÞóôå áðü ôçí éóôïóåëßäá ôçò &os; Foundation. Ðåñéóóüôåñåò ðëçñïöïñßåò ãéá ôçí ïñãÜíùóç &os; Foundation ìðïñåßôå íá âñåßôå óôçí áíáêïßíùóç The &os; Foundation -- an Introduction. Ç åðéêïéíùíßá ìå ôçí ïñãÜíùóç ìðïñåß íá ãßíåé êáé ìÝóù çëåêôñïíéêÞò áëëçëïãñáößáò óôç äéåýèõíóç bod@FreeBSDFoundation.org. ÄùñåÝò Õëéêïý donations äùñåÝò Ç ÏìÜäá ÁíÜðôõîçò ôïõ &os; äÝ÷åôáé êÜèå äùñåÜ õëéêïý ãéá ôçí ïðïßá ìðïñåß íá âñåé êÜðïéá êáëÞ ÷ñÞóç. Áí åíäéáöÝñåóôå íá ìáò äùñßóåôå êÜðïéï õëéêü, ðáñáêáëïýìå åðéêïéíùíÞóôå ìå ôçí ÏìÜäá Äéá÷åßñéóçò ôùí Äùñåþí. ÄùñÝåò Ðñüóâáóçò óôï Äéáäßêôõï ÐÜíôá åßíáé ÷ñÞóéìï íá Ý÷ïõìå êáéíïýñéá mirror sites ãéá ôï FTP, ôïí éóôüôïðü ìáò Þ ôï cvsup. Áí èÝëåôå íá åãêáôáóôÞóåôå Ýíá ôÝôïéï mirror, ðáñáêáëïýìå äåßôå ôo Üñèñï Mirroring &os;. Åêåß èá âñåßôå ðåñéóóüôåñåò ðëçñïöïñßåò. + +
diff --git a/el_GR.ISO8859-7/articles/nanobsd/article.xml b/el_GR.ISO8859-7/articles/nanobsd/article.xml index 30b61210e6..78f99c86ed 100644 --- a/el_GR.ISO8859-7/articles/nanobsd/article.xml +++ b/el_GR.ISO8859-7/articles/nanobsd/article.xml @@ -1,576 +1,578 @@
ÅéóáãùãÞ óôï NanoBSD Daniel Gerzo ÊõñéÜêïò ÊåíôñùôÞò 2006, 2009 Ç ÏìÜäá Ôåêìçñßùóçò ôïõ &os; &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Ôï Ýããñáöï áõôü ðáñÝ÷åé ðëçñïöïñßåò ãéá ôá åñãáëåßá ôïõ NanoBSD, ôá ïðïßá ìðïñïýí íá ÷ñçóéìïðïéçèïýí ðñïêåéìÝíïõ íá äçìéïõñãçèïýí åßäùëá ôïõ óõóôÞìáôïò &os; ãéá embedded åöáñìïãÝò, êáôÜëëçëåò ãéá ÷ñÞóç áðü êÜñôá Compact Flash (Þ Üëëï ìÝóï áðïèÞêåõóçò). ÅéóáãùãÞ óôï NanoBSD NanoBSD Ôï NanoBSD åßíáé Ýíá åñãáëåßï ôï ïðïßï áíáðôýóóåôáé åíåñãÜ áðü ôïí &a.phk;. Äçìéïõñãåß Ýíá åéêïíéêü åßäùëï ôïõ óõóôÞìáôïò &os; ãéá embedded åöáñìïãÝò, éäáíéêü ãéá êÜñôåò Compact Flash (Þ Üëëï ìÝóï áðïèÞêåõóçò). Ìðïñåß íá ÷ñçóéìïðïéçèåß ãéá íá öôéá÷ôïýí åîåéäéêåõìÝíåò åéêüíåò, ó÷åäéáóìÝíåò ãéá åýêïëç åãêáôÜóôáóç êáé óõíôÞñçóç óõóôçìÜôùí ôýðïõ computer appliance. Ôá óõóôÞìáôá ôÝôïéïõ åßäïõò Ý÷ïõí ôï õëéêü êáé ëïãéóìéêü ôïõò åíïðïéçìÝíá ìÝóá óôï ðñïúüí. Áõôü óçìáßíåé ðùò óõ÷íÜ åßíáé ðñïåãêáôåóôçìÝíá üëá ôá áðáñáßôçôá ðñïãñÜììáôá. Ç óõóêåõÞ óõíäÝåôáé óå Ýíá õðÜñ÷ïí äßêôõï êáé ìðïñåß íá ëåéôïõñãÞóåé (ó÷åäüí) áìÝóùò. Ôá âáóéêÜ ÷áñáêôçñéóôéêÜ ôïõ NanoBSD åßíáé: Ôá ports êáé ôá ðáêÝôá ëåéôïõñãïýí üðùò óôï &os; — ïðïéïäÞðïôå ðñüãñáììá ìðïñåß íá åãêáôáóôáèåß êáé íá ÷ñçóéìïðïéçèåß óôï &os; ìðïñåß íá åíóùìáôùèåß êáé óå Ýíá åßäùëï NanoBSD êáé íá ëåéôïõñãÞóåé ìå ôïí ßäéï ôñüðï. Äå õóôåñåß óå ëåéôïõñãéêüôçôá — Áí åßíáé åöéêôü íá ãßíåé êÜôé ìå ôï &os;, ôüôå åßíáé åöéêôü íá ãßíåé ôï ßäéï ðñÜìá êáé ìå ôï NanoBSD, åêôüò áí ôï óõãêåêñéìÝíï ÷áñáêôçñéóôéêü Ý÷åé óêüðéìá áöáéñåèåß áðü ôï åßäùëï ôïõ NanoBSD. Ôï NanoBSD ôñÝ÷åé ìå ôï óýóôçìá óå êáôÜóôáóç ðñïóôáóßáò áðü åããñáöÞ. Ìðïñåßôå áêüìá êáé íá ôï áðïóõíäÝóåôå áðü ôï ñåýìá ôçí þñá ðïõ ëåéôïõñãåß. Äåí åßíáé áíáãêáßï íá åêôåëåóôåß ôï &man.fsck.8; ìåôÜ áðü ìéá Üãáñìðç äéáêïðÞ ëåéôïõñãßáò ôïõ óõóôÞìáôïò. Åßíáé åýêïëï íá äçìéïõñãçèåß êáé íá ðñïóáñìïóôåß Ýíá åßäùëï NanoBSD. Ìå ôç ÷ñÞóç åíüò ìüíï óåíáñßïõ öëïéïý êáé åíüò áñ÷åßïõ äéáìüñöùóçò åßíáé åöéêôÞ ç äüìçóç ðñïóáñìïóìÝíùí åéäþëùí ðïõ éêáíïðïéïýí ïðïéáäÞðïôå áíÜãêç. Ñýèìéóç ôïõ NanoBSD Ç Ó÷åäßáóç ôïõ NanoBSD Áöïý ãñáöôåß Ýíá åßäùëï ôïõ NanoBSD óå êÜðïéï áðïèçêåõôéêü ìÝóï, ìðïñåß íá ÷ñçóéìïðïéçèåß ãéá íá îåêéíÞóåé Ýíá óýóôçìá &os;. Ç ðñïêáèïñéóìÝíç äéáìüñöùóç ôïõ ìÝóïõ åêêßíçóçò áðïôåëåßôáé áðü ôñßá ìÝñç: Äýï äéáìåñßóìáôá åêêßíçóçò: code#1 êáé code#2. Ôï äéáìÝñéóìá ñõèìßóåùí, Áõôü ìðïñåß íá ðñïóáñôçèåß óôïí êáôÜëïãï /cfg ôçí þñá ëåéôïõñãßáò ôïõ NanoBSD. ÁõôÜ ôá ôñßá äéáìåñßóìáôá êáíïíéêÜ åßíáé ðñïóáñôçìÝíá ìüíï ãéá áíÜãíùóç. Ïé êáôÜëïãïé /etc êáé /var åßíáé åéêïíéêïß äßóêïé &man.md.4; (malloc). Ôï äéáìÝñéóìá ñõèìßóåùí ìðïñåß íá ðñïóáñôçèåß óôïí êáôÜëïãï /cfg. ÐåñéÝ÷åé áñ÷åßá ôá ïðïßá áíôéãñÜöïíôáé óôïí êáôÜëïãï /etc. ÊáôÜ ôçí åêêßíçóç ôïõ óõóôÞìáôïò ôï äéáìÝñéóìá ñõèìßóåùí ðñïóáñôÜôáé ðñïóùñéíÜ ìüíï ãéá áíÜãíùóç êáé áíôéãñÜöïíôáé ôá áñ÷åßá ôïõ óôïí êáôÜëïãï /etc. Ïðüôå ãéá íá åßíáé êÜðïéá áëëáãÞ ñõèìßóåùí ðéï ìüíéìç êáé íá éó÷ýåé áêüìá êáé ìåôÜ áðü åðáíåêêßíçóç ôïõ óõóôÞìáôïò, ðñÝðåé íá áíôéãñÜöåôáé áðü ôïí êáôÜëïãï /etc óôï äéáìÝñéóìá ñõèìßóåùí, áöïý áõôü ðñïóáñôçèåß ãéá ãñÜøéìï óôïí êáôÜëïãï /cfg. ÊÜíïíôáò ìüíéìåò áëëáãÝò óôï <filename>/etc/resolv.conf</filename> &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg Ôï äéáìÝñéóìá ôï ïðïßï ðåñéÝ÷åé ôïí êáôÜëïãï /cfg ðñÝðåé íá ðñïóáñôÜôáé ìüíï êáôÜ ôçí åêêßíçóç êáé üôáí Ý÷ïõí ðñïôåñáéüôçôá ôá áñ÷åßá ñõèìßóåùí ôïõ /cfg. Äåí åßíáé êáëÞ éäÝá íá ìÝíåé ìüíéìá ðñïóáñôçìÝíï ôï äéáìÝñéóìá /cfg. Áí Ýíá äéáìÝñéóìá åßíáé ðñïóáñôçìÝíï ãéá ãñÜøéìï êáé ôï áðïèçêåõôéêü ìÝóï ôïõ NanoBSD åðéôñÝðåé ðåñéïñéóìÝíï áñéèìü êýêëùí åããñáöÞò (üðùò ð.÷. ìåñéêÝò êÜñôåò CF), ìðïñåß íá åðçñåáóôåß áñíçôéêÜ ôï áðïèçêåõôéìü ìÝóï åðåéäÞ ï ðõñÞíáò ãñÜöåé êÜèå ëßãï óôïõò äßóêïõò ôïõ óõóôÞìáôïò (syncer). Äçìéïõñãßá Åíüò ÐñïóáñìïóìÝíïõ ÓõóôÞìáôïò NanoBSD Ôï åßäùëï ôïõ NanoBSD äçìéïõñãåßôáé áðü Ýíá áðëü óåíÜñéï êïíóüëáò, ôï nanobsd.sh, ôï ïðïßï ìðïñåß íá âñåèåß óôïí êáôÜëïãï /usr/src/tools/nanobsd. Áõôü ôï óåíÜñéï äçìéïõñãåß Ýíá åßäùëï äßóêïõ, ôï ïðïßï ìðïñåß íá áíôéãñáöåß áðåõèåßáò óå êÜðïéï áðïèçêåõôéêü ìåóï ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá &man.dd.1;. Ïé áðáñáßôçôåò åíôïëÝò ðñïêåéìÝíïõ íá äçìéïõñãçèåß Ýíá åßäùëï ôïõ NanoBSD åßíáé ïé åîÞò: &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k ÁëëáãÞ áðü ôïí ôñÝ÷ïíôá êáôÜëïãï óôïí âáóéêü êáôÜëïãï ôïõ óåíáñßïõ äçìéïõñãßáò ôïõ NanoBSD. Åêêßíçóç ôçò äçìéïõñãßáò ôïõ åéäþëïõ. ÁëëáãÞ áðü ôïí ôñÝ÷ïíôá êáôÜëïãï óôïí êáôÜëïãï ðïõ ðåñéÝ÷åé ôï åßäùëï ôïõ NanoBSD. ÁíôéãñáöÞ ôïõ NanoBSD óå Ýíá ìÝóï áðïèÞêåõóçò. Ðñïóáñìüæïíôáò ôï åßäùëï ôïõ NanoBSD Áõôü åßíáé ðéèáíüôáôá ôï ðéï óçìáíôéêü êáé ðéï åíäéáöÝñïí ÷áñáêôçñéóôéêü ôïõ NanoBSD. Áõôü åßíáé êáé ôï ìÝñïò ôçò äéáäéêáóßáò áíÜðôõîçò ôïõ åéäþëïõ NanoBSD ãéá ôï ïðïßï èá îïäÝøåôå Ýíá ìåãÜëï ðïóïóôü ôïõ ÷ñüíïõ ðñïåôïéìáóßáò ôïõ åéäþëïõ. Ç áêüëïõèç åíôïëÞ èá êÜíåé ôï nanobsd.sh íá äéáâÜóåé ôéò ñõèìßóåéò ôïõ áðü ôï áñ÷åßï myconf.nano ðïõ âñßóêåôáé óôï ôñÝ÷ïíôá êáôÜëïãï: &prompt.root; sh nanobsd.sh -c myconf.nano Ç ðñïóáñìïãÞ êáé ðáñáìåôñïðïßçóç ôïõ NanoBSD ãßíåôáé óõíÞèùò ìå äýï ôñüðïõò: ÅðéëïãÝò äéáìüñöùóçò ÐñïóáñìïóìÝíåò óõíáñôÞóåéò ÅðéëïãÝò äéáìüñöùóçò Ïé ñõèìßóåéò ôïõ NanoBSD ìðïñïýí íá ÷ñçóéìïðïéçèïýí ãéá íá ïñéóôïýí ðñïóáñìïóìÝíåò åðéëïãÝò ìåôáãëþôôéóçò êáé åãêáôÜóôáóçò ôïõ &os;. ÁõôÝò ïé åðéëïãÝò åðçñåÜæïõí ôá óôÜäéá buildworld êáé installworld ôïõ NanoBSD, êáèþò êáé Üëëåò åðéëïãÝò ôçò äçìéïõñãßáò ôïõ ôåëéêïý åéäþëïõ. Ìå ôéò êáôÜëëçëåò ñõèìßóåéò ôï NanoBSD ìðïñåß íá ìéêñýíåé áñêåôÜ óå ìÝãåèïò· ìðïñåß íá ÷ùñÝóåé Ýíá ðïëý ìéêñü õðïóýíïëï ôïõ âáóéêïý &os; óå ÷þñï ìéêñüôåñï áðü 64MB. Ìðïñåßôå åðßóçò íá ÷ñçóéìïðïéÞóåôå ôéò åðéëïãÝò ôïõ NanoBSD ãéá íá äçìéïõñãÞóåôå Ýíá åßäùëï ðïõ Ý÷åé ìüíï ôïí ðõñÞíá êáé äõï-ôñßá áñ÷åßá óôï âáóéêü óýóôçìá. Ôï áñ÷åßï ñõèìßóåùí ôïõ NanoBSD ðåñéÝ÷åé åíôïëÝò ïé ïðïßåò ïñßæïõí íÝåò ôéìÝò ãéá êÜðïéá ðñïêáèïñéóìÝíç ìåôáâëçôÞ Þ åðåêôåßíïõí ôéò õðÜñ÷ïõóåò ñõèìßóåéò. Ïé ðéï óçìáíôéêÝò ìåôáâëçôÝò åßíáé ïé åîÞò: NANO_NAME — Ôï üíïìá ôïõ åéäþëïõ NanoBSD ðïõ èá äçìéïõñãçèåß (÷ñçóéìïðïéåßôáé ãéá íá öôéÜîåé ôá ïíüìáôá ôùí êáôÜëïãùí åñãáóßáò). NANO_SRC — Ç äéáäñïìÞ ôïõ äÝíôñïõ ðçãáßïõ êþäéêá ôï ïðïßï èá ÷ñçóéìïðïéçèåß ãéá íá ìåôãëùôôéóôåß ôï åßäùëï. NANO_KERNEL — Ôï üíïìá ôïõ áñ÷åßïõ ñõèìßóåùí ðõñÞíá ôï ïðïßï èá ÷ñçóéìïðïéçèåß ãéá íá ÷ôéóôåß ï ðõñÞíáò ôïõ åéäþëïõ. CONF_BUILD — ÅðéëïãÝò ðïõ ðåñíïýí óôï óôÜäéï buildworld ôçò ìåôáãëþôôéóçò ôïõ &os;. CONF_INSTALL — ÅðéëïãÝò ðïõ ðåñíïýí óôï óôÜäéï installworld ôçò ðñïåôïéìáóßáò ôïõ åéäþëïõ. CONF_WORLD — ÅðéëïãÝò ðïõ ðåñíïýí êáé óôá äýï óôÜäéá ôçò ðñïåôïéìáóßáò ôïõ åéäþëïõ, êáé óôï buildworld êáé óôï installworld. FlashDevice — Ïñßæåé ôïí ôýðï ôïõ ìÝóïõ áðïèÞêåõóçò ðïõ èá ÷ñçóéìïðïéçèåß. Ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò äåßôå ôï áñ÷åßï FlashDevise.sub. ÐñïóáñìïóìÝíåò ÓõíáñôÞóåéò Óôï áñ÷åßï ñýèìéóçò ôïõ NanoBSD ìðïñåß íá ñõèìéóôåß ó÷åäüí êÜèå ëåðôïìÝñåéá ôçò ðñïåôïéìáóßáò ôïõ åéäþëïõ êáé ôïõ ôåëéêïý åéäþëïõ ôï ïðïßï èá äçìéïõñãçèåß. ×ñçóéìïðïéþíôáò ìéêñÝò óõíáñôÞóåéò öëïéïý, ìðïñïýìå íá ñõèìßóïõìå ôá ðÜíôá. Ãéá ðáñÜäåéãìá, ìðïñïýìå íá ôñÝîïõìå äéêÝò ìáò åíôïëÝò ïé ïðïßåò ðáñáìåôñïðïéïýí ôï ôåëéêü åßäùëï ùò åîÞò: cust_foo () ( echo "bar=topless" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo ¸íá ðéï ÷ñÞóéìï ðáñÜäåéãìá óõíÜñôçóçò öëïéïý, ç ïðïßá ñõèìßæåé êÜðïéá ðáñÜìåôñï ôïõ ôåëéêïý åéäþëïõ, åßíáé áõôü ðïõ áêïëïõèåß. Ç óõíÜñôçóç cust_etc_size áëëÜæåé ôçí ðñïåðéëåãìÝíç ôéìÞ ìåãÝèïõò ôïõ êáôáëüãïõ /etc áðü 5MB óå 30MB: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size Ôï óåíÜñéï öëïéïý ðïõ äçìéïõñãåß ôï NanoBSD Ý÷åé ìåñéêÝò Ýôïéìåò óõíáñôÞóåéò öëïéïý ïé ïðïßåò åêôåëïýí ôÝôïéåò åðéðëÝïí ñõèìßóåéò: cust_comconsole — Áðåíåñãïðïéåß ôï &man.getty.8; óôéò êïíóüëåò VGA (ïé óõóêåõÝò /dev/ttyv*) êáé åíåñãïðïéåß ôçí ÷ñÞóç ôçò óåéñéáêÞò èýñáò COM1 ùò êïíóüëá óõóôÞìáôïò. cust_allow_ssh_root — ÅðéôñÝðåé ôçí åßóïäï ôïõ ÷ñÞóôç root ìÝóù ôïõ &man.sshd.8;. cust_install_files — ÅãêáèéóôÜ áñ÷åßá áðü ôïí êáôÜëïãï nanobsd/Files. Óå áõôü ôïí êáôÜëïãï âñßóêïíôáé ìåñéêÜ ÷ñÞóéìá óåíÜñéá öëïéïý ãéá ôç äéá÷åßñéóç åíüò óõóôÞìáôïò NanoBSD. ÐñïóèÝôïíôáò ÐáêÝôá Óå Ýíá åßäùëï NanoBSD ìðïñïýí íá ðñïóôåèïýí êáé Ýôïéìá ðáêÝôá, ðïõ Ý÷ïõí öôéá÷ôåß áðü ðñéí ÷ñçóéìïðïéþíôáò ôç ÓõëëïãÞ ôùí Ports. Ìéá óõíÜñôçóç öëïéïý ìðïñåß íá åãêáôáóôÞóåé Ýîôñá ðáêÝôá ôçí þñá ðïõ ðñïåôïéìÜæåôáé ôï åßäùëï. Ãéá ðáñÜäåéãìá, ç ðáñáêÜôù óõíÜñôçóç èá åãêáôáóôÞóåé óôï åßäùëï üëá ôá ðáêÝôá ðïõ âñßóêïíôáé óôïí êáôÜëïãï /usr/src/tools/tools/nanobsd/packages: install_packages () ( mkdir -p ${NANO_WORLDDIR}/packages cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;' rm -rf ${NANO_WORLDDIR}/packages ) customize_cmd install_packages ÐáñÜäåéãìá Áñ÷åßïõ Ñõèìßóåùí ôïõ NanoBSD ¸íá ðëÞñåò ðáñÜäåéãìá áñ÷åßïõ ñõèìßóåùí ãéá ôï NanoBSD, ìå äéÜöïñåò ñõèìßóåéò ãéá ôç ìåôáãëþôôéóç ôïõ &os; êáé ôçí ðñïåôïéìáóßá ôïõ ôåëéêïý åéäþëïõ, ìðïñåß íá ìïéÜæåé êÜðùò Ýôóé: NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie Åíçìåñþíïíôáò ôï NanoBSD Ç äéáäéêáóßá åíçìÝñùóçò ôïõ NanoBSD åßíáé ó÷åôéêÜ áðëÞ: Äçìéïõñãßá åíüò íÝïõ åéäþëïõ NanoBSD, ìå ôï óõíçèéóìÝíï ôñüðï. ÁíÝâáóìá ôïõ íÝïõ åéäþëïõ óå ìéá á÷ñçóéìïðïßçôç êáôÜôìçóç ìéáò óõóêåõÞò ðïõ ôñÝ÷åé NanoBSD. Ç ðéï óçìáíôéêÞ äéáöïñÜ áõôïý ôïõ óçìåßïõ áðü ôçí áñ÷éêÞ åãêáôÜóôáóç ôïõ NanoBSD åßíáé üôé ôþñá áíôß ôïõ áñ÷åßïõ _.disk.full (ôï ïðïßï ðåñéÝ÷åé ôï åßäùëï åíüò ïëüêëçñïõ äßóêïõ), åãêáôáóôÜèçêå ôï áñ÷åßï _.disk.image (ôï ïðïßï ðåñéÝ÷åé ôï åßäùëï ìéáò ìüíï êáôÜôìçóçò ôïõ äßóêïõ). Êëåßóéìï êáé åðáíåêêßíçóç ôïõ óõóôÞìáôïò áðü ôçí íÝá åãêáôåóôçìÝíç êáôÜôìçóç. Áí üëá ðÜíå êáëÜ, ç áíáâÜèìéóç ôåëåßùóå. Áí ïôéäÞðïôå ðÜåé óôñáâÜ, åðáíåêêéíÞóôå ôç óõóêåõÞ áðü ôçí ðñïçãïýìåíç êáôÜôìçóç (ç ïðïßá ðåñéÝ÷åé ôï ðáëéü åßäùëï, ðïõ ëåéôïõñãåß óùóôÜ). ¸ôóé ìðïñåßôå íá åðáíáöÝñåôå Üìåóá ôï óýóôçìá óå ëåéôïõñãéêÞ êáôÜóôáóç. Äéïñèþóôå ïðïéáäÞðïôå ðñïâëÞìáôá Ý÷åé ôï íÝï åßäùëï, êáé åðáíáëÜâåôå ôçí äéáäéêáóßá. Ãéá íá åãêáôáóôáèåß ôï íÝï åßäùëï óå Ýíá óýóôçìá NanoBSD, ôï ïðïßï Þäç âñßóêåôáé óå ëåéôïõñãßá, ìðïñåß íá ÷ñçóéìïðïéçèåß åßôå ôï óåíÜñéï updatep1 åßôå ôï updatep2. ÁõôÜ ôá äýï óåíÜñéá öëïéïý âñßóêïíôáé óôïí êáôÜëïãï /root. ÁíÜëïãá ìå ôéò õðçñåóßåò ôïõ óõóôÞìáôïò óôï ïðïßï äçìéïõñãåßôáé Ýíá åßäùëï NanoBSD, ìðïñåß íá ìåôáöåñèåß Ýíá íÝï åßäùëï óôï ôåëéêü óýóôçìá ìå äéÜöïñïõò ôñüðïõò: ×ñçóéìïðïéþíôáò ôï &man.ftp.1; Áí óáò åíäéáöÝñåé ç êáëÞ ôá÷ýôçôá ìåôáöïñÜò, ÷ñçóéìïðïéÞóôå ôï FTP ãéá ôç ìåôáöïñÜ ôïõ åéäþëïõ: &prompt.root; ftp myhost get _.disk.image "| sh updatep1" ×ñçóéìïðïéþíôáò ôï &man.ssh.1; Áí óáò åíäéáöÝñåé ç ìåôáöïñÜ ôïõ åéäþëïõ íá ãßíåé ìå áóöáëÞ ôñüðï êáé äåí Ý÷åôå áöáéñÝóåé áðü ôï áñ÷éêü åßäùëï ôï &man.ssh.1;, ðñïôéìÞóôå ôç ìåôáöïñÜ ìÝóù SSH: &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 ×ñçóéìïðïéþíôáò ôï &man.nc.1; Áí ôï óýóôçìá óôï ïðïßï Ý÷åé äçìéïõñãçèåß ôï íÝï åßäùëï ôïõ NanoBSD äåí ôñÝ÷åé ïýôå &man.ftpd.8; ïýôå &man.sshd.8;, ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå Üëëá åñãáëåßá ãéá ôç ìåôáöïñÜ, üðùò ôï &man.nc.1;: Ðñþôá áíïßîôå Ýíá åîõðçñåôçôÞ TCP óôï óýóôçìá ôï ïðïßï èá ðáñÝ÷åé ôï íÝï åßäùëï, êáé ïñßóôå ôï íÝï åßäùëï ùò åßóïäï ãéá ôç ìåôáöïñÜ ðïõ èá ãßíåé áñãüôåñá: myhost&prompt.root; nc -l 2222 < _.disk.image Ðñéí áðü áõôü âåâáéùèåßôå üôé ç èýñá ðïõ ÷ñçóéìïðïéåßôå ãéá ôïí åîõðçñåôçôÞ ìðïñåß íá äå÷èåß åéóåñ÷üìåíåò óõíäÝóåéò áðü ôï óýóôçìá NanoBSD ðñïò ôï óýóôçìá ôïõ åîõðçñåôçôÞ, êáé äåí åìðïäßæåôáé, ãéá ðáñÜäåéãìá, áðü êÜðïéï ôåß÷ïò ðñïóôáóßáò (firewall). Óõíäåèåßôå áðü ôï NanoBSD óôïí åîõðçñåôçôÞ, ï ïðïßïò åßíáé Þäç Ýôïéìïò íá ðáñÝ÷åé ôï íÝï åßäùëï, êáé ôñïöïäïôåßóôå ôï óåíÜñéï öëïéïý updatep1 ìå ôçí Ýîïäï ôïõ åñãáëåßïõ &man.nc.1;: &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/el_GR.ISO8859-7/articles/problem-reports/article.xml b/el_GR.ISO8859-7/articles/problem-reports/article.xml index 5ee2aa9f02..dde89453af 100644 --- a/el_GR.ISO8859-7/articles/problem-reports/article.xml +++ b/el_GR.ISO8859-7/articles/problem-reports/article.xml @@ -1,1055 +1,1057 @@
ÃñÜöïíôáò ÁíáöïñÝò ÐñïâëçìÜôùí ãéá ôï &os; &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Áõôü ôï Üñèñï ðåñéãñÜöåé ðùò íá ìïñöïðïéÞóåôå êáé íá óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò óôçí ïìÜäá áíÜðôõîçò ôïõ &os;. Dag-Erling Smørgrav ÃñÜöôçêå áðü áíáöïñÝò ðñïâëçìÜôùí
ÅéóáãùãÞ Ìéá áðü ôéò ðéï áðïêáñäéùôéêÝò åìðåéñßåò ðïõ ìðïñåß êÜðïéïò íá Ý÷åé óáí ÷ñÞóôçò åíüò ðñïãñÜììáôïò åßíáé íá óôåßëåé ìéá áíáöïñÜ ðñïâëÞìáôïò ìüíï êáé ìüíï ãéá íá äåé íá ôçí êëåßíïõí áðüôïìá ìå ìéá óýíôïìç êáé áðüôïìç åîÞãçóç üðùò ð.÷. áõôü äåí åßíáé ðñüâëçìá Þ ëÜèïò PR. ÊáôÜ ðáñüìïéï ôñüðï, ìéá áðü ôéò ðéï áðïêáñäéùôéêÝò åìðåéñßåò åíüò ðñïãñáììáôéóôÞ åßíáé íá êáôáêëýæåôáé áðü áíáöïñÝò ðñïâëçìÜôùí ðïõ äåí åßíáé ðñáãìáôéêÜ ðñïâëÞìáôá áëëÜ áéôÞóåéò ãéá âïÞèåéá êáé õðïóôÞñéîç Þ áíáöïñÝò ðïõ ðåñéÝ÷ïõí ëßãåò Ýùò êáèüëïõ ðëçñïöïñßåò ó÷åôéêÜ ìå ôï ðñüâëçìá êáé ðùò ìðïñåß êÜðïéïò íá ôï áíáðáñÜãåé. Áõôü ôï êåßìåíï åßíáé ìéá ðñïóðÜèåéá íá ðåñéãñÜøïõìå ðùò ìðïñåßôå íá ãñÜöåôå êáëÝò áíáöïñÝò ðñïâëçìÜôùí. Ôé åßíáé, èá áíáñùôéÝóôå, ìéá êáëÞ áíáöïñÜ ðñïâëÞìáôïò; Ëïéðüí, ãéá íá åßìáóôå áêñéâåßò, ìéá êáëÞ áíáöïñÜ ðñïâëÞìáôïò åßíáé áõôÞ ðïõ ìðïñåß íá áíáëõèåß êáé íá ôç ÷åéñéóôåß êÜðïéïò ãñÞãïñá, ìå áðïôÝëåóìá ôçí éêáíïðïßçóç ôüóï ôïõ áðïóôïëÝá üóï êáé ôïõ ðñïãñáììáôéóôÞ ðïõ ôçí áíÝëáâå. Ôï êõñéüôåñï ìÝñïò áõôïý ôïõ Üñèñïõ áíáöÝñåôáé óôéò áíáöïñÝò ðñïâëçìÜôùí ôïõ &os;. Ôá ðéï ðïëëÜ áðü üóá èá ðïýìå åäþ éó÷ýïõí üìùò êáé ãåíéêüôåñá, ãéá ðïëëÜ Üëëá ðñÜãìáôá. Áõôü ôï Üñèñï åßíáé ïñãáíùìÝíï èåìáôéêÜ êé ü÷é ÷ñïíïëïãéêÜ, ïðüôå åßíáé ðéï óùóôü íá ôï äéáâÜóåôå ïëüêëçñï ðñéí óôåßëåôå êÜðïéá áíáöïñÜ ðñïâëÞìáôïò êáé ü÷é íá ôï ÷ñçóéìïðïéÞóåôå óáí ïäçãü, âÞìá ðñïò âÞìá.
Ðüôå íá óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò ÕðÜñ÷ïõí ðïëëïß ôýðïé ðñïâëçìÜôùí, êáé äåí áîßæïõí üëïé ìéá áíáöïñÜ ðñïâëÞìáôïò. ÖõóéêÜ êáíåßò äåí åßíáé ôÝëåéïò, êáé èá õðÜñîïõí öïñÝò ðïõ èá Ý÷åôå ðåéóôåß üôé âñÞêáôå êÜðïéï ðñüâëçìá óå Ýíá ðñüãñáììá, üôáí óôçí ðñáãìáôéêüôçôá èá Ý÷åôå êáôáëÜâåé ëÜèïò ôç óýíôáîç ìéáò åíôïëÞò Þ èá Ý÷åôå êÜíåé êÜðïéï ôõðïãñáöéêü ëÜèïò óå Ýíá áñ÷åßï ñõèìßóåùí (áí êé áõôü ìåñéêÝò öïñÝò åßíáé åíäåéêôéêü êáêÞò Þ ëåéøÞò ôåêìçñßùóçò Þ áêüìá êáé êáêÞò äéá÷åßñéóçò ëáèþí áðü êÜðïéá åöáñìïãÞ). Áêüìá, õðÜñ÷ïõí ðåñéðôþóåéò ðïõ ôï íá óôåßëåôå êÜðïéá áíáöïñÜ ðñïâëÞìáôïò äåí åßíáé óùóôÞ êßíçóç êáé ôï ìüíï ðïõ ìðïñåß íá ðåôý÷åé åßíáé íá åíï÷ëÞóåé Þ åóÜò Þ ôïõò ðñïãñáììáôéóôÝò. Áðü ôçí Üëëç üìùò, õðÜñ÷ïõí ðåñéðôþóåéò ðïõ ìðïñåß íá åßíáé êáëÞ óêÝøç íá óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò ãéá êÜôé ðïõ äåí åßíáé bug—ìéá âåëôßùóç Þ ìéá áßôçóç ãéá êÜðïéï íÝï ÷áñáêôçñéóôéêü, ãéá ðáñÜäåéãìá. Ôüôå ëïéðüí, ðþò ìðïñåßôå íá áðïöáóßóåôå áí êÜôé åßíáé ðñüâëçìá Þ ü÷é; ¸íáò áðëüò êáíüíáò åßíáé üôé ôï ðñüâëçìÜ óáò äåí åßíáé bug áí ìðïñåß íá åêöñáóôåß óáí åñþôçóç (óõíÞèùò ôçò ìïñöÞò Ðþò êÜíù ôï ×; Þ Ðïý ìðïñþ íá âñù ôï Ø;). Äåí åßíáé ðÜíôá ôüóï Üóðñï-ìáýñï ôá ðñÜãìáôá âÝâáéá, áëëÜ ï êáíüíáò ôçò åñþôçóçò êáëýðôåé ôçí ìåãáëýôåñç ðëåéïøçößá ôùí ðåñéðôþóåùí. Áí áõôü ðïõ øÜ÷íåôå åßíáé êÜðïéá áðÜíôçóç, ßóùò åßíáé êáëýôåñá íá óôåßëåôå ôçí åñþôçóÞ óáò óôçí &a.questions;. ÊÜðïéåò ðåñéðôþóåéò ðïõ ðéèáíüí íá åßíáé êáëÞ éäÝá íá óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò ãéá êÜôé ðïõ äåí åßíáé bug, åßíáé: ÁéôÞóåéò ãéá ìåëëïíôéêÝò âåëôéþóåéò. Åßíáé ãåíéêÜ êáëÞ éäÝá íá äïêéìÜóåôå íá óõæçôÞóåôå ðñþôá ôÝôïéåò éäÝåò óå êÜðïéá ëßóôá çëåêôñïíéêïý ôá÷õäñïìåßïõ ðñéí óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò. Åéäïðïßçóç ãéá åíçìåñùìÝíåò åêäüóåéò ðñïãñáììÜôùí (êõñßùò ports, áëëÜ êáé ìÝñç ôïõ âáóéêïý óõóôÞìáôïò ðïõ óõíôçñïýíôáé áðü ôñßôïõò, üðùò ôï BIND êáé ôá äéÜöïñá GNU åñãáëåßá). ¼ôáí Ýíá ðáêÝôï äåí åßíáé õðü ôçí Üìåóç åðßâëåøç åíüò åðßóçìïõ õðåýèõíïõ (ç ôéìÞ ôïõ MAINTAINER åßíáé ports@FreeBSD.org) ìðïñåß ïðïéïóäÞðïôå committer Þ Üëëïò åíäéáöåñüìåíïò íá äéá÷åéñéóôåß áõôÝò ôéò åéäïðïéÞóåéò. Ìðïñåß, áêüìç, íá óáò æçôçèåß êáé êÜðïéï patch ãéá åíçìåñùèåß ôï ðáêÝôï. Áí Ý÷åôå Þäç öôéÜîåé êÜðïéï patch, êáëü åßíáé íá ôï óõìðåñéëÜâåôå êé áõôü óôçí áíáöïñÜ ðñïâëÞìáôïò ðïõ èá óôåßëåôå. ¸ôóé áõîÜíïíôáé ïé ðéèáíüôçôåò íá ôï äåé êÜðïéïò committer ðïõ åíäéáöÝñåôáé êáé íá ÷åéñéóôåß áõôÞ ôçí áíáöïñÜ ðñïâëÞìáôïò ðéï óýíôïìá. ¼ôáí Ýíá ðáêÝôï åßíáé õðü ôçí åðßâëåøç êÜðïéïõ, óõíÞèùò äåí åßíáé éäéáßôåñá ÷ñÞóéìåò ïé áíáöïñÝò ðïõ áðëþò áíáêïéíþíïõí ìéá êáéíïýñéá Ýêäïóç áðü ôïí óõããñáöÝá ôïõ ðçãáßïõ êþäéêá ôïõ ðáêÝôïõ. ÓõíÞèùò ôï îÝñåé Þäç ï õðåýèõíïò ôïõ ðáêÝôïõ ãéá ôï &os;, Þ Ý÷åé óõíåñãáóôåß ìå ôïí óõããñáöÝá ôïõ ðçãáßïõ êþäéêá ãéá ôç íÝá Ýêäïóç, Þ äïêéìÜæåé ôï ðáêÝôï ãéá íá äåé üôé üëá åîáêïëïõèïýí íá äïõëåýïõí, êïê. ¼ðùò êáé íá '÷åé, åßíáé êáëÞ éäÝá íá áêïëïõèÞóåôå ôç äéáäéêáóßá áðü ôï Porter's Handbook. ¸íá bug ðïõ äåí ìðïñåß êáíåßò íá ôï áíáðáñÜãåé åßíáé ðïëý äýóêïëï íá äéïñèùèåß. Áí ôï bug åìöáíßóôçêå ìéá öïñÜ ìüíï êáé äåí ìðïñåßôå íá ôï áíáðáñÜãåôå åóåßò, êáé öáéíïìåíéêÜ äåí åìöáíßæåôáé óå êáíÝíáí Üëëï, åßíáé ðïëý ìéêñÝò ïé ðéèáíüôçôåò íá ìðïñåß êÜðïéïò ðñïãñáììáôéóôÞò íá ôï áíáêáëýøåé êáé íá êáôáëÜâåé ôß åßíáé áõôü ðïõ ðñïêáëåß ôï ëÜèïò. Áõôü äåí óçìáßíåé ðùò äåí óõìâáßíåé, áëëÜ óçìáßíåé ðùò ç ðéèáíüôçôá íá ïäçãÞóåé ç áíáöïñÜ óáò óôçí ëýóç ôïõ ðñïâëÞìáôïò åßíáé ðÜñá ðïëý ìéêñÞ, êáé ìÜëëïí åßíáé êáëýôåñï íá óôáìáôÞóåôå íá áó÷ïëåßóôå ìå ôï èÝìá. Áêüìá ÷åéñüôåñá, êÜðïéåò öïñÝò áõôïý ôïõ åßäïõò ôá ðñïâëÞìáôá ïöåßëïíôáé óå ðñïâëÞìáôá ôïõ õëéêïý (÷áëáóìÝíïõò óêëçñïýò äßóêïõò Þ åðåîåñãáóôÝò ðïõ õðåñèåñìáßíïíôáé). ÐñÝðåé ðÜíôïôå ðñéí óôÝëíåôå ìéá áíáöïñÜ ðñïâëÞìáôïò, üôáí öõóéêÜ åßíáé äõíáôüí íá ãßíåé êÜôé ôÝôïéï, íá ðñïóðáèåßôå íá áðïêëåßóåôå ôÝôïéåò ðåñéðôþóåéò. Ãéá íá áðïöáóßóåôå óå ðïéÜ êáôçãïñßá ðñïâëçìÜôùí áíÞêåé ç áíáöïñÜ óáò, ðñÝðåé íá Ý÷åôå êáôÜ íïõ ôá äéÜöïñá ìÝñç ôïõ ëïãéóìéêïý áðü ôï ïðïßï áðïôåëåßôáé ôï &os;: Ï êþäéêáò ôïõ âáóéêïý óõóôÞìáôïò ðïõ Ý÷åé ãñáöôåß êáé óõíôçñåßôáé áðü ôçí ïìÜäá ôïõ &os;. Óå áõôÞ ôçí êáôçãïñßá ëïãéóìéêïý áíÞêïõí ï ðõñÞíáò, ç âéâëéïèÞêç ôçò C, êáé ïé ïäçãïß óõóêåõþí (êáôçãïñßá kern), ôá åñãáëåßá ãñáììÞò åíôïëþí ôïõ âáóéêïý óõóôÞìáôïò (êáôçãïñßá bin), ïé óåëßäåò âïÞèåéáò êáé ç ôåêìçñßùóç ôïõ &os; (êáôçãïñßá docs), êáé ï éóôüôïðïò ôïõ &os; (êáôçãïñßá www). ¼ëá ôá ðñïâëÞìáôá ìå êÜðïéï áðü áõôÜ ôá ìÝñç ôïõ &os; ðñÝðåé íá áíáöÝñïíôáé óôçí ïìÜäá áíÜðôõîçò ôïõ &os;. Ï êþäéêáò ôïõ âáóéêïý óõóôÞìáôïò ðïõ Ý÷åé ãñáöôåß êáé óõíôçñåßôáé áðü ôñßôïõò áëëÜ Ý÷åé åíóùìáôùèåß óôï &os; êé Ý÷åé ðñïóáñìïóôåß óå áõôü. Ðáñáäåßãìáôá ôÝôïéùí ðñïãñáììÜôùí åßíáé ôï bind, ï ìåôáãëùôôéóôÞò &man.gcc.1; êáé ôï &man.sendmail.8;. Ôá ðåñéóóüôåñá ðñïâëÞìáôá ìå êÜðïéï áðü áõôÜ ôá ðñïãñÜììáôá ðñÝðåé íá áíáöÝñïíôáé óôçí ïìÜäá áíÜðôõîçò ôïõ &os;. Óå ìåñéêÝò ðåñéðôþóåéò ìðïñåß íá ÷ñåéáóôåß íá áíáöåñèïýí óôïõò áñ÷éêïýò óõããñáöåßò ôïõ áíôßóôïé÷ïõ ðñïãñÜììáôïò· åéäéêÜ áí ôï ðñüâëçìá äåí åìöáíßæåôáé ìüíï óôï &os;. Ïé ðéï óõíçèéóìÝíåò êáôçãïñßåò ãéá ôéò áíáöïñÝò ðñïâëçìÜôùí ó÷åôéêÜ ìå áõôÜ ôá ðñïãñÜììáôá åßíáé ïé bin êáé gnu. ¶ëëåò åöáñìïãÝò, ïé ïðïßåò äåí åßíáé ìÝñïò ôïõ âáóéêïý óõóôÞìáôïò ôïõ &os;, áëëÜ õðïóôçñßæïíôáé ùò ìÝñïò ôçò ÓõëëïãÞò ôùí Ports (êáôçãïñßá ports). Ç óõíôñéðôéêÞ ðëåéïøçößá áõôþí ôùí åöáñìïãþí äåí Ý÷åé ãñáöôåß áðü ôçí ïìÜäá ôïõ &os;. Áõôü ðïõ ðáñÝ÷åôáé áðü ôï &os; åßíáé áðëÜ ç äõíáôüôçôá íá åãêáôáóôáèïýí áõôÝò ïé åöáñìïãÝò (ìå ìåñéêÝò ÷ñÞóéìåò áëëÜ üóï ôï äõíáôüí ëéãüôåñåò Þ ìéêñüôåñåò óå Ýêôáóç áëëáãÝò) óå Ýíá óýóôçìá &os;. Ïðüôå ðñÝðåé íá áíáöÝñåôå ïðïéïäÞðïôå ðñüâëçìá Ý÷ïõí áõôÝò ïé åöáñìïãÝò óôçí ïìÜäá ôïõ &os; êõñßùò üôáí ðéóôåýåôå üôé ôï ðñüâëçìá åìöáíßæåôáé ìüíï óôï &os;. Óå áíôßèåôç ðåñßðôùóç åßíáé êáëýôåñç éäÝá íá áíáöÝñåôáé ôï ðñüâëçìá óôïí áñ÷éêü óõããñáöÝá ôïõ áíôßóôïé÷ïõ ðñïãñÜììáôïò. ÔÝëïò, åëÝãîôå üôé ç áíáöïñÜ ðïõ óôÝëíåôå áöïñÜ Ýíá ðñüâëçìá ôï ïðïßï õðÜñ÷åé áêüìá. ÌåñéêÝò öïñÝò åßíáé êÜðùò åíï÷ëçôéêü ãéá Ýíáí ðñïãñáììáôéóôÞ íá ðáßñíåé åéäïðïéÞóåéò ãéá Ýíá ðñüâëçìá ôï ïðïßï Ý÷åé Þäç äéïñèùèåß. Áí ôï ðñüâëçìá ðïõ áíôéìåôùðßæåôå áöïñÜ ôï âáóéêü óýóôçìá êáé äåí Ý÷åôå åíçìåñùèåß Þäç ãéá ôéò ôåëåõôáßåò åêäüóåéò ôïõ &os;, äéáâÜóôå ôï ôìÞìá åêäüóåéò ôïõ &os; óôç Ëßóôá Óõ÷íþí ÅñùôÞóåùí ôïõ &os;. Ç ïìÜäá ôïõ &os; ìðïñåß íá óõíôçñåß ìüíï Ýíá ïñéóìÝíï (ìéêñü) áñéèìü êëÜäùí áíÜðôõîçò ôïõ &os;. Äå ìðïñåß íá äéïñèþíåé ðñïâëÞìáôá ãéá ïðïéáäÞðïôå Ýêäïóç ôïõ &os;. Ïðüôå áí áíáöÝñåôå üôé Ý÷åôå ðñüâëçìá ìå ìéá ðïëý ðáëéÜ Ýêäïóç ôïõ óõóôÞìáôïò, ç ðéï ðéèáíÞ áðÜíôçóç ðïõ èá ðÜñåôå èá åßíáé íá áíáâáèìßóåôå ôï óýóôçìÜ óáò óå ìéá Ýêäïóç ðïõ õðïóôçñßæåôáé åðßóçìá áðü ôçí ïìÜäá ôïõ &os; êáé íá êÜíåôå äïêéìÝò ãéá íá äåßôå áí ôï ðñüâëçìá Ý÷åé Þäç äéïñèùèåß Þ õðÜñ÷åé áêüìç. Ç ÏìÜäá ÁóöÜëåéáò ôïõ &os; óõíôçñåß êáé åíçìåñþíåé ìéá ëßóôá åêäüóåùí ôïõ &os; ðïõ õðïóôçñßæïíôáé åðßóçìá. Áí ôï ðñüâëçìá ðïõ áíôéìåôùðßæåôå áöïñÜ Ýíá ðáêÝôï, ôüôå ðñÝðåé êáô' áñ÷Þí íá åíçìåñþóåôå ôá Ports óáò óôçí ôåëåõôáßá Ýêäïóç ôçò ÓõëëïãÞò ôùí Ports êáé íá äåßôå áí ôï ðñüâëçìá õðÜñ÷åé áêüìá. Ïé åöáñìïãÝò ðïõ ðåñéÝ÷ïíôáé óôç ÓõëëïãÞ ôùí Ports áëëÜæïõí ðïëý ãñÞãïñá. Ëüãù ôïõ ãñÞãïñïõ ñõèìïý ìå ôïí ïðïßï åíçìåñþíïíôáé åßíáé ðñáêôéêÜ áäýíáôïí ãéá ôçí ïìÜäá ôïõ &os; íá õðïóôçñßîåé ïðïéáäÞðïôå ðáëéüôåñç Ýêäïóç ôùí Ports. Áõôü óçìáßíåé üôé ôá ðñïâëÞìáôá ðïõ Ý÷ïõí ïé ðáëéÝò åêäüóåéò êÜðïéùí ðñïãñáììÜôùí áðëÜ äå ãßíåôáé íá äéïñèùèïýí.
Ðñïåôïéìáóßá Åßíáé êáëÞ éäÝá íá êÜíåôå ðÜíôá ìéá ìéêñÞ Ýñåõíá ðñéí íá óôåßëåôå êÜðïéá áíáöïñÜ ðñïâëÞìáôïò. Ìðïñåß ôï ðñüâëçìÜ óáò íá ôï Ý÷åé Þäç áíáöÝñåé êáé êÜðïéïò Üëëïò. Ìðïñåß íá åßíáé èÝìá óõæçôÞóåùí óå êÜðïéá ëßóôá çëåêôñïíéêïý ôá÷õäñïìåßïõ Þ íá Þôáí ðñüóöáôá. Ìðïñåß áêüìá, íá åßíáé Þäç äéïñèùìÝíï ôï ðñüâëçìá óå êÜðïéá Ýêäïóç íåþôåñç áðü áõôÞ ðïõ ôñÝ÷åôå. ÐñÝðåé ëïéðüí íá åëÝã÷åôå üëá ôá ðñïöáíÞ óçìåßá, ðñéí íá óôåßëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò. Ãéá ôï &os; áõôü óçìáßíåé: Ôçí ëßóôá ìå ôéò ðéï óõ÷íÝò åñùôÞóåéò (FAQ) ãéá ôï &os;. Ç ëßóôá áõôÞ ðáñÝ÷åé áðáíôÞóåéò óå ìéá ìåãÜëç ðïéêéëßá åñùôÞóåùí, üðùò áõôÝò ðïõ áöïñïýí ôï õëéêü, ôéò åöáñìïãÝò êáé ôéò ñõèìßóåéò ôïõ ðõñÞíá. Ïé ëßóôåò çëåêôñïíéêïý ôá÷õäñïìåßïõ—áí äåí Ý÷åôå ãñáöôåß óå êÜðïéá áðü áõôÝò, ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôï áñ÷åßï óôéò óåëßäåò ôïõ &os; ãéá íá áíáæçôÞóåôå ðëçñïöïñßåò ó÷åôéêÝò ìå ôï ðñüâëçìá. Áí ôï ðñüâëçìÜ óáò äåí Ý÷åé óõæçôçèåß óôéò ëßóôåò åßíáé, ãåíéêÜ, êáëÞ éäÝá íá óôåßëåôå Ýíá ãñÜììá óôéò ëßóôåò çëåêôñïíéêïý ôá÷õäñïìåßïõ êáé íá ðåñéìÝíåôå ëßãåò ìÝñåò ìÞðùò êÜðïéïò âñåé êÜôé ðïõ åóåßò äåí ðñïóÝîáôå. ÐñïáéñåôéêÜ, üëï ôï äßêôõï. ×ñçóéìïðïéÞóôå ôçí áãáðçìÝíç óáò ìç÷áíÞ áíáæÞôçóçò ãéá íá âñåßôå ðëçñïöïñßåò ó÷åôéêÜ ìå ôï ðñüâëçìá. ¸ôóé ìðïñåß íá âñåßôå áêüìç êáé áíáöïñÝò áðü ëßóôåò çëåêôñïíéêïý ôá÷õäñïìåßïõ Þ ïìÜäåò óõæçôÞóåùí ðïõ äåí îÝñáôå üôé õðÜñ÷ïõí Þ äåí óêåöôÞêáôå íá øÜîåôå. ¾óôåñá ìðïñåßôå íá áíáæçôÞóåôå ó÷åôéêÝò áíáöïñÝò óôçí âÜóç áíáöïñþí ôïõ &os; (GNATS). Áí ôï ðñüâëçìÜ óáò äåí åßíáé ðñüóöáôï Þ áñêåôÜ ðåñßåñãï, åßíáé ðïëý ðéèáíüí íá Ý÷åé Þäç óôåßëåé êÜðïéïò Üëëïò ìéá áíáöïñÜ. Ôï ðéï óçìáíôéêü áðü üëá üìùò åßíáé íá äåßôå ìÞðùò ç ôåêìçñßùóç ôïõ &os; ðåñéÝ÷åé êÜðïéá ëýóç óôï ðñüâëçìÜ óáò. Ãéá ôï âáóéêü óýóôçìá ôïõ &os; ðñÝðåé íá ìåëåôÞóåôå ðñïóåêôéêÜ ôéò ïäçãßåò ðïõ ðåñéÝ÷åé ôï áñ÷åßï /usr/src/UPDATING óôï óýóôçìÜ óáò Þ áõôÝò ðïõ ðåñéÝ÷åé ç ôåëåõôáßá Ýêäïóç ôïõ áñ÷åßïõ, ç ïðïßá åßíáé äéáèÝóéìç óôç äéåýèõíóç: . (Áõôü ôï áñ÷åßï ðåñéÝ÷åé êñßóéìåò ðëçñïöïñßåò ãéá áíáâÜèìéóç áðü ìéá Ýêäïóç ôïõ &os; óå êÜðïéá Üëëç—åéäéêÜ ãéá ôéò åêäüóåéò ôïõ &os.current;). Áí ôï ðñüâëçìá åìöáíßæåôáé óå êÜôé ðïõ åãêáôáóôÜèçêå ùò ìÝñïò ôçò ÓõëëïãÞò ôùí Ports ôïõ &os;, ôá áíôßóôïé÷á áñ÷åßá ìå ðëçñïöïñßåò åßíáé ôá: /usr/ports/UPDATING (ãéá ðëçñïöïñßåò ó÷åôéêÜ ìå óõãêåêñéìÝíá ðáêÝôá), /usr/ports/CHANGES (ãéá áëëáãÝò ðïõ áöïñïýí üëç ôçí ÓõëëïãÞ ôùí Ports). Êé áõôÜ ôá áñ÷åßá åßíáé äéáèÝóéìá ìÝóù CVSweb, óôéò äéåõèýíóåéò êáé áíôßóôïé÷á.
ÃñÜöïíôáò áíáöïñÝò ðñïâëçìÜôùí Ôþñá ðïõ Ý÷åôå áðïöáóßóåé üôé áîßæåé íá ãñÜøåôå êÜðïéá áíáöïñÜ ðñïâëÞìáôïò, êáé üôé üíôùò åßíáé êÜðïéï ðñüâëçìá ôïõ &os; áõôü ðïõ èÝëåôå íá ðåñéãñÜøåôå, åßíáé þñá íá ãñÜøåôå ôçí áíáöïñÜ. Ðñéí ìðïýìå óå ëåðôïìÝñåéåò ó÷åôéêÜ ìå ôï ðñüãñáììá ðïõ ÷ñçóéìïðïéåßôáé ãéá íá ãñÜöïíôáé êáé íá óôÝëíïíôáé ïé áíáöïñÝò ðñïâëçìÜôùí, áò äïýìå ìåñéêÜ êüëðá ðïõ èá óáò âïçèÞóïõí íá óôåßëåôå ÷ñÞóéìåò áíáöïñÝò.
Êüëðá ãéá íá ãñÜöåôå ÷ñÞóéìåò áíáöïñÝò ðñïâëçìÜôùí Ìçí áöÞíåôå êåíÞ ôçí ãñáììÞ Synopsis. Ïé áíáöïñÝò ðñïâëçìÜôùí óôÝëíïíôáé óå ìéá ëßóôá çëåêôñïíéêïý ôá÷õäñïìåßïõ, ç ïðïßá ðñïùèåß ôçí áíáöïñÜ óáò óå áíèñþðïõò óå üëï ôïí êüóìï (üðïõ ôï êåßìåíï ôçò ãñáììÞò Synopsis ÷ñçóéìïðïéåßôáé ùò èÝìá ôïõ ìçíýìáôïò), áëëÜ êáé óå ìéá âÜóç äåäïìÝíùí. ÏðïéïóäÞðïôå ðñïóðáèÞóåé áñãüôåñá íá äåé ìéá ëßóôá ìå ôéò áíáöïñÝò ðñïâëçìÜôùí ìðïñåß íá áãíïÞóåé åíôåëþò ôçí áíáöïñÜ óáò áí äåí Ý÷åé èÝìá. Íá Ý÷åôå êáôá íïõ óáò üôé ïé áíáöïñÝò ìÝíïõí óå áõôÞ ôç âÜóç ìÝ÷ñé êÜðïéïò íá áó÷ïëçèåß ìáæß ôïõò êáé íá ôéò êëåßóåé. Ìéá áíþíõìç áíáöïñÜ, ÷ùñßò êáíÝíá èÝìá, óõíÞèùò, ÷Üíåôáé óôï èüñõâï. Ìç ÷ñçóéìïðïéåßôå áôáßñéáóôåò ðåñéãñáöÝò óôç ãñáììÞ Synopsis. Ìçí èåùñåßôå üôé ïðïéïóäÞðïôå äéáâÜóåé ôçí áíáöïñÜ óáò èá Ý÷åé êáé ôï êáôÜëëçëï õðüâáèñï ãéá íá êáôáëÜâåé ôé ëÝôå, ïðüôå üóï ðåñéóóüôåñåò ëåðôïìÝñåéåò óõìðåñéëÜâåôå ôüóï êáëýôåñá åßíáé. Ãéá ðáñÜäåéãìá, ç áíáöïñÜ êáé ôï ðñüâëçìá ðïõ óôÝëíåôå ðïéï ìÝñïò ôïõ óõóôÞìáôüò óáò áöïñÜ; Ôï ðñüâëçìá åìöáíßæåôáé ìüíï êáôÜ ôç äéÜñêåéá ôçò åãêáôÜóôáóçò Þ êáé ìåôÜ; Ãéá ðáñÜäåéãìá, äåßôå ðüóï ðéï êáëÜ åßíáé áí áíôß íá ãñÜøåôå Synopsis: portupgrade is broken ãßíåôå ðéï ðåñéãñáöéêïß Synopsis: port sysutils/portupgrade coredumps on -current. (ÅéäéêÜ óôçí ðåñßðôùóç ôùí ports åßíáé ðïëý ÷ñÞóéìï íá õðÜñ÷åé ôüóï ç êáôçãïñßá üóï êáé ôï üíïìá ôïõ port óôç ãñáììÞ ôçò óýíïøçò). Áí Ý÷åôå êÜðïéï patch, ðåßôå ôï. Åßíáé ðïëý ððéï ðéèáíü íá áó÷ïëçèåß êÜðïéïò ìå ìéá áíáöïñÜ ðñïâëÞìáôïò ðïõ ðåñéëáìâÜíåé êáé êÜðïéï patch áðü üôé ìå êÜðïéá ðïõ áðëÜ áíáöÝñåé ôï ðñüâëçìá. Áí ç áíáöïñÜ óáò ðåñéëáìâÜíåé êÜðïéï patch ôüôå åßíáé êáëÞ éäÝá íá ðñïóèÝóåôå ôï êåßìåíï [patch] óôçí áñ÷Þ ôçò Synopsis óáò. (Ðáñüëï ðïõ äåí åßíáé õðï÷ñåùôéêü íá ÷ñçóéìïðïéÞóåôå áêñéâþò áõôü ôï êåßìåíï, óõíÞèùò áõôü ÷ñçóéìïðïéïýí ïé ðåñéóóüôåñïé ìÝ÷ñé óÞìåñá.) Áí åßóôå åóåßò ï õðåýèõíïò ãéá ôç óõíôÞñçóç êÜðïéïõ ìÝñïõò ôïõ êþäéêá, ðåßôå ôï. Áí åßíáé äéêÞ óáò åõèýíç ç óõíôÞñçóç êÜðïéïõ ìÝñïõò ôïõ êþäéêá ôïõ &os; (ãéá ðáñÜäåéãìá åßóôå ï MAINTAINER êÜðïéïõ port), äåí åßíáé Üó÷çìç éäÝá íá ðñïóèÝóåôå ôï êåßìåíï [maintainer update] óôçí áñ÷Þ ôçò Synopsis óáò. ÏðùóäÞðïôå üìùò íá èõìçèåßôå íá èÝóåôå ôçí ôéìÞ ôïõ Class ôçò áíáöïñÜò óáò óå maintainer-update. ¸ôóé üðïéï ìÝëïò ôçò ïìÜäáò áíÜðôõîçò áó÷ïëçèåß ìå ôçí áíáöïñÜ óáò äå èá ÷ñåéÜæåôáé íá åëÝãîåé áí üíôùò åóåßò åßóôå ï maintainer. Íá åßóôå áêñéâåßò & óõãêåêñéìÝíïé. ¼óï ðåñéóóüôåñåò ðëçñïöïñßåò ãñÜøåôå ó÷åôéêÜ ìå ôï ðñüâëçìá ðïõ áíôéìåôùðßæåôå, ôüóï áõîÜíïíôáé ïé ðéèáíüôçôåò íá ðÜñåôå ìéá ÷ñÞóéìç êáé óùóôÞ áðÜíôçóç. ÓõìðåñéëÜâåôå ôçí Ýêäïóç ôïõ &os; ðïõ ÷ñçóéìïðïéåßôå (ðáñáêÜôù èá äïýìå ðùò õðÜñ÷åé óõãêåêñéìÝíï ìÝñïò ðïõ ìðïñåßôå íá ôï ãñÜøåôå áõôü) êáé ðïéáò áñ÷éôåêôïíéêÞò åßíáé ôï ìç÷ÜíçìÜ óáò. Åßíáé éäéáßôåñá ÷ñÞóéìï íá ãñÜøåôå áí ôñÝ÷åôå êÜðïéá åðßóçìç Ýêäïóç (ð.÷. áðü Ýíá CDROM Þ êÜðïéá ðïõ êáôåâÜóáôå áðü ôï äßêôõï) Þ áí ôï óýóôçìá óáò ôï åíçìåñþíåôå ìå ôï &man.cvsup.1; (êé áí íáé, ðüóï ðñüóöáôá ôï åíçìåñþóáôå). Áí ÷ñçóéìïðïéåßôå ôï &os.current;, áõôü åßíáé êáé ôï ðñþôï ðñÜãìá ðïõ èá óáò ñùôÞóåé êÜðïéïò, åðåéäÞ ïé áëëáãÝò êáé ïé äéïñèþóåéò (åéäéêÜ ãéá ôá óçìáíôéêÜ ðñïâëÞìáôá) ãßíïíôáé, ãåíéêÜ, ðïëý ãñÞãïñá êáé óõ÷íÜ. Ïé ÷ñÞóôåò ôïõ &os.current; ðñÝðåé íá ôéò ðáñáêïëïõèïýí ìå ðñïóï÷Þ êáé íá åíçìåñþíïõí óõ÷íÜ ôï óýóôçìÜ ôïõò. ÓõìðåñéëÜâåôå êáé ôéò ñõèìßóåéò ðïõ ðåñéÝ÷åé ôï áñ÷åßï make.conf óôï óýóôçìÜ óáò. Óçìåéþóôå ðùò ç ÷ñÞóç ôçò åðéëïãÞò -O2 ôïõ &man.gcc.1; åßíáé ãíùóôÞ ðçãÞ ðñïâëçìÜôùí. Ðáñüëï ðïõ ç ïìÜäá áíÜðôõîçò ôïõ &os; äåí èá 'ëåãå ü÷é óå patches ðïõ íá äéïñèþíïõí áõôÜ ôá ðñïâëÞìáôá åßíáé ãåíéêÜ áðñüèõìç óôï íá áíáæçôÜ ôéò áéôßåò ôÝôïéùí ðñïâëçìÜôùí åðåéäÞ äåí Ý÷åé ôï ÷ñüíï Þ ôï áíèñþðéíï äõíáìéêü íá ôï êÜíåé. Áí ôá ðñïâëÞìáôÜ óáò ïöåßëïíôáé óå áõôü ôï ðñüâëçìá ôùí optimizations ìðïñåß íá óáò áðáíôÞóïõí üôé äåí õðïóôçñßæåôáé áõôüò ï ôñüðïò ÷ñÞóçò ôïõ &os;. Áí ôï ðñüâëçìÜ óáò áöïñÜ ôïí ðõñÞíá, ôüôå íá åßóôå ðñïåôïéìáóìÝíïé íá äþóåôå êáé ôéò åîÞò Ýîôñá ðëçñïöïñßåò. (Äåí åßíáé áíÜãêç íá ôéò óõìðåñéëÜâåôå Ýôóé êé áëëéþò, áöïý ôï ìüíï ðïõ èá êáôáöÝñåôå åßíáé íá áõîÞóåôå ÷ùñßò ëüãï ôï ÷þñï ðïõ áðáéôåß ç âÜóç ðñïâëçìÜôùí óôï äßóêï, áëëÜ äåí åßíáé êáêÞ éäÝá íá óõìðåñéëÜâåôå ìüíï ôá ìÝñç ðïõ èåùñåßôå ó÷åôéêÜ): ôéò ñõèìßóåéò ôïõ ðõñÞíá óáò (êáé ðïéÝò óõóêåõÝò Ý÷åôå åãêáôåóôçìÝíåò óôï ìç÷ÜíçìÜ óáò) áí Ý÷åôå åíåñãïðïéçìÝíåò åðéëïãÝò debugging óôïí ðõñÞíá óáò (üðùò ð.÷. ôçí åðéëïãÞ WITNESS) êé áí íáé áí ôï ðñüâëçìá óõíå÷ßæåé íá õðÜñ÷åé áöáéñþíôáò áõôÝò ôéò åðéëïãÝò Ýíá backtrace, áí ìðïñÝóáôå íá êáôáãñÜøåôå êÜðïéï áí Ý÷åôå äéáâÜóåé ðñïóåêôéêÜ ôï áñ÷åßï src/UPDATING êé áí ôï ðñüâëçìÜ óáò áíáöÝñåôáé Þ ü÷é óå áõôü (åßíáé óßãïõñï üôé êÜðïéïò èá óáò ñùôÞóåé ãé áõôü) áí ìðïñåßôå íá ôñÝîåôå êÜðïéï Üëëï ðõñÞíá óáí ðñïóùñéíÞ ëýóç (Ýôóé áðïêëåßïíôáé ðñïâëÞìáôá ìå ôï õëéêü, üðùò äßóêïé ðïõ Üñ÷éóáí íá ÷áëÜíå Þ åðåîåñãáóôÝò ðïõ õðåñèåñìáßíïíôáé, ðïõ ìðïñåß íá óáò ìðåñäÝøïõí êáé íá íïìßóåôå üôé Ý÷åé ðñüâëçìá ï ðõñÞíáò) Áí Ý÷åôå ðñüâëçìá ìå êÜðïéï port, ôüôå íá Ý÷åôå äéáèÝóéìåò ôéò åîÞò ðëçñïöïñßåò. (Äåí åßíáé áíÜãêç íá ôéò óõìðåñéëÜâåôå Ýôóé êé áëëéþò, áëëÜ äåí åßíáé êáêÞ éäÝá íá óõìðåñéëÜâåôå ìüíï ôá ìÝñç ðïõ èåùñåßôå ó÷åôéêÜ): ðïéá ports Ý÷åôå åãêáôáóôÞóåé ìåôáâëçôÝò ôïõ ðåñéâÜëëïíôïò ðïõ ìðïñåß íá åðçñåÜæïõí ôéò ðñïêáèïñéóìÝíåò ñõèìßóåéò ôïõ óõóôÞìáôïò óôï áñ÷åßï bsd.port.mk, üðùò ð.÷. ç ìåôáâëçôÞ ðåñéâÜëëïíôïò PORTSDIR áí Ý÷åôå äéáâÜóåé ôï áñ÷åßï ports/UPDATING êé áí ôï ðñüâëçìÜ óáò áíáöÝñåôáé Þ ü÷é óå áõôü (åßíáé óßãïõñï üôé êÜðïéïò èá óáò ñùôÞóåé ãé áõôü) Áðïöýãåôå ôéò áóáöåßò áéôÞóåéò ãéá íÝá ÷áñáêôçñéóôéêÜ. Ïé áíáöïñÝò ôçò ìïñöÞò óô' áëÞèåéá, êÜðïéïò ðñÝðåé íá õëïðïéÞóåé êÜôé ðïõ íá êÜíåé ôï ôÜäå Þ ôï äåßíá äåí åßíáé ðïëý óßãïõñï üôé èá ôý÷ïõí êáëýôåñçò áíôéìåôþðéóçò áðü ôéò áíáöïñÝò ðïõ ðåñéãñÜöïõí óõãêåêñéìÝíåò áëëáãÝò. Íá èõìÜóôå üôé ï êþäéêáò åßíáé äéáèÝóéìïò óå üëïõò, ïðüôå áí èÝëåôå êÜðïéï íÝï ÷áñáêôçñéóôéêü ï êáëýôåñïò ôñüðïò íá ôï äåßôå íá õëïðïéåßôáé óáí ìÝñïò ôïõ &os; åßíáé íá ôï öôéÜîåôå åóåßò. ÐïëëÝò öïñÝò ìÜëéóôá åßíáé ðñïôéìüôåñï íá ñùôÞóåôå óôçí freebsd-questions ðáñÜ íá äçìéïõñãÞóåôå ìéá êáéíïýñéá åããñáöÞ óôç âÜóç áíáöïñþí ðñïâëçìÜôùí. Óéãïõñåõôåßôå üôé äåí Ý÷åé óôåßëåé Þäç êÜðïéïò Üëëïò ìéá ðáñüìïéá áíáöïñÜ. Ðáñüëï ðïõ ôï Ý÷ïõìå îáíáðåß áõôü, áîßæåé íá ôï áíáöÝñïõìå ðÜëé åäþ. ×ñåéÜæåôáé ìüíï Ýíá ëåðôü ãéá íá áíïßîåôå Ýíá öõëëïìåôñçôÞ êáé íá ÷ñçóéìïðïéÞóåôå ôç ìç÷áíÞ áíáæÞôçóçò áíáöïñþí ðñïâëçìÜôùí ôïõ &os; óôç äéåýèõíóç . (ÖõóéêÜ, üëïé Ý÷ïõìå îå÷Üóåé êÜðïéåò öïñÝò íá ôï êÜíïõìå áõôü.) Áðïöýãåôå ôéò åðéêßíäõíåò áéôÞóåéò. Áí ç áíáöïñÜ óáò åðçñåÜæåé Ýíá ìÝñïò ôïõ êþäéêá ãéá ôï ïðïßï õðÞñîáí äéáöùíßåò óôï ðáñåëèüí, ìÜëëïí ðñÝðåé åêôüò áðü ôá patches ðïõ èá åôïéìÜóåôå íá åßóôå ðñïåôïéìáóìÝíïé êáé ãéá íá äéêéïëïãÞóåôå ôéò áëëáãÝò óáò, åîçãþíôáò ãéáôß åßíáé Óùóôü íá Ãßíïõí. ¼ðùò åßðáìå êáé ðéï ðñéí, ìéá ðñïóåêôéêÞ áíáæÞôçóç óôá áñ÷åßá ôùí ëéóôþí çëåêôñïíéêïý ôá÷õäñïìåßïõ óôç äéåýèõíóç åßíáé ðÜíôá êáëüò ôñüðïò íá ðñïåôïéìáóôåßôå ãéá ôÝôïéåò êáôáóôÜóåéò. Íá åßóôå åõãåíéêïß. Ó÷åäüí üëïé üóïé ðñüêåéôáé íá áó÷ïëçèïýí ìå ôçí áíáöïñÜ óáò ãéá êÜðïéï ðñüâëçìá åßíáé åèåëïíôÝò. Óå êáíÝíáí äåí áñÝóåé íá ôïõò ëÝíå ôé íá êÜíïõí üôáí Þäç êÜíïõí ôï ßäéï ðñÜãìá åäþ êáé êáéñü ãéá ëüãïõò ðïõ äåí Ý÷ïõí ó÷Ýóç ìå ïéêïíïìéêÝò áðïëáâÝò. Åßíáé êáëü íá ôï Ý÷åôå êáôÜ íïõ áõôü üôáí áó÷ïëåßóôå ìå ðñïãñÜììáôá Áíïé÷ôïý Ëïãéóìéêïý Þ Ëïãéóìéêïý Åëåýèåñïõ Êþäéêá.
Ðñéí áñ÷ßóåôå Áí ÷ñçóéìïðïéåßôå ôï ðñüãñáììá &man.send-pr.1;, óéãïõñåõôåßôå üôé ç ìåôáâëçôÞ ðåñéâÜëëïíôïò VISUAL (Þ ç ìåôáâëçôÞ ðåñéâÜëëïíôïò EDITOR áí äåí åßíáé ïñéóìÝíç ç VISUAL) Ý÷åé êÜðïéá ëïãéêÞ ôéìÞ. ÅëÝãîôå åðßóçò üôé ç áðïóôïëÞ çëåêôñïíéêÞò áëëçëïãñáößáò ëåéôïõñãåß óùóôÜ. Ôï ðñüãñáììá &man.send-pr.1; ÷ñçóéìïðïéåß ìçíýìáôá çëåêôñïíéêÞò áëëçëïãñáößáò ãéá ôçí áðïóôïëÞ êáé ôçí ðáñáêïëïýèçóç ôùí áíáöïñþí ðñïâëçìÜôùí. Áí äå ìðïñåßôå íá óôåßëåôå ìçíýìáôá çëåêôñïíéêÞò áëëçëïãñáößáò áðü ôï ìç÷Üíçìá óôï ïðïßï ÷ñçóéìïðïéåßôå ôï ðñüãñáììá &man.send-pr.1;, ôï ìÞíõìÜ óáò êáé ç áíáöïñÜ äå èá öôÜóåé ðïôÝ óôç âÜóç áíáöïñþí ðñïâëçìÜôùí ôïõ &os;. Ãéá ëåðôïìÝñåéåò ó÷åôéêÜ ìå ôç ñýèìéóç ôçò çëåêôñïíéêÞò áëëçëïãñáößáò óôï &os; äåßôå ôï êåöÜëáéï ðåñß ÇëåêôñïíéêÞò Áëëçëïãñáößáò óôï Åã÷åéñßäéï ôïõ &os; óôç äéåýèõíóç . Óéãïõñåõôåßôå üôé ôï ðñüãñáììá áëëçëïãñáößáò ôï ïðïßï ÷ñçóéìïðïéåßôå äåí èá áëëÜîåé ïýôå ôï ðåñéå÷üìåíï ïýôå ôç ìïñöÞ ôïõ êåéìÝíïõ ðïõ óôÝëíåôå ðñéí áõôü öôÜóåé óôï óýóôçìá GNATS ôïõ &os;. Ðéï óõãêåêñéìÝíá, áí ôï ðñüãñáììá áëëçëïãñáößáò óáò áðïöáóßæåé áõôüìáôá ãéá ôï ìÞêïò êÜèå ãñáììÞò êåéìÝíïõ, áëëÜæåé ôïõò ÷áñáêôÞñåò óôçëïèÝôç ìå êåíÜ Þ åðåìâáßíåé óôïõò ÷áñáêôÞñåò áëëáãÞò ãñáììÞò, ôüôå êÜèå patch ðïõ óôÝëíåôå ìðïñåß íá åßíáé åíôåëþò Ü÷ñçóôï. Áðü ôçí Üëëç, óôá ðåäßá ôçò áíáöïñÜò ðñïâëÞìáôïò ôá ïðïßá ðåñéÝ÷ïõí áðëü êåßìåíï åßíáé ðéï âïëéêü íá Ý÷åé ðåñßðïõ 70 óôÞëåò ç êÜèå ãñáììÞ. ¸ôóé äéáâÜæåôáé ðéï åýêïëá ôï êåßìåíï ôçò áíáöïñÜò ìÝóá áðü ôï web interface ìáò. Ðáñüìïéá ðñïóï÷Þ ÷ñåéÜæåôáé êáé üôáí, áíôß ãéá ôï åñãáëåßï &man.send-pr.1;, ÷ñçóéìïðïéåßôå ôç öüñìá õðïâïëÞò áíáöïñþí ðïõ Ý÷åé ç éóôïóåëßäá ìáò. Ç áíôéãñáöÞ êáé åðéêüëëçóç êåéìÝíïõ ìðïñåß íá åðçñåÜóåé ôç ìïñöïðïßçóç ôïõ êåéìÝíïõ. Óå ìåñéêÝò ðåñéðôþóåéò ìðïñåß íá ÷ñåéáóôåß áêüìá êáé ôï åñãáëåßï &man.uuencode.1; ãéá íá åßóôå óßãïõñïé üôé Ýíá patch öôÜíåé ùò åìÜò ÷ùñßò áëëáãÝò. ÔÝëïò, áí ç áíáöïñÜ óáò ðåñéÝ÷åé ìåãÜëá áñ÷åßá Þ áñêåôü êåßìåíï, ßóùò åßíáé êáëýôåñá íá ôçí ðñïåôïéìÜóåôå óå Ýíá îå÷ùñéóôü áñ÷åßï êáé íá ôçí áðïèçêåýóåôå ðñéí ðñïóðáèÞóåôå íá ôç óôåßëåôå. Áí äåí ðåôý÷åé ç áðïóôïëÞ ôçò áíáöïñÜò, äå èá ñéøïêéíäõíÝøåôå íá ÷áèåß üôé Ý÷åôå ãñÜøåé ìÝ÷ñé åêåßíç ôç óôéãìÞ. Ç öüñìá áðïóôïëÞò ìÝóù web åßíáé óõ÷íÜ ðçãÞ ôÝôïéùí ðñïâëÞìáôùí.
ÅðéóõíÜðôïíôáò patches Þ áñ÷åßá Ôï ðñüãñáììá &man.send-pr.1; Ý÷åé ôçí äõíáôüôçôá íá åðéóõíÜøåé áñ÷åßá óå ìéá áíáöïñÜ ðñïâëÞìáôïò. Ìðïñåßôå íá åðéóõíÜøåôå üóá áñ÷åßá èÝëåôå, áñêåß ôï êáèÝíá íá Ý÷åé ìïíáäéêü âáóéêü üíïìá (ôï üíïìá ôïõ áñ÷åßïõ ÷ùñßò ôçí äéáäñïìÞ). ÁðëÜ ÷ñçóéìïðïéÞóôå ôçí ðáñÜìåôñï óôçí ãñáììÞ åíôïëþí ãéá íá êáôáäåßîåôå ôá ïíüìáôá ôùí áñ÷åßùí ðïõ èÝëåôå íá åðéóõíÜøåôå: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors Äåí ÷ñåéÜæåôáé íá áíçóõ÷åßôå ãéá ôá áñ÷åßá ðïõ äåí åßíáé êåßìåíï. Èá êùäéêïðïéçèïýí êáôÜëëçëá ãéá íá ìçí ôá áëëÜîåé ôï ðñüãñáììá áðïóôïëÞò çëåêôñïíéêÞò áëëçëïãñáößáò ðïõ ÷ñçóéìïðïéåßôå. Áí ìáæß ìå ôçí áíáöïñÜ óôåßëåôå êáé êÜðïéï patch, öñïíôßóôå íá ÷ñçóéìïðïéÞóåôå ôçí åðéëïãÞ Þ ôçí óôçí åíôïëÞ &man.diff.1; ãéá íá äçìéïõñãÞóåôå Ýíá context Þ unified áñ÷åßï äéáöïñþí, êáé ìçí îå÷Üóåôå íá óçìåéþóåôå ôéò áêñéâåßò åêäüóåéò ôùí áñ÷åßùí ðïõ áëëÜîáôå Ýôóé þóôå ïé ðñïãñáììáôéóôÝò ðïõ èá äéáâÜóïõí ôçí áíáöïñÜ óáò íá ìðïñïýí íá êÜíïõí ôéò ßäéåò áëëáãÝò åýêïëá. Ãéá ôá ðñïâëÞìáôá ðïõ áöïñïýí ôïí ðõñÞíá Þ ôá åñãáëåßá ôïõ âáóéêïý óõóôÞìáôïò åßíáé ðñïôéìüôåñï ôï patch óáò íá âáóßæåôáé óôï &os.current; (ôï HEAD branch ôïõ CVS) áöïý üëåò ïé áëëáãÝò ðñÝðåé ðñþôá íá ãßíïíôáé óå áõôü ôï branch ãéá íá äïêéìáóôïýí. Áöïý ðåñÜóåé êÜðïéïò êáéñüò êé ïé áëëáãÝò äïêéìáóôïýí áñêåôÜ ìüíï ôüôå åíóùìáôþíïíôáé/ìåôáöÝñïíôáé ïé áëëáãÝò óôï &os.stable; branch. Áí åíóùìáôþóåôå ôï patch óáò óôçí áíáöïñÜ, áíôß íá ôï óôåßëåôå óáí åðéóýíáøç, ðñïóÝîôå áñêåôÜ ãéáôß Ýíá áñêåôÜ óõ÷íü ðñüâëçìá åßíáé ðùò ðïëëÜ ðñïãñÜììáôá çëåêôñïíéêÞò áëëçëïãñáößáò Ý÷ïõí ôçí ôÜóç íá ìåôáôñÝðïõí ôïõò óôçëïèÝôåò óå êåíÜ, êÜôé ðïõ êáôáóôñÝöåé åíôåëþò ïôéäÞðïôå áðïôåëåß ìÝñïò êÜðïéïõ Makefile. Ìç óôÝëíåôå ôá patches óáò ùò åðéóõíÜøåéò ìå ôçí êùäéêïðïßçóç Content-Transfer-Encoding: quoted-printable. ÁõôÞ ç êùäéêïðïßçóç áëëÜæåé êÜðïéïõò ÷áñáêôÞñåò ìå áðïôÝëåóìá íá åßíáé Ü÷ñçóôï ïëüêëçñï ôï patch. ÃåíéêÜ, ðÜíôùò, äåí ôñÝ÷åé ôßðïôá áí åíóùìáôþóåôå êÜðïéï ìéêñü patch óôçí áíáöïñÜ óáò—åéäéêÜ áí åßíáé öáíåñü ðùò äéïñèþíåé ôï ðñüâëçìá ðïõ ðåñéãñÜöåôáé óôçí áíáöïñÜ. Ôá ðéï ìåãÜëá patches, êõñßùò êþäéêáò ðïõ ìðïñåß íá áðáéôåß ëåðôïìåñÞ áíÜëõóç êáé äïêéìÝò ðñéí ãßíåé commit, åßíáé êáëýôåñá íá ôá áíåâÜæåôå óå êÜðïéï web Þ ftp server êáé íá ðåñéëáìâÜíåôå óôçí áíáöïñÜ óáò ôï URL ãéá íá ôá âñßóêåé ï áíáãíþóôçò ôçò áíáöïñÜò áíôß íá åíóùìáôþíåôå ôï ßäéï ôï patch. ÐïëëÝò öïñÝò ôá patches êáôáóôñÝöïíôáé üôáí åßíáé ìÝñïò åíüò email, åéäéêÜ üôáí ðåñíïýí áðü ôï ðñüãñáììá GNATS, êé üóï ðéï ìåãÜëï åßíáé ôï patch ôüóï ðéï äýóêïëï èá åßíáé ãéá üðïéïí åíäéáöÝñåôáé íá ôï äéïñèþóåé ãéá íá ôï äïêéìÜóåé. ¸íá Üëëï êáëü ðïõ Ý÷åé ç äéáíïìÞ åíüò patch ìÝóù web Þ ftp åßíáé üôé ìðïñåßôå íá áëëÜîåôå ôï patch ÷ùñßò íá ÷ñåéÜæåôáé íá ôï îáíáóôåßëåôå üëï óáí ìÝñïò ìéáò áðÜíôçóçò óôçí áñ÷éêÞ áíáöïñÜ. Ôá ìåãÜëá patches áõîÜíïõí ìüíéìá ôï ìÝãåèïò ôçò âÜóçò áíáöïñþí, áöïý áêüìç êé üôáí äéïñèùèåß Ýíá ðñüâëçìá êáé êëåßóåé ç áíôßóôïé÷ç áíáöïñÜ ðñïâëÞìáôïò äå óâÞíåôáé ôßðïôá áðü ôç âÜóç áíáöïñþí, áëëÜ áðëÜ óçìåéþíåôáé ùò closed. Ìçí îå÷íÜôå åðßóçò üôé, áí äåí ôï äçëþóåôå ñçôÜ óôçí áíáöïñÜ ðïõ èá óôåßëåôå Þ óôï ßäéï ôï patch, ïðïéåóäÞðïôå áëëáãÝò óôåßëåôå èåùñåßôáé áõôüìáôá üôé åßíáé äéáèÝóéìåò êÜôù áðü ôïõò ßäéïõò üñïõò êáé ìå ôçí ßäéá Üäåéá ðïõ Ý÷åé ç Ýêäïóç ôïõ êÜèå áñ÷åßïõ ðïõ Ý÷åôå ôñïðïðïéÞóåé.
Óõìðëçñþíïíôáò ôçí öüñìá ôçò áíáöïñÜò ¼ôáí ôñÝîåôå ôï ðñüãñáììá &man.send-pr.1; èá äåßôå ìéá öüñìá áíáöïñÜò. Ç öüñìá ôçò áíáöïñÜò áðïôåëåßôáé áðü ìéá óåéñÜ ðåäßùí. ÊÜðïéá áðü áõôÜ åßíáé åßíáé ðñïóõìðëçñùìÝíá. ÊÜðïéá Üëëá Ý÷ïõí ó÷üëéá ðïõ åîçãïýí ôïí óêïðü ôïõò Þ áíáöÝñïõí ôéò áðïäåêôÝò ôéìÝò. Ìçí áíçóõ÷åßôå ãéá ôá ó÷üëéá, áöïý Ýôóé êé áëëéþò èá áöáéñåèïýí áõôüìáôá áí äåí ôá áëëÜîåôå Þ äåí ôá óâÞóåôå. Óôçí êïñõöÞ ôçò öüñìáò, êÜôù áðü ôéò ãñáììÝò ðïõ áñ÷ßæïõí ìå SEND-PR: õðÜñ÷ïõí ïé åðéêåöáëßäåò åíüò ãñÜììáôïò. ÓõíÞèùò äåí ÷ñåéÜæåôå íá êÜíåôå êÜðïéá áëëáãÞ óå áõôÝò, åêôüò êé áí óôÝëíåôå ôçí áíáöïñÜ áðü êÜðïéï ìç÷Üíçìá ôï ïðïßï ìðïñåß íá óôåßëåé email áëëÜ äåí ìðïñåß íá ëÜâåé, ðïõ èá ðñÝðåé íá ðñïóÝîåôå ïé ãñáììÝò From: êáé Reply-To: íá Ý÷ïõí ôçí ðñáãìáôéêÞ óáò email äéåýèõíóç. Ìðïñåßôå öõóéêá íá óôåßëåôå óôïí åáõôü óáò Þ êÜðïéïí Üëëï Ýíá áíôßãñáöï ôçò áíáöïñÜò ðñïâëÞìáôïò ðñïóèÝôïíôáò ôéò êáôÜëëçëåò Cc: ãñáììÝò. ÌåôÜ èá äåßôå ìéá óåéñÜ áðü ðåäßá ìéáò ãñáììÞò: Submitter-Id: Ìçí ôï áëëÜîåôå áõôü. Ç ðñïêáèïñéóìÝíç ôéìÞ ôïõ, current-users, åßíáé óùóôÞ áêüìá êé áí ÷ñçóéìïðïéåßôå ôï &os.stable;. Originator: Áõôü ôï ðåäßï åßíáé êáíïíéêÜ ðñïóõìðëçñùìÝíï ìå ôï üíïìá ôïõ ôñÝ÷ïíôïò ÷ñÞóôç. Áí áõôü äåí åßíáé óùóôü, ðáñáêáëþ óõìðëçñþóôå ôçí ôéìÞ áõôïý ôïõ ðåäßïõ ìå ôï ðñáãìáôéêü óáò üíïìá êáé ðñïáéñåôéêÜ ôçí email äéåýèõíóÞ óáò ìÝóá óå < êáé >. Organization: Áõôü ôï ðåäßï äåí ÷ñçóéìïðïéåßôáé ãéá ôßðïôá óçìáíôéêü. Confidential: Áõôü ôï ðåäßï åßíáé ðñïóõìðëçñùìÝíï ìå no. Äåí Ý÷åé íüçìá íá ôï áëëÜîåôå óå êÜôé Üëëï, áöïý äåí õðÜñ÷ïõí åìðéóôåõôéêÝò áíáöïñÝò ðñïâëçìÜôùí óôï &os;—ç óõëëïãÞ ôùí ðñïâëçìÜôùí åßíáé áíïé÷ôÞ êáé äéáèÝóéìç ìÝóù CVSup ãéá üëï ôïí êüóìï. Synopsis: Óõìðëçñþóôå áõôü ìå ìéá óýíôïìç êáé áêñéâÞ ðåñéãñáöÞ ôïõ ðñïâëÞìáôïò. Ç synopsis ÷ñçóéìïðïéåßôáé óáí ôï èÝìá óôá email ôá ó÷åôéêÜ ìå ôçí áíáöïñÜ, êáèþò êáé óå ëßóôåò áíáöïñþí êáé ðåñéëÞøåéò. Ïé áíáöïñÝò ðñïâëÞìáôïò ìå ðåñßåñãåò ðåñéãñáöÝò óôï ðåäßï áõôü óõíÞèùò áãíïïýíôáé. ¼ðùò åßðáìå ðáñáðÜíù, áí ç áíáöïñÜ óáò ðåñéëáìâÜíåé êÜðïéï patch êáëü åßíáé íá îåêéíÞóåôå ôçí ãñáììÞ ôçò óýíïøçò ìå ôï êåßìåíï [patch]. Áí ðÜëé åßóôå ï õðåýèõíïò (maintainer) ãéá êÜðïéï ìÝñïò ôïõ êþäéêá, êáëü åßíáé íá ðñïóèÝóåôå óôç óýíïøç ôï êåßìåíï [maintainer update] êáé íá èÝóåôå ôçí ôéìÞ ôçò åðéêåöáëßäáò Class óå maintainer-update. Severity: Ìðïñåß íá ðÜñåé ôéìÞ non-critical, serious Þ critical. Ìçí áíôéäñÜôå õðåñâïëéêÜ. Áðïöýãåôå íá ÷áñáêôçñßæåôå ôéò áíáöïñÝò óáò critical åêôüò êé áí åßíáé üíôùò ìåãÜëçò óçìáóßáò (ð.÷. root exploit, êÜðïéï panic ðïõ ìðïñåß íá áíáðáñá÷èåß åýêïëá) Þ serious åêôüò êé áí åßíáé êÜôé ðïõ áöïñÜ ðïëëïýò ÷ñÞóôåò (ðñïâëÞìáôá ìå óõãêåêñéìÝíïõò ïäçãïýò óõóêåõþí Þ åñãáëåßá ôïõ óõóôÞìáôïò). Äåí åßíáé áðáñáßôçôï ðùò ïé ðñïãñáììáôéóôÝò ôïõ &os; èá áó÷ïëçèïýí ðéï íùñßò ìå ôï ðñüâëçìÜ óáò áí õðåñâÜëëåôå ãéá ôçí óçìáóßá ôïõ åðåéäÞ õðÜñ÷åé ðïëýò êüóìïò ðïõ ôï êÜíåé áõôü—ìÜëéóôá, õðÜñ÷ïõí ðñïãñáììáôéóôÝò ðïõ áãíïïýí åíôåëþò áõôü ôï ðåäßï êáé ôï åðüìåíï, áêñéâþò åðåéäÞ áõôïß ðïõ óôÝëíïõí ôéò áíáöïñÝò Ý÷ïõí ôçí ôÜóç íá õðåñåêôéìïýí ôá ðñïâëÞìáôÜ ôïõò. Priority: Ìðïñåß íá ðÜñåé ôéìÞ low, medium Þ high. Ðñïôåñáéüôçôá high ðñÝðåé íá äßíåôáé ìüíï óå áíáöïñÝò ðñïâëçìÜôùí ôá ïðïßá åðçñåÜæïõí ðñáêôéêÜ üëïõò ôïõò ÷ñÞóôåò ôïõ &os; êáé medium óôá ðñïâëÞìáôá ðïõ áöïñïýí Ýíá ìåãÜëï áñéèìü ÷ñçóôþí. Category: ÅðéëÝîôå ìéá áðü ôéò áêüëïõèåò êáôçãïñßåò (áðü ôï áñ÷åßï ): advocacy: áíáöïñÝò ó÷åôéêÝò ìå ôçí äçìüóéá åéêüíá ôïõ &os;. ×ñçóéìïðïéåßôáé óðÜíéá. alpha: áíáöïñÝò ó÷åôéêÝò ìå ôçí ðëáôöüñìá Alpha platform. amd64: áíáöïñÝò ó÷åôéêÜ ìå ðñïâëÞìáôá ôçò ðëáôöüñìáò AMD64. bin: áíáöïñÝò ó÷åôéêÝò ìå ðñïãñÜììáôá óôï âáóéêü óýóôçìá. conf: áíáöïñÝò ó÷åôéêÝò ìå áñ÷åßá ñõèìßóåùí, ðñïêáèïñéóìÝíåò ôéìÝò, êëð. docs: áíáöïñÝò ó÷åôéêÝò ìå ôéò manual pages Þ ãåíéêÜ ôçí ôåêìçñßùóç. gnu: áíáöïñÝò ó÷åôéêÝò ìå ðñïãñÜììáôá GNU, üðùò ð.÷. &man.gcc.1; Þ &man.grep.1;. i386: áíáöïñÝò ó÷åôéêÝò ìå ôçí ðëáôöüñìá i386 platform. ia64: áíáöïñÝò ó÷åôéêÝò ìå ôçí ðëáôöüñìá ia64. java: áíáöïñÝò ó÷åôéêÝò ìå ôçí õëïðïßçóç ôçò ÅéêïíéêÞò Ìç÷áíÞò &java;. (Ïé áíáöïñÝò ãéá ðáêÝôá ôá ïðïßá áðëÜ áðáéôïýí ôç &java; ãéá íá ôñÝîïõí êáôá÷ùñïýíôáé óôçí êáôçãïñßá ports.) kern: áíáöïñÝò ãéá ôïí ðõñÞíá. misc: ïôéäÞðïôå äåí ôáéñéÜæåé óå êÜðïéá áðü ôéò õðüëïéðåò êáôçãïñßåò. (Óçìåéþóôå ðùò åßíáé åýêïëï íá ÷áèåß ìéá áíáöïñÜ óå áõôÞ ôçí êáôçãïñßá.) ports: áíáöïñÝò ó÷åôéêÝò ìå ôá ports. powerpc: áíáöïñÝò ó÷åôéêÝò ìå ôçí ðëáôöüñìá PowerPC. sparc64: áíáöïñÝò ó÷åôéêÝò ìå ôçí ðëáôöüñìá SPARC. standards: áíáöïñÝò ó÷åôéêÝò ìå ôçí óõìâáôüôçôá ìå ôá äéÜöïñá Ðñüôõðá. threads: áíáöïñÝò ó÷åôéêÝò ìå ôçí õëïðïßçóç ôùí threads óôï &os; (åéäéêÜ óôï &os.current;). usb: áíáöïñÝò ó÷åôéêÜ ìå ôï õðïóýóôçìá USB ôïõ &os; êáé ôçí õðïóôÞñéîç óõóêåõþí USB. www: áëëáãÝò Þ âåëôéþóåéò óôçí äéêôõáêÞ óåëßäá ôïõ &os;. Class: Ãéá ôï ðåäßï áõôü, åðéëÝîôå ìéá áðü ôéò ðáñáêÜôù ôéìÝò: sw-bug: software bugs. doc-bug: ëÜèç óôçí ôåêìçñßùóç. change-request: éäÝåò êáé áéôÞóåéò ãéá ðñüóèåôá ÷áñáêôçñéóôéêÜ Þ áëëáãÝò óå õðÜñ÷ïíôá. update: åíçìåñþóåéò ôùí ports Þ Üëëùí ðñïãñáììÜôùí ðïõ öôéÜ÷íïíôáé áðü ôñßôïõò. maintainer-update: åíçìåñþóåéò óå ports ãéá ôá ïðïßá óõíôçñåßôå åóåßò. Release: Ç Ýêäïóç ôïõ &os; ðïõ ÷ñçóéìïðïéåßôå. Áõôü ôï ðåäßï óõìðëçñþíåôáé áõôüìáôá áðü ôçí &man.send-pr.1; êáé ÷ñåéÜæåôáé íá ôï áëëÜîåôå ìüíï óôçí ðåñßðôùóç ðïõ óôÝëíåôå ìéá áíáöïñÜ ðñïâëÞìáôïò áðü Üëëï ìç÷Üííçìá, êé ü÷é áðü áõôü ðïõ Ý÷åé ôï ðñüâëçìá. ÔÝëïò, õðÜñ÷åé ìéá óåéñÜ áðü ðåäßá ìå ðåñéóóüôåñåò áðü ìéá ãñáììÝò ôï êáèÝíá: Environment: Åäþ ðñÝðåé íá ðåñéãñÜöåôáé, ìå üóï ôï äõíáôüí ìåãáëýôåñç áêñßâåéá, ôï ðåñéâÜëëïí óôï ïðïßï ðáñáôçñÞóáôå ôï ðñüâëçìá. Áõôü ðåñéëáìâÜíåé ôçí Ýêäïóç ôïõ ëåéôïõñãéêïý óõóôÞìáôïò, ôçí Ýêäïóç ôïõ óõãêåêñéìÝíïõ ðñïãñÜììáôïò Þ áñ÷åßïõ ðïõ Ý÷åé ôï ðñüâëçìá êáé ïðïéáäÞðïôå Üëëá ÷áñáêôçñéóôéêÜ áðü ôï óýóôçìá êáé ôéò ñõèìßóåéò ôïõ èåùñåßôå óçìáíôéêÜ, Üëëá åãêáôåóôçìÝíá ðñïãñÜììáôá ðïõ ðéóôåýåôå üôé ðéèáíüí Ý÷ïõí ó÷Ýóç ìå ôï ðñüâëçìá, êëð—ðïëý áðëÜ, ïôéäÞðïôå ÷ñåéÜæåôáé íá îÝñåé Ýíáò ðñïãñáììáôéóôÞò ãéá íá åîïìïéþóåé ìå áêñßâåéá ôï ðåñéâÜëëïí óôï ïðïßï åìöáíßæåôáé ôï ðñüâëçìá. Description: Ìéá ðëÞñçò êáé áêñéâÞò ðåñéãñáöÞ ôïõ ðñïâëÞìáôïò ðïõ áíôéìåôùðßæåôå. Ðñïóðáèåßóôå íá áðïöýãåôå åéêáóßåò ó÷åôéêÜ ìå ôçí áéôßá ôïõ ðñïâëÞìáôïò åêôüò êé áí åßóôå óßãïõñïé üôé âñßóêåôå óå óùóôü äñüìï, êáèþò ìðïñåß íá ïäçãÞóåôå êÜðïéï ðñïãñáììáôéóôÞ íá êÜíåé ëÜèïò õðïèÝôïíôáò êÜðïéá ðñÜãìáôá ðïõ äåí åßíáé óùóôÜ. How-To-Repeat: Ìéá ðåñßëçøç ôùí åíåñãåéþí ðïõ ÷ñåéÜæïíôáé ãéá íá áíáðáñÜãåé êÜðïéïò ôï ðñüâëçìá. Fix: ÊáôÜ ðñïôßìçóç êÜðïéï patch Þ ôïõëÜ÷éóôïí êÜôé ðïõ îåðåñíÜ/áðïöåýãåé ôï ðñüâëçìá (êÜôé ðïõ ü÷é ìüíï âïçèÜ üðïéïí Ý÷åé ôï ßäéï ðñüâëçìá íá ôï áðïöýãåé, áëëÜ ìðïñåß áêüìç êáé íá âïçèÞóåé êÜðïéïí ðñïãñáììáôéóôÞ íá êáôáëÜâåé ôçí ðñáãìáôéêÞ áéôßá ôïõ ðñïâëÞìáôïò). Áí äåí Ý÷åôå âÝâáéá êÜðïéá éäÝá, ìðïñåßôå ðÜíôá íá áöÞóåôå áõôü ôï ðåäßï êåíü. Åßíáé ðïëý êáëýôåñá áðü ôï íá êÜíåôå áðëþò åéêáóßåò.
ÓôÝëíïíôáò ôçí áíáöïñÜ ¼ôáí ôåëåéþóåôå ìå ôï ãñÜøéìï, ôçí óõìðëÞñùóç ôçò öüñìáò, êáé óþóåôå ôï êåßìåíï ôçò áíáöïñÜò óå Ýíá áñ÷åßï, ôï ðñüãñáììá &man.send-pr.1; èá óáò äåßîåé ìéá ðñïôñïðÞ s)end, e)dit or a)bort?. Ìðïñåßôå ôüôå íá ðáôÞóåôå s ãéá íá óõíå÷ßóåôå êáé íá óôáëåß ç áíáöïñÜ, e ãéá íá îåêéíÞóåôå ðÜëé ôïí êåéìåíïãñÜöï óáò, Þ a ãéá íá åãêáôáëåßøåôå. Áí åðéëÝîåôå ôï ôåëåõôáßï, ôï êåßìåíï ôçò áíáöïñÜò óáò èá ðáñáìåßíåé óôï äßóêï (ç &man.send-pr.1; èá ãñÜøåé ôï üíïìá ôïõ áñ÷åßïõ ðñéí ôåñìáôßóåé), ïðüôå ìðïñåßôå íá ôï åðåîåñãáóôåßôå ìå ôçí çóõ÷ßá óáò áñãüôåñá Þ íá ôï ìåôáöÝñåôå óå êÜðïéï óýóôçìá ìå êáëýôåñç óýíäåóç äéêôýïõ, ðñéí íá ôï óôåßëåôå ìå ôçí åðéëïãÞ ôçò &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report ÁõôÞ ç åíôïëÞ èá äéáâÜóåé ìéá áíáöïñÜ ðñïâëÞìáôïò áðü ôï áñ÷åßï, èá êÜíåé êÜðïéïõò åëÝã÷ïõò óôá ðåñéå÷üìåíá, èá óâÞóåé ôá ó÷üëéá êáé óôåßëåé ôçí áíáöïñÜ.
ÁðáíôÞóåéò Ìüëéò ç áíáöïñÜ óáò êáôá÷ùñçèåß, èá ðÜñåôå ìéá áðÜíôçóç ìÝóù email ðïõ èá ðåñéëáìâÜíåé ôïí áñéèìü ðïõ Ý÷åé ó÷åôéóôåß ìå ôçí áíáöïñÜ óáò êáé ìéá äéåýèõíóç URL üðïõ ìðïñåßôå íá äéáâÜóåôå ôçí áíáöïñÜ êáé ôçí êáôÜóôáóÞ ôçò. Ìå ëßãç ôý÷ç, êÜðïéïò èá åíäéáöåñèåß ãéá ôçí áíáöïñÜ óáò êáé èá ðñïóðáèÞóåé íá ëýóåé ôï ðñüâëçìá Þ ôïõëÜ÷éóôïí, áíÜëïãá ìå ôçí ðåñßðôùóç, íá óáò åîçãÞóåé ãéáôß äåí åßíáé ðñüâëçìá. Èá åéäïðïéÞóôå áõôüìáôá ãéá êÜèå áëëáãÞ óôçí êáôÜóôáóç ôçò áíáöïñÜò, êáé èá ðáßñíåôå áíôßãñáöá ìÝóù áëëçëïãñáößáò ìå ïðïéáäÞðïôå ó÷üëéá Þ patches óôÝëíåé êÜðïéïò óáí áðÜíôçóç óôçí áíáöïñÜ óáò. Áí êÜðïéïò óáò æçôÞóåé åðéðëÝïí ðëçñïöïñßåò Þ èõìçèåßôå êÜôé Þ áíáêáëýøåôå êÜôé ðïõ äåí Ý÷åôå áíáöÝñåé óôçí áñ÷éêÞ óáò áíáöïñÜ, ôüôå ÷ñçóéìïðïéÞóôå Ýíáí áðü ôïõò áêüëïõèïõò ôñüðïõò ãéá íá óôåßëåôå óõìðëçñùìáôéêÝò ðëçñïöïñßåò: Ï ðéï åýêïëïò ôñüðïò åßíáé íá áêïëïõèÞóåôå ôï óýíäåóìï óôçí óåëßäá ôçò áíáöïñÜò, ôçí ïðïßá ìðïñåßôå íá âñåßôå áðü ôç óåëßäá áíáæÞôçóçò ôùí áíáöïñþí. Áí áêïëïõèÞóåôå ôï óýíäåóìï ðïõ Ý÷åé óôï êÜôù ìÝñïò ç óåëßäá èá áíïßîåé ôï ðñüãñáììá áëëçëïãñáößáò óáò ìå ôï óùóôü áðïóôïëÝá êáé ôï óùóôü èÝìá (áñêåß ï öõëëïìåôñçôÞò óáò õðïóôçñßæåé ôçí åêôÝëåóç åîùôåñéêþí ðñïãñáììÜôùí). ÅíáëëáêôéêÜ ìðïñåßôå íá óôåßëåôå áðëÜ Ýíá ìÞíõìá óôç äéåýèõíóç &a.bugfollowup;, ðñïóÝ÷ïíôáò íá âÜëåôå ôï óùóôü áñéèìü áíáöïñÜò óôï èÝìá Ýôóé þóôå íá ôïí âñåé ôï óýóôçìá ðáñáêïëïýèçóçò áíáöïñþí ôïõ &os; êáé íá îÝñåé óå ðïéÜ áíáöïñÜ ðñÝðåé íá åðéóõíÜøåé ôï ìÞíõìÜ óáò. Áí äåí óõìðåñéëÜâåôå ôï óùóôü áñéèìü áíáöïñÜò óôï èÝìá, ôï ðñüãñáììá GNATS ðïõ ïñãáíþíåé ôéò áíáöïñÝò óå êáôçãïñßåò èá ìðåñäåõôåß êáé èá áíïßîåé ìéá íÝá áíáöïñÜ ôçí ïðïßá ìåôÜ áíáèÝôåé óôïí äéá÷åéñéóôÞ ôïõ óõóôÞìáôïò GNATS. ¸ôóé ç áðÜíôçóÞ óáò èá ìåßíåé áöáíÞò ìÝ÷ñé íá øÜîåé êÜðïéïò ãéá áíáöïñÝò ðïõ åßíáé êáôá÷ùñçìÝíåò ëÜèïò êáé íá ôéò îåêáèáñßóåé, êÜôé ðïõ ìðïñåß íá ãßíåé ìåôÜ áðü ìÝñåò Þ êáé ïëüêëçñåò åâäïìÜäåò. ËÜèïò ôñüðïò: Subject: that PR I sent Óùóôüò ôñüðïò: Subject: Re: ports/12345: compilation problem with foo/bar Áí ç áíáöïñÜ ðñïâëÞìáôïò ðáñáìÝíåé óôçí êáôÜóôáóç open ðáñüëï ðïõ ôï ðñüâëçìá Ý÷åé óôáìáôÞóåé íá åìöáíßæåôáé ðëÝïí, áðëþò óôåßëôå ìéá áðÜíôçóç óôçí áíáöïñÜ (ìå ôïí ôñüðï ðïõ áíáöÝñáìå ðáñáðÜíù), åîçãþíôáò ðùò Þ ðüôå äéïñèþèçêå ôï ðñüâëçìá.
ÁíáöïñÝò ÐáñáêÜôù èá âñåßôå êÜðïéåò ðçãÝò ðïõ åßíáé ó÷åôéêÝò ìå ôï èÝìá ôùí áíáöïñþí ðñïâëÞìáôïò. Äåí åßíáé ìéá ðëÞñçò Þ åðáñêÞò ëßóôá, öõóéêÜ. How to Report Bugs Effectively—ìéá ðïëý êáëÞ Ýêèåóç áðü ôïí Simon G. Tatham ðïõ ðåñéãñÜöåé ðùò ìðïñåßôå íá ãñÜöåôå ÷ñÞóéìåò áíáöïñÝò ðñïâëÞìáôùí (ü÷é ìüíï ãéá ôï &os;). Problem Report Handling Guidelines—÷ñÞóéìåò ðëçñïöïñßåò ãéá ôïí ôñüðï ìå ôïí ïðïßï ÷åéñßæåôáé ôéò áíáöïñÝò ðñïâëçìÜôùí ç ïìÜäá áíÜðôõîçò ôïõ &os;
+ +
diff --git a/el_GR.ISO8859-7/books/handbook/Makefile b/el_GR.ISO8859-7/books/handbook/Makefile index fe5f159acd..e791d06ba2 100644 --- a/el_GR.ISO8859-7/books/handbook/Makefile +++ b/el_GR.ISO8859-7/books/handbook/Makefile @@ -1,359 +1,357 @@ # # $FreeBSD$ # # Ìïñöïðïßçóç ôïõ Åã÷åéñéäßïõ ôïõ FreeBSD # # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile # %SRCID% 1.119 # # ------------------------------------------------------------------------ # # ÌåôáâëçôÝò ó÷åôéêÝò ìå ôï Åã÷åéñßäéï # # WITH_PGPKEYS Ç åêôõðþóéìç ìïñöÞ ôïõ åã÷åéñéäßïõ ðåñéÝ÷åé êáíïíéêÜ # ìüíï ôá fingerprints áðü ôá PGP êëåéäéÜ. Áí èÝëåôå # íá åêôõðþíïíôáé ïëüêëçñá ôá êëåéäéÜ, ôüôå áõôÞ ç # ìåôáâëçôÞ ðñÝðåé íá åßíáé 'defined'. ÁõôÞ ç åðéëïãÞ # äåí åðçñåÜæåé óå ôßðïôá ôéò ìïñöÝò HTML. # # Make targets ìüíï ãéá ôï Åã÷åéñßäéï # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # Ãéá íá ðñïóèÝóåôå Ýíá íÝï êåöÜëáéï óôï Åã÷åéñßäéï: # # - Åíçìåñþóôå áõôü ôï Makefile, ôï chapters.ent êáé ôï book.xml # - ÐñïóèÝóôå ìéá óýíôïìç ðåñéãñáöÞ ôïõ êåöáëáßïõ óôï preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # Ç ëßóôá SRCS ðåñéÝ÷åé üëá ôá XML áñ÷åßá ðïõ áðïôåëïýí ìÝñç ôïõ êåéìÝíïõ. # ÁëëáãÝò óå ïðïéïäÞðïôå áðü áõôÜ ôá áñ÷åßá ðñïêáëïýí rebuild. # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ eresources:::eresources.xml.www.inc \ eresources-index:::eresources.xml.www.index.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/el_GR.ISO8859-7/books/handbook/chapters.ent b/el_GR.ISO8859-7/books/handbook/chapters.ent index a7834f11a8..8ed66d1a3f 100644 --- a/el_GR.ISO8859-7/books/handbook/chapters.ent +++ b/el_GR.ISO8859-7/books/handbook/chapters.ent @@ -1,78 +1,78 @@ %pgpkeys; - + "> diff --git a/en_US.ISO8859-1/articles/console-server/article.xml b/en_US.ISO8859-1/articles/console-server/article.xml index 1360b58373..0f05f72b2b 100644 --- a/en_US.ISO8859-1/articles/console-server/article.xml +++ b/en_US.ISO8859-1/articles/console-server/article.xml @@ -1,1476 +1,1478 @@
Console Server Gregory Bond
gnb@itga.com.au
 &tm-attrib.freebsd; &tm-attrib.cisco; &tm-attrib.intel; &tm-attrib.lantronix; &tm-attrib.microsoft; &tm-attrib.opengroup; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ This document describes how you can use &os; to set up a console server. A console server is a machine that you can use to monitor the consoles of many other machines, instead of a bunch of serial terminals. console-server The Problem You have a computer room with lots of &unix; server machines and lots of communications hardware. Each of these machines needs a serial console. But serial terminals are hard to find and quite expensive (especially compared to a much more capable PC). And they take up a lot of precious space in the computer room. You need access to the console because when things break, that is where error messages go. And some tasks have to be done on the console (e.g. boot problems or OS installs/upgrades). Some &unix; systems allow the console to break out to the ROM monitor which can sometimes be the only way to unstick a hung machine. This is often done with a LINE BREAK sent on the console serial port. If we are going to play about with consoles, then there are a couple of other things that would be great: Remote access. Even in the same office, it would be convenient to access all the consoles from your desk without walking into the computer room. But often the machines are off-site, perhaps even in another country. Logging. If something has gone wrong, you would like to be able to have a look at the previous console output to see what is up. Ordinary console screens give you the last 25 lines. More would be better. Network Independence. The solution needs to work even if the network is down. After all, a failed network is when you need consoles the most! Even better is network independence with remote access. No single-point failure. A console system that crashes every machine when it fails is no use. This is particularly tricky with Sun &unix; hosts as they will interpret a powered-off terminal as a BREAK, and drop back to the ROM monitor. Interface with a pager or some similar alerter device. Ability to power-cycle machines remotely. Not be too expensive. Free is even better! Possible Solutions If you use PC hardware for your servers, then a so-called KVM switch is one possible solution. A KVM switch allows the use of a single keyboard, video screen and mouse for multiple boxes. This cuts down on the space problem, but only works for PC hardware (not any communications gear you might have), and is not accessible from outside the computer room. Nor does it have much scroll-back or logging, and you have to handle alerting some other way. The big downside is that it will not work for serial-only devices, such as communications hardware. This means that even with a room full of PC-based servers, you are probably still going to need some sort of serial console solution. Actually, Doug Schache has pointed out that you can get KVM switches that also do serial consoles or Sun compatible KVM switching as well as PCs, but they are expensive. See Avocent for example.) You might be tempted to do without a console terminal, but when things go pear-shaped you really need to see what is on the console. And you have to use the console to boot the machine and do things like OS upgrades or installs. You might try having a single console terminal and switching from server to server as needed, either with a serial switch or just by patching it into the required machine. Serial switches are also hard to come by and not cheap, and may cause problems with sending BREAK when they switch. And (if your computer room is anything like ours) you never seem to have the right combination of patch leads to connect to the machine you need to, and even if the leads are there you can never work out exactly which combination of DTE/DCE headshells goes with which lead goes with which hardware. So you spend the first 10 minutes fooling around with breakout boxes and a box of leads, all while the server is down and the users are screaming. Of course this does not deal with the logging or remote access requirements. And inevitably the console is not switched to the machine you need so you lose all the console messages that might tell you what is going on. One popular solution is to use terminal server hardware. Typically, the serial ports are connected to the various machine consoles, and set up for reverse telnet access. This means a user can telnet to a given IP/port and be connected to the appropriate console. This can be very cost-effective, as suitable old terminal servers can be picked up fairly cheaply (assuming you do not have a couple lying around). And it is of course network-accessible so suitable for remote access. But it suffers from one major drawback: if the network is down, then you have no access to any console, even if you are standing right next to the machine. (This may be partially alleviated by having a suitable terminal connected to one of the terminal server ports and connecting from there, but the terminal server software may not support that.) Also there is no logging or replay of console messages. But with a bit of work, and the addition of some software such as conserver (described below), this can be made to work pretty well. A possibility suggested by Bron Gondwana is similar to the above solution. If you use servers with multiple serial ports, you can connect each spare serial port to the console port of the next server, creating a ring of console connections (in some sort of order). This can be made to work reasonably well with the aid of the conserver software, but can be a bit confusing otherwise (i.e. remembering which port is connected to which console). And you are stuck if you need to use serial ports for other things (such as modems) or you have machines without spare ports. Or, if your budget exceeds your willingness to hack, you can buy an off-the-shelf solution. These vary in price and capability. See, for example, Lightwave, Perle, Avocent or Black Box. These solutions can be quite expensive - typically $USD100 - $USD400 per port. Our Solution In light of the above requirements, we chose a solution based on a dedicated PC running &unix; with a multiport serial card, and some software designed to handle serial consoles. It includes the following elements: A surplus PC. We used a &pentium; 166, with a PCI bus, 2Gbyte hard disk and 64Mb of RAM. This is a massive overkill for this task, and P-100, 500Mb, 32Mb would be more than enough. A PC &unix; system. We used &os; 4.3 as that is used for other tasks within our office. A multi-port serial card. We chose the &easyio; PCI 8-port card from Stallion Technologies. This cost us about $AUD740, or under $100/port, from Harris Technologies (which has lots of stuff but is by no means the cheapest place in town - shop around and you might get it a lot cheaper). This card has a big DB80 connector on the back, and a cable plugs into that which has a block with 8 RJ-45 sockets on it. (We chose the RJ-45 version as our entire cable plant is RJ-45. This allows us to patch connections from the required box to the console server without any special cables.) This is the only thing we needed to buy to make this all happen. We build two servers, one for each computer room, with 8 ports in one and 16 ports (via two &easyio; PCI cards) in the other. If we needed more than 16 ports, then another of the Stallion cards would be more cost-effective. We could conceivably support 128 ports in each server (with 2 EasyConnect 8/64 host cards and 8 16 port RJ-45 modules) for about $AUD12,000. A modem for remote access to the console server host when the network is down. We have not done this yet as the computer room is next door, but when we put a server in Sydney we will add the modem. The idea is that when the network is down, you can dial up and log into the server machine and run the console program locally. For security, we will probably leave the modem powered off and ask the gopher in Sydney to turn on the well-labelled button when we need it. A program called conserver. This program does all the magic required to enable remote access to consoles, and do the replaying and logging etc. It comes in two parts: a server called conserver that runs as a daemon and connects to the serial ports, handles logging etc, and a client program called console that can connect to the server, display console messages, send keystrokes (and BREAK), etc. This design covers all the major requirements except remote power cycling: Remote access comes because the console client program works across the network. Logging is handled by the conserver program. If the network is down, then we can use the console on the PC to run the console client locally. For remote sites, we can add a modem for dial-in access to the server command line to run the client. By patching the &solaris; servers (see ), we can avoid pranging the whole computer room when the console server PC crashes (or the power supply fails, or whatever). We already have pager alerts from another system we have installed, but the console server has all the required log info so that could easily be implemented if we needed. And it even has a modem for calling the pager company! We do not currently support remote power cycling. Some versions of the conserver program support this, but it does require specialised serial-controlled power boards. We have no immediate need for remote power cycling (we have a gopher in each remote office who can do it by remote control) so this is not a major problem, and we could add it easily should we ever see the need and get the appropriate hardware. This solution was very cheap. Total cost for the 9-port server was $AUD750 for the IO card, as we re-used a surplus PC and already owned the hardware for the special cables. If we had to buy everything, then it would still only cost around $AUD1500 for the 8-port server. Setting Up The Server Checking the Stallion driver &os; has adequate support for modern Stallion cards since 4.4 release. If you are running an older version of &os;, you will need to upgrade to a more modern version of &os; (which you should do anyway, to make sure your system is not vulnerable to known security issues). See the &os; Handbook for information about updating your system. Configuring a new kernel The Stallion driver is not included in the default GENERIC kernel, so you will need to create a kernel config file with the appropriate entries. See &man.stl.4; and the appropriate section of the &os; Handbook. Making The Devices You will need to make the device notes for the Stallion card (which are not made by default). A new version of /dev/MAKEDEV with Stallion support will have been created by the mergemaster run during the above procedure. If you have a Stallion card with more than 8 ports, then you will need to edit /dev/MAKEDEV and change the definition of maxport at about line 250. By default, MAKEDEV only makes device nodes for 8 ports to keep the size of the /dev directory down. Run a command like: &prompt.root; cd /dev/ && sh MAKEDEV cuaE0 to create dial-out devices for the first Stallion card. See the comments in MAKEDEV and the &man.stl.4; man page for more details. Compiling conserver See the section on conserver versions ; the version I use is available in the &os; ports collection; however, it is not the only one.) There are two ways to install conserver. You can either compile from the source or use the &os; ports framework. Using the ports framework Using the ports is a bit cleaner, as the package system can then keep track of installed software and cleanly delete them when not being used. I recommend using the comms/conserver-com port. Change into the port directory and (as root) type: &prompt.root; make DEFAULTHOST=consolehost install where consolehost is the name of the machine running the console server. Specifying this when the binary is compiled will avoid having to either specify it each time the program is run on remote hosts or having to maintain a conserver.cf file on every host. This command will fetch, patch, configure, compile and install the conserver application. You can then run make package to create a binary package that can be installed on all the other &os; hosts with &man.pkg.add.1;. For extra style points, you can make a two versions of the package: one for the console server machine without a DEFAULTHOST argument, and one for all the other hosts with a DEFAULTHOST argument. This will mean the console client program on the console server machine will default to localhost, which will work in the absence of name servers when the network is busted, and also allow trusted (i.e. no password required) connections via the localhost IP address for users logged into the console server machine (either via the console screen or the emergency backup modem). The version for the other machines with a DEFAULTHOST argument means users can just use the console client without specifying a hostname every time, and without needing to configure the conserver.cf file on every machine. From the source tarball If you prefer, you can download conserver and compile it yourself. You might need to do this if you want to install the console client on non-&os; systems. We run the client on our &solaris; hosts and it inter-operates with the &os;-hosted server with no problems. This allows anyone in the whole company (many of whom have PCs and no &os; host access on their desk) to access the console server. Download the file from the conserver.com FTP site. Extract it into a handy directory then configure it by running &prompt.user; ./configure The argument avoids having to specify the master server every time the client is run remotely (or keeping up-to-date config files on all remote hosts). The argument avoids having to update on every machine. Then type make and, as root, make install. Configuring conserver The conserver program is configured via a file called conserver.cf. This file usually lives in /usr/local/etc and is documented in the &man.conserver.cf.5; manual page. Our config file looks like this: LOGDIR=/var/log/consoles gallows:/dev/cuaE0:9600p:&: roo:/dev/cuaE1:9600p:&: kanga:/dev/cuaE2:9600p:&: %% allow: itga.com.au trusted: 127.0.0.1 buzz The first line means all the console log files by default go into the /var/log/consoles directory. The & in each line says the log file for that machine will be /var/log/consoles/machine. The next three lines show three machines to which we need to connect. We use the cuaEx devices rather than the ttyEx devices because console ports typically do not show carrier. This means that opening ttyEx would hang and conserver would never connect. Using the cuaEx device avoids this problem. Another solution would be to use the ttyEx devices and enable soft carrier on these ports, perhaps by setting this using the ttyiEx device in the /etc/rc.serial file. See the comments in this file for more details. Also see &man.sio.4; for information on the initial-state and locked-state devices. (The Stallion driver also supports these conventions). And see the &man.stty.1; for details on setting device modes. The last section shows that any user logged into the server machine has passwordless access to all consoles. We do this because there are no user accounts on this machine and it is safely isolated from the wide world behind our firewall. The allow line allows anyone on a machine inside our organisation to access the console server if they provide their password, which is recorded in the conserver.passwd file (see next section). Setting conserver passwords The conserver.passwd file contains the encrypted version of the password that each user. The file is documented in the conserver.cf(5) manual page. The only tricky bit is loading the file with encoded passwords. It appeared in &os; that was is no obvious way to generate an encrypted password for inclusion in another file (but see below). So I put together a quick hack perl script to do this: @rands = (); foreach (0..4) { push(@rands, rand 64); } $salt = join '', ('.', '/', 0..9, 'A'..'Z', 'a'..'z')[@rands]; $salt = '$1$' . $salt . '$'; print 'Enter password: '; `stty -echo`; $cleartext = <>; `stty echo`; chop($cleartext); print crypt($cleartext, $salt), "\n"; This uses the &os; MD5-style encrypted passwords. Running this on other &unix; variants, or on &os; with DES passwords, will likely need a different style of salt. &a.kris.email; has since pointed out you can get the same effect using the openssl passwd command: &prompt.user; openssl passwd -1 Password: password $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/ Starting <application>conserver</application> at system boot time There are two ways this can be done. Firstly, you could start up conserver from init by including an entry in /etc/ttys that is similar to this: cuaE0 "/usr/local/sbin/conserver" unknown on insecure This has two advantages: init will restart the master console server if it ever crashes for any reason (but we have not noticed any crashes so far), and it arranges for standard output of the conserver process to be directed to the named tty (in this case cuaE0). This is useful because you can plug a terminal into this port, and the conserver program will show all console output not otherwise captured by a client console connection. This is useful as a general monitoring tool to see if anything is going on. We set this terminal up in the computer room but visible from the main office. It is a very handy feature. The downside of running conserver from the ttys file is that it cannot run in daemon mode (else &man.init.8; would continually restart it). This means conserver will not write a PID file, which makes it hard to rotate the log files. So we start conserver from an rc.d script. If you installed conserver via the port, there will be a conserver.sh.sample file installed in /usr/local/etc/rc.d. Copy and/or rename this to conserver.sh to enable conserver to start at boot time. In fact we use a modified version of this script which also connects conserver to a terminal via a tty device so we can monitor unwatched console output. Our conserver.sh script looks like this: #!/bin/sh # # Startup for conserver # PATH=/usr/bin:/usr/local/bin case "$1" in 'start') TTY=/dev/cuaE7 conserver -d > $TTY # get NL->CR+NL mapping so msgs look right stty < /dev/cuaE7 opost onlcr echo -n ' conserver' ;; 'stop') kill `cat /var/run/conserver.pid` && echo -n ' conserver' ;; *) echo "Usage: $0 { start | stop }" ;; esac exit 0 Note the use of cuaE0 device and the need to set tty modes for proper NL-<CR handling). Keeping the log files trimmed &os; has a program called newsyslog that will automatically handle log file trimming. Just add some lines to the configuration file /etc/newsyslog.conf for the console logs: # # The log files from conserver /var/log/consoles/gallows 644 10 1000 * Z /var/run/conserver.pid /var/log/consoles/kanga 644 10 1000 * Z /var/run/conserver.pid /var/log/consoles/roo 644 10 1000 * Z /var/run/conserver.pid This tells newsyslog (which is run from cron every hour on the hour) that the console log files should be archived and compressed once they reach 1Mb, that we should keep 10 of them, and that to signal the server program you send a SIGHUP to the process whose PID is in the conserver.pid file. This is the master server, and it will arrange to signal all the child processes. Yes, this will send a HUP to all clients whenever a single log file needs rotating, but that is quite cheap. See &man.newsyslog.8; for details. Cabling This is always the hardest part of this kind of problem. We had only a dozen or so cables/headshells to build, and we already had a collection of the appropriate crimping tools and hardware, so we did it ourselves. But if you are not set up for this, or you have a large number of cables to make, then you might consider getting some cables custom made. Look in the yellow pages, there are a surprising number of places that do this! Getting custom-made cabling is good, and you can get much more professional results, but can be expensive. For example, the RJ-45 to DB-25 adapter kits described below are about $10 each; custom-made headshells are about twice that (and take a couple of weeks to arrive). Similarly, crimping custom RJ-45 to RJ-45 leads is quite cheap (say, $5 each) but it takes a fair amount of time. Custom made RJ-45 socket to RJ-45 plug converters cost about $25 each. We have settled on RJ-45 Cat-V cabling for all our office and computer room cabling needs. This included patching between racks in the computer room. For serial connections, we use patchable headshells that have RJ-45 sockets on the back. This allows us to patch whatever RJ-45–DB-25 connections we need. Which is just as well, because there are many incompatible ways to represent serial connections on the RJ-45 plug. So the cabling has to be very careful to use the right mapping. RJ-45 colors RJ-45 cables and plugs have 8 pins/conductors. These are used as 4 matched pairs. There are a couple of conventions about how the pairs are mapped onto pins, but 100baseT uses the most common (known as EIA 586B). There are three common color-coding conventions for the individual conductors in RJ-45 cables. They are: <!-- XXX: Add title for this table --> Pin Scheme 1 Scheme 2 (EIA 568B) Scheme 3 (EIA 568A) Pair 1 Blue White+Green White+Orange 2+ 2 Orange Green Orange 2- 3 Black White+Orange White+Green 3+ 4 Red Blue Blue 1+ 5 Green White+Blue White+Blue 1- 6 Yellow Orange Green 3- 7 Brown White+Brown White+Brown 4+ 8 White or Grey Brown Brown 4-
Note EIA 468A and EIA 568B are very similar, simply swapping the colors assigned to pair 2 and pair 3. See for example the Cabletron Tech Support Site for more details. The pins in the RJ-45 plug are numbered from 1 to 8. Holding a patch lead with the cable pointing down and the clip away from you, pin 1 is at the left. Or, looking into an RJ-45 socket with the clip to the top, pin 1 is on the right. The following illustration (shamelessly lifted from the Cabletron web site above) shows it pretty well: We have four classes of equipment to deal with in our setup: Sun servers Sun servers operate as DTE (i.e. send data on TxD and read RxD, and assert DTR) with a female DB-25 socket on board. So we need to create a headshell for the Stallion that operates as DCE and has a male DB-25 plug (i.e. acts as a null modem cable as well as converts from RJ-45 to DB-25). We use headshells that have an RJ-45 socket in them and 8 short flyleads with DB-25 pins on the end. These pins can be inserted into the DB-25 plug as required. This allows us to create a custom RJ-45-DB-25 mapping. We used a couple of different sorts, including the MOD-TAP part no. 06-9888-999-00 and the FA730 series from Black Box. On our version of the headshells, these flyleads had the following colours (from Pin 1-8): Blue, Orange, Black, Red, Green, Yellow, Brown, White. (Looking into an RJ-45 socket, with the clip towards the top, pin 1 is on the right.) This is how they are connected to the DB-25 socket: <!-- XXX: Add a title here --> Stallion RJ-45 Pin Colour Signal Sun DB-25 Male Pin RS232 Signal 1 Blue DCD 20 DTR 2 Orange RTS 5 CTS 3 Black Chassis Gnd 1 Chassis Gnd 4 Red TxD 3 RxD 5 Green RxD 2 TxD 6 Yellow Signal Gnd 7 Signal Gnd 7 Brown CTS 4 RTS 8 White RTS 8 DCD
Note that colours may be different for your cables/headshells. In particular, pin 8 may be grey instead of white. Remember to label the headshell clearly, in a way that will not fade/fall off/rub off with time! Cisco 16xx/26xx/36xx Routers I think that all Cisco gear that has RJ-45 console ports and runs &ios; will have the same cable requirements. But best to check first. We have tried this on 1600s and 2600s only. Both the Stallion card and the 2600 have RJ-45 connections, but of course they are not compatible. So you need to crimp up a special RJ-45-RJ-45 cable. And this cable must be plugged in the right way round! We use normal RJ-45 flyleads from the router to the patch panel, then the special flylead from the patch panel to the Stallion card. We built two special Stallion-Cisco leads by cutting in half a 2m flylead and crimping an RJ-45 with the appropriate pinouts to each free end. The original connector will be the Cisco end of the cable, the new crimped connector will be the Stallion end. Holding the RJ-45 connector on the flylead with the cable pointing down and the clip pointing away, this is the order of the colours of the cables in our flylead (pins 1-8, from L to R): white/green, green, white/orange, blue, white/blue, orange, white/brown, brown. For the Stallion end, trim and discard the brown/white+brown and green/white+green pairs. Then holding the RJ-45 plug in the same manner (cable down, clip away), the connections should be (from L to R): None, None, Blue, Orange, White/Orange, White/Blue, None, None, as shown: <!-- XXX: add title for this table --> Cisco RJ-45 Pin Colour Cisco Signal Stallion RJ-45 Pin Stallion Signal 1 White/Green RTS N/C   2 Green DTR N/C   3 White/Orange TxD 5 RxD 4 Blue Gnd 3 Gnd 5 White/Blue Gnd 6 Gnd 6 Orange RxD 4 TxD 7 White/Brown DSR N/C   8 Brown CTS N/C  
Note again that colours may be different for your cables/headshells. Carefully label the cable, and each end of the cable, and test it. If it does not work, testing is really hard as they do not make RJ-45 serial line testers! Let me state this more strongly: Be very sure that you label this cable in a way that is easily, instantly and permanently recognisable as a special cable and not easily confused with normal drop cables. Some suggestions (from Hugh Irvine): Make them out of different coloured cable. For marking the ends, clear heat-shrink tubing slipped over printed labels *before* putting on the connectors is the best way I have seen for marking what they are. You can also use Panduit or similar tags that you put on with nylon tie straps, but I find the ink wears off the tags. Cisco &catalyst; switches Astoundingly, the pinout on the console ports of the &catalyst; switches is actually different to the pinout used on the 26xx-series Cisco hardware. I think the way to tell which is which is by considering the operating software. If it uses &ios;, then the previous pinout is required. If it uses the switch software, then this pinout is required. Fortunately, while the pinouts are different, the &catalyst; pinout is simply a mirror image of the pinout for the 2600. Even more fortunately, the Ciscos (both &catalyst; switches and 2600s) seem to ship with a special rollover cable, which is exactly what is required in this case. We use the rollover cable from the &catalyst; switches to the patch panel, then the same cable as above for the 2600s from the patch panel to the Stallion card, and it all works just fine. This rollover cable is an RJ-45-RJ-45 cable and is intended to be used with the shipped (hardwired) RJ-45 - DB-25 and RJ-45–DB-9 headshells for console connections. Ours are 2m long, either light blue or black, and are quite flat. Attempts to use them for 100baseT Ethernet will fail miserably! You can tell it is a rollover cable by holding both ends with the cable pointing down and the clip pointing away from you. Check the colour of the leads in each pin in the two connectors, they should be mirror images. (In our case, one goes grey-orange-black-red-green-yellow-blue-brown, the other brown-blue-yellow-green-red-black-orange-grey). This is a rollover cable. If you do not have a rollover cable present, then you can use the same cable as for the 26xx except plug it in the other way around (i.e. original 8-pin plug goes into the Stallion, the new crimped plug with only 4 active wires goes into the &catalyst; switch). &os; servers (or any other &i386; PC systems using a serial console) We run &os; 4 on a couple of &i386; PCs for various peripheral uses. &os; usually uses a screen and keyboard for the console, but can be configured to use a serial port (usually the first serial port known as COM1 in DOS/&windows; or ttyd0 in &unix;). The cabling for these servers depends on the PC hardware. If the PC has DB-25 female socket on board (as most older PCs do), then the same headshell as works for the Sun server above will work fine. If the PC has DB-9 male plug on board (as more recent PCs tend to do), then there are two choices. Either use a DB-9 to DB-25 converter (this is not recommended as it can lead to unreliable connections over the long term as the adapter is bumped/works loose), or build an RJ-45 to DB-9 cable as follows: <!-- XXX: add title for this table --> Stallion RJ-45 Pin Colour Signal PC DB-9 Female Pin RS232 Signal 1 Blue DCD 4 DTR 2 Orange RTS 8 CTS 3 Black Chassis Gnd N/C   4 Red TxD 2 RxD 5 Green RxD 3 TxD 6 Yellow Signal Gnd 5 Signal Gnd 7 Brown CTS 7 RTS 8 White RTS 1 DCD
See for tips on configuring &os; to use a serial console. On Sun Systems And Break Anyone who has turned off a terminal used as a console for a Sun system will know what happens and why this is a problem. Sun hardware recognises a serial BREAK as a command to halt the OS and return to the ROM monitor prompt. A serial BREAK is an out-of-band signal on an RS-232 serial port that involves making the TX DATA line active (i.e. pulled down to less than -5V) for more than two whole character times (or about 2ms on a 9600bps line). Alas, this BREAK signal is all to easily generated by serial hardware during power-on or power-off. And the Stallion card does, in fact, generate breaks when the power to the PC fails. Unless fixed, this problem would mean that every Sun box connected to the console server would be halted whenever the power failed (due to dead power supplies, or fat-fingered operators unplugging it, or whatever). This is clearly not an acceptable situation. Fortunately, Sun have come up with a set of fixes for this. For &solaris; 2.6 and later, the kbd(1) command can be used to disable the ROM-on-BREAK behaviour. This is a good start, but leaves you out of luck in the situation where a break is needed to get into a broken machine. Starting with &solaris; 8, the kbd command can also be used to enable an alternate break sequence using the kbd -a alternate command. When this is set, the key sequence ReturnTildeCtrlB (within 5 seconds) will drop to the ROM. You can enable this permanently by editing the /etc/default/kbd file; see the kbd(1) man page. Note that this alternate break sequence is only active once the kernel has started running multiuser and processed the default file. While the ROM is active (during power-on and during the boot process) and while running single-user, you still need to use a BREAK to get to the ROM prompt. The console client can cause the server to send a BREAK using the escape sequence Esccl1. If you have a Sun software support contract, there are patches available for &solaris; 2.6 and 2.7 that add the alternate break capability integrated into &solaris; 2.8. &solaris; 2.6 requires patch 105924-10 or higher. &solaris; 2.7 requires patch 107589-02 or higher. We have added this patch to all our &solaris; 2.6 servers, and added it (and the entry in the /etc/default/kbd file) to our jumpstart configuration so it will automatically be added to every new install. We have confirmed by direct testing that neither the Cisco 16xx, 26xx, or &catalyst; hardware suffers from the BREAK sent when the Stallion card loses power. Contemporary Cisco software listens for BREAK signal only for first 30 seconds after power-on or reboot. Using a Serial Console on &os; The procedure for doing this is described in detail in the &os; Handbook. This is a quick summary. Check the kernel configuration Check that the kernel configuration file has flags 0x10 in the config line for the sio0 device. This signals this device (known as COM1 in DOS/&windows; or /dev/ttyd0 in &os;) can be used as a console. This flag is set on the GENERIC and LINT sample configs, so is likely to be set in your kernel. Create the <filename>/boot.conf</filename> file This file should be created containing a single line containing just -h (minus the quotes). This tells the &os; boot blocks to use the serial console. Edit <filename>/etc/ttys</filename> Edit this file and make the following changes. If you are not going to have any keyboard/video screen on this server at all, you should find all the lines for ttyv devices like ttyv1 "/usr/libexec/getty Pc" cons25 on secure Change the on to off. This will stop login screens being run on the useless video consoles. Find the line containing ttyd0. Change it from ttyd0 "/usr/libexec/getty std.9600" dialup off secure to ttyd0 "/usr/libexec/getty std.9600" vt100 on secure (replacing vt100 with the term type of your console. The xterms terminal type might be a good choice). This allows you to log in to the console port once the system is running multi-user. Reboot and off you go! Security Implications The client-server protocol for conserver requires the user of the console client to enter a password. This password is passed across the net in cleartext! This means conserver is not really suitable for use across untrusted networks (such as the Internet). Use of conserver-only passwords (in the conserver.passwd file) slightly mitigate this problem, but anyone sniffing a conserver connection can easily get console access, and from there prang your machine using the console break sequence. For operating across the Internet, use something secure like SSH to log into to the server machine, and run the console client there. On Conserver Versions The conserver program has fractured into a number of versions. The home page referenced below seems to be the latest and most featureful version around, and for July 2004 carries a version number of 8.1.9. This is maintained by Bryan Stansell bryan@conserver.com, who has brought together the work of many people (listed on his webpage). The &os; ports collection contains a port for version 8.5 of conserver at comms/conserver. This seems to be older and less featureful than the 8.1.9 version (in particular, it does not support consoles connected to terminal server ports and does not support a conserver.passwd file), and is written in a fairly idiosyncratic manner (using a preprocessor to generate C code). Version 8.5 is maintained by Kevin S. Braunsdorf ksb+conserver@sa.fedex.com who did most of the original work on conserver, and whose work Bryan Stansell is building on. The 8.5 version does support one feature not in the 8.1.9 version (controlling power to remote machines via a specific serial-interfaced power controller hardware). Beginning with December 2001, Brian's version (currently 8.1.9) is also presented in ports collection at comms/conserver-com. We therefore recommend you to use this version as it is much more appropriate for console server building. Links Homepage for the latest version of conserver. ftp://ftp.conserver.com/conserver/conserver-8.1.9.tar.gz The source tarball for version 8.1.9 of conserver. Homepage of Stallion Technologies. Davis Harris' Minor Scroll of Console Knowledge contains a heap of useful information on serial consoles and serial communications in general. The Greater Scroll of Console Knowledge contains even more specific information on connecting devices to various other devices. Oh the joy of standards! Doug Hughes has a similar console server, based on the screen program and an old &sunos; host. The Real Weasel company makes a ISA or PCI video card that looks like a PC video card but actually talks to a serial port. This can be used to implement serial consoles on PC hardware for operating systems that can not be forced to use serial console ports early enough. Manual Pages console(8) conserver(8) conserver.cf(5) + +
diff --git a/en_US.ISO8859-1/articles/contributing-ports/article.xml b/en_US.ISO8859-1/articles/contributing-ports/article.xml index f9778f0e7d..c6b198ce22 100644 --- a/en_US.ISO8859-1/articles/contributing-ports/article.xml +++ b/en_US.ISO8859-1/articles/contributing-ports/article.xml @@ -1,830 +1,832 @@
Contributing to the FreeBSD Ports Collection Abstract This article describes the ways in which an individual can contribute to the FreeBSD Ports Collection. Sam Lawrance Mark Linimon &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ contributing to ports Introduction 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! 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. What you can do to 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. Creating a new port There is a separate document available to help guide you through creating (and upgrading) a port called the Porter's Handbook. The Porter's Handbook is the best reference to working with the ports system. It provides details about how the ports system operates and discusses recommended practices. 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. You should be running 7-STABLE or 8-STABLE, preferably the latter. 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-i386 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 Regularly check the automated ports building cluster, pointyhat, and the distfiles scanner to see if any of the ports you maintain are failing to build or fetch (see resources for more information about these systems). Reports of failures may also come to you from other users or automated systems via email. Collect information Once you are aware of a problem, collect information to help you fix it. Build errors reported by pointyhat 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 INDEX file 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 GNATS 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. Pointyhat is the ports build cluster. You can use Pointyhat to check port build logs across all architectures and major releases. 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. The ports tinderbox is the most thorough way to test a port through the entire cycle of installation, packaging, and deinstallation. It features a command-line interface but also can be controlled via a web interface. Please see ports/ports-mgmt/tinderbox. More documentation is located at the marcuscom tinderbox 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. + +
diff --git a/en_US.ISO8859-1/articles/contributing/article.xml b/en_US.ISO8859-1/articles/contributing/article.xml index bda4185f30..c2061bfc69 100644 --- a/en_US.ISO8859-1/articles/contributing/article.xml +++ b/en_US.ISO8859-1/articles/contributing/article.xml @@ -1,550 +1,552 @@
Contributing to FreeBSD This article describes the different ways in which an individual or organization may contribute to the FreeBSD Project. Jordan Hubbard Contributed by &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ contributing So you want to contribute to FreeBSD? That is great! FreeBSD relies on the contributions of its user base to survive. Your contributions are not only appreciated, they are vital to FreeBSD'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 available to do it, and more help is always appreciated. The FreeBSD 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 presentation, to the system installer and highly specialized types of kernel development. People of any skill level, in almost any area, can almost certainly help the project. Commercial entities engaged in FreeBSD-related enterprises are also encouraged to contact us. Do you need a special extension to make your product work? You will find us receptive to your requests, given that they are not too outlandish. Are you working on a value-added product? Please let us know! We may be able to work cooperatively on some aspect of it. The free software world is challenging many existing assumptions about how software is developed, sold, and maintained, and we urge you to at least give it a second look. What Is Needed The following list of tasks and sub-projects represents something of an amalgam of various TODO lists and user requests. Ongoing Non-Programmer Tasks Many people who are involved in FreeBSD are not programmers. The Project includes documentation writers, Web designers, and support people. All that these people need to contribute is an investment of time and a willingness to learn. Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (Docbook is not difficult to learn, but there is no objection to ASCII submissions). Help translate FreeBSD documentation into your native language. If documentation already exists for your language, you can help translate additional documents or verify that the translations are up-to-date. First take a look at the Translations FAQ in the FreeBSD Documentation Project Primer. You are not committing yourself to translating every single FreeBSD document by doing this — as a volunteer, you can do as much or as little translation as you desire. Once someone begins translating, others almost always join the effort. If you only have the time or energy to translate one part of the documentation, please translate the installation instructions. Read the &a.questions; and &ng.misc; 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 can also be a source of ideas for things to work on. Ongoing Programmer Tasks Most of the tasks listed here require either a considerable investment of time, or an in-depth knowledge of the FreeBSD kernel, or both. However, there are also many useful tasks which are suitable for weekend hackers. If you run FreeBSD-CURRENT and have a good Internet connection, there is a machine current.FreeBSD.org which builds a full release once a day—every now and again, try to install the latest release from it and report any failures in the process. Read the &a.bugs;. There might be a problem you can comment constructively on or with patches you can test. Or you could even try to fix one of the problems yourself. If you know of any bug fixes which have been successfully applied to -CURRENT but have not been merged into -STABLE after a decent interval (normally a couple of weeks), send the committer a polite reminder. Move contributed software to src/contrib in the source tree. Make sure code in src/contrib is up to date. Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. Fix warnings for ports which do deprecated things like using gets() or including malloc.h. If you have contributed any ports and you had to make &os;-specific changes, send your patches back to the original authors (this will make your life easier when they bring out the next version). Get copies of formal standards like &posix;. You can get some links about these standards at the FreeBSD C99 & POSIX Standards Conformance Project web site. Compare FreeBSD's behavior to that required by the standard. If the behavior differs, particularly in subtle or obscure corners of the specification, send in a PR about it. If you are able, figure out how to fix it and include a patch in the PR. If you think the standard is wrong, ask the standards body to consider the question. Suggest further tasks for this list! Work through the PR Database problem reports database The FreeBSD PR list shows all the current active problem reports and requests for enhancement that have been submitted by FreeBSD users. The PR database includes both programmer and non-programmer tasks. Look through the open PRs, and see if anything there takes your interest. Some of these might be very simple tasks that just need an extra pair of eyes to look over them and confirm that the fix in the PR is a good one. Others might be much more complex, or might not even have a fix included at all. Start with the PRs that have not been assigned to anyone else. If a PR is assigned to someone else, but it looks like something you can handle, email the person it is assigned to and ask if you can work on it—they might already have a patch ready to be tested, or further ideas that you can discuss with them. Pick one of the items from the <quote>Ideas</quote> page The &os; list of projects and ideas for volunteers is also available for people willing to contribute to the &os; project. The list is being regularly updated and contains items for both programmers and non-programmers with information about each project. How to Contribute Contributions to the system generally fall into one or more of the following 5 categories: Bug Reports and General Commentary An idea or suggestion of general technical interest should be mailed to the &a.hackers;. Likewise, people with an interest in such things (and a tolerance for a high volume of mail!) may subscribe to the &a.hackers;. See The FreeBSD Handbook for more information about this and other mailing lists. If you find a bug or are submitting a specific change, please report it using the &man.send-pr.1; program or its WEB-based equivalent. Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. If the patch is suitable to be applied to the source tree put [PATCH] in the synopsis of the report. When including patches, do not use cut-and-paste because cut-and-paste turns tabs into spaces and makes them unusable. When patches are a lot larger than 20KB, consider compressing them (eg. with &man.gzip.1; or &man.bzip2.1;) and using &man.uuencode.1; to include their compressed form in your problem report. After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can update us with details about the problem by sending mail to &a.bugfollowup;. Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some reason, unable to use the &man.send-pr.1; command, then you may ask someone to file it for you by sending mail to the &a.bugs;. See also this article on how to write good problem reports. Changes to the Documentation documentation submissions Changes to the documentation are overseen by the &a.doc;. Please look at the FreeBSD Documentation Project Primer for complete instructions. Send submissions and changes (even small ones are welcome!) using &man.send-pr.1; as described in Bug Reports and General Commentary. Changes to Existing Source Code FreeBSD-CURRENT An addition or change to the existing source code is a somewhat trickier affair and depends a lot on how far out of date you are with the current state of FreeBSD development. There is a special on-going release of FreeBSD known as FreeBSD-CURRENT which is made available in a variety of ways for the convenience of developers working actively on the system. See The FreeBSD Handbook for more information about getting and using FreeBSD-CURRENT. Working from older sources unfortunately means that your changes may sometimes be too obsolete or too divergent for easy re-integration into FreeBSD. Chances of this can be minimized somewhat by subscribing to the &a.announce; and the &a.current; lists, where discussions on the current state of the system take place. Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with the &man.diff.1; command. The preferred &man.diff.1; format for submitting patches is the unified output format generated by diff -u. diff &prompt.user; diff -u oldfile newfile or &prompt.user; diff -u -r -N olddir newdir would generate a set of unified diffs for the given source file or directory hierarchy. See &man.diff.1; for more information. Once you have a set of diffs (which you may test with the &man.patch.1; command), you should submit them for inclusion with FreeBSD. Use the &man.send-pr.1; program as described in Bug Reports and General Commentary. Do not just send the diffs to the &a.hackers; or they will get lost! We greatly appreciate your submission (this is a volunteer project!); because we are busy, we may not be able to address it immediately, but it will remain in the PR database until we do. Indicate your submission by including [PATCH] in the synopsis of the report. uuencode If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a tar file and run the &man.uuencode.1; program on it. Archives created with &man.shar.1; are also welcome. If your change is of a potentially sensitive nature, such as if you are unsure of copyright issues governing its further distribution then you should send it to &a.core; directly rather than submitting it with &man.send-pr.1;. The &a.core; reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also very busy and so you should only send mail to them where it is truly necessary. Please refer to &man.intro.9; and &man.style.9; for some information on coding style. We would appreciate it if you were at least aware of this information before submitting code. New Code or Major Value-Added Packages In the case of a significant contribution of a large body work, or the addition of an important new feature to FreeBSD, it becomes almost always necessary to either send changes as uuencoded tar files or upload them to a web or FTP site for other people to access. If you do not have access to a web or FTP site, ask on an appropriate FreeBSD mailing list for someone to host the changes for you. When working with large amounts of code, the touchy subject of copyrights also invariably comes up. Acceptable copyrights for code included in FreeBSD are: The BSD copyrightBSD copyright. This copyright is most preferred due to its no strings attached nature and general attractiveness to commercial enterprises. Far from discouraging such commercial use, the FreeBSD Project actively encourages such participation by commercial interests who might eventually be inclined to invest something of their own into FreeBSD. GPL GNU General Public License GNU General Public License The GNU General Public License, or GPL. This license is not quite as popular with us due to the amount of extra effort demanded of anyone using the code for commercial purposes, but given the sheer quantity of GPL'd code we currently require (compiler, assembler, text formatter, etc) it would be silly to refuse additional contributions under this license. Code under the GPL also goes into a different part of the tree, that being /sys/gnu or /usr/src/gnu, and is therefore easily identifiable to anyone for whom the GPL presents a problem. Contributions coming under any other type of copyright must be carefully reviewed before their inclusion into FreeBSD will be considered. Contributions for which particularly restrictive commercial copyrights apply are generally rejected, though the authors are always encouraged to make such changes available through their own channels. To place a BSD-style copyright on your work, include the following text at the very beginning of every source code file you wish to protect, replacing the text between the %% with the appropriate information: Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $&os;$ For your convenience, a copy of this text can be found in /usr/share/examples/etc/bsd-style-copyright. Money, Hardware or Internet Access We are always very happy to accept donations to further the cause of the FreeBSD Project and, in a volunteer effort like ours, a little can go a long way! Donations of hardware are also very important to expanding our list of supported peripherals since we generally lack the funds to buy such items ourselves. <anchor id="donations"/>Donating Funds The FreeBSD Foundation is a non-profit, tax-exempt foundation established to further the goals of the FreeBSD Project. As a 501(c)3 entity, the Foundation is generally exempt from US federal income tax as well as Colorado State income tax. Donations to a tax-exempt entity are often deductible from taxable federal income. Donations may be sent in check form to:
The FreeBSD Foundation P.O. Box 20247, Boulder, CO 80308 USA
The FreeBSD Foundation is now able to accept donations through the web with PayPal. To place a donation, please visit the Foundation web site. More information about the FreeBSD Foundation can be found in The FreeBSD Foundation -- an Introduction. To contact the Foundation by email, write to bod@FreeBSDFoundation.org. Donating Hardware donations The FreeBSD Project happily accepts donations of hardware that it can find good use for. If you are interested in donating hardware, please contact the Donations Liaison Office. + +
diff --git a/en_US.ISO8859-1/articles/contributors/article.xml b/en_US.ISO8859-1/articles/contributors/article.xml index 6d66577526..b0c1671a24 100644 --- a/en_US.ISO8859-1/articles/contributors/article.xml +++ b/en_US.ISO8859-1/articles/contributors/article.xml @@ -1,424 +1,426 @@ %contrib.ent; ]>
Contributors to FreeBSD &tm-attrib.freebsd; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ This article lists individuals and organizations who have made a contribution to FreeBSD. Donors Gallery As of 2010, the following section is several years out-of-date. Donations from the past several years appear here. The FreeBSD Project is indebted to the following donors and would like to publicly thank them here! Contributors to the central server project: The following individuals and businesses made it possible for the FreeBSD Project to build a new central server machine, which has replaced freefall.FreeBSD.org at one point, by donating the following items: &a.mbarkah.email; and his employer, Hemisphere Online, donated a Pentium Pro (P6) 200MHz CPU ASA Computers donated a Tyan 1662 motherboard. Joe McGuckin joe@via.net of ViaNet Communications donated a Kingston ethernet controller. Jack O'Neill jack@diamond.xtalwind.net donated an NCR 53C875 SCSI controller card. Ulf Zimmermann ulf@Alameda.net of Alameda Networks donated 128MB of memory, a 4 Gb disk drive and the case. Direct funding: The following individuals and businesses have generously contributed direct funding to the project: Annelise Anderson ANDRSN@HOOVER.STANFORD.EDU &a.dillon.email; Blue Mountain Arts Epilogue Technology Corporation &a.sef.email; Global Technology Associates, Inc Don Scott Wilde Gianmarco Giovannelli gmarco@masternet.it Josef C. Grosch joeg@truenorth.org Robert T. Morris &a.chuckr.email; Kenneth P. Stox ken@stox.sa.enteract.com of Imaginary Landscape, LLC. Dmitry S. Kohmanyuk dk@dog.farm.org Laser5 of Japan (a portion of the profits from sales of their various FreeBSD CDROMs). Fuki Shuppan Publishing Co. donated a portion of their profits from Hajimete no FreeBSD (FreeBSD, Getting started) to the FreeBSD and XFree86 projects. ASCII Corp. donated a portion of their profits from several FreeBSD-related books to the FreeBSD project. Yokogawa Electric Corp has generously donated significant funding to the FreeBSD project. BuffNET Pacific Solutions Siemens AG via Andre Albsmeier andre.albsmeier@mchp.siemens.de Chris Silva ras@interaccess.com Hardware contributors: The following individuals and businesses have generously contributed hardware for testing and device driver development/support: BSDi for providing the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are being used for our development work, to say nothing of the network access and other donations of hardware resources. Compaq has donated a variety of Alpha systems to the FreeBSD Project. Among the many generous donations are 4 AlphaStation DS10s, an AlphaServer DS20, AlphaServer 2100s, an AlphaServer 4100, 8 500Mhz Personal Workstations, 4 433Mhz Personal Workstations, and more! These machines are used for release engineering, package building, SMP development, and general development on the Alpha architecture. TRW Financial Systems, Inc. provided 130 PCs, three 68 GB file servers, twelve Ethernets, two routers and an ATM switch for debugging the diskless code. Dermot McDonnell donated the Toshiba XM3401B CDROM drive currently used in freefall. Chuck Robey chuckr@glue.umd.edu contributed his floppy tape streamer for experimental work. Larry Altneu larry@ALR.COM, and &a.wilko.email;, provided Wangtek and Archive QIC-02 tape drives in order to improve the wt driver. Ernst Winter (Deceased) contributed a 2.88 MB floppy drive to the project. This will hopefully increase the pressure for rewriting the floppy disk driver. Tekram Technologies sent one each of their DC-390, DC-390U and DC-390F FAST and ULTRA SCSI host adapter cards for regression testing of the NCR and AMD drivers with their cards. They are also to be applauded for making driver sources for free operating systems available from their FTP server . Larry M. Augustin contributed not only a Symbios Sym8751S SCSI card, but also a set of data books, including one about the forthcoming Sym53c895 chip with Ultra-2 and LVD support, and the latest programming manual with information on how to safely use the advanced features of the latest Symbios SCSI chips. Thanks a lot! &a.kuku.email; donated an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver development. Mike Tancsa mike@sentex.ca donated four various ATM PCI cards in order to help increase support of these cards as well as help support the development effort of the netatm ATM stack. Special contributors: BSDi (formerly Walnut Creek CDROM) has donated almost more than we can say (see the 'About the FreeBSD Project' section of the FreeBSD Handbook for more details). In particular, we would like to thank them for the original hardware used for freefall.FreeBSD.org, our primary development machine, and for thud.FreeBSD.org, a testing and build box. We are also indebted to them for funding various contributors over the years and providing us with unrestricted use of their T1 connection to the Internet. The interface business GmbH, Dresden has been patiently supporting &a.joerg.email; who has often preferred FreeBSD work over paid work, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or flaky to work with it... Berkeley Software Design, Inc. has contributed their DOS emulator code to the remaining BSD world, which is used in the doscmd command. The FreeBSD Developers These are the people who have commit privileges and do the engineering work on the FreeBSD source tree. All core team members are also developers. (in alphabetical order by last name): &contrib.committers; Core Team Alumni core team The following people were members of the FreeBSD core team during the periods indicated. We thank them for their past efforts in the service of the FreeBSD project. In rough reverse chronological order: &contrib.corealumni; Development Team Alumni development team The following people were members of the FreeBSD development team during the periods indicated. We thank them for their past efforts in the service of the FreeBSD project. In rough reverse chronological order: &contrib.develalumni; Ports Management Team Alumni portmgr team The following people were members of the FreeBSD portmgr team during the periods indicated. We thank them for their past efforts in the service of the FreeBSD project. In rough reverse chronological order: &contrib.portmgralumni; Development Team: In Memoriam development team During the many years that the FreeBSD Project has been in existence, sadly, some of our developers have passed away. Here are some remembrances. In rough reverse chronological order of their passing: &contrib.develinmemoriam; Derived Software Contributors This software was originally derived from William F. Jolitz's 386BSD release 0.1, though almost none of the original 386BSD specific code remains. This software has been essentially re-implemented from the 4.4BSD-Lite release provided by the Computer Science Research Group (CSRG) at the University of California, Berkeley and associated academic contributors. There are also portions of NetBSD and OpenBSD that have been integrated into FreeBSD as well, and we would therefore like to thank all the contributors to NetBSD and OpenBSD for their work. Additional FreeBSD Contributors (in alphabetical order by first name): &contrib.additional; 386BSD Patch Kit Patch Contributors (in alphabetical order by first name): &contrib.386bsd; + +
diff --git a/en_US.ISO8859-1/articles/cups/article.xml b/en_US.ISO8859-1/articles/cups/article.xml index 7f4f83578b..107c9e2b60 100644 --- a/en_US.ISO8859-1/articles/cups/article.xml +++ b/en_US.ISO8859-1/articles/cups/article.xml @@ -1,391 +1,393 @@
CUPS on FreeBSD Chess Griffin
chess@chessgriffin.com
 &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ An article about configuring CUPS on &os;. An Introduction to the Common Unix Printing System (CUPS) printing CUPS CUPS, the Common UNIX Printing System, provides a portable printing layer for &unix;-based operating systems. It has been developed by Easy Software Products to promote a standard printing solution for all &unix; vendors and users. CUPS uses the Internet Printing Protocol (IPP) as the basis for managing print jobs and queues. The Line Printer Daemon (LPD), Server Message Block (SMB), and AppSocket (aka JetDirect) protocols are also supported with reduced functionality. CUPS adds network printer browsing and PostScript Printer Description (PPD) based printing options to support real-world printing under &unix;. As a result, CUPS is ideally-suited for sharing and accessing printers in mixed environments of &os;, &linux;, &macos; X, or &windows;. The main site for CUPS is . Installing the CUPS Print Server CUPS can be installed from ports or by using a precompiled binary package. To install CUPS from ports, issue the following command from a root terminal: &prompt.root; cd /usr/ports/print/cups && make install clean To install CUPS using a precompiled binary, issue the following command from a root terminal: &prompt.root; pkg_add -r cups Other optional, but recommended, ports or packages are print/gutenprint-cups and print/hplip, both of which add drivers and utilities for a variety of printers. Once installed, the CUPS configuration files can be found in the directory /usr/local/etc/cups. Configuring the CUPS Print Server After installation, a few files must edited in order to configure the CUPS server. First, create or modify, as the case may be, the file /etc/devfs.rules and add the following information to set the proper permissions on all potential printer devices and to associate printers with the cups user group: [system=10] add path 'unlpt*' mode 0660 group cups add path 'ulpt*' mode 0660 group cups add path 'lpt*' mode 0660 group cups add path 'usb/X.Y.Z' mode 0660 group cups Note that X, Y, and Z should be replaced with the target USB device listed in the /dev/usb directory that corresponds to the printer. To find the correct device, examine the output of &man.dmesg.8;, where ugenX.Y lists the printer device, which is a symbolic link to a USB device in /dev/usb. Next, add two lines to /etc/rc.conf as follows: cupsd_enable="YES" devfs_system_ruleset="system" These two entries will start the CUPS print server on boot and invoke the local devfs rule created above, respectively. In order to enable CUPS printing under certain µsoft.windows; clients, the line below should be uncommented in /usr/local/etc/cups/mime.types and /usr/local/etc/cups/mime.convs: application/octet-stream Once these changes have been made, the &man.devfs.8; and CUPS systems must both be restarted, either by rebooting the computer or issuing the following two commands in a root terminal: &prompt.root; /etc/rc.d/devfs restart &prompt.root; /usr/local/etc/rc.d/cupsd restart Configuring Printers on the CUPS Print Server After the CUPS system has been installed and configured, the administrator can begin configuring the local printers attached to the CUPS print server. This part of the process is very similar, if not identical, to configuring CUPS printers on other &unix;-based operating systems, such as a &linux; distribution. The primary means for managing and administering the CUPS server is through the web-based interface, which can be found by launching a web browser and entering in the browser's URL bar. If the CUPS server is on another machine on the network, substitute the server's local IP address for localhost. The CUPS web interface is fairly self-explanatory, as there are sections for managing printers and print jobs, authorizing users, and more. Additionally, on the right-hand side of the Administration screen are several check-boxes allowing easy access to commonly-changed settings, such as whether to share published printers connected to the system, whether to allow remote administration of the CUPS server, and whether to allow users additional access and privileges to the printers and print jobs. Adding a printer is generally as easy as clicking Add Printer at the Administration screen of the CUPS web interface, or clicking one of the New Printers Found buttons also at the Administration screen. When presented with the Device drop-down box, simply select the desired locally-attached printer, and then continue through the process. If one has added the print/gutenprint-cups or print/hplip ports or packages as referenced above, then additional print drivers will be available in the subsequent screens that might provide more stability or features. Configuring CUPS Clients Once the CUPS server has been configured and printers have been added and published to the network, the next step is to configure the clients, or the machines that are going to access the CUPS server. If one has a single desktop machine that is acting as both server and client, then much of this information may not be needed. &unix; Clients CUPS will also need to be installed on your &unix; clients. Once CUPS is installed on the clients, then CUPS printers that are shared across the network are often automatically discovered by the printer managers for various desktop environments such as GNOME or KDE. Alternatively, one can access the local CUPS interface on the client machine at and click on Add Printer in the Administration section. When presented with the Device drop-down box, simply select the networked CUPS printer, if it was automatically discovered, or select ipp or http and enter the IPP or HTTP URI of the networked CUPS printer, usually in one of the two following syntaxes: ipp://server-name-or-ip/printers/printername http://server-name-or-ip:631/printers/printername If the CUPS clients have difficulty finding other CUPS printers shared across the network, sometimes it is helpful to add or create a file /usr/local/etc/cups/client.conf with a single entry as follows: ServerName server-ip In this case, server-ip would be replaced by the local IP address of the CUPS server on the network. &windows; Clients Versions of &windows; prior to XP did not have the capability to natively network with IPP-based printers. However, &windowsxp; and later versions do have this capability. Therefore, to add a CUPS printer in these versions of &windows; is quite easy. Generally, the &windows; administrator will run the &windows; Add Printer wizard, select Network Printer and then enter the URI in the following syntax: http://server-name-or-ip:631/printers/printername If one has an older version of &windows; without native IPP printing support, then the general means of connecting to a CUPS printer is to use net/samba3 and CUPS together, which is a topic outside the scope of this chapter. CUPS Troubleshooting Difficulties with CUPS often lies in permissions. First, double check the &man.devfs.8; permissions as outlined above. Next, check the actual permissions of the devices created in the file system. It is also helpful to make sure your user is a member of the cups group. If the permissions check boxes in the Administration section of the CUPS web interface do not seem to be working, another fix might be to manually backup the main CUPS configuration file located at /usr/local/etc/cups/cupsd.conf and edit the various configuration options and try different combinations of configuration options. One sample /usr/local/etc/cups/cupsd.conf to test is listed below. Please note that this sample cupsd.conf file sacrifices security for easier configuration; once the administrator successfully connects to the CUPS server and configures the clients, it is advisable to revisit this configuration file and begin locking down access. # Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel info # Administrator user group... SystemGroup wheel # Listen for connections on Port 631. Port 631 #Listen localhost:631 Listen /var/run/cups.sock # Show shared printers on the local network. Browsing On BrowseOrder allow,deny #BrowseAllow @LOCAL BrowseAllow 192.168.1.* # change to local LAN settings BrowseAddress 192.168.1.* # change to local LAN settings # Default authentication type, when authentication is required... DefaultAuthType Basic DefaultEncryption Never # comment this line to allow encryption # Allow access to the server from any machine on the LAN <Location /> Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Allow access to the admin pages from any machine on the LAN <Location /admin> #Encryption Required Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Allow access to configuration files from any machine on the LAN <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Set the default printer/job policies... <Policy default> # Job-related operations must be done by the owner or an administrator... <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs \ Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription \ Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job \ CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> # All administration operations require an administrator to authenticate... <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer \ Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs \ Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer \ Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class \ CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> AuthType Basic Require user @SYSTEM Order deny,allow </Limit> # Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> <Limit All> Order deny,allow </Limit> </Policy> Fine Tuning CUPS-Related Ports If CUPS is going to serve as the primary printing system, then one may choose to optionally add certain knobs to /etc/make.conf that will emphasize CUPS over other printing options. Some of these knobs that one may want to add are: WITH_CUPS=YES CUPS_OVERWRITE_BASE=YES WITHOUT_LPR=YES The first knob, WITH_CUPS, adds CUPS support to ports where applicable. The second knob, CUPS_OVERWRITE_BASE, will fix certain symlinks and paths that would otherwise apply to the default &os; printing system, LPR, and will prevent these fixes from being reverted upon the next buildworld system upgrade. The third knob, WITHOUT_LPR, will prevent LPR support from being added to ports where applicable. + +
diff --git a/en_US.ISO8859-1/articles/nanobsd/article.xml b/en_US.ISO8859-1/articles/nanobsd/article.xml index a12c10305d..64113c394e 100644 --- a/en_US.ISO8859-1/articles/nanobsd/article.xml +++ b/en_US.ISO8859-1/articles/nanobsd/article.xml @@ -1,507 +1,509 @@
Introduction to NanoBSD Daniel Gerzo 2006 The FreeBSD Documentation Project &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ This document provides information about the NanoBSD tools, which can be used to create &os; system images for embedded applications, suitable for use on a Compact Flash card (or other mass storage medium). Introduction to NanoBSD NanoBSD NanoBSD is a tool currently developed by &a.phk.email;. It creates a &os; system image for embedded applications, suitable for use on a Compact Flash card (or other mass storage medium). It can be used to build specialized install images, designed for easy installation and maintenance of systems commonly called computer appliances. Computer appliances have their hardware and software bundled in the product, which means all applications are pre-installed. The appliance is plugged into an existing network and can begin working (almost) immediately. The features of NanoBSD include: Ports and packages work as in &os; — Every single application can be installed and used in a NanoBSD image, the same way as in &os;. No missing functionality — If it is possible to do something with &os;, it is possible to do the same thing with NanoBSD, unless the specific feature or features were explicitly removed from the NanoBSD image when it was created. Everything is read-only at run-time — It is safe to pull the power-plug. There is no necessity to run &man.fsck.8; after a non-graceful shutdown of the system. Easy to build and customize — Making use of just one shell script and one configuration file it is possible to build reduced and customized images satisfying any arbitrary set of requirements. NanoBSD Howto The design of NanoBSD Once the image is present on the medium, it is possible to boot NanoBSD. The mass storage medium is divided into three parts by default: Two image partitions: code#1 and code#2. The configuration file partition, which can be mounted under the /cfg directory at run time. These partitions are normally mounted read-only. The /etc and /var directories are &man.md.4; (malloc) disks. The configuration file partition persists under the /cfg directory. It contains files for /etc directory and is briefly mounted read-only right after the system boot, therefore it is required to copy modified files from /etc back to the /cfg directory if changes are expected to persist after the system restarts. Making persistent changes to <filename>/etc/resolv.conf</filename> &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg The partition containing /cfg should be mounted only at boot time and while overriding the configuration files. Keeping /cfg mounted at all times is not a good idea, especially if the NanoBSD system runs off a mass storage medium that may be adversely affected by a large number of writes to the partition (i.e. when the filesystem syncer flushes data to the system disks). Building a NanoBSD image A NanoBSD image is built using a simple nanobsd.sh shell script, which can be found in the /usr/src/tools/tools/nanobsd directory. This script creates an image, which can be copied on the storage medium using the &man.dd.1; utility. The necessary commands to build a NanoBSD image are: &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k Change the current directory to the base directory of the NanoBSD build script. Start the build process. Change the current directory to the place where the built images are located. Install NanoBSD onto the storage medium. Customizing a NanoBSD image This is probably the most important and most interesting feature of NanoBSD. This is also where you will be spending most of the time when developing with NanoBSD. Invocation of the following command will force the nanobsd.sh to read its configuration from the myconf.nano file located in the current directory: &prompt.root; sh nanobsd.sh -c myconf.nano Customization is done in two ways: Configuration options Custom functions Configuration options With configuration settings, it is possible to configure options passed to both the buildworld and installworld stages of the NanoBSD build process, as well as internal options passed to the main build process of NanoBSD. Through these options it is possible to cut the system down, so it will fit on as little as 64MB. You can use the configuration options to trim down &os; even more, until it will consists of just the kernel and two or three files in the userland. The configuration file consists of configuration options, which override the default values. The most important directives are: NANO_NAME — Name of build (used to construct the workdir names). NANO_SRC — Path to the source tree used to build the image. NANO_KERNEL — Name of kernel configuration file used to build kernel. CONF_BUILD — Options passed to the buildworld stage of the build. CONF_INSTALL — Options passed to the installworld stage of the build. CONF_WORLD — Options passed to both the buildworld and the installworld stage of the build. FlashDevice — Defines what type of media to use. Check the FlashDevice.sub file for more details. Custom functions It is possible to fine-tune NanoBSD using shell functions in the configuration file. The following example illustrates the basic model of custom functions: cust_foo () ( echo "bar=baz" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo A more useful example of a customization function is the following, which changes the default size of the /etc directory from 5MB to 30MB: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size There are a few default pre-defined customization functions ready for use: cust_comconsole — Disables &man.getty.8; on the VGA devices (the /dev/ttyv* device nodes) and enables the use of the COM1 serial port as the system console. cust_allow_ssh_root — Allow root to login via &man.sshd.8;. cust_install_files — Installs files from the nanobsd/Files directory, which contains some useful scripts for system administration. Adding packages Packages can be added to a NanoBSD image using a custom function. The following function will install all the packages located in /usr/src/tools/tools/nanobsd/packages: install_packages () ( mkdir -p ${NANO_WORLDDIR}/packages cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;' rm -rf ${NANO_WORLDDIR}/packages ) customize_cmd install_packages Configuration file example A complete example of a configuration file for building a custom NanoBSD image can be: NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie Updating NanoBSD The update process of NanoBSD is relatively simple: Build a new NanoBSD image, as usual. Upload the new image into an unused partition of a running NanoBSD appliance. The most important difference of this step from the initial NanoBSD installation is that now instead of using the _.disk.full file (which contains an image of the entire disk), the _.disk.image image is installed (which contains an image of a single system partition). Reboot, and start the system from the newly installed partition. If all goes well, the upgrade is finished. If anything goes wrong, reboot back into the previous partition (which contains the old, working image), to restore system functionality as fast as possible. Fix any problems of the new build, and repeat the process. To install new image onto the running NanoBSD system, it is possible to use either the updatep1 or updatep2 script located in the /root directory, depending from which partition is running the current system. According to which services are available on host serving new NanoBSD image and what type of transfer is preferred, it is possible to examine one of these three ways: Using &man.ftp.1; If the transfer speed is in first place, use this example: &prompt.root; ftp myhost get _.disk.image "| sh updatep1" Using &man.ssh.1; If a secure transfer is preferred, consider using this example: &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 Using &man.nc.1; Try this example if the remote host is not running neither &man.ftpd.8; or &man.sshd.8; service: At first, open a TCP listener on host serving the image and make it send the image to client: myhost&prompt.root; nc -l 2222 < _.disk.image Make sure that the used port is not blocked to receive incoming connections from NanoBSD host by firewall. Connect to the host serving new image and execute updatep1 script: &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/en_US.ISO8859-1/articles/problem-reports/article.xml b/en_US.ISO8859-1/articles/problem-reports/article.xml index 61ad4fa589..6e49c64af8 100644 --- a/en_US.ISO8859-1/articles/problem-reports/article.xml +++ b/en_US.ISO8859-1/articles/problem-reports/article.xml @@ -1,1275 +1,1277 @@
Writing &os; Problem Reports &tm-attrib.freebsd; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ This article describes how to best formulate and submit a problem report to the &os; Project. Dag-Erling Smørgrav Contributed by Mark Linimon problem reports
Introduction One of the most frustrating experiences one can have as a software user is to submit a problem report only to have it summarily closed with a terse and unhelpful explanation like not a bug or bogus PR. Similarly, one of the most frustrating experiences as a software developer is to be flooded with problem reports that are not really problem reports but requests for support, or that contain little or no information about what the problem is and how to reproduce it. This document attempts to describe how to write good problem reports. What, you ask, is a good problem report? Well, to go straight to the bottom line, a good problem report is one that can be analyzed and dealt with swiftly, to the mutual satisfaction of both user and developer. Although the primary focus of this article is on &os; problem reports, most of it should apply quite well to other software projects. Note that this article is organized thematically, not chronologically, so you should read through the entire document before submitting a problem report, rather than treat it as a step-by-step tutorial.
When to submit a problem report There are many types of problems, and not all of them should engender a problem report. Of course, nobody is perfect, and there will be times when you are convinced you have found a bug in a program when in fact you have misunderstood the syntax for a command or made a typographical error in a configuration file (though that in itself may sometimes be indicative of poor documentation or poor error handling in the application). There are still many cases where submitting a problem report is clearly not the right course of action, and will only serve to frustrate you and the developers. Conversely, there are cases where it might be appropriate to submit a problem report about something else than a bug—an enhancement or a new feature, for instance. So how do you determine what is a bug and what is not? As a simple rule of thumb your problem is not a bug if it can be expressed as a question (usually of the form How do I do X? or Where can I find Y?). It is not always quite so black and white, but the question rule covers a large majority of cases. If you are looking for an answer, consider posing your question to the &a.questions;. Some cases where it may be appropriate to submit a problem report about something that is not a bug are: Notification of updates to externally maintained software (mainly ports, but also externally maintained base system components such as BIND or various GNU utilities). For unmaintained ports (MAINTAINER contains ports@FreeBSD.org), such update notifications might get picked up by an interested committer, or you might be asked to provide a patch to update the port; providing it upfront will greatly improve your chances that the port will get updated in a timely manner. If the port is maintained, PRs announcing new upstream releases are usually not very useful since they generate supplementary work for the committers, and the maintainer likely knows already there is a new version, they have probably worked with the developers on it, they are probably testing to see there is no regression, etc. In either case, following the process described in Porter's Handbook will yield the best results. (You might also wish to read Contributing to the FreeBSD Ports Collection.) A bug that can not be reproduced can rarely be fixed. If the bug only occurred once and you can not reproduce it, and it does not seem to happen to anybody else, chances are none of the developers will be able to reproduce it or figure out what is wrong. That does not mean it did not happen, but it does mean that the chances of your problem report ever leading to a bug fix are very slim. To make matters worse, often these kinds of bugs are actually caused by failing hard drives or overheating processors — you should always try to rule out these causes, whenever possible, before submitting a PR. Next, to decide to whom you should file your problem report, you need to understand that the software that makes up &os; is composed of several different elements: Code in the base system that is written and maintained by &os; contributors, such as the kernel, the C library, and the device drivers (categorized as kern); the binary utilities (bin); the manual pages and documentation (docs); and the web pages (www). All bugs in these areas should be reported to the &os; developers. Code in the base system that is written and maintained by others, and imported into &os; and adapted. Examples include bind, &man.gcc.1;, and &man.sendmail.8;. Most bugs in these areas should be reported to the &os; developers; but in some cases they may need to be reported to the original authors instead if the problems are not &os;-specific. Usually these bugs will fall under either the bin or gnu categories. Individual applications that are not in the base system but are instead part of the &os; Ports Collection (category ports). Most of these applications are not written by &os; developers; what &os; provides is merely a framework for installing the application. Therefore, you should only report a problem to the &os; developers when you believe the problem is &os;-specific; otherwise, you should report it to the authors of the software. Then you should ascertain whether or not the problem is timely. There are few things that will annoy a developer more than receiving a problem report about a bug she has already fixed. If the problem is in the base system, you should first read the FAQ section on &os; versions, if you are not already familiar with the topic. It is not possible for &os; to fix problems in anything other than certain recent branches of the base system, so filing a bug report about an older version will probably only result in a developer advising you to upgrade to a supported version to see if the problem still recurs. The Security Officer team maintains the list of supported versions. If the problem is in a port, note that you must first upgrade to the latest version of the Ports Collection and see if the problem still applies. Due to the rapid pace of changes in these applications, it is infeasible for &os; to support anything other than the absolute latest versions, and problems with older version of applications simply cannot be fixed.
Preparations A good rule to follow is to always do a background search before submitting a problem report. Maybe your problem has already been reported; maybe it is being discussed on the mailing lists, or recently was; it may even already be fixed in a newer version than what you are running. You should therefore check all the obvious places before submitting your problem report. For &os;, this means: The &os; Frequently Asked Questions (FAQ) list. The FAQ attempts to provide answers for a wide range of questions, such as those concerning hardware compatibility, user applications, and kernel configuration. The mailing lists—if you are not subscribed, use the searchable archives on the &os; web site. If your problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something you have overlooked. Optionally, the entire web—use your favorite search engine to locate any references to your problem. You may even get hits from archived mailing lists or newsgroups you did not know of or had not thought to search through. Next, the searchable &os; PR database (GNATS). Unless your problem is recent or obscure, there is a fair chance it has already been reported. Most importantly, you should attempt to see if existing documentation in the source base addresses your problem. For the base &os; code, you should carefully study the contents of the /usr/src/UPDATING file on your system or its latest version at . (This is vital information if you are upgrading from one version to another—especially if you are upgrading to the &os.current; branch). However, if the problem is in something that was installed as a part of the &os; Ports Collection, you should refer to /usr/ports/UPDATING (for individual ports) or /usr/ports/CHANGES (for changes that affect the entire Ports Collection). and are also available via svnweb.
Writing the problem report Now that you have decided that your issue merits a problem report, and that it is a &os; problem, it is time to write the actual problem report. Before we get into the mechanics of the program used to generate and submit PRs, here are some tips and tricks to help make sure that your PR will be most effective.
Tips and tricks for writing a good problem report Do not leave the Synopsis line empty. The PRs go both onto a mailing list that goes all over the world (where the Synopsis is used for the Subject: line), but also into a database. Anyone who comes along later and browses the database by synopsis, and finds a PR with a blank subject line, tends just to skip over it. Remember that PRs stay in this database until they are closed by someone; an anonymous one will usually just disappear in the noise. Avoid using a weak Synopsis line. You should not assume that anyone reading your PR has any context for your submission, so the more you provide, the better. For instance, what part of the system does the problem apply to? Do you only see the problem while installing, or while running? To illustrate, instead of Synopsis: portupgrade is broken, see how much more informative this seems: Synopsis: port ports-mgmt/portupgrade coredumps on -current. (In the case of ports, it is especially helpful to have both the category and portname in the Synopsis line.) If you have a patch, say so. A PR with a patch included is much more likely to be looked at than one without. If you are including one, put the string [patch] (including the brackets) at the beginning of the Synopsis. (Although it is not mandatory to use that exact string, by convention, that is the one that is used.) If you are a maintainer, say so. If you are maintaining a part of the source code (for instance, a port), you might consider adding the string [maintainer update] (including the brackets) at the beginning of your synopsis line, and you definitely should set the Class of your PR to maintainer-update. This way any committer that handles your PR will not have to check. Be specific. The more information you supply about what problem you are having, the better your chance of getting a response. Include the version of &os; you are running (there is a place to put that, see below) and on which architecture. You should include whether you are running from a release (e.g. from a CDROM or download), or from a system maintained by Subversion (and, if so, what revision number you are at). If you are tracking the &os.current; branch, that is the very first thing someone will ask, because fixes (especially for high-profile problems) tend to get committed very quickly, and &os.current; users are expected to keep up. Include which global options you have specified in your make.conf. Note: specifying -O2 and above to &man.gcc.1; is known to be buggy in many situations. While the &os; developers will accept patches, they are generally unwilling to investigate such issues due to simple lack of time and volunteers, and may instead respond that this just is not supported. If the problem can be reproduced easily, include information that will help a developer to reproduce it themselves. If a problem can be demonstrated with specific input then include an example of that input if possible, and include both the actual and the expected output. If this data is large or cannot be made public, then do try to create a minimal file that exhibits the same issue and that can be included within the PR. If this is a kernel problem, then be prepared to supply the following information. (You do not have to include these by default, which only tends to fill up the database, but you should include excerpts that you think might be relevant): your kernel configuration (including which hardware devices you have installed) whether or not you have debugging options enabled (such as WITNESS), and if so, whether the problem persists when you change the sense of that option the full text of any backtrace, panic or other console output, or entries in /var/log/messages, if any were generated the output of pciconf -l and relevant parts of your dmesg output if your problem relates to a specific piece of hardware the fact that you have read src/UPDATING and that your problem is not listed there (someone is guaranteed to ask) whether or not you can run any other kernel as a fallback (this is to rule out hardware-related issues such as failing disks and overheating CPUs, which can masquerade as kernel problems) If this is a ports problem, then be prepared to supply the following information. (You do not have to include these by default, which only tends to fill up the database, but you should include excerpts that you think might be relevant): which ports you have installed any environment variables that override the defaults in bsd.port.mk, such as PORTSDIR the fact that you have read ports/UPDATING and that your problem is not listed there (someone is guaranteed to ask) Avoid vague requests for features. PRs of the form someone should really implement something that does so-and-so are less likely to get results than very specific requests. Remember, the source is available to everyone, so if you want a feature, the best way to ensure it being included is to get to work! Also consider the fact that many things like this would make a better topic for discussion on freebsd-questions than an entry in the PR database, as discussed above. Make sure no one else has already submitted a similar PR. Although this has already been mentioned above, it bears repeating here. It only take a minute or two to use the web-based search engine at . (Of course, everyone is guilty of forgetting to do this now and then.) Report only one issue per Problem Report. Avoid including two or more problems within the same report unless they are related. When submitting patches, avoid adding multiple features or fixing multiple bugs in the same PR unless they are closely related—such PRs often take longer to resolve. Avoid controversial requests. If your PR addresses an area that has been controversial in the past, you should probably be prepared to not only offer patches, but also justification for why the patches are The Right Thing To Do. As noted above, a careful search of the mailing lists using the archives at is always good preparation. Be polite. Almost anyone who would potentially work on your PR is a volunteer. No one likes to be told that they have to do something when they are already doing it for some motivation other than monetary gain. This is a good thing to keep in mind at all times on Open Source projects.
Before you begin If you are using the &man.send-pr.1; program, make sure your VISUAL (or EDITOR if VISUAL is not set) environment variable is set to something sensible. You should also make sure that mail delivery works fine. &man.send-pr.1; uses mail messages for the submission and tracking of problem reports. If you cannot post mail messages from the machine you are running &man.send-pr.1; on, your problem report will not reach the GNATS database. For details on the setup of mail on &os;, see the Electronic Mail chapter of the &os; Handbook at . Make sure that your mailer will not mangle the message on its way to GNATS. In particular, if your mailer automatically breaks lines, changes tabs to spaces, or escapes newline characters, any patch that you submit will be rendered unusable. For the text sections, however, we request that you insert manual linebreaks somewhere around 70 characters, so that the web display of the PR will be readable. Similar considerations apply if you are using the web-based PR submission form instead of &man.send-pr.1;. Note that cut-and-paste operations can have their own side-effects on text formatting. In certain cases it may be necessary to use &man.uuencode.1; to ensure that patches arrive unmodified. Finally, if your submission will be lengthy, you should to prepare your work offline so that nothing will be lost in case there is a problem submitting it. This can especially be a problem with the web form.
Attaching patches or files The following applies to submitting PRs via email: The &man.send-pr.1; program has provisions for attaching files to a problem report. You can attach as many files as you want provided that each has a unique base name (i.e. the name of the file proper, without the path). Just use the command-line option to specify the names of the files you wish to attach: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors Do not worry about binary files, they will be automatically encoded so as not to upset your mail agent. If you attach a patch, make sure you use the or option to &man.diff.1; to create a context or unified diff (unified is preferred), and make sure to specify the exact SVN revision numbers of the files you modified so the developers who read your report will be able to apply them easily. For problems with the kernel or the base utilities, a patch against &os.current; (the HEAD Subversion branch) is preferred since all new code should be applied and tested there first. After appropriate or substantial testing has been done, the code will be merged/migrated to the &os.stable; branch. If you attach a patch inline, instead of as an attachment, note that the most common problem by far is the tendency of some email programs to render tabs as spaces, which will completely ruin anything intended to be part of a Makefile. Do not send patches as attachments using Content-Transfer-Encoding: quoted-printable. These will perform character escaping and the entire patch will be useless. Also note that while including small patches in a PR is generally all right—particularly when they fix the problem described in the PR—large patches and especially new code which may require substantial review before committing should be placed on a web or ftp server, and the URL should be included in the PR instead of the patch. Patches in email tend to get mangled, especially when GNATS is involved, and the larger the patch, the harder it will be for interested parties to unmangle it. Also, posting a patch on the web allows you to modify it without having to resubmit the entire patch in a followup to the original PR. Finally, large patches simply increase the size of the database, since closed PRs are not actually deleted but instead kept and simply marked as closed. You should also take note that unless you explicitly specify otherwise in your PR or in the patch itself, any patches you submit will be assumed to be licensed under the same terms as the original file you modified.
Filling out the template The next section applies to the email method only: When you run &man.send-pr.1;, you are presented with a template. The template consists of a list of fields, some of which are pre-filled, and some of which have comments explaining their purpose or listing acceptable values. Do not worry about the comments; they will be removed automatically if you do not modify them or remove them yourself. At the top of the template, below the SEND-PR: lines, are the email headers. You do not normally need to modify these, unless you are sending the problem report from a machine or account that can send but not receive mail, in which case you will want to set the From: and Reply-To: to your real email address. You may also want to send yourself (or someone else) a carbon copy of the problem report by adding one or more email addresses to the Cc: header. In the email template only, you will find the following single-line fields: Submitter-Id: Do not change this. The default value of current-users is correct, even if you run &os.stable;. Confidential: This is prefilled to no. Changing it makes no sense as there is no such thing as a confidential &os; problem report—the PR database is distributed worldwide. Severity: One of non-critical, serious or critical. Do not overreact; refrain from labeling your problem critical unless it really is (e.g., data corruption issues, serious regression from previous functionality in -CURRENT) or serious unless it is something that will affect many users (kernel panics or freezes; problems with particular device drivers or system utilities). &os; developers will not necessarily work on your problem faster if you inflate its importance since there are so many other people who have done exactly that — in fact, some developers pay little attention to this field because of this. Security problems should not be filed in GNATS, because all GNATS information is public knowledge. Please send such problems according to our security report guidelines. Priority: One of low, medium or high. high should be reserved for problems that will affect practically every user of &os; and medium for something that will affect many users. This field has become so widely abused that it is almost completely meaningless. The next section describes fields that are common to both the email interface and the web interface: Originator: Please specify your real name, optionally followed by your email address in angle brackets. In the email interface, this is normally prefilled with the gecos field of the currently logged-in user. The email address you use will become public information and may become available to spammers. You should either have spam handling procedures in place, or use a temporary email account. However, please note that if you do not use a valid email account at all, we will not be able to ask you questions about your PR. Organization: Whatever you feel like. This field is not used for anything significant. Synopsis: Fill this out with a short and accurate description of the problem. The synopsis is used as the subject of the problem report email, and is used in problem report listings and summaries; problem reports with obscure synopses tend to get ignored. As noted above, if your problem report includes a patch, please have the synopsis start with [patch] (including the brackets); if this is a ports PR and you are the maintainer, you may consider adding [maintainer update] (including the brackets) and set the Class of your PR to maintainer-update. Category: Choose an appropriate category. The first thing you need to do is to decide what part of the system your problem lies in. Remember, &os; is a complete operating system, which installs both a kernel, the standard libraries, many peripheral drivers, and a large number of utilities (the base system). However, there are thousands of additional applications in the Ports Collection. You'll first need to decide if the problem is in the base system or something installed via the Ports Collection. Here is a description of the major categories: If a problem is with the kernel, the libraries (such as standard C library libc), or a peripheral driver in the base system, in general you will use the kern category. (There are a few exceptions; see below). In general these are things that are described in section 2, 3, or 4 of the manual pages. If a problem is with a binary program such as &man.sh.1; or &man.mount.8;, you will first need to determine whether these programs are in the base system or were added via the Ports Collection. If you are unsure, you can do whereis programname. &os;'s convention for the Ports Collection is to install everything underneath /usr/local, although this can be overridden by a system administrator. For these, you will use the ports category (yes, even if the port's category is www; see below). If the location is /bin, /usr/bin, /sbin, or /usr/sbin, it is part of the base system, and you should use the bin category. (A few programs, such as &man.gcc.1;, actually use the gnu category, but do not worry about that for now.) These are all things that are described in section 1 or 8 of the manual pages. If you believe that the error is in the startup (rc) scripts, or in some kind of other non-executable configuration file, then the right category is conf (configuration). These are things that are described in section 5 of the manual pages. If you have found a problem in the documentation set (articles, books, man pages), the correct choice is docs. If you are having a problem with the FreeBSD web pages, the proper choice is www. if you are having a problem with something from a port named www/someportname, this nevertheless goes in the ports category. There are a few more specialized categories. If the problem would otherwise be filed in kern but has to do with the USB subsystem, the correct choice is usb. If the problem would otherwise be filed in kern but has to do with the threading libraries, the correct choice is threads. If the problem would otherwise be in the base system, but has to do with our adherence to standards such as &posix;, the correct choice is standards. If the problem has to do with errors internal to a &java.virtual.machine; (&jvm;), even though &java; was installed from the Ports Collection, you should select the java category. More general problems with &java; ports still go under ports. This leaves everything else. If you are convinced that the problem will only occur under the processor architecture you are using, select one of the architecture-specific categories: commonly i386 for Intel-compatible machines in 32-bit mode; amd64 for AMD machines running in 64-bit mode (this also includes Intel-compatible machines running in EMT64 mode); and less commonly arm, ia64, powerpc, and sparc64. These categories are quite often misused for I do not know problems. Rather than guessing, please just use misc. Correct use of arch-specific category You have a common PC-based machine, and think you have encountered a problem specific to a particular chipset or a particular motherboard: i386 is the right category. Incorrect use of arch-specific category You are having a problem with an add-in peripheral card on a commonly seen bus, or a problem with a particular type of hard disk drive: in this case, it probably applies to more than one architecture, and kern is the right category. If you really do not know where the problem lies (or the explanation does not seem to fit into the ones above), use the misc category. Before you do so, you may wish to ask for help on the &a.questions; first. You may be advised that one of the existing categories really is a better choice. Here is the current list of categories (taken from ): advocacy: problems relating to &os;'s public image. Obsolete. amd64: problems specific to the AMD64 platform. arm: problems specific to the ARM platform. bin: problems with userland programs in the base system. conf: problems with configuration files, default values, and so forth. docs: problems with manual pages or on-line documentation. gnu: problems with imported GNU software such as &man.gcc.1; or &man.grep.1;. i386: problems specific to the &i386; platform. ia64: problems specific to the ia64 platform. java: problems related to the &java; Virtual Machine. kern: problems with the kernel, (non-platform-specific) device drivers, or the base libraries. misc: anything that does not fit in any of the other categories. (Note that there is almost nothing that truly belongs in this category, except for problems with the release and build infrastructure. Temporary build failures on HEAD do not belong here. Also note that it is easy for things to get lost in this category). ports: problems relating to the Ports Collection. powerpc: problems specific to the &powerpc; platform. sparc64: problems specific to the &sparc64; platform. standards: Standards conformance issues. threads: problems related to the &os; threads implementation (especially on &os.current;). usb: problems related to the &os; USB implementation. www: Changes or enhancements to the &os; website. Class: Choose one of the following: sw-bug: software bugs. doc-bug: errors in documentation. change-request: requests for additional features or changes in existing features. update: updates to ports or other contributed software. maintainer-update: updates to ports for which you are the maintainer. Release: The version of &os; that you are running. This is filled out automatically if you are using &man.send-pr.1; and need only be changed if you are sending a problem report from a different system than the one that exhibits the problem. Finally, there is a series of multi-line fields: Environment: This should describe, as accurately as possible, the environment in which the problem has been observed. This includes the operating system version, the version of the specific program or file that contains the problem, and any other relevant items such as system configuration, other installed software that influences the problem, etc.—quite simply everything a developer needs to know to reconstruct the environment in which the problem occurs. Description: A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. How-To-Repeat: A summary of the actions you need to take to reproduce the problem. Fix: Preferably a patch, or at least a workaround (which not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem), but if you do not have any firm ideas for either, it is better to leave this field blank than to speculate.
Sending off the problem report If you are using &man.send-pr.1;: Once you are done filling out the template, have saved it, and exit your editor, &man.send-pr.1; will prompt you with s)end, e)dit or a)bort?. You can then hit s to go ahead and submit the problem report, e to restart the editor and make further modifications, or a to abort. If you choose the latter, your problem report will remain on disk (&man.send-pr.1; will tell you the filename before it terminates), so you can edit it at your leisure, or maybe transfer it to a system with better net connectivity, before sending it with the to &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report This will read the specified file, validate the contents, strip comments and send it off. If you are using the web form: Before you hit submit, you will need to fill in a field containing text that is represented in image form on the page. This unfortunate measure has had to be adopted due to misuse by automated systems and a few misguided individuals. It is a necessary evil that no one likes; please do not ask us to remove it. Note that you are strongly advised to save your work somewhere before hitting submit. A common problem for users is to have their web browser displaying a stale image from its cache. If this happens to you, your submission will be rejected and you may lose your work. If you are unable to view images for any reason, and are also unable to use &man.send-pr.1;, please accept our apologies for the inconvenience and email your problem report to the bugbuster team at freebsd-bugbusters@FreeBSD.org.
Follow-up Once your problem report has been filed, you will receive a confirmation by email which will include the tracking number that was assigned to your problem report and a URL you can use to check its status. With a little luck, someone will take an interest in your problem and try to address it, or, as the case may be, explain why it is not a problem. You will be automatically notified of any change of status, and you will receive copies of any comments or patches someone may attach to your problem report's audit trail. If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please use one of two methods to submit your followup: The easiest way is to use the followup link on the individual PR's web page, which you can reach from the PR search page. Clicking on this link will bring up an an email window with the correct To: and Subject: lines filled in (if your browser is configured to do this). Alternatively, you can just mail it to &a.bugfollowup;, making sure that the tracking number is included in the subject so the bug tracking system will know what problem report to attach it to. If you do not include the tracking number, GNATS will become confused and create an entirely new PR which it then assigns to the GNATS administrator, and then your followup will become lost until someone comes in to clean up the mess, which could be days or weeks afterwards. Wrong way: Subject: that PR I sent Right way: Subject: Re: ports/12345: compilation problem with foo/bar If the problem report remains open after the problem has gone away, just send a follow-up (in the manner prescribed above) saying that the problem report can be closed, and, if possible, explaining how or when the problem was fixed.
If you are having problems Most PRs go through the system and are accepted quickly; however, at times GNATS runs behind and you may not get your email confirmation for 10 minutes or even longer. Please try to be patient. In addition, because GNATS receives all its input via email, it is absolutely vital that &os; runs all its submissions through spam filters. If you do not get a response within an hour or two, you may have fallen afoul of them; if so, please contact the GNATS administrators at bugmeister@FreeBSD.org and ask for help. Among the anti-spam measures is one that weighs against many common abuses seen in HTML-based email (although not necessarily the mere inclusion of HTML in a PR). We strongly recommend against the use of HTML-based email when sending PRs: not only is it more likely to fall afoul of the filters, it also tends to merely clutter up the database. Plain old email is strongly preferred. On rare occasions you will encounter a GNATS bug where a PR is accepted and assigned a tracking number but it does not show up on the list of PRs on any of the web query pages. What may have happened is that the database index has gotten out of synchronization with the database itself. The way that you can test whether this has happened is to pull up the view a single PR page and see whether the PR shows up. If it does, please notify the GNATS administrators at bugmeister@FreeBSD.org. Note that there is a cron job that periodically rebuilds the database, so unless you are in a hurry, no action needs to be taken.
Further Reading This is a list of resources relevant to the proper writing and processing of problem reports. It is by no means complete. How to Report Bugs Effectively—an excellent essay by Simon G. Tatham on composing useful (non-&os;-specific) problem reports. Problem Report Handling Guidelines—valuable insight into how problem reports are handled by the &os; developers.
+ +
diff --git a/en_US.ISO8859-1/books/arch-handbook/Makefile b/en_US.ISO8859-1/books/arch-handbook/Makefile index 9ad49d0e62..5f933755f9 100644 --- a/en_US.ISO8859-1/books/arch-handbook/Makefile +++ b/en_US.ISO8859-1/books/arch-handbook/Makefile @@ -1,59 +1,57 @@ # # $FreeBSD$ # # Build the FreeBSD Architecture Handbook. # MAINTAINER=doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= boot/chapter.xml SRCS+= driverbasics/chapter.xml SRCS+= isa/chapter.xml SRCS+= jail/chapter.xml SRCS+= kobj/chapter.xml SRCS+= locking/chapter.xml SRCS+= mac/chapter.xml SRCS+= newbus/chapter.xml SRCS+= pci/chapter.xml SRCS+= scsi/chapter.xml SRCS+= smp/chapter.xml SRCS+= sound/chapter.xml SRCS+= pccard/chapter.xml SRCS+= sysinit/chapter.xml SRCS+= usb/chapter.xml SRCS+= vm/chapter.xml # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/en_US.ISO8859-1/books/arch-handbook/chapters.ent b/en_US.ISO8859-1/books/arch-handbook/chapters.ent index 7fdd3df4ad..bb4ac84dc0 100644 --- a/en_US.ISO8859-1/books/arch-handbook/chapters.ent +++ b/en_US.ISO8859-1/books/arch-handbook/chapters.ent @@ -1,39 +1,34 @@ - - - -]]> - +"> diff --git a/en_US.ISO8859-1/books/developers-handbook/Makefile b/en_US.ISO8859-1/books/developers-handbook/Makefile index 2d673e307e..8c5bb2209c 100644 --- a/en_US.ISO8859-1/books/developers-handbook/Makefile +++ b/en_US.ISO8859-1/books/developers-handbook/Makefile @@ -1,45 +1,43 @@ # # $FreeBSD$ # # Build the FreeBSD Developers' Handbook. # MAINTAINER=doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # Images IMAGES_EN= sockets/layers.eps sockets/sain.eps sockets/sainfill.eps sockets/sainlsb.eps sockets/sainmsb.eps sockets/sainserv.eps sockets/serv.eps sockets/serv2.eps sockets/slayers.eps # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= introduction/chapter.xml SRCS+= ipv6/chapter.xml SRCS+= kernelbuild/chapter.xml SRCS+= kerneldebug/chapter.xml SRCS+= l10n/chapter.xml SRCS+= policies/chapter.xml SRCS+= secure/chapter.xml SRCS+= sockets/chapter.xml SRCS+= testing/chapter.xml SRCS+= tools/chapter.xml SRCS+= x86/chapter.xml # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/en_US.ISO8859-1/books/developers-handbook/chapters.ent b/en_US.ISO8859-1/books/developers-handbook/chapters.ent index 555d115d40..727f67569a 100644 --- a/en_US.ISO8859-1/books/developers-handbook/chapters.ent +++ b/en_US.ISO8859-1/books/developers-handbook/chapters.ent @@ -1,38 +1,33 @@ - - - -]]> - +"> diff --git a/en_US.ISO8859-1/books/fdp-primer/book.xml b/en_US.ISO8859-1/books/fdp-primer/book.xml index c1e16f1040..5793e35839 100644 --- a/en_US.ISO8859-1/books/fdp-primer/book.xml +++ b/en_US.ISO8859-1/books/fdp-primer/book.xml @@ -1,271 +1,269 @@ %chapters; ]> FreeBSD Documentation Project Primer for New Contributors The FreeBSD Documentation Project 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 DocEng $FreeBSD$ $FreeBSD$ &legalnotice; Thank you for becoming a part of the FreeBSD Documentation Project. Your contribution is extremely valuable, and we appreciate it. This primer covers details needed to start contributing to the FreeBSD Documentation Project, or FDP, including tools, software, and the philosophy behind the Documentation Project. This is a work in progress. Corrections and additions are always welcome. Preface Shell Prompts This table shows the default system prompt and superuser prompt. The examples use these prompts to indicate which type of user is running the example. User Prompt Normal user &prompt.user; root &prompt.root; Typographic Conventions This table describes the typographic conventions used in this book. Meaning Examples The names of commands. Use ls -l to list all files. The names of files. Edit .login. On-screen computer output. You have mail. What the user types, contrasted with on-screen computer output. &prompt.user; date +"The time is %H:%M" The time is 09:18 Manual page references. Use &man.su.1; to change user identity. User and group names. Only root can do this. Emphasis. The user must do this. Text that the user is expected to replace with the actual text. To search for a keyword in the manual pages, type man -k keyword Environment variables. $HOME is set to the user's home directory. Notes, Tips, Important Information, Warnings, and Examples Notes, warnings, and examples appear within the text. Notes are represented like this, and contain information to take note of, as it may affect what the user does. Tips are represented like this, and contain information helpful to the user, like showing an easier way to do something. Important information is represented like this. Typically, these show extra steps the user may need to take. Warnings are represented like this, and contain information warning about possible damage if the instructions are not followed. This damage may be physical, to the hardware or the user, or it may be non-physical, such as the inadvertent deletion of important files. A Sample Example Examples are represented like this, and typically contain examples showing a walkthrough, or the results of a particular action. Acknowledgments My thanks to Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn, and Christopher Maden, who took the time to read early drafts of this document and offer many valuable comments and criticisms. &chap.overview; &chap.tools; &chap.working-copy; &chap.structure; &chap.doc-build; &chap.the-website; &chap.xml-primer; &chap.xhtml-markup; &chap.docbook-markup; &chap.stylesheets; &chap.translations; &chap.writing-style; &chap.editor-config; &chap.see-also; &app.examples; - diff --git a/en_US.ISO8859-1/books/handbook/Makefile b/en_US.ISO8859-1/books/handbook/Makefile index 5f176c6f62..cd17a0100c 100644 --- a/en_US.ISO8859-1/books/handbook/Makefile +++ b/en_US.ISO8859-1/books/handbook/Makefile @@ -1,348 +1,346 @@ # # $FreeBSD$ # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/pxe-nfs.png IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml ${DOC}.parsed.xml @${XSLTPROC} ${XSLPGP} ${DOC}.parsed.xml # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/en_US.ISO8859-1/books/handbook/chapters.ent b/en_US.ISO8859-1/books/handbook/chapters.ent index a2f58a9d2e..dd57d3ca8d 100644 --- a/en_US.ISO8859-1/books/handbook/chapters.ent +++ b/en_US.ISO8859-1/books/handbook/chapters.ent @@ -1,70 +1,70 @@ %pgpkeys; - + "> diff --git a/es_ES.ISO8859-1/articles/contributing/article.xml b/es_ES.ISO8859-1/articles/contributing/article.xml index 49212c4bef..3691383575 100644 --- a/es_ES.ISO8859-1/articles/contributing/article.xml +++ b/es_ES.ISO8859-1/articles/contributing/article.xml @@ -1,613 +1,615 @@
Contribuir a FreeBSD En éste artículo se describen las diferentes maneras en las que una persona o entidad pueden ayudar al Proyecto FreeBSD. &trans.es.bazcar; Jordan Hubbard Enviado por $FreeBSD$ $FreeBSD$ contributing ?Quiere ayudar a mejorar FreeBSD? ¡Eso es genial! FreeBSD depende del esfuerzo de base de usuarios y usuarias para sobrevivir. Su ayuda no sólamente muy apreciada sino que es vital para el contínuo crecimiento de FreeBSD. Contrariamente a lo que pudiera usted creer, no hace falta ser un brujo de la programación o un amigo íntimo del core team de FreeBSD para su trabajo sea aceptado. El desarrollo de FreeBSD está al cargo de un gran grupo internacional de voluntarios y voluntarias en contínuo crecimiento, de muy diversas edades y expertos en distintos campos del conocimiento. Siempre hay más trabajo por hacer que gente disponible para hacerlo y una mano más siempre es bienvenida. El proyecto FreeBSD tiene el compromiso de mantener un sistema operativo completo, no simplemente un kernel o unas cuantas aplicaciones sueltas. Por lo tanto nuestra lista de TAREAS PENDIENTES (TODO) incluye una vasta lista de tareas: desde documentación, prueba de versiones preliminares hasta el desarrollo del sistema de instalación y el desarrollo del kernel en aspectos altamente especializados. Casi con total seguridad puede usted ayudar al proyecto sea cual sea su preparación y el área en la que disponga de experiencia o interés. Invitamos a las empresas que tienen proyectos relacionados con FreeBSD a que se pongan en contacto con nosotros. ?Necesitan una extensión concreta para hacer que su producto funcione? Estaremos encantados de escuchar sus peticiones (suponiendo que no sean demasiado esotéricas). ?Su proyecto es interesante y/o beneficioso para su empresa y para FreeBSD? ¡Háganoslo saber! Podemos trabajar conjuntamente en algunos aspectos del mismo. El mundo del software libre está cambiando muchas de las normas establecidas sobre cómo el software debería ser desarrollado, vendido y mantenido así que le rogamos encarecidamente que al menos le dé un segundo vistazo. Qué es lo que hace falta La siguiente lista de tareas y subproyectos representa de algún modo la amalgama de listas de TAREAS PENDIENTES y peticiones de usuarios. Tareas en Curso para No Programadores Una gran parte de quienes trabajan en FreeBSD no son programadores. El Proyecto incluye escritores de documentación, diseñadores y técnicos de soporte. Los únicos requisitos necesarios son poner algo de su tiempo y ganas de aprender. Lea cuidadosamente las FAQ y el Handbook cada cierto tiempo. Si algo está mal explicado, desfasado o sencillamente completamente equivocado háganoslo saber. Aún mejor, envíenos la corrección (no es difícil aprender SGML pero no hay problema si lo envía en ASCII). Ayude a traducir la documentación de FreeBSD a su lengua materna. Si ya existe documentación en su idioma puede ayudar a traducir otros documentos o a mantener al día los que ya existan. Antes de nada consulte Translations FAQ en el FreeBSD Documentation Project Primer. El hecho de traducir algo no implica la obligación de traducir todo: al ser una tarea voluntaria puede usted traducir tanto o tan poco como prefiera. Cuando alguien empieza a traducir casi siempre hay alguien que se une. Si sólo tiene tiempo o ganas para traducir una parte de la documentación por favor, traduzca las instrucciones de instalación. Lea la &a.questions; y el &ng.misc; de vez en cuando (o incluso regularmente). Compartir sus conocimientos mientras ayuda a la gente a resolver sus problemas puede ser muy gratificante. ¡Puede ser que incluso aprenda usted también algo nuevo! Esos foros pueden ser también un importante foco de ideas para nuevas cosas en las que trabajar. Tareas en Curso para Programadores La mayoría de las tareas aquí expuestas requieren una considerable cantidad de tiempo o un conocimiento profundo del kernel de FreeBSD o ambas cosas. Existen, sin embargo, multitud de tareas muy útiles que son ideales para hackers de fin de semana. Si utiliza FreeBSD-CURRENT y tiene una buena conexión con Internet existe una máquina llamada current.FreeBSD.org que genera diariamente (en teoría, la frecuencia puede variar) una distribución completa. Intente instalar la última versión desde ella e informe de cualquier anomalía en el proceso. Lea la &a.bugs;. Puede encontrar algún problema sobre el que hacer un comentario constructivo o sobre el que probar parches. Puede incluso intentar arreglarlo usted. Si sabe de alguna corrección que ha sido aplicada con éxito a -CURRENT pero que aún no haya sido incluída en -STABLE tras un período de tiempo razonable (por lo general un par de semanas) envíe al committer responsable un (educado) mensaje recordándoselo. Mueva software de terceras partes a src/contrib en el árbol de fuentes. Asegúrese de que el código de src/contrib está actualizado. Compile el árbol de fuentes (o sólo una parte del mismo) con una cantidad extra de warnings activadas y depúrelas. Corrija warnings en los ports en los que aparecen cosas en desuso como gets() o que incluyen malloc.h. Si ha enviado algún port envíe sus parches a los autores originales: le hará la vida más fácil cuando liberen la siguiente versión. Consiga copias de estándares formales como POSIX. Hay enlaces relacionados con esos estándares en el sitio web del FreeBSD C99 & Posix Standards Conformance Project. Compare el funcionamiento interno de FreeBSD con el que exije el estándar. Si hay diferencias, en especial en algún rincón sutil y oscuro de la especificación, envíe un PR (Problem Report). Si es capaz de aventurar una solución incluya un parche en el PR. Si cree que el estándar es incorrecto póngase en contacto con los responsables del mismo para que tengan en cuenta su propuesta. ¡Sugiera nuevas tareas para ésta lista! Trabajo en la <quote>PR Database</quote> base de datos de informes de problemas (PR) La lista de PR de FreBSD muestra los informes de problemas activos así como las peticiones de mejoras que han enviado los usuarios de FreeBSD. La PR database incluye tanto problemas que han de ser corregidos por programadores como por no programadores. Busque entre los PR que están abiertos, puede haber alguno que le interese. Algunos pueden ser tareas muy sencillas que sólo necesiten una mirada adicional para confirmar que la solución adjunta es la adecuada. Otras, por el contrario, pueden llegar a ser muchísimo más complejas o incluso no incluír una solución. Comience con un PR no haya sido aún asignado. Si el PR ya ha sido asignado a alguien pero cree que puede ayudar envíe un correo electrónico a la persona responsable del PR y pregúntele si puede colaborar (tal vez ya exista un parche listo para ser probado o puedan contrastar ideas). Cómo Colaborar Las colaboraciones al sistema generalmente pueden catalogarse en las siguientes 5 categorías: Informes de Errores y Comentarios Generales Las ideas o sugerencias de interés técnico general deben enviarse a &a.hackers;. En consecuencia, si le interesan ese tipo de cuestiones (¡y no le importa recibir un gran volumen de correo!) debería suscribirse a la &a.hackers; enviando un correo electrónico a &a.majordomo;. Consulte el FreeBSD Handbook para más información sobre ésta y otras listas de correo. Si encuentra un error o quiere enviar un cambio concreto por favor utilice el programa &man.send-pr.1; o su equivalente en la web (N. del T.: El interfaz web de send-pr fué desactivado a causa del spam). Trate de rellenar todos los campos del informe de errores. A menos que exceda de 65KB puede incluír los parches directamente en el informe. Si es posible aplicar el parche al árbol de fuentes no olvide incluír [PATCH] en la sinópsis del informe. Cuando incluya parches no copie y pegue ya que las tabulaciones son transformadas en espacios, haciendo el parche inútil. Considere la posibilidad de comprimir los parches mediante &man.uuencode.1; si sobrepasan los 20KB. Tras rellenar el informe debería recibir un mensaje de confirmación junto con un número de seguimiento. Conserve ese número por si en algún momento pudiera añadir nueva información sobre el problema enviando correo a FreeBSD-gnats-submit@FreeBSD.org. Utilice el número como asunto del mensaje (por ejemplo, "Re: kern/3377". Así debería enviarse la información adicional sobre cualquier PR. Si no recibe confirmación en un período de tiempo razonable (entre 3 días y una semana, dependiendo de su tipo de conexión) o si por alguna razón no puede utilizar el comando &man.send-pr.1;, puede solicitar que alguien lo haga por usted enviando un correo a &a.bugs;. No olvide consultar éste article sobre cómo escribir buenos informes de problemas. Cambios en la Documentación envíos de documentación Los cambios en la documentación son revisados por la &a.doc;. Por favor, consulte FreeBSD Documentation Project Primer para recibir instrucciones detalladas. Envíe nuevos contenidos o cambios sobre los ya existentes (¡incluso los pequeños son bienvenidos!) mediante &man.send-pr.1; tal y como se detalla en Informes de Error y Comentarios Generales. Cambios al Código Fuente ya Existente FreeBSD-CURRENT Añadir cambios o modificar el código fuente existente es un tema delicado y depende mucho de hasta qué punto esté usted al día sobre el estado actual del desarrollo de FreeBSD. Hay una versión en desarrollo permanente de FreeBSD conocida como FreeBSD-CURRENT, disponible de muy diversas formas para mayor comodidad de los desarrolladores que están trabajando activamente en el sistema. Consulte el FreeBSD Handbook, donde se explica cómo obtener y utilizar FreeBSD-CURRENT. Si trabaja con versiones anticuadas de los fuentes desafortunadamente significará que sus cambios podrían con frecuencia resultar demasiado obsoletos o demasiado divergentes para una fácil reintegración dentro de FreeBSD. Ésta posibilidad puede minimizarse suscribiéndose a la &a.announce; y a la &a.current;, donde tienen lugar los debates sobre el estado actual del sistema. Asumiendo que puede manejarse con seguridad con unos fuentes totalmente actualizados sobre los que aplicar sus cambios, el siguiente paso es generar los diffs que enviará al equipo de FreeBSD. Hágalo con el comando &man.diff.1;. El formato &man.diff.1; que preferimos para el envío de parches es la salida unificada generada por diff -u. Sin embargo, para parches que implican cambios sustanciales en una región de código una salida contextual de diff generada por diff -c resultará más legible y en consecuencia preferible. diff Por ejemplo: &prompt.user; diff -c ficheroantíguo ficheronuevo o &prompt.user; diff -c -r directorioantíguo directorionuevo generarían un conjunto de diffs contextuales de fichero fuente o la jerarquía de directorios. Del mismo modo &prompt.user; diff -u ficheroantíguo ficheronuevo o &prompt.user; diff -u -r directorioantíguo directorionuevo nos darían el mismo resultado excepción hecha del formato unificado de los diffs resultantes. Consulte la página man de &man.diff.1; para más detalles. Una vez que disponga de un conjunto de diffs (que debería probar con el comando &man.patch.1;) puede enviarlos para que sean incluídos en FreeBSD. Utilice el programa &man.send-pr.1; tal y como se muestra Informes de Errores y Comentarios Generales. ¡No se limite simplemente a enviar sus diffs a la &a.hackers; o se perderán! Agradecemos inmensamente su colaboración (¡éste es un proyecto que funciona gracias al trabajo desinteresado de mucha gente!). Estamos muy ocupados, así que no podemos atender inmediatamente todos y cada uno de los envíos recibidos, pero permanecerán en la PR database hasta que lo hagamos. Etiquete sus envíos incluyendo [PATCH] en la sinópsis del informe. uuencode Si lo considera oportuno (ésto es, si ha añadido borrado o renombrado ficheros) empaquete sus cambios en un fichero tar y ejecute el programa &man.uuencode.1; sobre él. Puede usar también ficheros creados con &man.shar.1; Si su cambio puede tener un cariz potencialmente delicado ésto es, no está seguro de bajo qué tipo de licencia sería su distribución ulterior o simplemente no está listo para liberarlo sin una revisión exhaustiva, debería enviarlo directamente a &a.core; en lugar de usar &man.send-pr.1;. El &a.core; incluye un grupo de gente mucho más pequeño que lleva a cabo la mayor parte del trabajo diario en FreeBSD. Tenga en cuenta que el &a.core; está muy ocupado y por lo tanto sólo debería enviársele correo cuando sea estrictamente necesario. Consulte la páginas man de &man.intro.9; y &man.style.9; para saber más acerca del estilo de codificación requerido. Le agradeceríamos mucho que al menos tuviera en cuenta esa información antes de enviar código. New Code or Major Value-Added Packages En el caso de una contribución significativa o de gran impacto, o si se trata de añadir una nueva característica importante a FreeBSD, enviar ficheros tar tratados con uuencode o por el contrario ponerlos a disposición de otras personas en un sitio web o FTP se convierte en algo prácticamente imprescindible. Si no dispone de acceso a un sitio web o FTP pregunte en la lista apropiada de FreeBSD para que alguien se lo facilite. Cuando se trabaja con un gran volumen de código el espinoso tema de la licencia invariablemente sale a la palestra. Las licencias admitidas para la inclusión de código en FreeBSD son: La Licencia BSD La licencia BSD. Ésta licencia es la preferida a causa de su naturaleza carente de requerimientos añadidos y su atractivo general para la empresa. Lejos de buscar evitar el uso comercial, el Proyecto FreeBSD recomienda vivamente la participación de entidades comerciales que pudieran en casos determinados dedicar parte de sus recursos a FreeBSD. GPLGNU General Public License GNU General Public License La GNU General Public License, o GPL. Ésta licencia no es tan popular debido al esfuerzo añadido que requiere de cualquiera que usara el código con fines comerciales, pero dada la ingente cantidad de código GPL que usamos habitualmente (el compilador, el ensamblador, el procesador de texto, etc) sería estúpido rechazar contribuciones bajo ésta licencia. El código bajo licencia GPL también se incluye bajo una parte diferenciada del árbol, pudiendo ser /sys/gnu o /usr/src/gnu, y es por tanto fácilmente identificable para quienes la licencia GPL suponga un problema. Todo lo que vaya bajo cualquier otro tipo de licencia requiere que ésta deba ser cuidadosamente revisada antes de que su inclusión en FreeBSD sea llevada a consideración. Las aportaciones bajo licencias comerciales particularmente restrictivas en vigor por lo general son rechazadas aunque siempre se recomienda a los autores que hagan públicamente accesible su trabajo usando sus propios medios. Para poner su trabajo bajo la licencia BSD inserte el siguiente texto al principio de todos y cada uno de los ficheros de código que quiera amparar bajo la misma, reemplazando el texto entre %% con la información apropiada: Copyright (c) %%años_exactos%% %%su_nombre%%, %%su_estado/país%% %%su_código_postal%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%su_nombre%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%su_nombre%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ Para su comodidad existe una copia de éste texto en /usr/share/examples/etc/bsd-style-copyright. Dinero, Hardware o Acceso a Internet Estamos encantados de aceptar donaciones económicas para ayudar a impulsar el Proyecto FreeBSD y, como en cualquier proyecto mantenido por voluntarios, un poco puede hacer mucho. También son muy importantes las donaciones de hardware para ampliar nuestra lista de hardware soportado, dado que normalmente andamos cortos de fondos con los que comprar ese tipo de material. <anchor id="donations"/>Donación de Fondos La Fundación FreeBSD es una fundación sin ánimo de lucro y exenta de impuestos creada para impulsar los objetivos del Proyecto FreeBSD. Como una entidad 501(c)3, la Fundación está prácticamente exenta del pago del impuesto federal de la renta de los EEUU así como del del Estado de Colorado. Las donaciones a una entidad libre de impuestos suelen ser deducibles en la declaración federal de impuestos. Las donaciones pueden enviarse mediante cheque a:
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
La Fundación FreeBSD puede también aceptar donaciones via web mediante PayPal. Para hacer una donación visite la página web de la Fundación. Puede encontrar más información sobre la Fundación en The FreeBSD Foundation -- an Introduction. Puede enviar correo electrónico a la Fundación a bod@FreeBSDFoundation.org. Donación de Hardware donaciones El Proyecto FreeBSD acepta encantado donaciones de hardware que le resulte útil. Si desea donar hardware por favor póngase en contacto con la Donations Liaison Office. Donación de Acceso a Internet Nunca viene mal una nueva réplica para sitios FTP, WWW o cvsup. Si desea ofrecer alguno de esos servicios por favor consulte el siguiente artículo Mirroring FreeBSD para más información. + +
diff --git a/es_ES.ISO8859-1/articles/nanobsd/article.xml b/es_ES.ISO8859-1/articles/nanobsd/article.xml index 61890e630e..c4c88e024b 100644 --- a/es_ES.ISO8859-1/articles/nanobsd/article.xml +++ b/es_ES.ISO8859-1/articles/nanobsd/article.xml @@ -1,563 +1,565 @@
Introducción a NanoBSD Daniel Gerzo 2006 The FreeBSD Documentation Project &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Este documento trata sobre NanoBSD. NanoBSD es una herramienta que permite crear imágenes del sistema &os; para su uso en aplicaciones empotradas y listas para cargarse en una tarjeta Compact Flash (u otro medio de almacenamiento masivo). &trans.es.german; Introducción a NanoBSD NanoBSD NanoBSD es una herramienta actualmente desarrollada por &a.phk;. Crea una imagen del sistema &os; para aplicaciones empotradas lista para su uso en una tarjeta Compact Flash (u otro medio de almacenamiento masivo). Puede utilizarse para generar imágenes instalables especiales; está diseñado pensando en una instalación y mantenimiento fáciles en sistemas conocidos como sistemas empotrados. Los sistemas empotrados tienen hardware y software integrado en el producto, lo que significa que todas las aplicaciones están preinstaladas. Estos dispositivos pueden conectarse a una red dada y comenzar a trabajar (casi) inmediatamente. Las características de NanoBSD incluyen: Los ports y paquetes funcionan como en &os;: Cualquier aplicación puede instalarse y usarse en una imagen de NanoBSD de la misma forma que en &os;. No se pierde funcionalidad: Si es posible hacer algo en &os; es posible hacer lo mismo en NanoBSD, a menos que se haya eliminado explícitamente esa característica o características especiales al crear la imagen de NanoBSD. Todo está en modo de sólo lectura durante el funcionamiento del sistema: Un apagado brusco es totalmente seguro. No es necesario ejecutar &man.fsck.8; después de que el sistema sufra un apagón. Fácil de generar y personalizar: Usando un solo script de shell y un fichero de configuración pueden generarse imágenes reducidas y personalizadas que satisfagan cualquier necesidad. NanoBSD <quote>Howto</quote> El diseño de NanoBSD Una vez que la imagen está en el medio puede arrancar NanoBSD. El medio de almacenamiento se divide por omisión en tres partes: Dos particiones de la imagen: code#1 y code#2. La partición que contiene los ficheros de configuración, que puede montarse bajo /cfg durante el funcionamiento del sistema. Estas particiones se montan normalmente en modo de sólo lectura. Los directorios /etc y /var son discos &man.md.4; (malloc). La partición de los ficheros de configuración permanece bajo el directorio /cfg. Este directorio contiene ficheros que usa el directorio /etc y se monta en modo de sólo lectura inmediatamente después del arranque; por lo tanto, es necesario que los ficheros que se modifiquen en /etc se copien en /cfg si se desea que los cambios perduren después del reinicio del sistema. Cómo hacer cambios persistentes en <filename>/etc/resolv.conf</filename> &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg La partición que contiene el directorio /cfg debería montarse únicamente en el arranque y mientras se sobreescriben los ficheros de configuración. No es buena idea montar siempre el directorio /cfg, especialmente si el sistema NanoBSD se ejecuta en un dispositivo de almacenamiento masivo que pueda verse afectado negativamente por un número elevado de escrituras en la partición (i.e. cuando el sistema de ficheros sincroniza los datos con el sistema de discos). Cómo generar una imagen de NanoBSD Una imagen de NanoBSD se genera usando el sencillo script de shell nanobsd.sh, ubicado en el directorio /usr/src/tools/tools/nanobsd. El script crea una imagen que se deberá copiar al medio de almacenamiento mediante la utilidad &man.dd.1;. Los comandos necesarios para generar una imagen de NanoBSD son: &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k Cambia el directorio actual por el directorio base del script de generación de NanoBSD. Comienza el proceso de generación. Cambia el directorio actual por el directorio donde se encuentra la imagen generada. Instala NanoBSD dentro del medio de almacenamiento. Personalización de una imagen de NanoBSD Esta es probablemente la característica más importante y más interesante de NanoBSD. Tambié es donde usted pasará la mayor parte del tiempo cuando esté desarrollando con NanoBSD. La invocación del siguiente comando forzará al script nanobsd.sh a leer su configuración desde el fichero mi-configuracion.nano ubicado en el directorio actual: &prompt.root; sh nanobsd.sh -c mi-configuracion.nano La personalización se hace de dos maneras: Opciones de configuración Funciones personalizadas Opciones de configuración Por medio de ajustes de configuración es posible configurar las opciones que se pasan a las fases buildworld e installworld del proceso de generación de NanoBSD. Mediante estas opciones puede reducirse el tamaño del sistema de manera que pueda incluso encajar en algo tan pequeño como un dispositivo de 64MB. Es posible recortar &os; incluso más, hasta que consista únicamente en el kernel y dos o tres ficheros de userland. El fichero de configuración está compuesto por opciones de configuración que sobreescriben los valores por omisión. Las directivas más importantes son: NANO_NAME : Nombre de la generación que estamos ejecutando (se usa para dar nombres a los directorios donde encontraremos el resultado del proceso). NANO_SRC : Ruta al código fuente que se usará para generar la imagen. NANO_KERNEL : Nombre del fichero de configuración del kernel que se usará para generar el kernel. CONF_BUILD : Opciones que se pasan a la fase buildworld. CONF_INSTALL : Opciones que se pasan a la fase installworld. CONF_WORLD : Opciones que se pasan tanto a buildworld como a installworld. FlashDevice : Define el tipo de medio de almacenamiento que se usará. Para más información consulte el fichero FlashDevice.sub. Funciones personalizadas Puede ajustar NanoBSD de forma muy precisa mediante el uso de funciones de shell en el fichero de configuración. En el siguiente ejemplo vemos un modelo básico de función personalizada. cust_foo () ( echo "bar=topless" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo A continuación vemos un ejemplo más útil de función personalizada, que cambia el tamaño por omisión del directorio /etc de 5MB a 30MB: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size Hay unas pocas funciones de personalización predefinidas listas para su uso: cust_comconsole : Deshabilita &man.getty.8; en los dispositivos VGA (los nodos de dispositivo /dev/tty*) y habilita el uso del puerto serie COM1 para que sea la consola del sistema. cust_allow_ssh_root : Permite a root acceder a través de &man.sshd.8;. cust_install_files : Instala ficheros de configuración desde el directorio nanobsd/files, que contiene scripts útiles para la administración del sistema. Cómo añadir paquetes Se pueden añadir paquetes a la imagen de NanoBSD usando una función personalizada. La siguiente función instalará todos los paquetes que se encuentren en /usr/src/tools/tools/nanobsd/packages: install_packages () ( mkdir -p ${NANO_WORLDDIR}/packages cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;' rm -rf ${NANO_WORLDDIR}/packages ) customize_cmd install_packages Ejemplo de fichero de configuración El siguiente es un ejemplo completo de fichero de configuración para generar una imagen personalizada de NanoBSD: NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie Cómo actualizar NanoBSD El proceso de actualización de NanoBSD es relativamente simple: Generar una nueva imagen de NanoBSD de la forma habitual. Copiar la nueva imagen sobre la partición no utilizada del sistema empotrado que está usando NanoBSD. La diferencia más importante entre este paso y la instalación inicial de NanoBSD es que ahora en lugar de usar el fichero _.disk.full (que contiene una imagen de todo el disco) se instala la imagen _.disk.image (que contiene una imagen de una sola partición). Reiniciar y arrancar el sistema desde la partición que se acaba de instalar. Si todo va bien la actualización ha terminado. Si algo va mal reinicie desde la partición anterior (que contiene la imagen vieja, pero que funciona) para recuperar el funcionamiento del sistema lo antes posible. Arregle los problemas de la nueva generación y repita el proceso. Para facilitar la instalación de una imagen nueva en su sistema NanoBSD en funcionamiento dispone de los scripts updatep1 y updatep2, ubicados en el directorio /root. La elección de uno u otro script depende de qué partición esté ejecutando el sistema, la primera o la segunda. Dependiendo de los servicios disponibles en la máquina que va a servir la nueva imagen de NanoBSD y del tipo de transferencia de datos que prefiera uno de estos tres métodos le resultará más o menos interesante: Uso de &man.ftp.1; Si la prioridad es la velocidad de la transferencia use usted este ejemplo: &prompt.root; ftp mi-maquina get _.disk.image "| sh updatep1" Uso de &man.ssh.1; Si la prioridad es la seguridad de la transferencia seguramente ejecutará algo muy parecido a lo siguiente: &prompt.root; ssh mi-maquina cat _.disk.image.gz | zcat | sh updatep1 Uso de &man.nc.1; Si la máquina remota no dispone de servicios de &man.ftp.1; ni de &man.sshd.8; puede recurrir al siguiente ejemplo: Primero abra un puerto TCP de escucha en la máquina que sirve la imagen y envíela al cliente: mi-maquina&prompt.root; nc -l 2222 < _.disk.image Asegúrese de que el puerto elegido no tenga bloqueadas las conexiones entrantes desde la máquina NanoBSD por ningún cortafuegos. Conéctese a la máquina que va servir la nueva imagen y ejecute el script updatep1: &prompt.root; nc mi-maquina 2222 | sh updatep1 + +
diff --git a/es_ES.ISO8859-1/articles/problem-reports/article.xml b/es_ES.ISO8859-1/articles/problem-reports/article.xml index ad3ac9ab1b..ec3556b053 100644 --- a/es_ES.ISO8859-1/articles/problem-reports/article.xml +++ b/es_ES.ISO8859-1/articles/problem-reports/article.xml @@ -1,1015 +1,1017 @@
Cómo enviar informes de problemas de &os; $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; Este artículo describe cómo realizar y enviar informes de errores para el proyecto &os; de la mejor forma posible. &trans.es.jrh; Dag-Erling Smørgrav Escrito por $FreeBSD$ problem reports
Introducción Una de las experiencias más fustrantes que se pueden experimentar como usuario de software es aquella en la cual el usuario se toma la molestia de rellenar un informe de problemas detallado para observar tras un determinado espacio de tiempo que dicho informe se cierra con una explicación corta y abrupta como no es un error o PR erroneo. De forma semejante, una de las experiencias más fustrantes que puede experimentar un desarrollador de aplicaciones consiste en verse inundado por una cantidad ingente de informes de errores que en realidad vienen a ser solicitudes de soporte o ayuda, o que contienen poca o ninguna información sobre cúal es el problema y como se puede reproducir. Este documento intenta describir cómo escribir informes de problemas de calidad. Usted se preguntará cómo se pueden escribir informes de problemas de calidad. Bien, para ir directos al grano, un informe de problemas de calidad es aquél que se puede analizar y tratar rápidamente, para mútua satisfacción del usuario y del desarrollador. Aunque el objetivo principal de este artículo se centra en los informes de problemas de &os; la mayoría de los conceptos se pueden aplicar bastante bien en otros proyectos de software. Dése cuenta de que este artículo se organiza de forma temática, no cronológicamente, de tal forma que se debe leer el documento íntegro antes de enviar informes de problemas. No debe tratarse como un tutorial del estilo paso a paso.
Cuándo enviar informes de problemas Existen varios tipos de problemas y no todos ellos se merecen la creación de un informe de problemas. Por supuesto, nadie es perfecto, y existirán ocasiones en las que estaremos convencidos de haber encontrado un bug en un programa cuando realmente hemos malinterpretado la sintaxis o el funcionamiento de dicho programa, o simplemente hemos cometido un error tipográfico en un fichero de configuración (aunque en este último caso podría tratarse de un indicador de documentación escasa o que la aplicación peca de una gestión de errores defectuosa. Incluso teniendo estos aspectos en cuenta existen varios casos en los cuales el envío de un informe de problemas resulta claramente no ser la mejor forma de proceder, ya que dicho envío puede servir para frustrar tanto a quien envía el informe como a quien desarrolló la aplicación. Por el contrario, también existen casos en los que puede resultar apropiado enviar un informe de problemas sobre algo más aparte de bugs: una mejora o una solucitud nuevas características, por citar un par de ejemplos. Así que ?cómo podemos determinar qué constituye un bug y qué no? Como regla para principiantes podemos decir que su problema no es un bug si se puede expresar como una pregunta (normalmente del estilo de ?cómo hago X? o ?donde puedo encontrar Y?). No siempre las cosas son blancas o negras, pero la regla de las preguntas suele cubrir una gran mayoría de casos. Si lo que se quiere es una respuesta a una consulta, se pueden enviar dichas preguntas a la &a.questions;. A continuación se muestran algunos casos en los que resulta apropiado enviar un informe de problemas sobre algo que no se considera un bug: Solucitudes para mejora de características. Normalmente es una buena idea airear estas propuestas en las listas de distribución antes de enviar un informe de problemas. Notificación de actualizaciones de software que se mantiene externamente (principalmente ports, pero también componentes del sistema base al cargo de proyectos independientes de &os;, como BIND o diversas utilidades GNU) Otro tema es que si el sistema donde se experimentó el bug no está medianamente actualizado se debe considerar muy seriamente su actualización e intentar reproducir el problema en un sistema actualizado antes de emitir el informe. Existen pocas cosas que molesten más a un desarrollador que recibir un informe de problemas sobre un problema que ya ha resuelto. Por último, un bug que no se puede reproducir difícilmente puede arreglarse. Si el bug sólo ocurrió una vez y no somos capaces de reproducirlo, y parece que no le ocurre a nadie más, es muy probable que ni siquiera los desarrolladores puedan reproducirlo y por lo tanto ni siquiera puedan imaginarse qué es lo que falla. Esto no significa que el bug no haya ocurrido, sino que las probabilidades de que nuestro informe de errores sirva para corregir un defecto son muy pequeñas. Para complicar más las cosas, a menudo estas clases de errores se producen debido a fallos en los discos duros o al sobrecalentamiento del procesador: debe intentar siempre descubrir estos fallos, siempre que sea posible, antes de enviar un PR.
Preparativos Una buena regla que se puede seguir consiste en realizar siempre una búsqueda antes de enviar un informe de problemas. Quizá nuestro problema ya ha sido reportado; quizá se está discutiendo en las listas de distribución o fue discutido hace poco; incluso es posible que se haya arreglado en versiones más recientes del software. Por lo tanto, se deben consultar los sitios y fuentes más obvias antes de proceder con el envío del informe de errores. En &os; esto significa: Las Preguntas Más Frecuentes (FAQ) de &os;. Las FAQ intentan proporcionar respuestas para un amplio rango de dudas, tales como aquellas relacionadas con las compatibilidades hardware, las aplicaciones de usuario y la configuración del kernel. Las listas de correo. Si no está subscrito utilice la búsqueda en los archivos del sitio web de &os;. Si el problema no se ha discutido con anterioridad en las listas, se puede intentar enviar un mensaje y esperar unos pocos días para ver si alguien puede aconsejarle adecuadamente sobre algún punto que quizá haya pasado por alto en relación con el problema. Opcionalmente, la web entera—utilice su motor de búsqueda favorito para localizar cualquier referencia a su problema. Incluso pueden aparecer listas de correo o grupos de noticias de los cuales ni siquiera tuviera conocimiento de su existencia o quizá no consideró apropiado consultarlas al principio. A continuación, la búsqueda a través de la base de datos &os; PR (GNATS). A menos que nuestro problema sea muy reciente o rebuscado, existe un gran número de posibilidades de que ya haya sido informado o reportado. Lo más importante, se debería intentar comprobar si la documentación existente en el código fuente del programa puede resolver el problema. En el caso de las fuentes del sistema &os; debe estudiarse cuidadosamente el contenido del fichero /usr/src/UPDATING del sistema o su última versión, que se encuentra en . (Esta información se considera de vital importancia si se está actualizando de una versión a otra, especialmente si la actualización se realiza de la versión estable a la versión &os.current;). No obstante, si el problema se encuentra en algo que se instaló como parte de la collección de ports de &os;, se debe consultar el archivo /usr/ports/UPDATING (para ports individuales) o el archivo /usr/ports/CHANGES (para cambios que afectan a la colección de ports completa). y también se encuentran disponibles a través de CVSweb. A continuación debemos asegurarnos de que el informe de errores llega a las personas adecuadas. La primera consideración llegados a este punto consiste en: Si el problema resulta ser un bug en un software de terceras partes (un port o un paquete que se ha instalado) se debe informar sobre el bug al autor original del software, no al proyecto &os;. Existen dos excepciones a esta regla: la primera ocurre cuando el bug no se produce en otras plataformas, en cuyo caso el problema puede residir en cómo fue migrado el software a &os;; la segunda excepción ocurre cuando el autor original ya ha corregido el problema y distribuido un parche o una nueva versión de su software, pero el port de &os; todavía no se ha actualizado. La segunda consideración es que el sistema de seguimiento de bugs de &os; ordena los informes de problemas de acuerdo con la categoría que ha seleccionado el informador. De este modo, si se selecciona una categoría incorrecta cuando se envía el informe de problemas, existe una gran probabilidad de que nadie se de cuenta de su existencia durante un período de tiempo indefinido, hasta que alguien se encarge de re-categorizarlo.
Escribir el informe de problemas Ahora que hemos determinado que el problema que estamos experimentando se merece la redacción de un informe de problemas y que se trata de un problema de &os;, es la hora de comenzar a escribir dicho informe. Antes de pasar a describir los mecanismos utilizados por el programa encargado de generar los informes PR, vamos a describir una serie de trucos y consejos que nos asegurarán la mayor efectividad posible de nuestro informe.
Consejos y trucos para escribir un buen informe de problemas No deje la línea de Synopsis vacía. Los PRs se dirigen tanto a una lista de correo mundial (donde se utiliza el campo Synopsis para rellenar la línea Subject: del correo) como a una base de datos (GNATS). Cualquier persona que consulte la base de datos por el campo sinopsis y encuentre un PR con una línea de Asunto vacía tiende simplemente a pasar por alto el informe. Recuerde que un PR permanece en la base de datos hasta que alguien se encarga de cerrar el informe; un informe anónimo normalmente se perderá para siempre entre el ruido y tardará mucho en cerrarse. Evite utilizar una línea de Synopsis débil.. No debe suponerse que quien lea el PR conoce el contexto adecuado en el que su mensaje tiene sentido, así que cuanta más información se proporcione, mejor que mejor. Por ejemplo, ?qué parte del sistema se ve afectado por el informe?, ?el problema aparece cuando se está instalando o cuando se está ejecutando?. Para ejemplificar, en lugar de Synopsis: portupgrade is broken, se pueden ver las ventajas que proporciona una línea como la siguiente: Synopsis: port sysutils/portupgrade produce un coredump en -current. (En el caso concreto de los ports, resulta especialmente útil poseer tanto la categoría como el nombre del port en la línea Synopsis.) Si se dispone de un parche, dígalo. Un PR con un parche incluido tiene muchas más posibilidades de ser tratado que uno que no lo tiene. Si se include dicho parche, escriba la cadena [patch] al comienzo de la línea Synopsis. (Aunque no es obligatorio utilizar dicha cadena, se trata de un estándar de facto que se utiliza de forma mayoritaria.) Si es mantenedor del port, dígalo. Si se está manteniendo el código fuente de una aplicación (por ejemplo, de un port), se puede considerar la adición de la cadena [maintainer update] al comienzo de la línea de sinopsis, y además se debería asignar el campo Class del PR a la cadena maintainer-update. De esta forma cualquier committer que maneje el PR no tendrá que realizar comprobaciones. Sea concreto. Cuanta más información se proporcione sobre el problema que se tiene, más posiblidades de obtener una respuesta. Incluya la versión del &os; que se está ejecutando (existe un lugar donde escribir esta esta información, vea más abajo) y en qué arquitectura. Se debe incluir si se está ejecutando desde una release (e.g. desde un CDROM o descarga), o si es desde un sistema mantenido mediante &man.cvsup.1; (y, si esto último se cumple, con qué frecuencia se realiza la actualización). Si se está siguiendo la rama &os.current;, se trata de la primera pregunta que nos harán, debido a que los parches (sobre todo para problemas de alto nivel) tienden a aplicarse muy rápidamente, y se espera de los usuarios de &os.current; un seguimiento cercano de las actualizaciones aplicadas. Incluya qué opciones globales se han especificado en el archivo make.conf. Aviso: Es bien conocido por todos que especificar -O2 y valores superiores para &man.gcc.1; produce fallos y resulta ser proclive a errores en muchas situaciones. Aunque los desarrolladores de &os; normalmente dan por buenos y aceptan los parches proporcionados por el creador del informe de problemas, normalmente no desean investigar dichas condiciones extrañas debido simplemente a la falta de tiempo y de voluntarios, y puede que respondan diciendo simplemente que dicha opción de compilación no se encuentra soportada. Si se trata de un problema del kernel, prepárese para proporcionar la siguiente información. (No es necesario incluir esta información por defecto, puesto que lo único que produce es un crecimiento desmesurado de la base de datos GNATS, pero sí puede merecer la pena incluir resúmenes que usted considere importantes): La configuración del kernel (incluyendo los dispositivos hardware que se tienen instalados) Si se tienen opciones de depuración activadas (tales como WITNESS), y en tal caso, si el problema persiste cuando se cambia el valor de dichas opciones Una traza de depuración, si se pudo generar. El hecho de que se ha leido detenidamente el archivo src/UPDATING para constatar que el problema no se ha identificado allí (se garantiza que alguién le preguntará sobre este punto) Si se puede o no se puede ejecutar otro kernel sin problemas (se trata de identificar problemas relacionados con el hardware como discos con errores o CPUs sobrecalentadas, que pueden confundirse fácilmente con problemas del kernel) Si se trata de un problema relacionado con los ports, prepárese para poder proporcionar la información que se muestra a continuación. (No es necesario incluir esta información por defecto, ya que sólo produce un crecimiento indeseado de la base de datos, pero sí se pueden incluir resúmenes de aquellos datos que usted considere relevantes): Los ports que se tiene instalados Cualesquiera variables de entorno que sobreescriban los valores por defecto del archivo bsd.port.mk, tales como PORTSDIR El hecho de que se ha leido ports/UPDATING y que nuestro problema no se encuentra identificado en dicho archivo (se garantiza que alguien puede preguntar este hecho). Evitar peticiones de características vagas. Los PRs del estilo de alguien debería implementar algo que haga esto y aquello y lo de más allá son informes con pocas probabilidades de obtener resultados positivos. Las características deben ser muy concretas y específicas. Recuerde que el código fuente se encuentra disponible para todo el mundo, de tal forma que si usted necesita una característica, la mejor forma de verla incluida en futuras versiones de la herramienta consiste en ponerse usted mismo a trabajar sobre ella, manos a la obra. También tenga en cuenta que para discutir este tipo de problemas resulta más adecuado utilizar la lista freebsd-questions, como ya se ha comentado anteriormente. Asegúrese que nadie más ha enviado un PR similar. Aunque esto ya se ha mencionado anteriormente, merece la pena que se repita en este punto. Sólamente lleva uno o dos minutos realizar una búsqueda basada en un motor web en . (Por supuesto, a todo el mundo se le puede olvidar realizar esto de vez en cuando, pero por esa misma razón merece la pena hacer incapié en ello) Evite peticiones controvertidas. Si nuestro PR se dirige hacia un área o tema controvertido en el pasado, debemos prepararnos no sólo a ofrecer parches, si no también a justificar por qué motivo los parches proporcionados son la Forma Correcta de Hacerlo. Como se avisó anteriormente, una búsqueda meticulosa en las listas de correo en los archivos históricos sitos en resulta siempre una buena idea y sirve para preparar nuestro razonamiento y aprender de la experiencia y de las decisiones tomadas en el pasado. Sea educado. Casi cualquier persona que se encarge de tratar nuestro informe de problemas trabajará en el como un voluntario. A nadie le gusta que le digan cómo hacer las cosas cuando ya se están haciendo de una forma determinada, especialmente cuando la motivación para realizarlas no es monetaria. Este hecho es bueno tenerlo en mente y aplicarlo para cualquier proyecto de Software Libre.
Antes de comenzar. Antes de ejecutar el programa &man.send-pr.1;, asegúrese de que la variable de entorno VISUAL (o EDITOR si la variable VISUAL no se encuentra definida) se encuentra apuntando a algo con sentido. Es importante comprobar que la entrega de correo funciona correctamente. &man.send-pr.1; utiliza mensajes de correo para enviar y realizar un seguimiento de los informes de problemas. Si no se puede generar correo electrónico desde la máquina en la que se ejecuta &man.send-pr.1;, el informe jamás llegará a la base de datos GNATS. Si quiere saber más sobre la configuración del correo en &os; consulte el capítulo de Correo Electrónico del manual de &os; en .
Adjuntar parches o archivos El programa &man.send-pr.1; posee la capacidad de adjuntar archivos al informe de problemas. Se pueden adjuntar tantos archivos como se quiera siempre y cuando se utilice un nombre distinto para cada archivo (e.g. el nombre del archivo después de eliminar el path). Simplemente basta con utilizar la opción de línea de comandos para especificar los nombres de todos los archivos que se desean adjuntar: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors No se preocupe por los archivos binarios, dichos archivos se codifican automáticamente para no interferir con el agente de correo. Si se adjunta un parche, asegúrese que se utiliza la opción o la opción de &man.diff.1; para crear un contexto unificado (el contexto suele ser el preferido por quienes lo han de recibir) y además asegúrese de especificar los números de revisión de CVS de los archivos que se modifican para que los desarrolladores que lean el informe puedan aplicar dichos parches fácilmente. Para problemas relacionados con el kernel o con las utilidades del sistema base, se prefiere un parche contra &os.current; (la rama HEAD del árbol CVS) ya que cualquier código nuevo debe probar se primeramente en dicha rama. Después de comprobar su correcto funcionamiento de una forma sustancial y extensa, eventualmente dicho código pasará a formar parte de &os.stable;, mediante unión o migración. Si se envía un parte en línea, en vez de como adjunto, tenga en cuenta que el principal problema de esta forma de enviar los parches es que, dependiendo del lector de correo utilizado, algunos lectores muestran los tabuladores como espacios, lo cual arruina completamente el formato y la indentación del parche, e invalida totalmente un parche que forme parte de un Makefile. También tenga en cuenta que mientras que la inclusión de parches en un PR se considera como algo positivo—particularmente cuando se soluciona el problema que describe el informe—partes grandes y especialmente código nuevo que puede requerir una sustancial revisión antes de ser aplicado debería hacerse accesible a través de otros medios, como páginas web o servidores de ftp, y en vez de incluir el parche en el informe se puede incluir la URL. Los parches de gran tamaño en los correos electrónicos tienden a mezclarse o partirse, especialmente cuando GNATS los trata, y cuanto más grande es el parche más difícil resulta recuperar el original. También existe una ventaja añadida a la inclusión del parche a través de una URL, ya que de este modo se puede modificar el parche sin tener que reenviar el informe como una respuesta al informe inicial. Se debe prestar atención también al hecho de que, a menos que se especifique explícitamente lo contrario en el PR o en el propio parche, cualquier parche enviado se supone licenciado bajo los mismos términos y condiciones que el archivo original que modifica.
Rellenar la plantilla Cuando se ejecuta &man.send-pr.1; se nos presenta en pantalla una plantilla. Esta plantilla consiste en una lista de campos, algunos de los cuales se encuentran ya rellenados, mientras que otros poseen comentarios donde se explica su propósito o se comentan los valores aceptables. No se preocupe por los comentarios, puesto que se borran automáticamente antes de generar el informe. Al comienzo de la plantilla, justo debajo de las líneas de SEND-PR:, se encuentran las cabeceras de correo electrónico. Dichas cabeceras normalmente no se tienen que modificar, a menos que se esté rellenando el informe desde una máquina que puede enviar correo pero no puede recibirlo directamente, en cuyo caso usted tendrá que editar los campos From: y Reply-To: para escribir la dirección de correo válida. También puede enviarse una copia a usted mismo o a cualquier otra persona rellenando el campo Cc:. A continuación aparecen una serie de campos de una sola línea: Submitter-Id: No cambie este campo. El valor por defecto current-users es correcto, incluso si se está ejecutando &os.stable;. Originator: Se rellena automáticamente con el campo gecos del usuario que está actualmente dentro del sistema. Por favor, especifique su nombre real, opcionalmente acompañado por su dirección de correo electrónico entre < >. Organization: Escriba lo que usted quiera. Este campo no se utiliza para nada significativo. Confidential: Esto se rellena automáticamente con el literal no. Cambiar este valor carece de sentido ya que no existe ningún informe de problemas de &os; confidencial—la base de datos de PR se distribuye a todo el mundo de forma pública mediante CVSup. Synopsis: Rellene este campo con una descripción corta y precisa del problema. La sinopsis se utiliza como subject del correo electrónico del informe de problemas, y también se utiliza en los listados y resúmenes de informes de la base de datos; informes de problemas con obscuras sinopsis tienden a ser completamente ignorados. Como se avisó anteriormente, si su informe de problemas incluye un parche, por favor incluya en la sinopsis la etiqueta [patch] al comienzo; si usted es un mantenedor de software, también puede añadir la cadena [maintainer update] y asignar el campo Class del informe al valor maintainer-update. Severity: Los valores aceptados son non-critical, serious o critical. No sea exagerado; evite etiquetar el problema como critital a menos que sea realmente algo crítico (e.g. escalada de permisos hacia root, kernel panic fácilmente reproducible). Incluso debe pensarse detenidamente etiquetar algo como serious a menos que se trate de algo que afecte a muchos usuarios (problemas con drivers de dispositivos particulares o con utilidades del sistema). Los desarrolladores de &os; no van a resolver el problema más rápido por el hecho de variar esta etiqueta, debido a que existe mucha gente que infla este campo inadecuadamente. De hecho, los desarrolladores prestan muy poca atención al valor de este campo y del siguiente precisamente por esto último. Priority: Los valores aceptados son low, medium o high. high debe reservarse para problemas que afecten a la mayoría de los usuarios de &os; y medium para aquellos problemas que afecten a varios usuarios. Category: Seleccione uno de los siguientes valores (extraídos de /usr/gnats/gnats-adm/categories): advocacy: para problemas relacionados con la imagen pública de &os;. Raras veces utilizado. alpha: para problemas específicos de la plataforma Alpha. amd64: para problemas específicos de la plataforma AMD64. bin: para problemas con aplicaciones de la zona de usuario del sistema base. conf: para problemas de archivos de configuración, valores por defecto, etc. docs: para problemas con las páginas de manual o la documentación online. gnu: para problemas realacionados con aplicaciones gnu de &os; tales como &man.gcc.1; o &man.grep.1;. i386: para problemas específicos de la plataforma &i386;. ia64: para problemas específicos de la plataforma ia64. java: para problemas relacionados con &java;. kern: para problemas relacionados con el kernel o con (no especifícos de ninguna plataforma) controladores de dispositivos. misc: para cualquier cosa que no encaja en ninguna de las anteriores categorías. (Tenga en cuenta que es muy fácil que los problemas bajo esta categoría se pierdan en el olvido). ports: para problemas relacionados con el árbol de ports. powerpc: para problemas específicos de la plataforma &powerpc;. sparc64: para problemas específicos de la plataforma &sparc64;. standards: para problemas relativos a la adecuación con estándares. threads: para problemas relacionados con la implementación de threads de &os; (especialmente en &os.current;). www: para cambios o mejoras del sitio web de &os;. Class: Se puede seleccionar uno entre los siguientes: sw-bug: bugs de software. doc-bug: errores en la documentación. change-request: peticiones de características adicionales o de cambios en las características existentes. update: actualizaciones de ports o de software contribuido por terceros. maintainer-update: actualizaciones de ports de los cuales usted es mantenedor. Release: La versión de &os; que se está ejecutando. El programa &man.send-pr.1; rellena automáticamente este campo, por lo que sólamente resulta necesaria su modificación cuando estemos rellenando un informe de problemas desde un sistema distinto al sistema donde se ha producido dicho problema. Por último, existen una serie de campos multilínea: Environment: Este campo debe describir, tan preciso como sea posible, el entorno en el cual se ha observado el problema. Esto incluye la versión del sistema operativo, la versión del programa que contiene el problema y cualquier otro asunto relevante tales como la configuración del sistema o cualquier otro software instalado que pueda influir en la ejecución del primero, etc. Resumiendo todo lo anterior, se debe especificar todo lo que un desarrollador necesita conocer para poder reconstruir el entorno en el cual se ha producido el problema. Description: Una descripción completa y precisa del problema que se está sufriendo. Intente evitar especular sobre las posibles causas del problema a menos que se tenga la seguridad de que el camino descrito es el correcto, puesto que puede inducir al desarrollador a realizar falsas presunciones. How-To-Repeat: Un resumen de las acciones que deben llevarse a cabo para reproducir el problema. Fix: Preferentemente un parche, o al menos una solución temporal (la cual no sólo ayuda a otras personas que experimenten el mismo problema, sino que puede ayudar también al desarrollador para que investigue sobre las verdaderas causas del problema). No obstante, si no se dispone de ninguna de estas opciones, lo mas sabio es dejar vacío este campo y sobre todo no hacer especulaciones.
Envío del informe de problemas Una vez que hemos terminado de rellenar la plantilla, hemos salvado y hemos salido del editor, &man.send-pr.1; nos dará a conocer las siguientes opciones: s)end, e)dit or a)bort?. Es en estos momentos cuando podemos teclear s para continuar y enviar el informe de problemas, e para relanzar el editor y realizar más modificaciones a la plantilla o a para abortar el programa. Si se selecciona esta última alternativa, el informe de problemas no será destruido, sino que permanecerá en disco (&man.send-pr.1; nos indicará el nombre del fichero antes de finalizar), de tal forma que se puede editar de forma individual (sin &man.send-pr.1;) en cualquier momento, o también se puede transferir a otro sistema con mejor conectividad para finalmente enviarlo utilizando la opción de línea de comandos de &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report Esto leerá el archivo especificado, validando sus contenidos, y eliminará los comentarios para finalmente enviarlo.
Follow-up Una vez enviado el informe de problemas, se recibe una confirmación por correo electrónico en la que se incluye el número asignado al informe y la URL que puede utilizarse para consultar su estado. Con un poquito de suerte, alguien mostrará interés en el problema y tratará de solucionarlo, o de explicar por qué razón no se considera un problema, como ha ocurrido en muchas ocasiones. Recibiremos automáticamente una notificación relativa a cualquier cambio de estado, además de recibir copias de cualquier comentario o de los parches que se generen relacionados con nuestro informe. Si alguien solicita información adicional sobre el problema, o de repente descubre o recuerda algo que no tuvo ocasión de mencionar en el informe inicial, puede utilizar una de las siguientes opciones para enviar una continuación (followup) a dicho informe: La forma más sencilla consiste en utilizar el enlace followup que aparece en la página web asociada a nuestro informe de problemas, la cual se puede alcanzar a partir de la página de búsquedas de PRs en . Al pinchar en dicho enlace se mostrará una pantalla con las líneas de To: y Subject correctamente rellenadas (siempre y cuando el navegador soporte esta característica de autorelleno). Alternativamente, se puede enviar un correo eletrónico directamente a bug-followup@FreeBSD.org, asegurando que el número de seguimiento se incluye en el asunto para que el sistema de seguimiento de informes pueda adjuntar la respuesta al informe apropiado. Si no se incluye el número de seguimiento, GNATS no reconocerá el informe inicial y creará un PR totalmente nuevo, que quedará asignado al administrador de GNATS, de tal forma que el followup quedará en el vacío hasta que alguien resuelva el entuerto, lo cual puede tardar dias o semanas. Forma incorrecta:Subject: ese PR que envié en su día Forma correcta:Subject: Re: ports/12345: problema de compilación en foo/bar Si el informe de problemas permanece abierto una vez que dicho problema ha desaparecido, simplemente envíe un followup (de la forma descrita anteriormente) diciendo que el informe de problemas se puede cerrar y, a ser posible, también conviene explicar la forma en que el problema se resolvió.
Lecturas recomendadas A continuación se muestra una lista de recursos relacionados con la escritura adecuada de informes y con el procesamiento de dichos informes. No pretende ser una completa enumeración. How row to Report Bugs Effectively—un excelente ensayo por Simon G. Tatham sobre la redacción de informes de problemas (el texto no es específico sobre &os;) Problem Report Handling Guidelines—resumen de valor sobre cómo los desarrolladores de &os; manejan y gestionan los informes de problemas.
+ +
diff --git a/es_ES.ISO8859-1/books/handbook/Makefile b/es_ES.ISO8859-1/books/handbook/Makefile index 96f6a5e7fa..4dc9e523a2 100755 --- a/es_ES.ISO8859-1/books/handbook/Makefile +++ b/es_ES.ISO8859-1/books/handbook/Makefile @@ -1,217 +1,215 @@ # # $FreeBSD$ # $FreeBSDes: doc/es_ES.ISO8859-1/books/handbook/Makefile,v 1.6 2004/10/08 22:36:28 jesusr Exp $ # # Build the FreeBSD Handbook. # # The FreeBSD Spanish Documentation Project # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile # %SRCID% 0.0 # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ MAINTAINER= jesusr@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/desktop.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= install/xf86setup.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} DOC_PREFIX?= ${.CURDIR}/../../.. # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/es_ES.ISO8859-1/books/handbook/chapters.ent b/es_ES.ISO8859-1/books/handbook/chapters.ent index 8e4d01c7e3..d1737cd47c 100755 --- a/es_ES.ISO8859-1/books/handbook/chapters.ent +++ b/es_ES.ISO8859-1/books/handbook/chapters.ent @@ -1,79 +1,79 @@ %pgpkeys; - + "> diff --git a/fr_FR.ISO8859-1/articles/contributing-ports/article.xml b/fr_FR.ISO8859-1/articles/contributing-ports/article.xml index 8af66ba7b2..e0dac49909 100644 --- a/fr_FR.ISO8859-1/articles/contributing-ports/article.xml +++ b/fr_FR.ISO8859-1/articles/contributing-ports/article.xml @@ -1,1047 +1,1049 @@
Contribuer au Catalogue des logiciels portés de &os; $FreeBSD$ $FreeBSD$ Résumé Cet article décrit les différentes possibilités que chacun a de contribuer au catalogue des logiciels portés de &os;. &trans.a.culot; Sam Lawrance Mark Linimon &tm-attrib.freebsd; &tm-attrib.general; Contribuer Introduction Le catalogue des logiciels portés (appelé Ports en anglais) est le fruit d'un travail en perpétuelle évolution. Nous voulons fournir à nos utilisateurs une collection de logiciels tiers qui soit facile à utiliser, à jour, et de grande qualité. Pour nous aider à atteindre ce but, nous avons besoin que des personnes donnent de leur temps libre et participent à cet effort. Tout le monde peut participer et il existe de nombreuses possibilités pour ce faire. Contribuer aux logiciels portés est un excellent moyen de donner quelque chose en retour au projet. Que vous cherchiez à vous impliquer de manière continue ou bien juste un défi amusant pour chasser l'ennui un jour de pluie, nous aimerions beaucoup avoir votre aide! En tant que volontaire, ce que vous faites est limité uniquement par les barrières que vous vous imposez vous-même. Cependant, nous vous demandons d'être conscient de ce que les autres membres de la communauté &os; attendent de vous. Il serait souhaitable que vous le preniez en compte avant de vous décider à vous porter volontaire. Ce que vous pouvez faire pour aider Vous pouvez contribuer facilement à la mise à jour du catalogue des logiciels portés et à son maintien en bon état en utilisant une des possibilités suivantes: Trouvez un logiciel sympa ou utile et créez un logiciel porté de celui-ci. Il existe un grand nombre de logiciels portés qui n'ont pas de mainteneur. Devenez un mainteneur et adoptez un logiciel porté. Si vous avez créé ou adopté un logiciel porté, soyez conscient de vos devoirs en tant que mainteneur. Si vous êtes à la recherche d'un petit défi vous pouvez corriger un bogue ou un logiciel porté déficient. Créer un logiciel porté Un autre document est à votre disposition pour vous guider dans la création (et la mise à jour) d'un logiciel porté: le Guide du Porteur de logiciels. Ce guide est la meilleure référence pour travailler avec le système des logiciels portés. Il fournit des détails sur la manière dont fonctionne ce système et expose les pratiques recommandées. Adopter un logiciel porté non maintenu Choisir un logiciel porté non maintenu Prendre la relève en maintenant des logiciels portés abandonnés est un excellent moyen de s'impliquer. Les logiciels portés non maintenus sont mis à jour et réparés uniquement lorsque quelqu'un se porte volontaire pour travailler dessus. Il existe un grand nombre de logiciels portés non maintenus. C'est une bonne idée de commencer par adopter un logiciel porté que vous utilisez régulièrement. Les logiciels portés non maintenus ont leur MAINTAINER assigné à ports@FreeBSD.org. Une liste des logiciels portés non maintenus ainsi que de leurs bogues actuels et leurs rapports de problèmes peuvent être consultés dans le Système de suivi des logiciels portés &os;. Certains logiciels portés en affectent un grand nombre d'autres du fait des dépendances et des relations logiciels portés-esclaves. Généralement, nous voulons que les personnes aient de l'expérience avant qu'ils maintiennent de tels logiciels portés. Vous pouvez savoir si un logiciel portés a ou non des dépendances ou des logiciels portés esclaves en regardant un index maître du catalogue des logiciels portés appelé INDEX (Le nom de ce fichier varie en fonction des distributions de &os;; par exemple, INDEX-6). Certains logiciels portés ont des dépendances conditionnelles qui n'apparaissent pas dans la version par défaut de INDEX. Nous attendons de vous que vous soyez capable de reconnaître de tels logiciels portés en examinant les Makefiles d'autres logiciels portés. Comment adopter un logiciel porté Premièrement faites en sorte de comprendre vos responsabilités en tant que mainteneur. Lisez également le Guide du Porteur de logiciels. S'il-vous-plaît ne vous impliquez pas au delà de ce que vous pensez pouvoir raisonnablement assumer. Vous pouvez demander à devenir mainteneur de n'importe quel logiciel porté non maintenu dès que vous le souhaitez. Assignez simplement votre propre adresse de courriel à MAINTAINER et envoyez un PR (Rapport de Problème) avec cette modification. Si le logiciel porté montre des erreurs lors de sa compilation ou qu'il nécessite une mise à jour, vous devriez inclure tout autre changement dans le même PR. Ceci sera utile car beaucoup de committers sont moins enclins à assigner la maintenance à quelqu'un qui n'a pas d'antécédents connus avec &os;. Soumettre des PRs qui corrigent des erreurs de compilation ou mettent à jour des logiciels portés est le meilleur moyen de faire ses preuves. Remplissez votre PR en indiquant la catégorie ports et la classe change-request. Un committer examinera votre PR, enregistrera vos modifications, et finalement fermera le PR. Parfois ce processus peut prendre du temps (les committers sont des volontaires eux aussi :). Le défi pour les mainteneurs d'un logiciel porté Cette section vous donnera une idée de pourquoi les logiciels portés nécessitent qu'on les maintienne et met en évidence les responsabilités qui incombent au mainteneur d'un logiciel porté. Pourquoi les logiciels portés nécessitent une maintenance Créer un logiciel portés est une tâche ponctuelle dans le temps. S'assurer qu'un logiciel porté est à jour, compile, et s'exécute toujours correctement nécessite un effort de maintenance continu. Les mainteneurs sont des personnes qui consacrent une partie de leur temps à atteindre ce but. La raison principale pour laquelle les logiciels portés nécessitent une maintenance est d'apporter à la communauté &os; les tous derniers et meilleurs logiciels tiers disponibles. Un défi supplémentaire est de s'assurer que les logiciels portés continuent à fonctionner au sein de la structure du dépôt des logiciels portés lorsque celle-ci évolue. En tant que mainteneur, vous devrez relever les défis suivants: Nouvelles versions et mises à jour logicielles. De nouvelles versions et mises à jour de logiciels portés apparaissent fréquemment, et il est nécessaire de les incorporer au dépôt des logiciels portés afin de proposer des logiciels qui soient à jour. Changements dans les dépendances. Si des modifications significatives sont appliquées à des dépendances de votre logiciel porté, il pourrait être nécessaire de le mettre à jour pour qu'il continue à fonctionner correctement. Changements affectant des logiciels portés dépendants. Si d'autres logiciels portés dépendent d'un logiciel porté dont vous avez la maintenance, appliquer des changements à votre logiciel porté pourrait nécessiter une coordination avec d'autres mainteneurs. Interactions avec d'autres utilisateurs, mainteneurs et développeurs. Une des tâches du mainteneur est d'assurer un rôle de support. Vous n'êtes pas censé fournir un support d'ordre général (mais nous serions ravis si vous décidiez de le faire). Ce que vous devriez fournir, c'est un point de coordination pour les problèmes spécifiques à &os; liés à vos logiciels portés. Chasser les bogues. Un logiciel porté peut souffrir de bogues qui sont spécifiques à &os;. Il vous faudra enquêter, trouver, et corriger ces bogues lorsqu'ils seront rapportés. Tester minutieusement un logiciel porté pour identifier les problèmes avant qu'ils ne qu'ils atteignent le dépôt des logiciels portés est encore mieux. Changements dans l'infrastructure des logiciels portés et politique. Occasionnellement les systèmes qui sont utilisés pour construire les logiciels portés et les paquets binaires sont mis à jour ou bien de nouvelles recommendations affectant cette infrastructure sont établies. Vous devriez prendre connaissance de ces changements au cas où vos logiciels portés seraient affectés et nécessiteraient une mise à jour. Changements dans le système de base. &os; est en constant développement. Les changements de logiciels, bibliothèques, du noyau, ou même des changements de politique peuvent induire des demandes de modifications sur les logiciels portés, et ce de manière continue. Les responsabilités du mainteneur Maintenir ses logiciels portés à jour Cette section expose la manière de procéder pour maintenir vos logiciels portés à jour. Ceci est une vue d'ensemble. Des informations complémentaires sur la façon de mettre à jour un logiciel porté sont disponibles dans le Guide du Porteur d'applications. Surveillez les mises à jour Surveillez les sorties de nouvelles versions, mises à jour et correctifs de sécurité effectuées par l'éditeur du logiciel. Les listes diffusant les annonces ou les pages Web sont utiles pour cela. Parfois les utilisateurs vous contacteront et vous demanderont quand votre logiciel porté sera mis à jour. Si vous êtes occupé par d'autres tâches ou que vous n'êtes pas en mesure pour une raison ou une autre de le mettre à jour à ce moment, demandez-leur si ils peuvent vous aider en soumettant une mise à jour. Il se peut que vous receviez également un courrier électronique de la part du Vérificateur de version des logiciels portés de &os; vous informant qu'une version plus récente du fichier distribution pour votre logiciel porté est disponible. De plus amples informations à propos de ce système (incluant les instructions pour ne plus recevoir de notification) seront fournies dans les messages. Intégrer les changements Lorsqu'ils sont disponibles, intégrez les changements à votre logiciel porté. Vous devez être en mesure de pouvoir générer un patch entre le logiciel porté original et celui mis à jour. Vérification et test Vérifiez minutieusement et testez vos changements: Compilez, installez et testez votre logiciel porté sur autant de plates-formes et d'architectures que vous pouvez. Il est courant pour un logiciel porté de fonctionner sur une branche ou une plate-forme et d'échouer sur une autre. Faites en sorte qu'il ne manque aucune dépendance à votre logiciel porté. Il est recommandé pour cela d'installer votre propre tinderbox. Consultez les ressources pour plus d'informations. Vérifiez que la liste des fichiers du paquetage est à jour. Cela implique de rajouter tout nouveau fichier ou répertoire et de supprimer toutes les entrées non utilisées. Vérifiez votre logiciel porté en utilisant &man.portlint.1; comme guide. Consultez les ressources pour obtenir des informations importantes sur la manière d'utiliser portlint. Prenez en considération le fait que des changements sur votre logiciel porté pourraient casser d'autres logiciels portés. Si tel est le cas, coordonnez les modifications avec les mainteneurs de ces autres logiciel portés. Ceci est d'autant plus important que votre mise à jour modifie une version de bibliothèque partagée, dans ce cas les logiciels portés dépendants auront au moins besoin d'une incrémentation de PORTREVISION pour qu'ils soient automatiquement mis à jour par des outils d'automatisation comme &man.portupgrade.1;. Soumettre les changements Envoyez votre mise à jour en soumettant un PR contenant les raisons de vos changements ainsi que le correctif contenant les différences entre le logiciel porté original et celui mis à jour. Référez-vous à Ecrire des rapports de problème &os; pour obtenir des informations concernant la manière d'écrire un bon PR. S'il-vous-plaît, ne soumettez pas une archive &man.shar.1; du logiciel porté entier mais utilisez à la place &man.diff.1; -ruN. De cette manière, les committers pourront bien plus facilement voir exactement les changements qui ont été faits. La section du Guide du Porteur d'applications sur la Mise à jour contient de plus amples informations à ce sujet. Soyez patient À un moment donné un committer s'occupera de votre PR. Cela peut prendre quelque minutes, ou quelques semaines — donc s'il-vous-plaît, soyez patient. Faites-nous un retour Si un committer détecte un problème avec vos changements, il vous le mentionnera très probablement. Une réponse rapide de votre part aidera à ce que votre PR soit pris en compte plus rapidement, et cela est mieux pour maintenir le fil de la discussion lorsque l'on essaie de résoudre un problème. Et Finalement Vos changements seront enregistrés et votre logiciel porté aura été mis à jour. Le PR sera alors fermé par le committer. Et voilà! Assurez-vous que vos logiciels portés continuent à compiler correctement Cette section concerne la découverte et la correction de problèmes qui empêchent vos logiciels portés de compiler correctement. &os; garantit seulement que le catalogue des logiciels portés fonctionne sur la branche -STABLE. Vous devriez utiliser 5-STABLE ou 6-STABLE, préférablement cette dernière. Théoriquement vous devriez être capable de vous en sortir en faisant tourner la dernière version de chacune des branches stables (car les ABI ne sont pas supposées changer) mais si vous pouvez utiliser la branche c'est encore mieux. Etant donné que la majorité des installations de &os; tourne sur des machines compatibles PC (ce que l'on appelle l'architecture i386), nous attendons de vous que vous assuriez le bon fonctionnement du logiciel porté sur cette architecture. Cependant, comme de plus en plus de personnes commencent à utiliser l'architecture amd64 en natif, il va devenir de plus en plus important de s'assurer que les logiciels portés fonctionnent sur celle-ci aussi. Il est parfaitement acceptable de demander de l'aide si vous n'êtes pas en possession d'une telle machine. Les causes de dysfonctionnement les plus courants sur les architectures non-i386 proviennent du fait que les programmeurs sont partis du principe que, par exemple, les pointeurs sont des ints, ou que le compilateur relativement laxiste gcc 2.95 a été utilisé. De plus en plus, les auteurs d'applications retravaillent leur code pour supprimer ce genre d'hypothèses — mais si l'auteur ne maintient pas activement son code, il se pourrait que vous ayez à le faire vous-même. Voici les tâches dont vous devez vous acquitter pour vous assurer que votre logiciel porté peut être compilé: Surveillez les erreurs de compilation Vérifiez régulièrement les fermes de compilation automatique des logiciels portés, pointyhat, ainsi que le scanneur des fichiers distribution pour voir si un des logiciels portés que vous maintenez ne parvient pas à compiler ou ne peut télécharger l'archive dont il a besoin (voir ressources pour plus d'informations concernant ces systèmes). Des rapports d'erreurs peuvent également vous parvenir par courrier électronique en provenance d'autres utilisateurs ou systèmes automatisés. Collectez les informations Lorsque vous avez détecté un problème, collectez les informations vous permettant de le corriger. Les erreurs de compilation rapportées par pointyhat s'accompagnent de fichiers d'historique qui vous montreront l'endroit où l'erreur de compilation est survenue. Si le problème vous a été rapporté par un utilisateur, demandez-lui de vous envoyer les informations qui vous aideraient à diagnostiquer le problème, comme: Les fichiers d'historique de compilation Les commandes et options utilisées pour compiler le logiciel porté (incluant le jeu d'options présent dans /etc/make.conf) La liste des paquets installés sur leur système tel qu'indiqué par &man.pkg.info.1; La version de &os; qu'ils utilisent tel qu'indiqué par &man.uname.1; -a De quand date la dernière mise à jour de leur catalogue des logiciels portés De quand date la dernière mise à jour de leur fichier INDEX Enquêtez et trouvez une solution Malheureusement il n'existe pas de processus simple pour cela mais souvenez-vous cependant que si vous êtes bloqué, demandez de l'aide! La &a.ports; est un bon point de départ, et les développeurs en amont sont souvent très serviables. Soumettre les changements De la même manière que pour mettre à jour un logiciel porté, vous devriez inclure les changements, vérifier et tester, soumettre vos modifications dans un PR, et expliciter vos actions si besoin. Envoyez vos modifications aux auteurs Dans certains cas, il vous sera nécessaire de produire un correctif au logiciel porté pour qu'il fonctionne sur &os;. Certains auteurs (mais pas tous) accepteront d'inclure de tels correctifs dans leur code pour la prochaine version. Dans ce cas, cela pourrait même être utile aux utilisateurs d'autres systèmes basés sur BSD et peut-être éviter des efforts redondants. Par courtoisie, prenez s'il-vous-plaît en considération l'envoi de vos correctifs aux auteurs du logiciel. Analysez les rapports d'erreur et PRs liés à votre logiciel porté Cette section concerne la découverte et la correction des bogues. Les bogues spécifiques à &os; proviennent généralement d'hypothèses faites sur les environnements de compilation et d'exécution qui ne s'appliquent pas à &os;. Il est moins probable que vous rencontriez un problème de ce type, mais il se peut qu'il soit plus subtile et difficile à diagnostiquer. Voici les tâches que vous devrez effectuer pour vous assurer que votre logiciel porté continue à fonctionner comme attendu: Répondre aux rapports de bogues Les bogues peuvent vous être rapportés par courrier électronique par l'intermédiaire de la base de données des rapports de problème GNATS. Les bogues peuvent également vous être rapportés directement par les utilisateurs. Vous devriez répondre aux PRs et autres rapports dans les 14 jours, mais s'il-vous-plaît faites votre possible pour ne pas prendre autant de temps pour répondre. Essayez de le faire aussi vite que possible, même si c'est juste pour dire que vous avez besoin d'un peu de temps avant de pouvoir travailler sur ce PR. Collectez les informations Si la personne rapportant le bogue n'a pas dans le même temps fourni de correctif, vous devez collecter les informations nécessaires qui vous permettront d'en produire un. Si le bogue est reproductible, vous pouvez collecter la plupart des informations nécessaires vous-même. Dans le cas contraire, demandez à la personne qui vous a rapporté le bogue de collecter les informations pour vous, comme: Une description détaillée de leurs actions, le comportement attendu du programme ainsi que le comportement observé Une copie des données d'entrée qui ont déclenché l'apparition du bogue Les informations concernant leur environnement de compilation et d'exécution — par exemple, la liste des paquetages installés et la sortie de &man.env.1; Images mémoire (Core dumps) Traces de la pile mémoire (Stack traces) Eliminez les rapports incorrects Certains rapports de bogues peuvent être incorrects. Par exemple, l'utilisateur peut tout simplement avoir mal utilisé le programme; ou bien les paquets qu'ils ont installés peuvent être obsolètes et nécessiter une mise à jour. Parfois un rapport de bogue n'est pas spécifique à &os;. Rapportez dans ce cas le bogue aux développeurs en amont. Si vous avez les compétences requises pour résoudre le bogue, vous pouvez également corriger le logiciel porté de sorte que le correctif soit appliqué avant la diffusion par les développeurs de la version suivante du logiciel. Trouvez une solution Tout comme pour les erreurs de compilation, vous devrez trouver une solution au problème. A nouveau, souvenez-vous que vous pouvez demander de l'aide si vous êtes bloqué! Soumettez ou approuvez les changements Comme pour la mise à jour d'un logiciel porté, vous devriez intégrer vos changements, vérifier et tester, et soumettre vos modifications dans un PR (ou envoyer un suivi si un PR existe déjà pour ce problème). Si un autre utilisateur a soumis des changements dans le PR, vous pouvez également envoyer un suivi indiquant si vous approuvez ou non ces changements. Fournir du support Fournir du support fait partie des tâches incombant au mainteneur — pas pour le logiciel lui-même — mais pour son logiciel porté ainsi que tout problème lié à &os;. Les utilisateurs peuvent prendre contact avec vous concernant des questions, suggestions, problèmes ou correctifs. La plupart du temps leur correspondance sera spécifique à &os;. Occasionnellement vous devrez faire appel à vos talents diplomatiques, et aimablement orienter les utilisateurs à la recherche de support général vers les ressources appropriées. Moins fréquemment vous rencontrerez une personne demandant pourquoi les RPMs ne sont pas à jour ou comment il peut faire pour faire fonctionner le logiciel sous Linux Untel. Profitez de l'occasion pour lui dire que votre logiciel porté est à jour (si il l'est, bien évidemment!), et suggérez-lui d'essayer &os;. Parfois les utilisateurs et développeurs considéreront que vous êtes une personne occupée dont le temps est précieux et ils prendront en charge une partie de votre travail. Ils pourraient par exemple: soumettre un PR ou envoyer un correctif pour mettre à jour votre logiciel porté, enquêter et peut-être proposer un correctif à un PR, ou bien proposer une modification à appliquer à votre logiciel porté. Pour ce genre de situations votre principale obligation est de répondre rapidement. Le délai maximum qu'a un mainteneur pour répondre est de 14 jours. Après cette période les changements peuvent être appliqués même sans accord. Les utilisateurs ont pris la peine de faire le travail pour vous donc s'il-vous-plaît essayez de leur répondre rapidement. Puis vérifiez, approuvez, modifiez ou discutez leurs changements avec eux dès que possible. Si vous parvenez à leur faire sentir que leur contribution est appréciée (cela devrait être le cas) vous serez plus en mesure de les persuader de faire plus de choses pour vous à l'avenir :-). Trouver et corriger un logiciel porté défectueux Il existe deux endroits vraiment appropriés pour trouver un logiciel porté qui requière de l'attention. Vous pouvez utiliser l'interface Web vers la base de données des rapports de problèmes pour rechercher et consulter les PRs non résolus. La majorité des PRs relatifs aux logiciels portés sont des mises à jour, mais en recherchant un peu et en parcourant les résumés vous devriez être capable de trouver quelque chose d'intéressant sur lequel travailler (la catégorie sw-bug est un endroit approprié pour commencer). L'autre endroit approprié est le Système de suivi des logiciels portés &os;. Recherchez en particulier les logiciels portés non maintenus qui présentent des erreurs de compilation et les logiciels portés qui sont marqués BROKEN (cassé). Il est aussi acceptable d'envoyer des changements pour un logiciel porté qui est maintenu, mais rappelez-vous de prévenir le mainteneur au cas où il serait déjà en train de travailler sur le problème. Dès lors que vous avez trouvé un bogue ou problème, collectez les informations, enquêter et corrigez! Si il existe déjà un PR, envoyez un suivi. Sinon créez un nouveau PR. Vos changements seront vérifiés et, si tout paraît correct, enregistrés. Savoir quand mettre un terme à sa participation Vos intérêts et vos engagements évoluant, il se peut que vous vous rendiez compte que vous n'avez plus le temps de continuer à contribuer à vos logiciels portés. Aucun soucis ! Faites-le nous savoir si vous n'utilisez plus un logiciel porté ou que vous n'avez plus le temps ou perdu l'intérêt d'être mainteneur. De la sorte nous pouvons prendre les mesures nécessaires et permettre à d'autres personnes d'essayer de travailler sur des problèmes concernant le logiciel porté sans attendre votre réponse. N'oubliez-pas, &os; est un projet de volontaires, donc si maintenir un logiciel porté n'est plus amusant alors c'est probablement le bon moment pour laisser à quelqu'un d'autre le soin de s'en occuper! En tous les cas, l'Equipe de Gestion des Logiciels Portés (portmgr) se réserve le droit d'annuler votre droit de mainteneur si vous n'avez pas activement maintenu votre logiciel porté pendant un certain temps (actuellement, cette période est de 3 mois). Par là nous voulons dire qu'il y a eu des problèmes non résolus ou des mises à jour en attente qui n'ont pas été traitées pendant cette période. Ressources pour les mainteneurs de logiciels portés et les participants Le Guide du Porteur est votre guide du routard pour le système des logiciels portés. Gardez-le à porté de main! Ecrire des rapports de problème pour &os; décrit quelle est la meilleure manière de rédiger et soumettre un PR. En 2005 plus de onze mille PRs pour les logiciels portés ont été soumis! Respecter les consignes de cet article nous aidera grandement à réduire le temps temps nécessaire pour traiter vos PRs. La Base de données des rapports de problèmes. Pointyhat (chapeau pointu) est la ferme de compilation des logiciels portés. Vous pouvez utiliser Pointyhat pour vérifier les historiques de compilation des logiciels portés pour toutes les architectures et versions majeures. Le Système de Surveillance des logiciels portés &os; peut vous montrer des informations croisées concernant les logiciels portés comme les erreurs de compilation et les rapports de problème. Si vous êtes un mainteneur vous pouvez l'utiliser pour vérifier le status de vos logiciels portés. En tant que participant vous pouvez l'utiliser pour trouver des logiciels portés défectueux ou non maintenus qui ont besoin d'un correctif. Le scanneur des fichiers distribution des logiciels portés &os; peut vous montrer les portages pour lesquels le fichier distribution n'est pas téléchargeable. Vous pouvez vérifier vos propres logiciels portés ou bien trouver des logiciels portés pour lesquels leur MASTER_SITES a besoin d'une mise à jour. Utiliser tinderbox est le moyen le plus rigoureux pour tester un logiciel porté sur tout le cycle d'installation, empaquetage, et désinstallation. Il présente une interface en ligne de commande mais peut aussi être contrôlé par l'intermédiaire d'une interface Web. Référez-vous à ports/ports-mgmt/tinderbox. Plus de documentation peut être trouvée à la page principale de tinderbox de marcuscom. &man.portlint.1; est une application qui peut être utilisée pour vérifier que votre logiciel porté est en conformité avec une multitude de recommendations stylistiques et fonctionnelles. portlint est une application simple basée sur des heuristiques, donc vous devriez l'utiliser seulement à titre indicatif. Si portlint vous suggère des modifications qui ne vous semblent pas appropriées, consultez le Guide du Porteur ou demandez conseil. La &a.ports; convient pour les discussions générales sur les logiciels portés. C'est un bon endroit pour demander de l'aide. Vous pouvez souscrire, ou lire et rechercher dans les archives de la liste. Lire les archives de la &a.ports-bugs; et de la &a.cvs-ports; peut aussi présenter de l'intérêt. + +
diff --git a/fr_FR.ISO8859-1/articles/contributing/article.xml b/fr_FR.ISO8859-1/articles/contributing/article.xml index b560aa2b68..1436a31a60 100644 --- a/fr_FR.ISO8859-1/articles/contributing/article.xml +++ b/fr_FR.ISO8859-1/articles/contributing/article.xml @@ -1,631 +1,633 @@
Collaborer à FreeBSD $FreeBSD$ $FreeBSD$ Cet article décrit les différentes manières pour une personne individuelle ou une organisation de collaborer au projet FreeBSD. &trans.a.fonvieille; Première version de &a.fr.dntt; Jordan Hubbard Contribution de &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ collaborer Alors, comme ça vous voulez collaborer à FreeBSD? C'est génial! FreeBSD s'appuie sur les contributions de sa base d'utilisateurs pour survivre. Vos contributions ne sont pas seulement appréciées, elles sont vitales pour la constante progression de FreeBSD. Contrairement à ce que certains pourraient vous faire croire, vous n'avez pas besoin d'être un expert programmeur ou un ami proche de l'équipe principale de FreeBSD pour avoir vos contributions acceptées. Un grand nombre, toujours en augmentation, de collaborateurs à travers le monde, dont les âges et l'expertise technique sont très variables, développent FreeBSD. Il y a toujours plus de travail à faire que de personnes disponibles pour s'en occuper, et davantage d'aide est toujours appréciée. Le projet FreeBSD est responsable de tout l'environnement du système d'exploitation, et pas seulement d'un noyau ou de quelques utilitaires éparpillés. Ainsi, nos listes TODO (à faire) s'étendent sur une large gamme de tâches: depuis la documentation, les béta-tests et la présentation, jusqu'à l'installateur système et des types de développement du noyau hautement spécialisés. Des personnes de n'importe quel niveau de compétence, dans presque tous les domaines, pourront sûrement aider le projet. Les entités commerciales engagées dans des entreprises relatives à FreeBSD sont également encouragées à nous contacter. Vous avez besoin d'une extension spéciale pour faire fonctionner votre produit? Vous nous trouverez réceptif à vos requêtes, du moment quelles ne sont pas trop exotiques. Vous travaillez sur un produit à valeur ajoutée? Faites-le nous savoir! Nous serons peut être en mesure de coopérer sur certains aspects. Le monde du logiciel libre va à l'encontre de nombreuses idées reçues sur la manière dont les logiciels sont développés, vendus, et maintenus, et nous vous invitons à lui donner au moins un second regard. Les besoins La liste suivante de tâches et de sous-projets représente une sorte d'amalgame des différentes listes TODO et des demandes d'utilisateurs. Tâches de non-programmeur De nombreuses personnes impliquées dans FreeBSD ne sont pas des programmeurs. Le projet comprend des rédacteurs de documentation, des concepteurs de site web, et des personnes assurant le support. La contribution de ces personnes se matérialise sous la forme d'un investissement en temps et une volonté d'apprendre. Lisez la FAQ et le Manuel régulièrement. Si quelque chose est mal expliquée, pas à jour ou tout simplement complètement faux, signalez-le nous. Mieux, envoyez nous un correctif (le SGML n'est pas difficile à apprendre, mais il n'y aucune objection à des soumissions en format ASCII). Aidez à traduire la documentation FreeBSD dans votre langue. Si la documentation existe déjà dans votre langue, vous pouvez aider à traduire des documents supplémentaires ou contrôler que les traductions sont à jour. Consultez tout d'abord la FAQ sur les traductions dans l'Introduction au Projet de Documentation de FreeBSD. Notez que vous ne vous engagez pas à traduire chacun des documents FreeBSD ce faisant — en tant que volontaire, vous pouvez faire autant que vous le désirez. Une fois que quelqu'un commence à traduire, presque toujours d'autres personnes rejoindront l'effort. Si vous n'avez le temps et l'énergie pour ne traduire qu'une partie de la documentation, traduisez les instructions d'installation. Lisez la &a.questions; et le &ng.misc; de temps en temps (ou même régulièrement). Il peut être très gratifiant de partager son expérience et d'aider les gens à résoudre leurs problèmes; parfois vous pourrez même apprendre quelque chose de nouveau! Ces forums peuvent être également une source d'idées sur ce qu'il faut améliorer. Tâches de programmeur La plupart des tâches listées ici nécessitent soit un investissement considérable en temps, soit une connaissance en profondeur du noyau, ou les deux. Cependant, il y a également de nombreuses tâches utiles pour les “programmeurs occasionnels”. Si vous utilisez FreeBSD-CURRENT et que vous avez une bonne connexion Internet, il existe une machine current.FreeBSD.org qui compile une version complète une fois par jour—à chaque fois, essayez d'installer la dernière version et rapportez toutes les erreurs durant le processus. Lisez la &a.bugs;. Il peut y avoir un problème que vous pouvez commenter de manière constructive ou avec des correctifs que vous pouvez tester. Ou vous pourrez même tenter de corriger un de ces problèmes vous-même. Si vous connaissez un correctif qui a été appliqué avec succès sur la branche -CURRENT mais qui n'a pas été intégré dans la branche -STABLE après un intervalle de temps raisonnable (normalement quelques semaines), envoyez au responsable un rappel poli. Déplacer des contributions logiciels vers src/contrib dans l'arborescence des sources. Assurez vous que le code dans src/contrib est à jour. Compiler l'arbre des sources (ou une partie) avec tous les messages d'avertissements activés et corriger les avertissements. Corriger les avertissements pour les logiciels portés qui font des choses obsolètes comme utiliser gets() ou inclure malloc.h. Si vous avez collaboré à un des logiciels portés, envoyez vos correctifs à leur auteur original (cela vous rendra la vie plus facile lors de la sortie de la prochaine version). Récupérer des copies de normes précises comme &posix;. Vous pouvez trouver des liens sur ces normes sur le site du Projet FreeBSD de conformité aux normes C99 et POSIX. Comparer le comportement de FreeBSD avec celui requis par la norme. Si le comportement diffère, en particulier pour des éléments subtiles et obscures de la spécification, envoyez un rapport de bogue à ce sujet. Si vous en êtes capable, déterminez comment le corriger et joignez un correctif à votre rapport de bogue. Si vous pensez que la norme est erronée, demandez à l'organisme de normalisation de considérer la question. Suggérer d'autres tâches pour cette liste! Travailler avec la base de données des rapports de bogue (PR) base de données des rapports de bogue La liste des PRs de FreeBSD donne tous les rapports de problème actuellement actifs et les demandes d'amélioration qui ont été soumis par les utilisateurs de FreeBSD. La base de données des PRs comprend des tâches de programmeurs et de non-programmeurs. Consultez les PRs ouverts, et voyez s'il y a quelque chose qui peut vous intéresser. Certaines de ces tâches peuvent être des tâches très simples qui ne nécessitent qu'une paire d'yeux supplémentaire pour vérifier et confirmer que le correctif dans le PR est correct. D'autres peuvent être bien plus complexes, ou pourront même ne pas inclure de correctif du tout. Commencez avec des PRs qui n'ont pas été assignés à quelqu'un d'autre. Si le PR est assigné à quelqu'un d'autre, mais qu'il semble que c'est quelque chose dont vous pouvez vous charger, envoyez un courrier électronique à la personne en question et demandez si vous pouvez travailler dessus—elle pourra déjà avoir un correctif prêt à être testé, ou des idées supplémentaires sur lesquelles vous pourrez discuter. Comment participer Les contributions au système tombent généralement dans une ou plusieurs des 5 catégories suivantes: Rapport de bogue et commentaires généraux Une idée ou une suggestion d'intérêt technique général devrait être envoyée à la &a.hackers;. De même, les personnes intéressées par de telles choses (et qu'un grand volume de courrier électronique ne dérange pas) devraient s'abonner à la &a.hackers; en envoyant un courrier électronique à &a.majordomo;. Voir le Manuel FreeBSD pour plus d'information à ce propos et sur les autres listes de diffusion. Si vous trouvez un bogue ou que vous soumettez une modification spécifique, rapportez-le en utilisant le programme &man.send-pr.1; ou son équivalent web. Essayez de remplir chaque champ du rapport de bogue. A moins qu'ils ne dépassent 65KO, inclure tous les correctifs directement dans le rapport. Si le correctif peut être appliqué directement sur l'arbre des sources ajoutez [PATCH] dans le synopsis du rapport. Quand vous ajoutez des correctifs, ne pas utiliser le copier-coller car ce dernier transforme les tabulations en espaces et rend les correctifs inutilisables. Pensez à compresser les correctifs et à utiliser &man.uuencode.1; s'ils dépassent 20KO. Après avoir rempli un rapport, vous devriez recevoir une confirmation accompagnée d'un numéro de suivi. Conservez ce numéro de suivi afin que vous puissiez nous soumettre plus de détails au sujet du problème en envoyant un courrier électronique à FreeBSD-gnats-submit@FreeBSD.ORG. Utilisez le numéro comme sujet du message, e.g. "Re: kern/3377". Toute information supplémentaire sur un rapport de bogue devrait être soumise de cette manière. Si vous ne recevez aucune confirmation dans un temps raisonnable (de 3 jours à une semaine, en fonction de votre connexion pour le courrier électronique) ou qu'il vous est, pour quelque raison que ce soit, impossible d'utiliser la commande &man.send-pr.1;, vous pouvez demander à quelqu'un de le faire pour vous en envoyant un courrier électronique à la &a.bugs;. Voir aussi cet article sur comment écrire de bon rapports de bogue. Modifications de la documentation soumissions concernant la documentation Les modifications de la documentation sont supervisées par la &a.doc;. Veuillez consulter l'Introduction au Projet de Documentation de FreeBSD pour des instructions complètes. Envoyez les soumissions et les modifications (même les plus petites sont les bienvenues!) en utilisant la commande send-pr comme décrit dans Rapport de bogue et commentaires généraux. Modifications dans le code source existant FreeBSD-CURRENT Un ajout ou une modification du code source existant est une toute autre affaire et dépend beaucoup de comment est à jour votre version par rapport à l'état courant du développement de FreeBSD. Il y a une version spéciale de FreeBSD, connue sous le nom de “FreeBSD-CURRENT” qui est disponible de diverses manières pour le confort des développeurs qui travaillent activement sur le système. Voir le Manuel FreeBSD pour plus d'informations sur la manière d'obtenir et d'utiliser FreeBSD-CURRENT. Travailler sur des sources plus anciennes signifie que malheureusement parfois vos modifications pourront être trop obsolètes ou trop divergentes pour permettre une réintégration aisée dans FreeBSD. On peut limiter ce type de changements en souscrivant à la &a.announce; et la &a.current;, où des discussions sur l'état courant du système ont lieu. En supposant que vous pouvez vous arranger pour avoir de manière sure des sources à jour comme base pour vos modifications, l'étape suivante est de produire un ensemble de diffs à envoyer à ceux qui sont chargés de maintenir FreeBSD. Cela est fait à l'aide de la commande &man.diff.1;. Le format &man.diff.1; préféré pour soumettre des correctifs est le format unifié généré par la commande diff -u. Cependant, pour des correctifs qui modifient sensiblement une partie du code, le format de contexte généré par diff -c peut s'avérer plus lisible et donc préférable. diff Par exemple: &prompt.user; diff -c oldfile newfile ou &prompt.user; diff -c -r olddir newdir générera un ensemble de “context diffs” pour un fichier source ou une hiérarchie de répertoires donnés. De même, &prompt.user; diff -u oldfile newfile ou &prompt.user; diff -u -r olddir newdir effectuera la même chose, mais dans le format unifié. Voir la page de manuel de &man.diff.1; pour plus de détails. Une fois que vous avez un ensemble de diffs (que vous pouvez tester avec la commande &man.patch.1;), vous devrez les soumettre pour qu'ils puissent être inclus dans FreeBSD. Utiliser le programme &man.send-pr.1; comme décrit dans Rapport de bogue et commentaires généraux. Ne pas simplement envoyez les diffs à la &a.hackers; ou ils seront perdus! Nous apprécions énormément votre soumission (c'est un projet fait par des volontaires!), mais parce que nous sommes très occupés, nous ne pourrons pas les étudier immédiatement, mais cela restera dans la base de données des PRs jusqu'à ce que nous le fassions. Identifiez votre soumission en ajoutant [PATCH] dans le synopsis du rapport. uuencode Si cela vous semble approprié (e.g. vous avez ajouté, effacé ou renommé des fichiers), archivez vos modifications dans un fichier tar et lancez le programme &man.uuencode.1; dessus. Les archives &man.shar.1; sont aussi les bienvenues. Si votre modification est de nature potentiellement sensible, e.g. si vous n'êtes pas sûr des problèmes de copyright concernant sa distribution ou que vous n'êtes tout simplement pas prêt à le distribuer sans relecture attentive, alors vous devriez l'envoyer directement à la &a.core; plutôt que de le soumettre avec &man.send-pr.1;. La liste de diffusion de l'équipe de base atteint un plus petit groupe de personnes qui réalise la plupart du travail quotidien de FreeBSD. Notez que ce groupe est aussi très occupé et donc que vous ne devriez leur envoyez de courrier électronique que lorsque cela est vraiment nécessaire. Veuillez vous référer à &man.intro.9; et &man.style.9; pour plus d'informations sur la manière de coder. Nous apprécierons le fait que vous soyez au moins conscient de ces problèmes avant de soumettre du code. Nouveau code source ou logiciel à valeur ajoutée importante Dans le cas d'une contribution importante, ou l'addition d'une importante fonctionnalité à FreeBSD, il devient presque nécessaire d'envoyer les modifications soit sous la forme d'archives tar uuencodées soit en les chargeant sur un site web ou FTP. Si vous n'avez pas accès à un site web ou FTP, demandez sur la liste de diffusion appropriée à ce que quelqu'un héberge ces modifications pour vous. Lorsque l'on travaille avec un grand volume de code, le sujet sensible des copyrights revient invariablement. Les copyrights acceptables pour le code inclus dans FreeBSD sont: copyright BSD Le copyright BSD. Ce copyright est le plus apprécié de par son côté “sans attaches” et très attractif pour les entreprises commerciales. Loin de décourager un usage commercial, le projet FreeBSD encourage activement une telle participation avec intérêts commerciaux pour ceux qui pourraient être tentés par la suite d'investir quelque chose dans FreeBSD. GPLLicence Publique Générale GNU Licence Publique Générale GNU La Licence Publique Générale GNU, ou “GPL”. Cette licence n'est pas aussi populaire chez nous à cause du volume d'efforts supplémentaires demandés à celui qui voudrait utiliser le code dans un but commercial, mais étant donné la quantité de code GPL dont nous avons actuellement besoin (compilateur, assembleur, formateur de texte, etc...) il serait absurde de refuser des contributions sous cette licence. Le code sous GPL va également dans une partie différente de l'arborescence, soit /sys/gnu soit/usr/src/gnu, et est de ce fait aisément identifiable par toute personne pour laquelle la licence GPL poserait un problème. Les contributions venant avec un autre type de copyright doivent être soigneusement vérifiées avant que leur intégration à FreeBSD ne soit prise en considération. Les contributions pour lesquelles des restrictions commerciales particulières s'appliquent sont généralement rejetées, bien que les auteurs sont toujours encouragés à rendre disponible de telles modifications par leurs propres moyens. Pour mettre un copyright de “style BSD” sur votre travail, inclure le texte suivant au tout début de chaque fichier de code source que vous voulez protéger, en remplaçant le texte entre les %% par l'information appropriée. Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ Pour votre convenance, une copie de ce texte peut être trouvée dans /usr/share/examples/etc/bsd-style-copyright. Contribution financière, matérielle ou accès Internet Nous sommes toujours très heureux d'accepter des donations pour poursuivre la cause du projet FreeBSD, et dans un effort volontaire comme le notre, un rien peut faire du chemin! Les donations de matériel sont également très importantes pour augmenter notre liste de périphériques supportés puisque nous manquons généralement de fonds pour acheter de tels éléments nous-mêmes. <anchor id="donations"/>Donation de fonds La Fondation FreeBSD est une fondation à but non lucratif et exempte d'impôts fondée pour servir les objectifs du projet FreeBSD. En tant qu'entitée 501(c)3, la Fondation est généralement exempte de l'impôt fédéral des Etats Unis comme de l'impôt de l'état du Colorado. Les dons à une entitée exempte d'impôts sont souvent déductibles de l'impôt fédéral. Les dons sous forme de chèques peuvent être adressés à:
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
La Fondation FreeBSD est désormais en mesure d'accepter les donations par l'intermédiaire du service web PayPal. Pour faire un don, veuillez visiter le site web de la Fondation. Plus d'informations au sujet de la Fondation FreeBSD peuvent être trouvés dans La Fondation FreeBSD -- une introduction. Pour contacter la Fondation par courrier électronique, écrire à bod@FreeBSDFoundation.org. Contribution en matériel dons Le projet FreeBSD accepte avec joie les donations de matériel. Si vous êtes interessés pour nous faire un don de matériel, contactez le Bureau de liaison des donations. Contribution d'accès Internet Nous pouvons toujours utiliser de nouveau sites miroirs pour les site FTP, WWW ou cvsup. Si vous voulez devenir un tel miroir, voyez le document devenir un site mirroir FreeBSD pour plus d'informations. + +
diff --git a/fr_FR.ISO8859-1/articles/contributors/article.xml b/fr_FR.ISO8859-1/articles/contributors/article.xml index 92913e883e..b7b8f1acd2 100644 --- a/fr_FR.ISO8859-1/articles/contributors/article.xml +++ b/fr_FR.ISO8859-1/articles/contributors/article.xml @@ -1,7841 +1,7843 @@
Contributeurs au projet FreeBSD $FreeBSD$ $FreeBSD$ Cet article liste les organisations et les personnes ayant contribué à FreeBSD. Gallerie des dons Le projet FreeBSD Project est redevable à ces donneurs et veut les remercier publiquement ici! Contributeurs au serveur central du projet: Les personnes et sociétés suivantes ont fait qu'il a été possible au projet FreeBSD de mettre en place un nouveau serveur central, qui a remplacé freefall.FreeBSD.org, grace aux dons suivants: &a.mbarkah; et son employeur, Hemisphere Online, ont fournis un Pentium Pro (P6) 200MHz CPU ASA Computers a fourni un carte mere Tyan 1662 . Joe McGuckin joe@via.net de ViaNet Communications a fourni une carte Ethernet Kingston. Jack O'Neill jack@diamond.xtalwind.net a fourni une carte NCR 53C875 SCSI. Ulf Zimmermann ulf@Alameda.net de Alameda Networks a fourni 128MB de mémoire, et un disque de 4 Gb. Dons en numéraires: Les personnes et entreprises suivantes ont directement donnés des fonds au projet: Annelise Anderson ANDRSN@HOOVER.STANFORD.EDU &a.dillon; Blue Mountain Arts Epilogue Technology Corporation &a.sef; Global Technology Associates, Inc Don Scott Wilde Gianmarco Giovannelli gmarco@masternet.it Josef C. Grosch joeg@truenorth.org Robert T. Morris &a.chuckr; Kenneth P. Stox ken@stox.sa.enteract.com de Imaginary Landscape, LLC. Dmitry S. Kohmanyuk dk@dog.farm.org Laser5 du Japon (une partie des bénéfices de leur ventes des CDROMs de FreeBSD). Fuki Shuppan Publishing Co. a donné une partie des bénéfices du livre Hajimete no FreeBSD (FreeBSD, Getting started) à FreeBSD et au projet XFree86. ASCII Corp. a donné une partie des bénéfices de la vente de certains livres en rapport avec FreeBSD. Yokogawa Electric Corp a généreusement donné une somme significative au projet FreeBSD. BuffNET Pacific Solutions Siemens AG via Andre Albsmeier andre.albsmeier@mchp.siemens.de Chris Silva ras@interaccess.com Contributeurs matériels Les personnes et sociétés suivantes ont généreusement contribués en fournissant du matériel pour les tests et le développement des gestionnaires de périphériques: BSDi a fourni les systèmes Pentium P5-90 et 486/DX2-66 EISA/VL qui sont utilisés pour notre développement. Compaq a fourni 3 AlphaStation DS10s au projet FreeBSD. Parmi ces dons, il y a 4 AlphaStations DS10s, un AlphaServer DS20, un AlphaServer 2100s, un AlphaServer 4100, 8 stations personnelles 500Mhz, 4 stations personnelles 433Mhz ! Ces machines sont actuellement utilisés pour la gestion de la chaine de version et les développements de la plateforme FreeBSD/Alpha. TRW Financial Systems, Inc. a fourni 130 PCs, trois serveurs de fichiers de 68 GB, douze Ethernets, deux routeurs et un switch ATM pour débogguer le code ddiskless. Dermot McDonnell a fourni le CDROM Toshiba XM3401B utilisé actuellement sur freefall. Chuck Robey chuckr@glue.umd.edu a fourni son lecteur de bande pour les tests. Larry Altneu larry@ALR.COM, et &a.wilko;, ont fournis les lecteurs de bandes Wangtek et Archive QIC-02 pour améliorer les gestionnaires de périphériques wt. Ernst Winter ewinter@lobo.muc.de a fourni le lecteur de disquette de 2.88 MB. Cela permettra de ré-écrire le gestionnaire de disquette pour le supporter. Tekram Technologies a fourni les cartes DC-390, DC-390U ,DC-390F FAST et ULTRA SCSI pour les tests de non-régression des gestionnaires de périphérique NCR et AMD. Nous les remercions aussi pour la mise à disposition des sources des gestionnaires pour les systèmes d'exploitations libres sur leur serveur FTP ftp://ftp.tekram.com/scsi/FreeBSD/. Larry M. Augustin a fourni en plus de la carte Symbios Sym8751S SCSI, un ensemble de livres dont, un livre sur le support des composants Sym53c895, Ultra-2 et LVD, ainsi qu'un livre sur la programmation des fonctions avancées des composants SCSI Symbios. Christoph Kukulies kuku@FreeBSD.org a fourni un CDROM 12x, FX120 Mitsumi, pour le développement du gestionnaire de périphériques des CDROM IDE. Mike Tancsa mike@sentex.ca a fourni quatre différentes cartes PCI ATM, pour nous aider a améliorer le support de ces cartes et de la pile ATM netatm. Contributeurs spéciaux: BSDi (encore connu sous Walnut Creek CDROM) a fourni plus que ce que nous pourrions dire (voyez l'historique dans le Manuel FreeBSD pour plus de détails). En particulier, nous aimerions les remercier pour le matériel originel utilisé surfreefall.FreeBSD.org, notre machine de développement principal et pour thud.FreeBSD.org, la machine de test et de compilation. Nous voulons aussi les remercier pour l'ensemble de leurs dons et contributions depuis des années et la fourniture de la connection T1 à l'Internet. La société Interface business GmbH, Dresden a patiemment supporté &a.joerg; qui a préfére son travail sur FreeBSD, et utilisé la connexion (tres chère) internet EUnet lorsque sa connexion privé devint trop lente pour travailler avec... Berkeley Software Design, Inc. a fourni le code d'émulation DOS au monde BSD, qui est utilisé dans la commande doscmd. Le bureau dirigeant Le bureau dirigeant de FreeBSD (core team) constitue le Comité dirigeant du projet, responsable des décisions sur le projet, telles que les buts à atteindre tout comme la gestion de certaines portions du projet FreeBSD (par ordre alphabétique et trié par nom de famille): &a.jhb; &a.kuriyama; &a.grog; &a.imp; &a.markm; &a.wes; &a.murray; &a.rwatson; &a.peter; Les développeurs FreeBSD Ce sont des personnes disposant du privilège d'écriture dans l'arboresence des sources. Tous les membres du bureau dirigeant sont aussi développeurs. (par ordre alphabétique et trié par nom de famille): &a.akiyama; &a.jmas; &a.ambrisko; &a.will; &a.anholt; &a.ugen; &a.toshi; &a.babkin; &a.dbaker; &a.jhb; &a.dmlb; &a.mike; &a.mbarkah; &a.rvb; &a.dougb; &a.tobez; &a.stb; &a.pb; &a.abial; &a.jb; &a.nbm; &a.mbr; &a.torstenb; &a.mb; &a.obraun; &a.jmb; &a.wilko; &a.jake; &a.dburr; &a.adrian; &a.perky; &a.dwcjr; &a.charnier; &a.jon; &a.luoqi; &a.ache; &a.ejc; &a.seanc; &a.kjc; &a.cjh; &a.cjc; &a.marcus; &a.nik; &a.archie; &a.chris; &a.alc; &a.cracauer; &a.dec; &a.pds; &a.adam; &a.davidc; &a.ceri; &a.brooks; &a.bsd; &a.jwd; &a.pdeuskar; &a.dillon; &a.mdodd; &a.dd; &a.iedowse; &a.robert; &a.gad; &a.dufault; &a.uhclem; &a.tegge; &a.deischen; &a.eivind; &a.alane; &a.julian; &a.rse; &a.ue; &a.ru; &a.se; &a.bde; &a.jasone; &a.sef; &a.jedgar; &a.green; &a.fenner; &a.lioux; &a.jfieber; &a.fanf; &a.jfitz; &a.blackend; &a.scrappy; &a.lars; &a.petef; &a.dirk; &a.sf; &a.shige; &a.billf; &a.furuta; &a.gallatin; &a.patrick; &a.tg; &a.gibbs; &a.brandon; &a.gioria; &a.daichi; &a.cg; &a.rgrimes; &a.edwin; &a.jmg; &a.znerd; &a.hanai; &a.roger; &a.mharo; &a.dannyboy; &a.thepish; &a.jhay; &a.sheldonh; &a.mikeh; &a.mheinen; &a.helbig; &a.ghelmer; &a.mux; &a.erich; &a.cshumway; &a.chm; &a.nhibma; &a.flathill; &a.orion; &a.pho; &a.horikawa; &a.hosokawa; &a.cognet; &a.jeh; &a.hsu; &a.foxfair; &a.jkh; &a.tom; &a.mph; &a.imura; &a.shin; &a.itojun; &a.iwasaki; &a.mjacob; &a.keith; &a.gj; &a.trevor; &a.kan; &a.phk; &a.tomsoft; &a.cokane; &a.johan; &a.joe; &a.kato; &a.kris; &a.keramida; &a.fjoe; &a.kiri; &a.andreas; &a.ikob; &a.lkoeller; &a.motoyuki; &a.maxim; &a.jkoshy; &a.kuriyama; &a.alex; &a.njl; &a.reg; &a.chern; &a.leeym; &a.sam; &a.stephane; &a.netchild; &a.jlemon; &a.truckman; &a.glewis; &a.pat; &a.ijliao; &a.lile; &a.clive; &a.arved; &a.kevlo; &a.scottl; &a.ade; &a.mwlucas; &a.smace; &a.bmah; &a.jmallett; &a.dwmalone; &a.nobutaka; &a.matusita; &a.mckay; &a.mckusick; &a.eric; &a.ken; &a.dinoex; &a.hm; &a.sanpei; &a.bmilekic; &a.mini; &a.mita; &a.non; &a.jim; &a.marcel; &a.emoore; &a.amorita; &a.dan; &a.tmm; &a.amurai; &a.rich; &a.markm; &a.knu; &a.nakai; &a.max; &a.maho; &a.yoichi; &a.newton; &a.anders; &a.rnordier; &a.davidn; &a.obrien; &a.danny; &a.okazaki; &a.olgeni; &a.ljo; &a.onoe; &a.marko; &a.gpalmer; &a.fsmp; &a.smpatel; &a.cp; &a.wpaul; &a.mp; &a.roam; &a.alfred; &a.wes; &a.gerald; &a.cpiazza; &a.pirzyk; &a.jdp; &a.bp; &a.rpratt; &a.steve; &a.mpp; &a.markp; &a.thomas; &a.darrenr; &a.csgr; &a.greid; &a.mr; &a.arr; &a.trhodes; &a.benno; &a.paul; &a.luigi; &a.tjr; &a.jeff; &a.roberto; &a.chuckr; &a.jesusr; &a.guido; &a.groudier; &a.dima; &a.ps; &a.sada; &a.hrs; &a.wsanchez; &a.nsayer; &a.sos; &a.wosch; &a.cy; &a.schweikh; &a.dick; &a.jseger; &a.gshapiro; &a.shiba; &a.nork; &a.tshiozak; &a.simokawa; &a.vanilla; &a.silby; &a.shafeeq; &a.demon; &a.jesper; &a.skv; &a.scop; &a.msmith; &a.ben; &a.des; &a.sobomax; &a.dcs; &a.brian; &a.nsouch; &a.mks; &a.stark; &a.murray; &a.sumikawa; &a.gsutter; &a.suz; &a.unfurl; &a.nyan; &a.tanimura; &a.taoka; &a.mtaylor; &a.dt; &a.mi; &a.gordon; &a.yar; &a.cwt; &a.pst; &a.ume; &a.semenu; &a.rv; &a.hoek; &a.logo; &a.nectar; &a.jayanth; &a.wjv; &a.bean; &a.swallace; &a.ticso; &a.takawata; &a.adamw; &a.naddy; &a.assar; &a.dwhite; &a.nate; &a.wollman; &a.keichii; &a.joerg; &a.kbyanc; &a.jennifer; &a.yokota; &a.andy; &a.zarzycki; &a.phantom; &a.jmz; Le projet de documentation de FreeBSD Le projet de documentation de FreeBSD est responsable de différents services, chaque service étant fourni par un responsable, et ses assistants (si il y a):: L'architecte du projet de documentation &a.nik; Le contact pour le manuel de référence &a.jim; Le contact de la FAQ &a.doc; Le contact pour les News &a.jim; Le contact presse &a.jkoshy; Le contact pour la "FreeBSD Really-Quick NewsLetter" Chris Coleman chrisc@vmunix.com Le contact pour les galleries &a.phantom; Le contact commercial &a.ceri; Le contact des groupes d'utilisateurs &a.grog; Le projet Java FreeBSD &a.patrick; La conversion LinuxDoc vers DocBook &a.nik; Qui est reponsable de quoi Responsable du projet de documentation &a.nik; Coordinateur des mirroirs CVSup &a.jdp; Internationalisation &a.ache; Gestion du courrier &a.jmb; Coordination des versions &a.re; coaché par &a.murray; Relations publiques Actuellement personne Officier de Securité &a.security-officer; coaché par &a.nectar; Responsable du répertoire des sources Principal: &a.peter; Assistants: &a.markm;, &a.joe; Gestion du site Web &a.www; Collection des packages &a.portmgr; qui inclue: &a.ade;, &a.asami;, &a.knu;, &a.kris;, &a.sobomax;, &a.steve;, &a.will; Standards &a.wollman; Liaison avec le projet XFree86 &a.rich; Administration de la base GNATS &a.steve; Bugmeister &a.keramida; Bureau de liaison des donations &a.donations; qui inclue: &a.mwlucas; &a.nsayer; &a.obrien; &a.rwatson; Liste des anciens de la "Core Team" core team Ces personnes ont été membres de la "core team" durant la période indiquée. Nous les remercions pour leur efforts passés au service du projet FreeBSD. Par ordre chronologique: &a.dg; (1992 - 2002) &a.dfr; (1999 - 2002) &a.msmith; (2000 - 2002) &a.jkh; (1992 - 2002) &a.asami; (1993 - 2001) &a.ache; (1993 - 2000) &a.jmb; (1993 - 2000) &a.bde; (1992 - 2000) &a.gibbs; (1993 - 2000) &a.rich; (1994 - 2000) &a.phk; (1992 - 2000) &a.gpalmer; (1993 - 2000) &a.sos; (1993 - 2000) &a.wollman; (1993 - 2000) &a.joerg; (1995 - 2000) &a.jdp; (1997 - 2000) &a.guido; (1995 - 1999) John Dyson (1993 - 1998) &a.nate; (1992 - 1996) &a.rgrimes; (1992 - 1995) Andreas Schulz (1992 - 1995) &a.csgr; (1993 - 1995) &a.paul; (1992 - 1995) &a.smace; (1993 - 1994) Andrew Moore (1993 - 1994) Christoph Robitschko (1993 - 1994) J. T. Conklin (1992 - 1993) Liste des anciens développeurs development team Ces personnes ont été membres de l'équipe de développement durant la période indiquée. Nous les remercions pour leur efforts passés au service du projet FreeBSD. Par ordre chronologique: &a.martin; (???? - 2002) &a.graichen; (???? - 2002) &a.asmodai; (1999 - 2002) &a.uch; (2000 - 2002) &a.jmacd; (???? - 2002) &a.issei; (2000 - 2002) &a.tedm; (???? - 2000) &a.karl; (???? - 2000) Gary Clark II (1993 - 2000) James Raynard (???? - 2000) &a.jgreco; (???? - 1999) Andreas Schulz (???? - 1999) Jamil Weatherby (1997 - 1999) meganm (???? - 1998) John Dyson (???? - 1998) Amancio Hasty (1997 - 1998) Drew Derbyshire (1997 - 1998) Liste des logiciels contribués Ce logiciel a été originellement dérivé de la version 0.1 de William F. Jolitz's 386BSD, qui ne comportait plus de code spécifique à 386BSD. Ce logiciel a été essentiellement ré-implémenté depuis la version 4.4BSD-Lite fourni par le groupe de Computer Science Research (CSRG) de l'université de California, Berkeley et des contributeurs associés. Des portions de NetBSD et OpenBSD ont été intégrés à &os;, et nous remercions aussi les contributeurs de ces projets pour leur travail. Contributeurs additionnels à FreeBSD (par ordre alphabétique et trié par prénom): ABURAYA Ryushirou rewsirow@ff.iij4u.or.jp AMAGAI Yoshiji amagai@nue.org Aaron Bornstein aaronb@j51.com Aaron Smith aaron@mutex.org Achim Patzner ap@noses.com Ada T Lim ada@bsd.org Adam Baran badam@mw.mil.pl Adam Glass glass@postgres.berkeley.edu Adam Herzog adam@herzogdesigns.com Adam Kranzel adam@alameda.edu Adam McDougall mcdouga9@egr.msu.edu Adam Strohl troll@digitalspark.net Adoal Xu adoal@iname.com Adrian Colley aecolley@ois.ie Adrian Hall ahall@mirapoint.com Adrian Mariano adrian@cam.cornell.edu Adrian Steinmann ast@marabu.ch Adrian T. Filipi-Martin atf3r@agate.cs.virginia.edu Ajit Thyagarajan unknown Akira SAWADA unknown Akira Watanabe akira@myaw.ei.meisei-u.ac.jp Akito Fujita fujita@zoo.ncl.omron.co.jp Alain Kalker A.C.P.M.Kalker@student.utwente.nl Alan Bawden alan@curry.epilogue.com Alec Wolman wolman@cs.washington.edu Aled Morris aledm@routers.co.uk Aleksandr A Babaylov .@babolo.ru Alex D. Chen dhchen@Canvas.dorm7.nccu.edu.tw Alex Dupre sysadmin@alexdupre.com Alex G. Bulushev bag@demos.su Alex Kapranoff kappa@zombie.antar.bryansk.ru Alex Le Heux alexlh@funk.org Alex Perel veers@disturbed.net Alex Rodioukov simuran@shaw.ca Alex Semenyaka alex@rinet.ru Alex Varju varju@webct.com Alex Zepeda garbanzo@hooked.net Alexander B. Povolotsky tarkhil@mgt.msk.ru Alexander Gelfenbain mail@gelf.com Alexandre Peixoto alexandref@tcoip.com.br Alexandre Snarskii snar@paranoia.ru Alexey Dokuchaev danfe@regency.nsu.ru Alexey V. Neyman alex.neyman@auriga.ru Alexis Yushin alexis@forest.NLnetLabs.nl Alistair G. Crooks agc@uts.amdahl.com Allan Bowhill bowhill@bowhill.vservers.com Allan Saddi asaddi@philosophysw.com Allen Campbell allenc@verinet.com Amakawa Shuhei amakawa@hoh.t.u-tokyo.ac.jp Amancio Hasty hasty@star-gate.com Amar Takhar verm@drunkmonk.net Amir Farah amir@comtrol.com Amir Shalem amir@boom.org.il Amy Baron amee@beer.org Anatoliy Dmytriyev tolid@plab.ku.dk Anatoly A. Orehovsky tolik@mpeks.tomsk.su Anatoly Vorobey mellon@pobox.com Anders Andersson anders@codefactory.se Anders Thulin Anders.X.Thulin@telia.se Andras Olah olah@cs.utwente.nl Andre Albsmeier Andre.Albsmeier@mchp.siemens.de Andre Goeree abgoeree@uwnet.nl Andre Oppermann andre@pipeline.ch Andreas Haakh ah@alman.robin.de Andreas Kohout shanee@rabbit.augusta.de Andreas Lohr andreas@marvin.RoBIN.de Andreas Schulz unknown Andreas Wetzel mickey@deadline.snafu.de Andreas Wrede andreas@planix.com Andres Vega Garcia unknown Andrew Atrens atreand@statcan.ca Andrew Boothman andrew@cream.org Andrew Gillham gillham@andrews.edu Andrew Gordon andrew.gordon@net-tel.co.uk Andrew Herbert andrew@werple.apana.org.au Andrew J. Korty ajk@purdue.edu Andrew L. Moore alm@mclink.com Andrew L. Neporada andrew@chg.ru Andrew McRae amcrae@cisco.com Andrew P. Lentvorski bsder@allcaps.org Andrew S. Midthune amidthune@cableone.net Andrew Shevtsov nyxo@dnuc.polyn.kiae.su Andrew Stevenson andrew@ugh.net.au Andrew Timonin tim@pool1.convey.ru Andrew V. Stesin stesin@elvisti.kiev.ua Andrew Webster awebster@dataradio.com Andrey Novikov andrey@novikov.com Andrey Simonenko simon@comsys.ntu-kpi.kiev.ua Andrey Sverdlichenko rblaze@users.sourceforge.net Andrey Tchoritch andy@venus.sympad.net Andy Farkas andyf@speednet.com.au Andy Sparrow spadger@best.com Andy Valencia ajv@csd.mot.com Andy Whitcroft andy@sarc.city.ac.uk Angel Todorov todorov_bg@gmx.net Angelo Turetta ATuretta@stylo.it Anthony C. Chavez acc@anthonychavez.org Anthony Yee-Hang Chan yeehang@netcom.com Antoine Beaupre anarcat@anarcat.ath.cx Anton N. Bruesov antonz@library.ntu-kpi.kiev.ua Anton Voronin anton@urc.ac.ru Antti Kaipila anttik@iki.fi Are Bryne are.bryne@communique.no Ari Suutari ari@suutari.iki.fi Arindum Mukerji rmukerji@execpc.com Arjan de Vet devet@IAEhv.nl Arnaud S. Launay asl@launay.org Arne Henrik Juul arnej@Lise.Unit.NO Arun Sharma adsharma@sharmas.dhs.org Ashley Penney ashp@unloved.org Ask Bjoern Hansen ask@valueclick.com Atsushi Furuta furuta@sra.co.jp Atsushi Murai amurai@spec.co.jp Atushi Sakauchi sakauchi@yamame.to Bakul Shah bvs@bitblocks.com Barry Bierbauch pivrnec@vszbr.cz Barry Lustig barry@ictv.com Ben Hutchinson benhutch@xfiles.org.uk Ben Jackson unknown Ben Walter bwalter@itachi.swcp.com Benedikt Köhler benedikt@furukama.de Benjamin Lewis bhlewis@gte.net Berend de Boer berend@pobox.com Bernd Rosauer br@schiele-ct.de Bill Kish kish@osf.org Bill Trost trost@cloud.rain.com Blaz Zupan blaz@amis.net Bob Van Valzah Bob@whitebarn.com Bob Wilcox bob@obiwan.uucp Bob Willcox bob@luke.pmr.com Boris Staeblow balu@dva.in-berlin.de Boyd Faulkner faulkner@mpd.tandem.com Boyd R. Faulkner faulkner@asgard.bga.com Brad Chapman chapmanb@arches.uga.edu Brad Hendrickse bradh@uunet.co.za Brad Jones brad@kazrak.com Brad Karp karp@eecs.harvard.edu Bill Lloyd wlloyd@mpd.ca Bradley Dunn bradley@dunn.org Bram Moolenaar bram@moolenaar.net Brandon Fosdick bfoz@glue.umd.edu Brandon Gillespie brandon@roguetrader.com Brent J. Nordquist bjn@visi.com Brett Lymn blymn@mulga.awadi.com.AU Brett Taylor brett@peloton.runet.edu Brian Campbell brianc@pobox.com Brian Clapper bmc@willscreek.com Brian Cully shmit@kublai.com Brian Handy handy@lambic.space.lockheed.com Brian Litzinger brian@MediaCity.com Brian McGovern bmcgover@cisco.com Brian Moore ziff@houdini.eecs.umich.edu Brian R. Haug haug@conterra.com Brian Skrab brian@quynh-and-brian.org Brian Tao taob@risc.org Brion Moss brion@queeg.com Bruce Albrecht bruce@zuhause.mn.org Bruce Gingery bgingery@gtcs.com Bruce J. Keeler loodvrij@gridpoint.com Bruce M Simpson bms@spc.org Bruce Murphy packrat@iinet.net.au Bruce Walter walter@fortean.com Camson Huynh chuynh@biolateral.com.au Carey Jones mcj@acquiesce.org Carl Fongheiser cmf@netins.net Carl Mascott cmascott@world.std.com Casper casper@acc.am Castor Fu castor@geocast.com Chain Lee chain@110.net Charles Hannum mycroft@ai.mit.edu Charles Henrich henrich@msu.edu Charles Mott cmott@scientech.com Charles Owens owensc@enc.edu Chet Ramey chet@odin.INS.CWRU.Edu Chia-liang Kao clkao@CirX.ORG Chiharu Shibata chi@bd.mbn.or.jp Chip Norkus unknown Chris Csanady cc@tarsier.ca.sandia.gov Chris Dabrowski chris@vader.org Chris Dillon cdillon@wolves.k12.mo.us Chris Pepper pepper@mail.rockefeller.edu Chris Shenton cshenton@angst.it.hq.nasa.gov Chris Stenton jacs@gnome.co.uk Chris Timmons skynyrd@opus.cts.cwu.edu Chris Torek torek@ee.lbl.gov Christian Brueffer chris@unixpages.org Christian Gusenbauer cg@fimp01.fim.uni-linz.ac.at Christian Haury Christian.Haury@sagem.fr Christian Zander zander@minion.de Christoph P. Kukulies kuku@FreeBSD.org Christoph Robitschko chmr@edvz.tu-graz.ac.at Christoph Weber-Fahr wefa@callcenter.systemhaus.net Christoph Weber-Fahr wefa@callcenter.systemhaus.net Christopher G. Demetriou cgd@postgres.berkeley.edu Christopher K. Davis ckd-freebsd@ckdhr.com Christopher N. Harrell cnh@ivmg.net Christopher Preston rbg@gayteenresource.org Christopher T. Johnson cjohnson@neunacht.netgsi.com Chrisy Luke chrisy@flix.net Chuck Hein chein@cisco.com Cliff Rowley dozprompt@onsea.com Colman Reilly careilly@tcd.ie Conrad Sabatier conrads@home.com Coranth Gryphon gryphon@healer.com Cornelis van der Laan nils@guru.ims.uni-stuttgart.de Cove Schneider cove@brazil.nbn.com Craig Leres leres@ee.lbl.gov Craig Loomis unknown Craig Metz cmetz@inner.net Craig Spannring cts@internetcds.com Craig Struble cstruble@vt.edu Cristian Ferretti cfs@riemann.mat.puc.cl Curt Mayer curt@toad.com Cyrille Lefevre clefevre@citeweb.net Cyrus Rahman cr@jcmax.com DI. Christian Gusenbauer cg@scotty.edvz.uni-linz.ac.at Dai Ishijima ishijima@tri.pref.osaka.jp Daisuke Watanabe NU7D-WTNB@asahi-net.or.jp Damian Hamill damian@cablenet.net Damien Tougas damien@tougas.net Dan Cross tenser@spitfire.ecsel.psu.edu Dan Langille dan@freebsddiary.org Dan Lukes dan@obluda.cz Dan Nelson dnelson@emsphone.com Dan Papasian bugg@bugg.strangled.net Dan Pelleg dpelleg+unison@cs.cmu.edu Dan Piponi wmtop@tanelorn.demon.co.uk Dan Walters hannibal@cyberstation.net Daniel B. Hemmerich dan@spot.org Daniel Hagan dhagan@acm.vt.edu Daniel O'Connor doconnor@gsoft.com.au Daniel Poirot poirot@aio.jsc.nasa.gov Daniel Rock rock@cs.uni-sb.de Daniel W. McRobb dwm@caimis.com Danny Egen unknown Danny Howard dannyman@toldme.com Danny J. Zerkel dzerkel@phofarm.com Dave Adkins adkin003@tc.umn.edu Dave Andersen angio@aros.net Dave Blizzard dblizzar@sprynet.com Dave Bodenstab imdave@synet.net Dave Burgess burgess@hrd769.brooks.af.mil Dave Chapeskie dchapes@ddm.on.ca Dave Cornejo dave@dogwood.com Dave Edmondson davided@sco.com Dave Glowacki dglo@ssec.wisc.edu Dave Marquardt marquard@austin.ibm.com Dave Tweten tweten@FreeBSD.org David A. Adkins adkin003@tc.umn.edu David A. Bader dbader@eece.unm.edu David Borman dab@bsdi.com David Bremner bremner@unb.ca David Bushong david+ports@bushong.net David Dawes dawes@XFree86.org David Filo unknown David H. Munro munro1@llnl.gov David Holland dholland@eecs.harvard.edu David Holloway daveh@gwythaint.tamis.com David Horwitt dhorwitt@ucsd.edu David Hovemeyer daveho@infocom.com David Jones dej@qpoint.torfree.net David Kelly dkelly@tomcat1.tbe.com David Kulp dkulp@neomorphic.com David L. Nugent davidn@blaze.net.au David Leonard d@scry.dstc.edu.au David Muir Sharnoff muir@idiom.com David S. Miller davem@jenolan.rutgers.edu David Sugar dyfet@gnu.org David Wolfskill david@catwhisker.org David Yeske dyeske@yahoo.com Dean Gaudet dgaudet@arctic.org Dean Huxley dean@fsa.ca Denis Fortin unknown Denis N. Peplin info@volginfo.ru Denis Shaposhnikov dsh@vlink.ru Dennis Glatting dennis.glatting@software-munitions.com Denton Gentry denny1@home.com Derek Inksetter derek@saidev.com Diane Bruce db@db.net Dirk Gouders gouders@et.bocholt.fh-gelsenkirchen.de Dirk Keunecke dk@panda.rhein-main.de Dirk Nehrling nerle@pdv.de Dishanker Rajakulendren draj@oceanfree.net Dmitry A. Yanko fm@astral.ntu-kpi.kiev.ua Dmitry Karasik dmitry@karasik.eu.org Dmitry Khrustalev dima@xyzzy.machaon.ru Dmitry Kohmanyuk dk@farm.org Dmitry Morozovsky marck@rinet.ru Dom Mitchell dom@myrddin.demon.co.uk Domas Mituzas midom@dammit.lt Dominic Marks dominic_marks@btinternet.com Dominik Brettnacher domi@saargate.de Dominik Rothert dr@domix.de Don Croyle croyle@gelemna.ft-wayne.in.us Don Morrison dmorrisn@u.washington.edu &a.whiteside; Don Yuniskis dgy@rtd.com Donald Maddox dmaddox@conterra.com Donn Miller dmmiller@cvzoom.net Douglas Carmichael dcarmich@mcs.com Douglas Crosher dtc@scrooge.ee.swin.oz.au Drew Derbyshire ahd@kew.com Dustin Sallings dustin@spy.net Le projet ELISA Font Eckart "Isegrim" Hofmann Isegrim@Wunder-Nett.org Ed Gold vegold01@starbase.spd.louisville.edu Ed Hudson elh@p5.spnet.com Edgardo Garcia Hoeffler edybsd@yahoo.com.ar Edward Chuang edwardc@firebird.org.tw Edward Wang edward@edcom.com Edwin Mons e@ik.nu Ege Rekk aagero@aage.priv.no Eiji-usagi-MATSUmoto usagi@clave.gr.jp Eike Bernhardt eike.bernhardt@gmx.de Elmar Bartel bartel@informatik.tu-muenchen.de Eoin Lawless eoin@maths.tcd.ie Eric A. Griff eric@talesfromthereal.com Eric Anderson anderson@centtech.com Eric Blood eblood@cs.unr.edu Eric D. Futch efutch@nyct.net Eric J. Haug ejh@slustl.slu.edu Eric J. Schwertfeger eric@cybernut.com Eric L. Hernes erich@lodgenet.com Eric P. Scott eps@sirius.com Eric Sprinkle eric@ennovatenetworks.com Erich Stefan Boleyn erich@uruk.org Erich Zigler erich@tacni.net Erik E. Rantapaa rantapaa@math.umn.edu Erik H. Bakke erikhb@bgnett.no Erik H. Moe ehm@cris.com Ernst Winter ewinter@lobo.muc.de Erwin Lansing erwin@lansing.dk Espen Skoglund esk@ira.uka.de Eugene M. Kim astralblue@usa.net Eugene Radchenko genie@qsar.chem.msu.su Eugeney Ryzhyk rzheka@users.sourceforge.net Eugeny Kuzakov CoreDumped@coredumped.null.ru Evan Champion evanc@synapse.net FUJIMOTO Kensaku fujimoto@oscar.elec.waseda.ac.jp FURUSAWA Kazuhisa furusawa@com.cs.osakafu-u.ac.jp Fanying Jen fanying@fynet.com Faried Nawaz fn@Hungry.COM Filippo Natali filippo@widestore.net Flemming Jacobsen fj@batmule.dk Fong-Ching Liaw fong@juniper.net Francis M J Hsieh mjshieh@life.nthu.edu.tw Francisco Reyes fjrm@yahoo.com Frank Bartels knarf@camelot.de Frank Chen Hsiung Chan frankch@waru.life.nthu.edu.tw Frank Durda IV uhclem@nemesis.lonestar.org Frank Gründer elwood@mc5sys.in-berlin.de Frank J. Lazlo laszlof@freebsdmatrix.net Frank MacLachlan fpm@n2.net Frank Nobis fn@Radio-do.de Frank Volf volf@oasis.IAEhv.nl Frank ten Wolde franky@pinewood.nl Frank van der Linden frank@fwi.uva.nl Franz Klammer klammer@webonaut.com Fred Cawthorne fcawth@jjarray.umn.edu Fred Gilham gilham@csl.sri.com Fred Templin templin@erg.sri.com Freddie Cash fcash@bigfoot.com Frederic Dubuy fdubuy@free.fr Frederick Earl Gray fgray@rice.edu Frerich Raabe frerich.raabe@gmx.de Fuyuhiko Maruyama fuyuhik8@is.titech.ac.jp &a.stanislav; Gabor Kincses gabor@acm.org Gabor Zahemszky zgabor@CoDe.hu Gareth McCaughan gjm11@dpmms.cam.ac.uk Garrett Rooney rooneg@electricjellyfish.net Gary A. Browning gab10@griffcd.amdahl.com Gary Howland gary@hotlava.com Gary J. garyj@rks32.pcs.dec.com Gary Kline kline@thought.org Gary W. Swearingen swear@aa.net Gaspar Chilingarov nightmar@lemming.acc.am Gea-Suan Lin gslin@ccca.nctu.edu.tw Gene Raytsin pal@paladin7.net Geoff Rehmet csgr@alpha.ru.ac.za Georg Wagner georg.wagner@ubs.com Gianlorenzo Masini masini@uniroma3.it Gianmarco Giovannelli gmarco@giovannelli.it Gil Kloepfer Jr. gil@limbic.ssdl.com Gilad Rom rom_glsa@ein-hashofet.co.il Giles Lean giles@nemeton.com.au Ginga Kawaguti ginga@amalthea.phys.s.u-tokyo.ac.jp Glen Foster gfoster@gfoster.com Glenn Johnson gljohns@bellsouth.net Godmar Back gback@facility.cs.utah.edu Goran Hammarback goran@astro.uu.se Gord Matzigkeit gord@enci.ucalgary.ca Gordon Greeff gvg@uunet.co.za Graham Wheeler gram@cdsec.com Greg A. Woods woods@zeus.leitch.com Greg Ansley gja@ansley.com Greg Robinson greg@rosevale.com.au Greg Troxel gdt@ir.bbn.com Greg Ungerer gerg@stallion.oz.au Gregory Bond gnb@itga.com.au Gregory D. Moncreaff moncrg@bt340707.res.ray.com Gurkan Sengun gurkan@linuks.mine.nu Guy Harris guy@netapp.com HAMADA Naoki hamada@astec.co.jp HIYAMA Takeshi gibbon@cocoa.freemail.ne.jp HONDA Yasuhiro honda@kashio.info.mie-u.ac.jp HOSOBUCHI Noriyuki hoso@buchi.tama.or.jp HOTARU-YA hotaru@tail.net Hammurabi Mendes hmendes_br@yahoo.com Hannes Sowa satbran@web.de Hannu Savolainen hannu@voxware.pp.fi Hans Huebner hans@artcom.de Hans Petter Bieker zerium@webindex.no Hans Zuidam hans@brandinnovators.com Hans-Christian Ebke hans-christian_ebke@gmx.de Harlan Stenn Harlan.Stenn@pfcs.com Harold Barker hbarker@dsms.com Harry Newton harry_newton@telinco.co.uk Havard Eidnes Havard.Eidnes@runit.sintef.no Heath Nielson heath@cs.byu.edu Heikki Suonsivu hsu@cs.hut.fi Heiko W. Rupp unknown Helmut F. Wirth hfwirth@ping.at Hendrik Scholz hendrik@scholz.net Henrik Vestergaard Draboel hvd@terry.ping.dk Henry Whincup henry@techiebod.com Herb Peyerl hpeyerl@NetBSD.org Hideaki Ohmon ohmon@tom.sfc.keio.ac.jp Hidekazu Kuroki hidekazu@cs.titech.ac.jp Hideki Yamamoto hyama@acm.org Hideyuki Suzuki hideyuki@sat.t.u-tokyo.ac.jp Hirayama Issei iss@mail.wbs.ne.jp Hiroaki Sakai sakai@miya.ee.kagu.sut.ac.jp Hiroharu Tamaru tamaru@ap.t.u-tokyo.ac.jp Hironori Ikura hikura@kaisei.org Hiroshi Nishikawa nis@pluto.dti.ne.jp Hiroya Tsubakimoto unknown Hiten Pandya hiten@uk.FreeBSD.org Holger Lamm holger@eit.uni-kl.de Holger Veit Holger.Veit@gmd.de Holm Tiffe holm@geophysik.tu-freiberg.de Horance Chou horance@freedom.ie.cycu.edu.tw Horihiro Kumagai kuma@jp.FreeBSD.org Hr.Ladavac lada@ws2301.gud.siemens.co.at Hubert Feyrer hubertf@NetBSD.ORG Hugh F. Mahon hugh@nsmdserv.cnd.hp.com Hugh Mahon h_mahon@fc.hp.com Hung-Chi Chu hcchu@r350.ee.ntu.edu.tw IMAI Takeshi take-i@ceres.dti.ne.jp IMAMURA Tomoaki tomoak-i@is.aist-nara.ac.jp IWASHITA Yoji shuna@pop16.odn.ne.jp Ian Holland ianh@tortuga.com.au Ian Struble ian@broken.net Ian Vaudrey i.vaudrey@bigfoot.com Igor Khasilev igor@jabber.paco.odessa.ua Igor Pokrovsky tiamat@telegraph.spb.ru Igor Roshchin str@giganda.komkon.org Igor Serikov bt@turtle.pangeatech.com Igor Sviridov siac@ua.net Igor Vinokurov igor@zynaps.ru Ikuo Nakagawa ikuo@isl.intec.co.jp Ilia Chipitsine ilia@jane.cgu.chel.su Ilya V. Komarov mur@lynx.ru Itsuro Saito saito@miv.t.u-tokyo.ac.jp J. Bryant jbryant@argus.flash.net J. David Lowe lowe@saturn5.com J. Han hjh@photino.com J. Hawk jhawk@MIT.EDU J Shoemaker shoemaker@softhome.net J.T. Conklin jtc@cygnus.com Jack jack@zeus.xtalwind.net Jacob Bohn Lorensen jacob@jblhome.ping.mk Jagane D Sundar jagane@netcom.com Jake Hamby jehamby@anobject.com James Clark jjc@jclark.com James D. Stewart jds@c4systm.com James Raynard fhackers@jraynard.demon.co.uk James T. Liu jtliu@phlebas.rockefeller.edu James da Silva jds@cs.umd.edu Jamie Heckford jamie@jamiesdomain.co.uk Jan Conard charly@fachschaften.tu-muenchen.de Jan Jungnickel Jan@Jungnickel.com Jan Koum jkb@FreeBSD.org Jan L. Peterson jlp@flipdog.com Janick Taillandier Janick.Taillandier@ratp.fr Janos Mohacsi janos.mohacsi@bsd.hu Janusz Kokot janek@gaja.ipan.lublin.pl Jarle Greipsland jarle@idt.unit.no Jason DiCioccio geniusj@ods.org Jason Garman init@risen.org Jason Harris jharris@widomaker.com Jason R. Mastaler jason-freebsd@mastaler.com Jason Thorpe thorpej@NetBSD.org Jason Wright jason@OpenBSD.org Jason Young doogie@forbidden-donut.anet-stl.com Javier Martin Rueda jmrueda@diatel.upm.es Jay Fenlason hack@datacube.com Jay Krell jay.krell@cornell.edu Jaye Mathisen mrcpu@cdsnet.net Jean-Sebastien Roy js@jeannot.org Jean-Yves Lefort jylefort@brutele.be Jeff Bartig jeffb@doit.wisc.edu Jeff Brown jabrown@caida.org Jeff Forys jeff@forys.cranbury.nj.us Jeff Kletsky Jeff@Wagsky.com Jeff Palmer scorpio@drkshdw.org Jeffrey Evans evans@scnc.k12.mi.us Jeffrey Wheat jeff@cetlink.net Jeremy Allison jallison@whistle.com Jeremy Chadwick yoshi@parodius.com Jeremy Chatfield jdc@xinside.com Jeremy Karlson karlj000@unbc.ca Jeremy Prior unknown Jeremy Shaffner jeremy@external.org Jesse McConnell jesse@cylant.com Jesse Rosenstock jmr@ugcs.caltech.edu Jian-Da Li jdli@csie.nctu.edu.tw Jim Babb babb@FreeBSD.org Jim Binkley jrb@cs.pdx.edu Jim Bloom bloom@acm.org Jim Carroll jim@carroll.com Jim Flowers jflowers@ezo.net Jim Geovedi negative@toxic.magnesium.net Jim Leppek jleppek@harris.com Jim Lowe james@cs.uwm.edu Jim Mattson jmattson@sonic.net Jim Mercer jim@komodo.reptiles.org Jim Sloan odinn@atlantabiker.net Jim Wilson wilson@moria.cygnus.com Jimbo Bahooli griffin@blackhole.iceworld.org Jin Guojun jin@george.lbl.gov Joachim Kuebart kuebart@mathematik.uni-ulm.de Joao Carlos Mendes Luis jonny@jonny.eng.br Jochen Pohl jpo.drs@sni.de Joe Abley jabley@automagic.org Joe Halpin joe.halpin@attbi.com Joe Jih-Shian Lu jslu@dns.ntu.edu.tw Joe Kelsey joek@flyingcroc.net Joe Orthoefer j_orthoefer@tia.net Joe Traister traister@mojozone.org Joel Faedi Joel.Faedi@esial.u-nancy.fr Joel Ray Holveck joelh@gnu.org Joel Sutton jsutton@bbcon.com.au Johan Granlund johan@granlund.nu Johan Larsson johan@moon.campus.luth.se Johann Tonsing jtonsing@mikom.csir.co.za Johannes 5 Joemann joemann@beefree.free.de Johannes Helander unknown Johannes Stille unknown John Beckett jbeckett@southern.edu John Beukema jbeukema@hk.super.net John Brezak unknown John Capo jc@irbs.com John F. Woods jfw@jfwhome.funhouse.com John Goerzen jgoerzen@alexanderwohl.complete.org John Heidemann johnh@isi.edu John Hood cgull@owl.org John Kohl unknown John Lind john@starfire.mn.org John Mackin john@physiol.su.oz.au John Merryweather Cooper jmcoopr@webmail.bmi.net John P johnp@lodgenet.com John Perry perry@vishnu.alias.net John Preisler john@vapornet.com John Reynolds jjreynold@home.com John Rochester jr@cs.mun.ca John Sadler john_sadler@alum.mit.edu John Saunders john@pacer.nlc.net.au John Wehle john@feith.com John Woods jfw@eddie.mit.edu Johny Mattsson lonewolf@flame.org Jon Morgan morgan@terminus.trailblazer.com Jon Wilson jon@phuq.co.uk Jonathan Belson jon@witchspace.com Jonathan H N Chin jc254@newton.cam.ac.uk Jonathan Hanna jh@pc-21490.bc.rogers.wave.ca Jonathan Pennington john@coastalgeology.org Jordan DeLong fracture@allusion.net Jorge Goncalves j@bug.fe.up.pt Jorge M. Goncalves ee96199@tom.fe.up.pt Jos Backus jos@catnook.com Jose Abelardo Martinez jamartinez@altern.org Jose Marques jose@nobody.org Josef El-Rayes j.el-rayes@daemon.li Josef Grosch jgrosch@superior.mooseriver.com Joseph Scott joseph@randomnetworks.com Joseph Stein joes@wstein.com Josh Gilliam josh@quick.net Josh Tiefenbach josh@ican.net Joshua Goodall joshua@roughtrade.net Jostein Trondal jostein.trondal@sikkerhet.no Juan Salaverria rael@vectorstar.net Juergen Lock nox@jelal.hb.north.de Juha Inkari inkari@cc.hut.fi Juha Ylitalo juha.ylitalo@iki.fi Jukka A. Ukkonen jau@iki.fi Julian Assange proff@suburbia.net Julian Coleman j.d.coleman@ncl.ac.uk &a.jhs; Julian Jenkins kaveman@magna.com.au Jung-uk Kim jkim@niksun.com Junichi Satoh junichi@jp.FreeBSD.org Junji SAKAI sakai@jp.FreeBSD.org Junya WATANABE junya-w@remus.dti.ne.jp Justas justas@mbank.lv Justin Stanford jus@security.za.net KATO Tsuguru tkato@prontomail.ne.jp KIMURA Shigekazu zau50357@lion.zero.ad.jp KUNISHIMA Takeo kunishi@c.oka-pu.ac.jp K.Higashino a00303@cc.hc.keio.ac.jp Kai Vorma vode@snakemail.hut.fi Kaleb S. Keithley kaleb@ics.com Kaneda Hiloshi vanitas@ma3.seikyou.ne.jp Kang-ming Liu gugod@gugod.org Kapil Chowksey kchowksey@hss.hns.com Karl Denninger karl@mcs.com Karl Dietz Karl.Dietz@triplan.com Karl Lehenbauer karl@NeoSoft.com Karsten W. Rohrbach karsten@rohrbach.de Kawanobe Koh kawanobe@st.rim.or.jp Kees Jan Koster kjkoster@kjkoster.org Keith Bostic bostic@bostic.com Keith E. Walker kew@icehouse.net Keith Moore unknown Keith Sklower unknown Ken Hornstein unknown Ken Key key@cs.utk.edu Ken Mayer kmayer@freegate.com Ken McGlothlen mcglk@artlogix.com Ken Tom sub@mui.net Kenji Saito marukun@mx2.nisiq.net Kenji Tomita tommyk@da2.so-net.or.jp Kenneth Furge kenneth.furge@us.endress.com Kenneth Monville desmo@bandwidth.org Kenneth R. Westerback krw@tcn.net Kenneth Stailey kstailey@gnu.ai.mit.edu Kent Talarico kent@shipwreck.tsoft.net Kent Vander Velden graphix@iastate.edu Kentaro Inagaki JBD01226@niftyserve.ne.jp Kevin Bracey kbracey@art.acorn.co.uk Kevin Day toasty@dragondata.com Kevin Lahey kml@nas.nasa.gov Kevin Meltzer perlguy@perlguy.com Kevin Street street@iname.com Kevin Van Maren vanmaren@fast.cs.utah.edu Killer killer@prosalg.no Kim Scarborough sluggo@unknown.nu Kimura Fuyuki fuyuki@hadaly.org Kiril Mitev kiril@ideaglobal.com Kiroh HARADA kiroh@kh.rim.or.jp Klaus Goger klaus.goger@reflex.at Klaus Herrmann klaus.herrmann@gmx.net Klaus Klein kleink@layla.inka.de Klaus-J. Wolf Yanestra@t-online.de Koichi Sato copan@ppp.fastnet.or.jp Konrad Heuer kheuer@gwdu60.gwdg.de Konstantin Chuguev Konstantin.Chuguev@dante.org.uk Kostya Lukin lukin@okbmei.msk.su Kouichi Hirabayashi kh@mogami-wire.co.jp Kris Dow kris@vilnya.demon.co.uk Kurt D. Zeilenga Kurt@Boolean.NET Kurt Olsen kurto@tiny.mcs.usu.edu Kyle Martin mkm@ieee.org L. Jonas Olsson ljo@ljo-slip.DIALIN.CWRU.Edu Landon Fullerlandonf@opendarwin.org Larry Altneu larry@ALR.COM Lars Bernhardsson lab@fnurt.net Lars Köller Lars.Koeller@Uni-Bielefeld.DE Laurence Lopez lopez@mv.mv.com Lauri Watts lauri@kde.org Lee Cremeans lcremean@tidalwave.net Lefteris Chatzibarbas lefcha@hellug.gr Leo Kim leo@florida.sarang.net Lev A. Serebryakov lev@serebryakov.spb.ru Liang Tai-hwa avatar@www.mmlab.cse.yzu.edu.tw Lon Willett lon%softt.uucp@math.utah.edu Louis A. Mamakos loiue@TransSys.com Lowell Gilbert lowell@world.std.com Lucas James Lucas.James@ldjpc.apana.org.au Lyndon Nerenberg lyndon@orthanc.ab.ca M. L. Dodson bdodson@scms.utmb.EDU M.C. Wong unknown MOROHOSHI Akihiko moro@race.u-tokyo.ac.jp Magnus Enbom dot@tinto.campus.luth.se Mahesh Neelakanta mahesh@gcomm.com Makoto WATANABE watanabe@zlab.phys.nagoya-u.ac.jp Makoto YAMAKURA makoto@pinpott.spnet.ne.jp Malte Lance malte.lance@gmx.net Manu Iyengar iyengar@grunthos.pscwa.psca.com Marc Frajola marc@dev.com Marc Ramirez mrami@mramirez.sy.yale.edu Marc Recht marc@informatik.uni-bremen.de Marc Silver marcs@draenor.org Marc Slemko marcs@znep.com Marc van Kempen wmbfmk@urc.tue.nl Marc van Woerkom van.woerkom@netcologne.de Marcin Cieslak saper@system.pl Marco Molteni molter@tin.it Marcus vA mva121@gmx.net Marius Strobl marius@alchemy.franken.de Mark Andrews unknown Mark Cammidge mark@gmtunx.ee.uct.ac.za Mark Diekhans markd@grizzly.com Mark Huizer xaa@stack.nl Mark J. Taylor mtaylor@cybernet.com Mark Knight markk@knigma.org Mark Krentel krentel@rice.edu Mark Mayo markm@vmunix.com Mark Thompson thompson@tgsoft.com Mark Tinguely tinguely@plains.nodak.edu Mark Treacy unknown Mark Valentine mark@thuvia.org Markus Holmberg saska@acc.umu.se Martin Birgmeier unknown Martin Blapp blapp@attic.ch Martin Hinner mhi@linux.gyarab.cz Martin Ibert mib@ppe.bb-data.de Martin Kammerhofer dada@sbox.tu-graz.ac.at Martin Karlsson martin.karlsson@visit.se Martin Klaffenboeck martin.klaffenboeck@gmx.at Martin Matuska matuska@wu-wien.ac.at Martin Minkus diskiller@cnbinc.com Martin Renters martin@tdc.on.ca Martti Kuparinen martti.kuparinen@ericsson.com Masachika ISHIZUKA ishizuka@isis.min.ntt.jp Masahiro Sekiguchi seki@sysrap.cs.fujitsu.co.jp Masahiro TAKEMURA mastake@msel.t.u-tokyo.ac.jp Masanobu Saitoh msaitoh@spa.is.uec.ac.jp Masanori Kanaoka kana@saijo.mke.mei.co.jp Masanori Kiriake seiken@ARGV.AC Masatoshi TAMURA tamrin@shinzan.kuee.kyoto-u.ac.jp Mats Lofkvist mal@algonet.se Matt Bartley mbartley@lear35.cytex.com Matt Douhan matt@athame.co.uk Matt Heckaman matt@LUCIDA.QC.CA Matt Loschertloschert@servint.com Matt Peterson matt@peterson.org Matt Thomas matt@3am-software.com Matt White mwhite+@CMU.EDU Matthew C. Mead mmead@Glock.COM Matthew Cashdollar mattc@rfcnet.com Matthew Emmerton root@gabby.gsicomp.on.ca Matthew Flatt mflatt@cs.rice.edu Matthew Fuller fullermd@over-yonder.net Matthew Stein matt@bdd.net Matthew West mwest@uct.ac.za Matthias Pfaller leo@dachau.marco.de Matthias Scheler tron@netbsd.org Matthias Schündehütte msch@snafu.de Mattias Gronlund Mattias.Gronlund@sa.erisoft.se Mattias Pantzare pantzer@ludd.luth.se Maurice Castro maurice@planet.serc.rmit.edu.au Max Euston meuston@jmrodgers.com Maxim Bolotin max@rsu.ru Maxime Romano verbophobe@hotmail.com Micha Class michael_class@hpbbse.bbn.hp.com Michael A. Kohn naken@naken.cc Michael Alyn Miller malyn@strangeGizmo.com Michael Butler imb@scgt.oz.au Michael Butschky butsch@computi.erols.com Michael Clay mclay@weareb.org Michael Collette metrol@metrol.net Michael Ebert ebert@informatik.unibw-muenchen.de Michael Galassi nerd@percival.rain.com Michael Hancock michaelh@cet.co.jp Michael Handler handler@grendel.net Michael Hohmuth hohmuth@inf.tu-dresden.de Michael Hostbaek mich@freebsdcluster.org Michael Lyngbøl michael@lyngbol.dk Michael Perlman canuck@caam.rice.edu Michael Petry petry@netwolf.NetMasters.com Michael Sardo jaeger16@yahoo.com Michael Schout mschout@gkg.net Michael Searle searle@longacre.demon.co.uk Michael Urban murban@tznet.com Michael Vasilenko acid@stu.cn.ua Michal Listos mcl@Amnesiac.123.org Michal Pasternak doc@lublin.t1.pl Michio Karl Jinbo karl@marcer.nagaokaut.ac.jp Miguel Angel Sagreras msagre@cactus.fi.uba.ar Miguel Mendez flynn@energyhq.homeip.net Mihoko Tanaka m_tonaka@pa.yokogawa.co.jp Mika Nystrom mika@cs.caltech.edu Mikael Hybsch micke@dynas.se Mikael Karpberg karpen@ocean.campus.luth.se Mike Bristow mike@urgle.com Mike Del repenting@hotmail.com Mike Durian durian@plutotech.com Mike Durkin mdurkin@tsoft.sf-bay.org Mike E. Matsnev mike@azog.cs.msu.su Mike Evans mevans@candle.com Mike Futerko mike@LITech.lviv.ua Mike Grupenhoff kashmir@umiacs.umd.edu Mike Harding mvh@ix.netcom.com Mike Hibler mike@marker.cs.utah.edu Mike Karels unknown Mike Makonnen makonnen@pacbell.net Mike McGaughey mmcg@cs.monash.edu.au Mike Meyer mwm@mired.org Mike Mitchell mitchell@ref.tfs.com Mike Murphy mrm@alpharel.com Mike Peck mike@binghamton.edu Mike Sherwood mike@fate.com Mike Spengler mks@msc.edu Mikhail A. Sokolov mishania@demos.su Ming-I Hseh PA@FreeBSD.ee.Ntu.edu.TW Mitsuru Yoshida mitsuru@riken.go.jp Monte Mitzelfelt monte@gonefishing.org Morgan Davis root@io.cts.com Mostyn Lewis mostyn@mrl.com Motomichi Matsuzaki mzaki@e-mail.ne.jp Motoyuki Kasahara m-kasahr@sra.co.jp Munish Chopra munish@engmail.uwaterloo.ca N.G.Smith ngs@sesame.hensa.ac.uk NAGAO Tadaaki nagao@cs.titech.ac.jp NAKAJI Hiroyuki nakaji@tutrp.tut.ac.jp NAKAMURA Kazushi nkazushi@highway.or.jp NAKAMURA Motonori motonori@econ.kyoto-u.ac.jp NIIMI Satoshi sa2c@and.or.jp NOKUBI Hirotaka h-nokubi@yyy.or.jp Nadav Eiron nadav@barcode.co.il Nanbor Wang nw1@cs.wustl.edu Naofumi Honda honda@Kururu.math.sci.hokudai.ac.jp Naoki Hamada nao@tom-yam.or.jp Narvi narvi@haldjas.folklore.ee Nathan Dorfman nathan@rtfm.net Neal Fachan kneel@ishiboo.com Niall Smart rotel@indigo.ie Nicholas Esborn nick@netdot.net Nick Barnes Nick.Barnes@pobox.com Nick Handel nhandel@NeoSoft.com Nick Hilliard nick@foobar.org Nick Johnson freebsd@spatula.net Nick Williams njw@cs.city.ac.uk Nickolay N. Dudorov nnd@itfs.nsk.su Niklas Hallqvist niklas@filippa.appli.se Nils M. Holm nmh@t3x.org Nisha Talagala nisha@cs.berkeley.edu No Name ZW6T-KND@j.asahi-net.or.jp No Name adrian@virginia.edu No Name alex@elvisti.kiev.ua No Name anto@netscape.net No Name bobson@egg.ics.nitch.ac.jp No Name bovynf@awe.be No Name burg@is.ge.com No Name chris@gnome.co.uk No Name colsen@usa.net No Name coredump@nervosa.com No Name dannyman@arh0300.urh.uiuc.edu No Name davids@SECNET.COM No Name derek@free.org No Name devet@adv.IAEhv.nl No Name djv@bedford.net No Name dvv@sprint.net No Name enami@ba2.so-net.or.jp No Name flash@eru.tubank.msk.su No Name flash@hway.ru No Name fn@pain.csrv.uidaho.edu No Name frf@xocolatl.com No Name gclarkii@netport.neosoft.com No Name gordon@sheaky.lonestar.org No Name graaf@iae.nl No Name greg@greg.rim.or.jp No Name grossman@cygnus.com No Name gusw@fub46.zedat.fu-berlin.de No Name hfir@math.rochester.edu No Name hnokubi@yyy.or.jp No Name iaint@css.tuu.utas.edu.au No Name invis@visi.com No Name ishisone@sra.co.jp No Name iverson@lionheart.com No Name jpt@magic.net No Name junker@jazz.snu.ac.kr No Name k-sugyou@ccs.mt.nec.co.jp No Name kenji@reseau.toyonaka.osaka.jp No Name kfurge@worldnet.att.net No Name lh@aus.org No Name lhecking@nmrc.ucc.ie No Name mrgreen@mame.mu.oz.au No Name nakagawa@jp.FreeBSD.org No Name ohki@gssm.otsuka.tsukuba.ac.jp No Name owaki@st.rim.or.jp No Name pechter@shell.monmouth.com No Name pete@pelican.pelican.com No Name pritc003@maroon.tc.umn.edu No Name risner@stdio.com No Name roman@rpd.univ.kiev.ua No Name root@ns2.redline.ru No Name root@uglabgw.ug.cs.sunysb.edu No Name stephen.ma@jtec.com.au No Name sumii@is.s.u-tokyo.ac.jp No Name takas-su@is.aist-nara.ac.jp No Name tamone@eig.unige.ch No Name tjevans@raleigh.ibm.com No Name tony-o@iij.ad.jp amurai@spec.co.jp No Name torii@tcd.hitachi.co.jp No Name uenami@imasy.or.jp No Name uhlar@netlab.sk No Name vode@hut.fi No Name wlloyd@mpd.ca No Name wlr@furball.wellsfargo.com No Name wmbfmk@urc.tue.nl No Name yamagata@nwgpc.kek.jp No Name ziggy@ryan.org Nobuhiro Yasutomi nobu@psrc.isac.co.jp Nobuyuki Koganemaru kogane@koganemaru.co.jp Norio Suzuki nosuzuki@e-mail.ne.jp Noritaka Ishizumi graphite@jp.FreeBSD.org Noriyuki Soda soda@sra.co.jp Oddbjorn Steffensen oddbjorn@tricknology.org Oh Junseon hollywar@mail.holywar.net Olaf Wagner wagner@luthien.in-berlin.de Oleg Semyonov os@altavista.net Oleg Sharoiko os@rsu.ru Oleg V. Volkov rover@lglobus.ru Olexander Kunytsa kunia@wolf.istc.kiev.ua Oliver Breuninger ob@seicom.NET Oliver Friedrichs oliver@secnet.com Oliver Fromme oliver.fromme@heim3.tu-clausthal.de Oliver Helmling oliver.helmling@stud.uni-bayreuth.de Oliver Laumann net@informatik.uni-bremen.de Oliver Lehmann Kai_Allard_Liao@gmx.de Oliver Oberdorf oly@world.std.com Olivier Tharan olive@oban.frmug.org Olof Johansson offe@ludd.luth.se Osokin Sergey aka oZZ ozz@FreeBSD.org.ru Pace Willisson pace@blitz.com Paco Rosich rosich@modico.eleinf.uv.es Palle Girgensohn girgen@partitur.se Paolo Flag flag@gufi.org Parag Patel parag@cgt.com Pascal Pederiva pascal@zuo.dec.com Pasvorn Boonmark boonmark@juniper.net Patrick Alken cosine@ellipse.mcs.drexel.edu Patrick Bihan-Faou patrick@mindstep.com Patrick Hausen unknown Patrick Powell papowell@astart.com Patrick Seal patseal@hyperhost.net Paul Antonov apg@demos.su Paul F. Werkowski unknown Paul Fox pgf@foxharp.boston.ma.us Paul Koch koch@thehub.com.au Paul Kranenburg pk@NetBSD.org Paul M. Lambert plambert@plambert.net Paul Mackerras paulus@cs.anu.edu.au Paul Popelka paulp@uts.amdahl.com Paul S. LaFollette, Jr. unknown Paul Sandys myj@nyct.net Paul T. Root proot@horton.iaces.com Paul Vixie paul@vix.com Paulo Menezes paulo@isr.uc.pt Paulo Menezes pm@dee.uc.pt Pedro A M Vazquez vazquez@IQM.Unicamp.BR Pedro Giffuni giffunip@asme.org Per Wigren wigren@home.se Pete Bentley pete@demon.net Peter Avalos pavalos@theshell.com Peter Childs pjchilds@imforei.apana.org.au Peter Cornelius pc@inr.fzk.de Peter Haight peterh@prognet.com Peter Jeremy peter.jeremy@alcatel.com.au Peter M. Chen pmchen@eecs.umich.edu Peter Much peter@citylink.dinoex.sub.org Peter Olsson unknown Peter Philipp pjp@bsd-daemon.net Peter Stubbs PETERS@staidan.qld.edu.au Peter W. Schmiedeskamp pschmied@qwest.net Peter van Heusden pvh@wfeet.za.net Phil Maker pjm@cs.ntu.edu.au Phil Sutherland philsuth@mycroft.dialix.oz.au Phil Taylor phil@zipmail.co.uk Philip Musumeci philip@rmit.edu.au Philippe Lefebvre nemesis@balistik.net Pierre Y. Dampure pierre.dampure@k2c.co.uk Pius Fischer pius@ienet.com Pomegranate daver@flag.blackened.net Powerdog Industries kevin.ruddy@powerdog.com Priit Järv priit@cc.ttu.ee R Joseph Wright rjoseph@mammalia.org R. Kym Horsell Radoslav Vasilev rvasilev@uni-svishtov.bg Ralf Friedl friedl@informatik.uni-kl.de Randal S. Masutani randal@comtest.com Randall Hopper rhh@ct.picker.com Randall W. Dean rwd@osf.org Randy Bush rbush@bainbridge.verio.net Rasmus Kaj kaj@Raditex.se Reinier Bezuidenhout rbezuide@mikom.csir.co.za Remy Card Remy.Card@masi.ibp.fr Ricardas Cepas rch@richard.eu.org Riccardo Veraldi veraldi@cs.unibo.it Rich Wood rich@FreeBSD.org.uk Richard Henderson richard@atheist.tamu.edu Richard Hwang rhwang@bigpanda.com Richard J Kuhns rjk@watson.grauel.com Richard Kiss richard@homemail.com Richard M. Neswold rneswold@enteract.com Richard Seaman, Jr. dick@tar.com Richard Stallman rms@gnu.ai.mit.edu Richard Straka straka@user1.inficad.com Richard Tobin richard@cogsci.ed.ac.uk Richard Wackerbarth rkw@Dataplex.NET Richard Winkel rich@math.missouri.edu Richard Wiwatowski rjwiwat@adelaide.on.net Rick Macklem rick@snowhite.cis.uoguelph.ca Rick Macklin unknown Rob Austein sra@epilogue.com Rob Mallory rmallory@qualcomm.com Rob Snow rsnow@txdirect.net Robert Crowe bob@speakez.com Robert D. Thrush rd@phoenix.aii.com Robert Eckardt roberte@MEP.Ruhr-Uni-Bochum.de Robert P Ricci ricci@cs.utah.edu Robert Sanders rsanders@mindspring.com Robert Sexton robert@kudra.com Robert Shady rls@id.net Robert Swindells swindellsr@genrad.co.uk Robert Withrow witr@rwwa.com Robert Yoder unknown Robin Carey robin@mailgate.dtc.rankxerox.co.uk Rod Taylor rod@idiotswitch.org Roger Hardiman roger@cs.strath.ac.uk Roland Jesse jesse@cs.uni-magdeburg.de Roman Shterenzon roman@xpert.com Ron Bickers rbickers@intercenter.net Ron Lenk rlenk@widget.xmission.com Ronald Kuehn kuehn@rz.tu-clausthal.de Rudolf Cejka cejkar@fit.vutbr.cz Ruslan Belkin rus@home2.UA.net Ruslan Shevchenko rssh@cam.grad.kiev.ua Russell L. Carter rcarter@pinyon.org Russell Vincent rv@groa.uct.ac.za Ryan Younce ryany@pobox.com Ryuichiro IMURA imura@af.airnet.ne.jp SANETO Takanori sanewo@strg.sony.co.jp SASAKI Shunsuke ele@pop17.odn.ne.jp SAWADA Mizuki miz@qb3.so-net.ne.jp SUGIMURA Takashi sugimura@jp.FreeBSD.org SURANYI Peter suranyip@jks.is.tsukuba.ac.jp Sakai Hiroaki sakai@miya.ee.kagu.sut.ac.jp Sakari Jalovaara sja@tekla.fi Sam Hartman hartmans@mit.edu Samuel Lam skl@ScalableNetwork.com Samuel Tardieu sam@inf.enst.fr Samuele Zannoli zannoli@cs.unibo.it Sander Janssen janssen@rendo.dekooi.nl Sander Vesik sander@haldjas.folklore.ee Sandro Sigala ssigala@globalnet.it Sascha Blank blank@fox.uni-trier.de Sascha Wildner swildner@channelz.GUN.de Satoh Junichi junichi@astec.co.jp Scot Elliott scot@poptart.org Scot W. Hetzel hetzels@westbend.net Scott A. Kenney saken@rmta.ml.org Scott A. Moberly smoberly@xavier.dyndns.org Scott Blachowicz scott.blachowicz@seaslug.org Scott Burris scott@pita.cns.ucla.edu Scott Hazen Mueller scott@zorch.sf-bay.org Scott Michel scottm@cs.ucla.edu Scott Mitchel scott@uk.FreeBSD.org Scott Reynolds scott@clmqt.marquette.mi.us Sebastian Strollo seb@erix.ericsson.se Serge V. Vakulenko vak@zebub.msk.su Sergei Chechetkin csl@whale.sunbay.crimea.ua Sergei Kolobov sergei@kolobov.com Sergei S. Laskavy laskavy@pc759.cs.msu.su Sergey Gershtein sg@mplik.ru Sergey Kosyakov ks@itp.ac.ru Sergey N. Vorokov serg@tmn.ru Sergey Potapov sp@alkor.ru Sergey Samoyloff gonza@techline.ru Sergey Shkonda serg@bcs.zp.ua Sergey V.Dorokhov svd@kbtelecom.nalnet.ru Sergio Lenzi lenzi@bsi.com.br Shaun Courtney shaun@emma.eng.uct.ac.za Shawn M. Carey smcarey@mailbox.syr.edu Shell Hung shell@shellhung.org Shigio Yamaguchi shigio@tamacom.com Shinichiro Komatsu koma2@jiro.c.u-tokyo.ac.jp Shinya Esu esu@yk.rim.or.jp Shinya FUJIE fujie@tk.elec.waseda.ac.jp Shuichi Tanaka stanaka@bb.mbn.or.jp Simon simon@masi.ibp.fr Simon Burge simonb@telstra.com.au Simon Dick simond@irrelevant.org Simon J Gerraty sjg@melb.bull.oz.au Simon Marlow simonm@dcs.gla.ac.uk Simon Schubert corecode@corecode.ath.cx Simon Shapiro shimon@simon-shapiro.org Sin'ichiro MIYATANI siu@phaseone.co.jp Slaven Rezic eserte@cs.tu-berlin.de Soochon Radee slr@mitre.org Soren Dayton csdayton@midway.uchicago.edu Soren Dossing sauber@netcom.com Soren S. Jorvang soren@wheel.dk Stefan Bethke stb@hanse.de Stefan Eggers seggers@semyam.dinoco.de Stefan Farfeleder e0026813@stud3.tuwien.ac.at Stefan Moeding s.moeding@ndh.net Stefan Petri unknown Stefan `Sec` Zehl sec@42.org Steffen Vogelreuter Steffen@Vogelreuter.De Steinar Haug sthaug@nethelp.no Stephane E. Potvin sepotvin@videotron.ca Stephen Clawson sclawson@marker.cs.utah.edu Stephen F. Combs combssf@salem.ge.com Stephen Farrell stephen@farrell.org Stephen Gunn csg@fedex.com Stephen Hocking sysseh@devetir.qld.gov.au Stephen J. Roznowski sjr@home.net Stephen McKay syssgm@devetir.qld.gov.au Stephen Melvin melvin@zytek.com Steve Bauer sbauer@rock.sdsmt.edu Steve Coltrin spcoltri@unm.edu Steve Deering unknown Steve Gerakines steve2@genesis.tiac.net Steve Gericke steveg@comtrol.com Steve Piette steve@simon.chi.il.US Steve Schwarz schwarz@alpharel.com Steven Enderle panic@subphase.de Steven G. Kargl kargl@troutmask.apl.washington.edu Steven H. Samorodin samorodi@NUXI.com Steven McCanne mccanne@cs.berkeley.edu Steven Plite splite@purdue.edu Steven Wallace unknown Stijn Hoop stijn@win.tue.nl Stuart Henderson stuart@internationalschool.co.uk Sue Blake sue@welearn.com.au Sugimoto Sadahiro ixtl@komaba.utmc.or.jp Sugiura Shiro ssugiura@duo.co.jp Sujal Patel smpatel@wam.umd.edu Sune Stjerneby stjerneby@usa.net Sungman Cho smcho@tsp.korea.ac.kr Suzuki Yoshiaki zensyo@ann.tama.kawasaki.jp Svein Skogen tds@dmnstech.net Sybolt de Boer bolt@xs4all.nl TAKAHASHI Kaoru kaoru@kaisei.org Tadashi Kumano kumano@strl.nhk.or.jp Taguchi Takeshi taguchi@tohoku.iij.ad.jp Takahiro Yugawa yugawa@orleans.rim.or.jp Takashi Mega mega@minz.org Takashi Uozu j1594016@ed.kagu.sut.ac.jp Takayuki Ariga a00821@cc.hc.keio.ac.jp Takayuki Nakao t@nakao.org Takeru NAIKI naiki@bfd.es.hokudai.ac.jp Takeshi Amaike amaike@iri.co.jp Takeshi MUTOH mutoh@info.nara-k.ac.jp Takeshi Ohashi ohashi@mickey.ai.kyutech.ac.jp Takeshi WATANABE watanabe@crayon.earth.s.kobe-u.ac.jp Takuya SHIOZAKI tshiozak@makino.ise.chuo-u.ac.jp Tatoku Ogaito tacha@tera.fukui-med.ac.jp Tatsuya Kudoh cdr@cosmonet.org Ted Buswell tbuswell@mediaone.net Ted Faber faber@isi.edu Ted Lemon mellon@isc.org Terry Lambert terry@lambert.org Terry Lee terry@uivlsi.csl.uiuc.edu Teruaki Ata PFA03027@nifty.ne.jp Tetsuro Yabu yabu@uopmu.ees.osakafu-u.ac.jp Tetsuya Furukawa tetsuya@secom-sis.co.jp Theo de Raadt deraadt@OpenBSD.org Thierry Thomas thierry@pompo.net Thomas thomas@mathematik.uni-Bremen.de Thomas A. Stephens tas@stephens.org Thomas D. Dean tomdean@ix.netcom.com Thomas David Rivers rivers@dignus.com Thomas E. Zander rriggs@rrr.de Thomas G. McWilliams tgm@netcom.com Thomas König Thomas.Koenig@ciw.uni-karlsruhe.de Thomas M. Hermann Thomas.Hermann@cox.net Thomas Ptacek unknown Thomas Stromberg tstrombe@rtci.com Thomas Valentino Crimi tcrimi+@andrew.cmu.edu Thomas Vogt thomas.vogt@bsdunix.ch Thomas Wintergerst thomas@lemur.nord.de Þórður Ìvarsson totii@est.is Tim Kientzle kientzle@netcom.com Tim Singletary tsingle@sunland.gsfc.nasa.gov Tim Wilkinson tim@sarc.city.ac.uk Timo J. Rinne tri@iki.fi Timothy Jensen toast@blackened.com Tobias Reifenberger treif@mayn.de Todd Miller millert@openbsd.org Tom root@majestix.cmr.no Tom tom@sdf.com Tom Gray - DCA dcasba@rain.org Tom Jobbins tom@tom.tj Tom Pusateri pusateri@juniper.net Tom Rush tarush@mindspring.com Tom Samplonius tom@misery.sdf.com Tomohiko Kurahashi kura@melchior.q.t.u-tokyo.ac.jp Tony Kimball alk@Think.COM Tony Li tli@jnx.com Tony Lynn wing@cc.nsysu.edu.tw Tony Maher tonym@biolateral.com.au Torbjorn Granlund tege@matematik.su.se Toshihiko SHIMOKAWA toshi@tea.forus.or.jp Toshihiro Kanda candy@kgc.co.jp Toshiomi Moriki Toshiomi.Moriki@ma1.seikyou.ne.jp Trefor S. trefor@flevel.co.uk Trenton Schulz twschulz@cord.edu Trevor Blackwell tlb@viaweb.com URATA Shuichiro s-urata@nmit.tmg.nec.co.jp Udo Schweigert ust@cert.siemens.de Ugo Paternostro paterno@dsi.unifi.it Ulf Kieber kieber@sax.de Ulli Linzen ulli@perceval.camelot.de Uwe Arndt arndt@mailhost.uni-koblenz.de Uwe Pierau uwe.pierau@tu-clausthal.de Vadim Belman voland@catpipe.net Vadim Chekan vadim@gc.lviv.ua Vadim Kolontsov vadim@tversu.ac.ru Vadim Mikhailov mvp@braz.ru Valentin Nechayev netch@lucky.net Van Jacobson van@ee.lbl.gov Vasily V. Grechishnikov bazilio@ns1.ied-vorstu.ac.ru Vasim Valejev vasim@uddias.diaspro.com Vassili Tchersky vt@bsd-fr.org Vernon J. Schryver vjs@mica.denver.sgi.com Veselin Slavov vess@btc.net Vic Abell abe@cc.purdue.edu Ville Eerola ve@sci.fi Vince Valenti vince@blue-box.net Vincent Poy vince@venus.gaianet.net Vincenzo Capuano VCAPUANO@vmprofs.esoc.esa.de Virgil Champlin champlin@pa.dec.com Vladimir A. Jakovenko vovik@ntu-kpi.kiev.ua Vladimir Kushnir kushn@mail.kar.net Vladimir Savichev vlad@ariel.phys.wesleyan.edu Vsevolod Lobko seva@alex-ua.com W. Gerald Hicks wghicks@bellsouth.net W. Richard Stevens rstevens@noao.edu Walt Howard howard@ee.utah.edu Walt M. Shandruk walt@erudition.net Walter Hop walter@binity.com Warren Toomey wkt@csadfa.cs.adfa.oz.au Wayne Scott wscott@ichips.intel.com Werner Griessl werner@btp1da.phy.uni-bayreuth.de Wes Santee wsantee@wsantee.oz.net Wietse Venema wietse@wzv.win.tue.nl Wiljo Heinen wiljo@freeside.ki.open.de Willem van Engen wvengen@stack.nl Willem Jan Withagen wjw@surf.IAE.nl William Jolitz withheld William Josephson wkj-freebsd@honk.eecs.harvard.edu William Liao william@tale.net Wojtek Pilorz wpilorz@celebris.bdk.lublin.pl Wolfgang Helbig helbig@ba-stuttgart.de Wolfgang Solfrank ws@tools.de Wolfgang Stanglmeier wolf@FreeBSD.org Wouter Van Hemel wouter@pair.com Wu Ching-hong woju@FreeBSD.ee.Ntu.edu.TW &a.wylie; Xavier Beaudouin kiwi@oav.net Yannis Kotsinos zookie@med.auth.gr Yarema yds@ingress.com Yaroslav Terletsky ts@polynet.lviv.ua Yasuhiro Fukama yasuf@big.or.jp Yasuhito FUTATSUKI futatuki@fureai.or.jp Yen-Shuo Su yssu@CCCA.NCTU.edu.tw Yin-Jieh Chen yinjieh@Crazyman.Dorm13.NCTU.edu.tw Yixin Jin yjin@rain.cs.ucla.edu Yoichi Asai yatt@msc.biglobe.ne.jp Yonatan Bokovza Yonatan@xpert.com Yoshiaki Uchikawa yoshiaki@kt.rim.or.jp Yoshihiko SARUMRU mistral@imasy.or.jp Yoshihisa NAKAGAWA y-nakaga@ccs.mt.nec.co.jp Yoshikazu Goto gotoh@ae.anritsu.co.jp Yoshimasa Ohnishi ohnishi@isc.kyutech.ac.jp Yoshishige Arai ryo2@on.rim.or.jp Yu-Shun Wang yushunwa@isi.edu Yuichi MATSUTAKA matutaka@osa.att.ne.jp Yujiro MIYATA miyata@bioele.nuee.nagoya-u.ac.jp Yusuke Nawano azuki@azkey.org Yuu Yashiki s974123@cc.matsuyama-u.ac.jp Yuuichi Narahara aconitum@po.teleway.ne.jp Yuuki SAWADA mami@whale.cc.muroran-it.ac.jp Yuval Yarom yval@cs.huji.ac.il Yves Fonk yves@cpcoup5.tn.tudelft.nl Yves Fonk yves@dutncp8.tn.tudelft.nl Zach Garner zach@neurosoft.org Zach Heilig zach@gaffaneys.com Zach Zurflu zach@pabst.bendnet.com Zahemszhky Gabor zgabor@code.hu Zhong Ming-Xun zmx@mail.CDPA.nsysu.edu.tw arci vega@sophia.inria.fr der Mouse mouse@Collatz.McRCIM.McGill.EDU Contributeurs du kit de patch 386BSD (par ordre alphabétique trié par prénom): Adam Glass glass@postgres.berkeley.edu Adrian Hall ahall@mirapoint.com Andrey A. Chernov ache@astral.msk.su Andrew Gerweck andy@gerweck.dynup.net Andrew Herbert andrew@werple.apana.org.au Andrew Moore alm@netcom.com Andy Valencia ajv@csd.mot.com jtk@netcom.com Arne Henrik Juul arnej@Lise.Unit.NO Bakul Shah bvs@bitblocks.com Barry Lustig barry@ictv.com Bob Wilcox bob@obiwan.uucp Branko Lankester Brett Lymn blymn@mulga.awadi.com.AU Charles Hannum mycroft@ai.mit.edu Chris G. Demetriou cgd@postgres.berkeley.edu Chris Torek torek@ee.lbl.gov Christoph Robitschko chmr@edvz.tu-graz.ac.at Daniel Poirot poirot@aio.jsc.nasa.gov Dave Burgess burgess@hrd769.brooks.af.mil Dave Rivers rivers@ponds.uucp David Dawes dawes@physics.su.OZ.AU David Greenman dg@Root.COM Eric J. Haug ejh@slustl.slu.edu Felix Gaehtgens felix@escape.vsse.in-berlin.de Frank Maclachlan fpm@crash.cts.com Gary A. Browning gab10@griffcd.amdahl.com Gary Howland gary@hotlava.com Geoff Rehmet csgr@alpha.ru.ac.za Goran Hammarback goran@astro.uu.se Guido van Rooij guido@gvr.org Guy Antony Halse guy@rucus.ru.ac.za Guy Harris guy@auspex.com Havard Eidnes Havard.Eidnes@runit.sintef.no Herb Peyerl hpeyerl@novatel.cuc.ab.ca Holger Veit Holger.Veit@gmd.de Ishii Masahiro, R. Kym Horsell J.T. Conklin jtc@cygnus.com Jagane D Sundar jagane@netcom.com James Clark jjc@jclark.com James Jegers jimj@miller.cs.uwm.edu James W. Dolter James da Silva jds@cs.umd.edu et al Jay Fenlason hack@datacube.com Jim Wilson wilson@moria.cygnus.com Jörg Lohse lohse@tech7.informatik.uni-hamburg.de Jörg Wunsch joerg_wunsch@uriah.heep.sax.de John Dyson John Woods jfw@eddie.mit.edu Jordan K. Hubbard jkh@whisker.hubbard.ie Julian Elischer julian@dialix.oz.au Julian Stacey jhs@FreeBSD.org Karl Dietz Karl.Dietz@triplan.com Karl Lehenbauer karl@NeoSoft.com karl@one.neosoft.com Keith Bostic bostic@toe.CS.Berkeley.EDU Ken Hughes Kent Talarico kent@shipwreck.tsoft.net Kevin Lahey kml%rokkaku.UUCP@mathcs.emory.edu kml@mosquito.cis.ufl.edu Konstantinos Konstantinidis kkonstan@duth.gr Marc Frajola marc@dev.com Mark Tinguely tinguely@plains.nodak.edu tinguely@hookie.cs.ndsu.NoDak.edu Martin Renters martin@tdc.on.ca Michael Clay mclay@weareb.org Michael Galassi nerd@percival.rain.com Mike Durkin mdurkin@tsoft.sf-bay.org Naoki Hamada nao@tom-yam.or.jp Nate Williams nate@bsd.coe.montana.edu Nick Handel nhandel@NeoSoft.com nick@madhouse.neosoft.com Pace Willisson pace@blitz.com Paul Kranenburg pk@cs.few.eur.nl Paul Mackerras paulus@cs.anu.edu.au Paul Popelka paulp@uts.amdahl.com Peter da Silva peter@NeoSoft.com Phil Sutherland philsuth@mycroft.dialix.oz.au Poul-Henning Kamp phk@FreeBSD.org Ralf Friedl friedl@informatik.uni-kl.de Rick Macklem root@snowhite.cis.uoguelph.ca Robert D. Thrush rd@phoenix.aii.com Rodney W. Grimes rgrimes@cdrom.com Sascha Wildner swildner@channelz.GUN.de Scott Burris scott@pita.cns.ucla.edu Scott Reynolds scott@clmqt.marquette.mi.us Seamus Venasse svenasse@polaris.ca Sean Eric Fagan sef@kithrup.com Simon J Gerraty sjg@melb.bull.oz.au sjg@zen.void.oz.au Stephen McKay syssgm@devetir.qld.gov.au Terry Lambert terry@icarus.weber.edu Terry Lee terry@uivlsi.csl.uiuc.edu Tor Egge Tor.Egge@idi.ntnu.no Warren Toomey wkt@csadfa.cs.adfa.oz.au Wiljo Heinen wiljo@freeside.ki.open.de William Jolitz withheld Wolfgang Solfrank ws@tools.de Wolfgang Stanglmeier wolf@dentaro.GUN.de Yuval Yarom yval@cs.huji.ac.il + +
diff --git a/fr_FR.ISO8859-1/articles/nanobsd/article.xml b/fr_FR.ISO8859-1/articles/nanobsd/article.xml index ebd7d3df8a..be739a4435 100644 --- a/fr_FR.ISO8859-1/articles/nanobsd/article.xml +++ b/fr_FR.ISO8859-1/articles/nanobsd/article.xml @@ -1,572 +1,574 @@
Introduction à NanoBSD Daniel Gerzo 2006 The FreeBSD Documentation Project &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Ce document fournit des informations à propos des outils NanoBSD, qui peuvent être utilisés pour créer des images du système &os; pour des applications embarquées, adaptées pour utiliser comme support une carte Compact Flash (ou tout autre support de stockage). &trans.a.tignon; Introduction à NanoBSD NanoBSD NanoBSD est un outil actuellement développé par &a.phk;. Il permet de créer une image du système &os; pour des applications embarquées, pouvant utiliser une carte Compact Flash comme support (ou un autre support de stockage) Il peut être utilisé pour créer des images d'installation spécialisées, conçues pour une installation et une maintenance aisées de systèmes communément appelés appliances. Les appliances ont leur matériel et leur logiciel intégrés dans le produit, ce qui signifie que toutes les applications sont pré-installées. L'appliance est connectée à un réseau existant et peut entrer en fonction (presque) immédiatement. Les fonctionnalités de NanoBSD incluent: Les logiciels portés et les paquetages fonctionnent comme sous &os; — Chaque application peut être installée et utilisée dans une image NanoBSD, de la même façon que sous &os;. Aucune fonctionnalité ne manque — S'il est possible de faire quelque chose avec &os;, il sera possible de faire la même chose avec NanoBSD, sauf si la fonctionnalité spécifique ou des fonctionnalités ont été explicitement supprimées de l'image NanoBSD lors de sa création. Tout est en lecture seule pendant l'exécution — Débrancher le cordon d'alimentation est sans danger. Il n'est pas nécessaire d'exécuter &man.fsck.8; après un arrêt inopiné du système. Facile à créer et à personnaliser — A l'aide d'une seule procédure et d'un fichier de configuration il est possible de créer des images personnalisées et de taille réduite répondant à n'importe quel type de besoin. Comment utiliser NanoBSD L'organisation de NanoBSD Une fois que l'image est présente sur le support, il est possible de démarrer NanoBSD. Le périphérique de stockage est divisé en trois parties par défaut: Deux partitions image: code#1 et code#2. La partition de configuration, qui peut être montée sur le répertoire /cfg à l'exécution. Ces partitions sont normalement montées en lecture seule. Les répertoires /etc et /var sont des disques &man.md.4; (malloc). La partition de configuration est montée sur le répertoire /cfg. Elle contient les fichiers du répertoire /etc et est brièvement montée en lecture seule juste après le démarrage du système, par conséquent il est nécessaire de recopier les fichiers modifiés de /etc vers le répertoire /cfg si l'on souhaite que les changements soient encore effectifs après le redémarrage du système. Apporter des changements permanents à <filename>/etc/resolv.conf</filename> &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg La partition qui abrite /cfg doit être montée uniquement au démarrage et lors de la copie des fichiers de configuration. Garder /cfg monté en permanence n'est pas une bonne idée, en particulier si le système NanoBSD tourne sur un périphérique de stockage qui peut être endommagé par un grand nombre d'écritures sur la partition (c'est à dire quand le contenu des tampons de données est transféré sur les disques). Créer une image NanoBSD Une image NanoBSD est créée à l'aide d'une simple procédure nanobsd.sh, qui peut être trouvée dans le répertoire /usr/src/tools/tools/nanobsd. Ce programme crée une image, qui peut être copiée sur le support de stockage à l'aide de &man.dd.1;. Les commandes nécessaires à la création d'une image NanoBSD sont: &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k Se placer dans le répertoire de base du programme de création de NanoBSD. Démarrer le processus de création. Se placer dans le répertoire où les images ont été créees. Installer NanoBSD sur le support de stockage. Personnaliser une image NanoBSD C'est probablement la fonctionnalité la plus importante et la plus intéressante de NanoBSD. C'est aussi là où vous passerez le plus de temps lors de vos développements avec NanoBSD. L'invocation de la commande suivante va obliger nanobsd.sh à lire sa configuration dans le fichier myconf.nano situé dans le répertoire courant: &prompt.root; sh nanobsd.sh -c myconf.nano La personnalisation est effectuée de 2 façons: à l'aide d'options de configuration à l'aide de fonctions de personnalisation Les options de configuration Grace aux paramètres de configuration, il est possible de configurer des options qui sont passées aux étapes buildworld et installworld du processus de compilation de NanoBSD, ainsi que des options internes qui sont passées au processus principal de compilation de NanoBSD. A l'aide de ces options, il est possible de diminuer la taille du système, de façon à ce qu'il tienne dans 64Mo. Vous pouvez utiliser les options de configuration pour réduire encore plus &os;, jusqu'à ce qu'il ne consiste plus qu'en un noyau et 2 ou 3 fichiers dans le système de base. Le fichier de configuration consiste en une série d'options de configuration, qui surchargent les valeurs par défaut. Les directives les plus importantes sont: NANO_NAME — Nom de compilation (utilisé pour créer le nom des répertoires de travail). NANO_SRC — Chemin de l'arbre des sources utilisé pour construire l'image. NANO_KERNEL — Nom du fichier de configuration utilisé pour compiler le noyau. CONF_BUILD — Options passées à la phase buildworld de la compilation. CONF_INSTALL — Options passées à la phase installworld de la compilation. CONF_WORLD — Options passées aux étapes buildworld et installworld. FlashDevice — Définit le type de support à utiliser. Consulter le fichier FlashDevice.sub pour plus de détails. Les fonctions de personnalisation Il est possible d'optimiser NanoBSD en utilisant des fonctions d'interpréteur de commandes dans le fichier de configuration. L'exemple suivant présente la trame de base des fonctions de personnalisation: cust_foo () ( echo "bar=topless" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo Un exemple plus utile de fonction de personnalisation est le suivant, qui change la taille par défaut du répertoire /etc de 5Mo à 30Mo: cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size Il existe par défaut quelques fonctions de personnalisation prédéfinies et prêtes à être utilisées: cust_comconsole — Désactive &man.getty.8; sur les consoles VGA (les périphériques /dev/ttyv*) et paramètre la console système sur le port série COM1. cust_allow_ssh_root — Autorise l'ouverture de sessions root via &man.sshd.8;. cust_install_files — Installe les fichiers du répertoire nanobsd/Files, qui contient des programmes utiles pour l'administration système. Exemple de fichier de configuration Un exemple complet de fichier de configuration pour créer une image NanoBSD personnalisée peut être: NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie Mettre à jour NanoBSD Le processus de mise à jour de NanoBSD est relativement simple: Créer une nouvelle image NanoBSD, comme d'habitude. Télécharger la nouvelle image dans une partition inutilisée d'une appliance NanoBSD opérationnelle. La différence la plus importante de cette étape par rapport à l'installation initiale de NanoBSD est que maintenant au lieu d'utiliser le fichier _.disk.full (qui contient une image de la totalité du disque), l'image _.disk.image est installée (qui contient seulement l'image d'une seule partition système). Redémarrer le système sur la nouvelle partition. Si tout s'est bien passé, la mise à jour est terminée. Si quelque chose s'est mal passé, redémarrez de nouveau sur la partition précédente (qui contient l'ancienne image, fonctionnelle celle-ci), pour remettre le système en état de marche le plus rapidement possible. Corriger les problèmes de la nouvelle image, et répéter le processus. Pour installer la nouvelle image sur le système NanoBSD opérationnel, il est possible d'utiliser la procédure updatep1 ou updatep2 située dans le répertoire /root, en fonction de la partition qui est en cours d'utilisation sur le système. En fonction des services disponibles sur la machine qui dispose de la nouvelle image NanoBSD et du type de transfert qui est préféré, il est possible d'utiliser une de ces trois méthodes: Utiliser &man.ftp.1; Si la vitesse de transfert est la priorité, utiliser cet exemple: &prompt.root; ftp myhost get _.disk.image "| sh updatep1" Utiliser &man.ssh.1; Si un transfert sécurisé est préférable, considérer l'utilisation de cet exemple: &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 Utiliser &man.nc.1; Utiliser cet exemple si la machine distante n'utilise ni &man.ftp.1; ni &man.sshd.8;: Tout d'abord, ouvrez un écouteur TCP sur la machine qui dispose de l'image et faites-lui envoyer l'image au client: myhost&prompt.root; nc -l 2222 < _.disk.image Assurez vous que le port utilisé n'est pas bloqué par un pare-feu afin de recevoir les connexions entrantes de la machine NanoBSD. Se connecter à la machine qui dispose de la nouvelle image et exécuter la procédure updatep1: &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/fr_FR.ISO8859-1/articles/problem-reports/article.xml b/fr_FR.ISO8859-1/articles/problem-reports/article.xml index 6b6eccd30f..e16fcc660c 100644 --- a/fr_FR.ISO8859-1/articles/problem-reports/article.xml +++ b/fr_FR.ISO8859-1/articles/problem-reports/article.xml @@ -1,585 +1,587 @@
Ecrire des rapports de bogue pour FreeBSD Cet article décrit comment formuler et soumettre au mieux un rapport de bogue au projet FreeBSD. &trans.a.fonvieille; Dag-Erling Smørgrav Contributed by $FreeBSD$ $FreeBSD$ rapports de bogue Introduction Une des expériences la plus frustrante que peut vivre un utilisateur de logiciel est de soumettre un rapport de bogue et de le voir être fermé sommairement avec une explication laconique et sans aide du type “ce n'est pas un bogue” ou “PR bogué”. De même une des expériences la plus frustrante pour un programmeur est d'être submergé de rapports de bogue qui ne sont pas vraiment des rapports de bogue mais plutôt des demandes d'aide, ou qui contiennent peu ou pas d'information au sujet du problème et sur comment le reproduire. Ce document essaye de décrire comment écrire de bons rapports de bogue. Qu'est-ce qu'un bon rapport de bogue, allez-vous demander? Bien, pour aller directement au but, un bon rapport de bogue est celui qui peut être analysé et traité rapidement, pour la satisfaction mutuelle de l'utilisateur et du développeur. Bien que l'objectif principal de cet article soit les rapports de bogue pour FreeBSD, sa majeure partie devrait s'appliquer relativement bien à d'autres projets de logiciels. Notez que cet article est organisé thématiquement, et non pas de façon chronologique, ainsi vous devriez lire entièrement ce document avant de soumettre un rapport de bogue, plutôt que de le traiter comme un guide pas-à-pas. Quand soumettre un rapport de bogue Il existe beaucoup de types de problèmes, et tous ne devraient pas être à l'origine d'un rapport de bogue. Naturellement, personne n'est parfait, et il y aura des moments où vous serez convaincus d'avoir trouvé un bogue dans un programme alors qu'en fait vous avez mal compris la syntaxe d'une commande ou fait une erreur dans un fichier de configuration (cependant cela peut en soi être significatif d'une documentation sommaire ou d'une mauvaise gestion des erreurs dans l'application). Il reste beaucoup de cas où la soumission d'un rapport de bogue n'est clairement pas la bonne ligne de conduite, et ne servira qu'à frustrer les développeurs et vous-même. Réciproquement, il y a des cas où il peut être approprié de soumettre un rapport de bogue à propos de quelque chose d'autre qu'un bogue—une amélioration ou une demande de fonctionnalité, par exemple. Aussi comment déterminer ce qui est un bogue et ce qui ne l'est pas? Un principe de base simple est que votre problème n'est pas un bogue s'il peut être exprimé sous la forme d'une question (habituellement de la forme “Comment puis-je faire X?” ou “Où puis-je trouver Y?”). Ce n'est pas toujours aussi simple que cela, mais la règle de la question couvre une majorité de cas. Les quelques cas où il peut être approprié de soumettre un rapport de bogue au sujet de quelque chose qui n'est pas un bogue sont: demandes d'amélioration de caractéristiques. C'est généralement une bonne idée de discuter de cela sur les listes de diffusion avant de soumettre un rapport de bogue. Avis de mise à jour de logiciels maintenus à l'extérieur (principalement des logiciels portés, mais également des composants du système de base maintenus à l'extérieur comme BIND ou divers utilitaires GNU). Une autre chose est que si le système sur lequel vous expérimentez le bogue n'est pas suffisamment à jour, vous devriez considérer sérieusement de mettre à jour et d'essayer de reproduire le problème sur un système à jour avant de soumettre le rapport de bogue. Il y peu de choses qui ennuieront plus un développeur que de recevoir un rapport de bogue au sujet d'un problème déjà corrigé. Et finalement, un bogue qui ne peut être reproduit peut rarement être corrigé. Si le bogue se produit une seule fois et que vous ne pouvez pas le reproduire, et qu'il ne semble pas faire une autre victime, il y des chances qu'aucun des développeurs ne sera en mesure de le reproduire ou de comprendre ce qui ne va pas. Cela ne signifie pas que rien ne s'est produit, mais plutôt que les chances que votre rapport de bogue mène à un correctif sont très minces, et que vous devriez envisager de laisser tomber. Préparations Une bonne règle à suivre est de toujours effectuer une recherche avant de soumettre un rapport de bogue. Peut-être que votre problème a déjà été signalé; peut-être même qu'on en discute actuellement sur les listes de diffusion, ou l'était récemment; il se peut qu'il soit même déjà corrigé dans une nouvelle version de ce que vous utilisez. Vous devriez donc vérifier tous les lieux d'information avant de soumettre votre rapport de bogue. Pour FreeBSD, cela signifie: La FAQ. Les listes de diffusion—si vous n'êtes pas inscrit, utilisez l'outil de recherche des archives sur le site de FreeBSD. Si votre problème n'a pas été abordé sur les listes, vous pourriez essayer de poster un message à ce sujet et attendre quelques jours pour voir si quelqu'un peut déceler quelque chose que vous n'avez pas remarqué. Eventuellement, l'intégralité du web—utilisez votre moteur de recherche favoris pour chercher toutes les références à votre problème. Vous pouvez même obtenir des résultats des archives des listes de diffusion ou des forums de discussion que vous ne connaissiez pas ou parmi lesquels vous n'aviez pas pensé chercher. Et finalement, la base de données des PRs. A moins que votre problème ne soit récent ou obscure, il y a assez de chance pour qu'il soit déjà signalé. Ensuite, vous devez être sûr que le rapport de bogue est envoyé aux bonnes personnes. Le premier point ici est que si un problème est un bogue dans un logiciel tiers (un logiciel porté ou pré-compilé que vous avez installé), vous devrez rapporter le bogue à l'auteur originel, et pas au projet FreeBSD. Il y a deux exceptions à cette règle: la première est que si le bogue n'apparaît pas sur d'autres plate-formes, dans quel cas le problème peut venir de la façon dont le logiciel a été porté sous FreeBSD; la seconde est si l'auteur original a déjà corrigé le problème et sorti un correctif ou une nouvelle version de son logiciel, et que le logiciel porté de FreeBSD n'a pas encore été mis à jour. Le second point est que le système de suivi des bogues de FreeBSD classe les rapports de bogue en fonction de la catégorie que l'auteur a choisie. Donc, si vous choisissez la mauvaise catégorie, il y a de fortes chances qu'il passera inaperçu pendant un moment, jusqu'à ce que quelqu'un le re-catégorise. Ecrire le rapport de bogue Maintenant que vous avez décidé que votre problème mérite un rapport de bogue, et que c'est un problème avec FreeBSD, il est temps d'écrire le rapport. Assurez-vous que votre variable d'environnement VISUAL (ou EDITOR si VISUAL n'existe pas) est configurée avec quelque chose de pratique, et lancez &man.send-pr.1;. Attacher des correctifs ou des fichiers Le programme &man.send-pr.1; prévoit l'attachement de fichiers à un rapport de bogue. Vous pouvez attacher autant de fichiers que vous le désirez à condition que chacun ait un nom de base unique (i.e. le nom propre du fichier, sans le chemin). Utilisez juste l'option en ligne de commande pour spécifier le nom des fichiers que vous souhaitez attacher: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors Ne vous inquiétez pas pour les fichiers binaires; ils seront automatiquement encodés de façon à ne pas déranger votre logiciel de courrier. Si vous attachez un correctif, assurez-vous d'employer l'option ou avec &man.diff.1; pour créer un fichier diff unifié ou contextuel, et soyez sûr d'indiquer les numéros exacts des révisions CVS des fichiers que vous avez modifiés afin que les développeurs qui liront votre rapport soient capables d'appliquer facilement vos correctifs. Vous devez également prendre note à moins que vous ne le précisiez explicitement dans votre PR, que tous les correctifs que vous soumettez seront présumés être sous les mêmes termes de licence que le fichier original que vous avez modifié. Remplir le formulaire Le formulaire se compose d'une liste de champs, dont certains sont déjà préremplis, et qui peuvent avoir des commentaires expliquant leur but et la liste des valeurs utilisables. Ne vous inquiétez pas des commentaires; ils seront retirés automatiquement si vous ne les modifiez ou retirez pas vous-même. En haut du formulaire, sous les lignes SEND-PR:, se trouvent les entêtes d'émail. Vous n'avez normalement pas besoin de les modifier, à moins que vous envoyiez le rapport de bogue à partir d'une machine ou d'un compte qui peut envoyer mais pas recevoir de courrier, dans ce cas vous voudrez remplir les champs From: et Reply-To: suivant votre adresse émail réelle. Vous pouvez vouloir vous envoyer (ou à quelqu'un d'autre) une copie carbone du rapport de bogue en ajoutant une ou plusieurs adresses émail au champ Cc:. Ensuite vient une série de champ à une ligne: Submitter-Id: ne rien changer. La valeur par défaut current-users est correcte, même si vous utilisez FreeBSD-STABLE. Originator: ceci est normalement complété avec le champ gecos de l'utilisateur actuellement attaché au système. Veuillez indiquer votre véritable nom, suivi optionnellement de votre émail entre les symboles inférieur et supérieur. Organization: comme vous le sentez. Ce champ n'est pas employé pour quelque chose de significatif. Confidential: ceci est prérempli avec no; le changer ne signifie pas grand chose car il n'y a aucun rapport de bogue confidentiel pour FreeBSD—la base de données des PRs est distribuée dans le monde entier par CVSup. Synopsis: complétez ceci avec une description courte et précise du problème. Le synopsis est utilisé comme sujet du rapport de bogue, et est employé dans les listes et résumés de rapport de bogue; les rapports de bogue avec d'obscures sujets ont tendance à être ignorés. Si votre rapport de bogue inclus un correctif, veuillez utiliser un synopsis débutant avec le mot [PATCH]. Severity: une parmi non-critical, serious ou critical. Pas de surestimation, abstenez-vous de marquer votre problème comme critical à moins qu'il ne le soit vraiment (e.g. root exploit, panique du système facilement reproductible). Les développeurs ont tendance à ignorer ce champ et le suivant, précisément parce que les auteurs ont tendance à surestimer l'importance de leurs problèmes. Priority: une parmi low, medium ou high. Voir ci-dessus. Category: choisir l'une des suivantes: advocacy: problèmes concernant l'image publique de FreeBSD. Rarement utilisé. alpha: problèmes spécifiques à la plateforme Alpha. bin: problèmes avec les programmes utilisateur du système de base. conf: problèmes avec les fichiers de configuration, les valeurs par défaut etc... docs: problèmes avec les pages de manuel ou la documentation en ligne. gnu: problèmes avec les logiciels GNU comme &man.gcc.1; ou &man.grep.1;. i386: problèmes spécifiques à la plateforme i386. kern: problèmes avec le noyau. misc: tout ce qui ne va pas dans une des autres catégories. ports: problèmes concernant le catalogue des logiciels portés. sparc: problèmes spécifiques à la plate-forme Sparc. Class: choisissez une des suivantes: sw-bug: bogues logiciel. doc-bug: erreurs dans la documentation. change-request: demande de fonctionnalités supplémentaires ou de changement dans des fonctionnalités existantes. update: mise à jour de logiciels portés ou d'autres logiciels. maintainer-update: mise à jour de logiciels portés dont vous êtes le responsable. Release: La version de FreeBSD que vous utilisez. Ceci sera complété automatiquement par &man.send-pr.1; et devra être modifié seulement si vous envoyez le rapport de bogue à partir d'un système différent de celui qui présente le problème. Et enfin, il y a une série de champs à plusieurs lignes: Environment: Ceci devrait décrire, le plus exactement que possible, l'environnement dans lequel le problème a été observé. Cela inclus la version du système d'exploitation, la version du programme spécifique ou fichier qui contient le problème, et tout autre élément important comme la configuration du système, d'autres logiciels qui influencent le problème, etc. — presque tout ce dont a besoin un développeur pour reconstruire l'environnement dans lequel le problème apparaît. Description: une description complète et précise du problème que vous expérimentez. Essayez d'éviter de spéculer au sujet des causes du problème à moins que vous soyez certain d'être dans le vrai, car cela peut tromper le développeur. How-To-Repeat: Un résumé des actions nécessaires pour reproduire le problème. Fix: De préférence un correctif, ou au moins une solution de fortune (qui n'aidera pas seulement les autres personnes avec le même problème, mais peut aussi aider un développeur à comprendre la cause du problème), mais si vous n'avez aucune idée pour l'un ou l'autre, il vaut mieux laisser ce champ en blanc plutôt que de spéculer. Envoi du rapport de bogue Une fois que vous avez rempli et sauvegardé le formulaire, puis quitté votre éditeur, &man.send-pr.1; vous proposera s)end, e)dit or a)bort? (envoyer, éditer ou abandonner?). Vous pouvez alors taper s pour continuer et envoyer le rapport, e pour relancer l'éditeur et faire d'autres modifications, ou encore a pour abandonner. Si vous choisissez cette dernière votre rapport de bogue restera sur le disque (&man.send-pr.1; vous donnera le nom du fichier avant de terminer), ainsi vous pouvez l'éditer à loisir, ou peut-être même le transférer sur un système avec une meilleure connexion à l'Internet, avant de l'envoyer avec l'option de &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report Il lira le fichier spécifié, en validera le contenu, retirera les commentaires et l'enverra. Suivi Une fois que votre rapport de bogue a été classé, vous recevrez une confirmation par courrier qui contiendra le numéro de suivi qui a été assigné à votre rapport de bogue et l'URL que vous pouvez utiliser pour vérifier son statut. Avec un peu de chance, quelqu'un sera intéressé par votre problème et essaiera de s'en occuper, ou, quand ce sera le cas, expliquera pourquoi ce n'est pas un problème. Vous serez automatiquement prévenu de tout changement d'état, et vous recevrez des copies de tout commentaire ou correctif que quelqu'un pourra attacher au suivi de votre rapport de bogue. Si quelqu'un vous demande des informations supplémentaires, ou vous vous rappelez ou découvrez quelque chose que vous n'avez pas mentionné dans le rapport initial, envoyez-le juste à bug-followup@FreeBSD.org, en vous assurant que le numéro de suivi est inclus dans le sujet ainsi le système de suivi des bogues connaîtra à quel rapport de problème l'attacher. Si le rapport de bogue reste ouvert après que le problème soit corrigé, envoyez juste un courrier de suivi (de la manière prescrite ci-dessus) disant que le rapport de bogue peut être fermé, et, si possible, expliquant comment et quand le problème fut corrigé. Lecture supplémentaire Voici une liste des ressources concernant l'écriture et le traitement appropriés des rapports de bogue. Cela ne veut pas dire exhaustive. Comment rapporter efficacement les bogues—un excellent essai de Simon G. Tatham sur l'écriture de rapports de bogue utiles (non spécifique à FreeBSD). + +
diff --git a/fr_FR.ISO8859-1/books/handbook/Makefile b/fr_FR.ISO8859-1/books/handbook/Makefile index e19bd2cc04..643e16dd3a 100644 --- a/fr_FR.ISO8859-1/books/handbook/Makefile +++ b/fr_FR.ISO8859-1/books/handbook/Makefile @@ -1,288 +1,286 @@ # The FreeBSD Documentation Project # The FreeBSD French Documentation Project # # $FreeBSD$ # Original revision: 1.108 # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ MAINTAINER=blackend@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES = advanced-networking/isdn-bus.eps IMAGES+= advanced-networking/isdn-twisted-pair.eps IMAGES+= advanced-networking/natd.eps IMAGES+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES+= install/disk-layout.eps IMAGES+= install/example-dir1.eps IMAGES+= install/example-dir2.eps IMAGES+= install/example-dir3.eps IMAGES+= install/example-dir4.eps IMAGES+= install/example-dir5.eps IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/fr_FR.ISO8859-1/books/handbook/chapters.ent b/fr_FR.ISO8859-1/books/handbook/chapters.ent index 33d9d7c01f..6fedc814e6 100644 --- a/fr_FR.ISO8859-1/books/handbook/chapters.ent +++ b/fr_FR.ISO8859-1/books/handbook/chapters.ent @@ -1,73 +1,73 @@ %pgpkeys; - + "> diff --git a/hu_HU.ISO8859-2/articles/cups/article.xml b/hu_HU.ISO8859-2/articles/cups/article.xml index acf35d5b9f..c085498caf 100644 --- a/hu_HU.ISO8859-2/articles/cups/article.xml +++ b/hu_HU.ISO8859-2/articles/cups/article.xml @@ -1,527 +1,529 @@
A CUPS használata &os; rendszereken Chess Griffin
chess@chessgriffin.com
 &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Ez a cikk a CUPS beállítását és használatát mutatja be a &os; operációs rendszeren. Fordította: Páli Gábor, utolsó ellenõrzés: 2010.11.28. A Common Unix Printing System (CUPS) rövid bemutatása nyomtatás CUPS A CUPS, avagy Common UNIX Printing System (Egységes UNIX Nyomtatási Rendszer) a &unix; alapú operációs rendszerekhez fejlesztett hordozható nyomtatási réteg. Az Easy Software Products egy szabványos nyomtatási technológiaként alkotta meg a &unix; gyártók és felhasználók számára. A CUPS az ún. Internet Printing Protocol (IPP, Internetes Nyomtatási Protokoll) megoldásaira támaszkodóan kezeli a nyomtatási feladatokat és sorokat. Emellett még a Line Printer Daemon (LPD), a Server Message Block (SMB) és AppSocket (vagy más néven JetDirect) protokollokat is ismeri valamennyire. A CUPS a hétköznapi igényeknek megfelelõ &unix; alapú nyomtatás megteremtéséhez ezenkívül még támogatja a hálózati nyomtatók böngészésének lehetõségét, illetve a PostScript Printer Description (PPD, PostScript Nyomtató Leírás) használatát. Ennek eredményeképpen a CUPS tökéletesen alkalmas nyomtatók megosztására és elérésére &os;, &linux; &macos; X vagy &windows; típusú rendszereket vegyesen tartalmazó környezetekben. A CUPS hivatalos oldala a címen érhetõ el. A CUPS nyomtatószerver telepítése A CUPS telepíthetõ portként vagy csomagként. Ha portként szeretnénk telepíteni, akkor ahhoz a következõ parancsot kell kiadnunk rendszergazdaként: &prompt.root; cd /usr/ports/print/cups && make install clean A CUPS csomagjának telepítését pedig ezzel a paranccsal tudjuk (szintén rendszergazdaként) elvégezni: &prompt.root; pkg_add -r cups További nem kötelezõen telepítendõ, de határozottan ajánlott csomagok még a print/gutenprint-cups és a print/hplip, amelyek különbözõ típusú nyomtatókhoz tartalmaznak meghajtókat és segédprogramokat. A CUPS telepítése után a hozzá tartozó konfigurációs állományokat a /usr/local/etc/cups könyvtárban találhatjuk. A CUPS nyomtatószerver beállítása A CUPS szerver telepítése után néhány állomány módosításával végezhetjük el a szükséges beállításokat. Elõször is hozzunk létre (ha még nem létezne) vagy nyissuk meg az /etc/devfs.rules állományt és a cups csoport számára adjunk hozzáférést a rendszerünkben található összes nyomtatóra: [system=10] add path 'unlpt*' mode 0660 group cups add path 'ulpt*' mode 0660 group cups add path 'lpt*' mode 0660 group cups add path 'usb/X.Y.Z' mode 0660 group cups Az X, Y és Z helyén a nyomtató /dev/usb könyvtárban szereplõ értékeit adjuk meg. A nyomtatóhoz tartozó eszközleírót a &man.dmesg.8; kimenetében találjuk meg ugenX.Y néven, amely egy szimbolikus link a /dev/usb könyvtárban található megfelelõjére. Ezután az /etc/rc.conf állományba még vegyük fel a következõ két sort: cupsd_enable="YES" devfs_system_ruleset="system" Az iménti bejegyzések gondoskodnak a CUPS nyomtatószerver beüzemelésérõl a rendszer indítása során, illetve töltik be az elõbbi lépésben létrehozott helyi devfs szabályokat. Bizonyos µsoft.windows; rendszert használó kliensekkel csak akkor fogunk tudni nyomtatni a CUPS esetében, ha a /usr/local/etc/cups/mime.types és /usr/local/etc/cups/mime.convs állományokban kivesszük a megjegyzésbõl ezt a sort: application/octet-stream Miután végrehajtottuk ezeket a módosításokat, az alábbi parancsok használatával vagy az operációs rendszerrel együtt indítsuk újra a &man.devfs.8; és CUPS szolgáltatásokat: &prompt.root; /etc/rc.d/devfs restart &prompt.root; /usr/local/etc/rc.d/cupsd restart Nyomtatók beállítása a CUPS nyomtatószerveréhez A CUPS sikeres telepítését és beállítását követõen elkezdhetjük a nyomtatószerverhez kapcsolódó helyi nyomtatók hozzáadását. Ez nagyon hasonló, ha nem is teljesen megegyezõ más &unix; alapú rendszerek, például &linux; esetén a nyomtatók beállításához. A CUPS szerver irányítása és mûködtetése elsõsorban az általa felkínált webes felületen történik, amelyet a címen keresztül tudunk elérni. Amennyiben a CUPS egy másik számítógépen fut, akkor a címben természetesen a localhost (saját gépünk) helyén az adott gép IP-címét kell megadnunk. A CUPS webes felületén meglehetõsen könnyen lehet tájékozódni, külön menüket találunk a nyomtatók és nyomtatási sorok beállítására, a felhasználók hitelesítésére és a többi. Ezeken felül még az Administration képernyõ jobb oldalán különbözõ jelölõnégyzetekkel tudunk egyszerûen dönteni a gyakori beállításokról, például a szerverhez csatlakozó nyomtatókat megosztjuk-e a hálózaton keresztül, engedünk-e további felhasználókat hozzáférni a szolgáltatásokhoz, kinek milyen engédelyei legyenek a nyomtatókra és nyomtatási sorokra. A nyomtatók hozzáadásához elegendõ a CUPS webes felületén az Administration menün belül az Add Printer gombra vagy valamelyik New Printers Found gombra kattintani. A Device legördülõ menü megjelenése után egyszerûen válasszuk ki belõle a megfelelõ helyileg csatlakoztatott nyomtatót, majd folytassuk a telepítését. Ha telepítettük a korábban ajánlott print/gutenprint-cups és print/hplip programokat, akkor ennek során a hozzájuk tartozó meghajtók is meg fognak jelenni, amelyek esetleg többet tudnak vagy megbízhatóbbak. A CUPS kliensek beállítása A CUPS szerver beállítása, illetve a nyomtatók telepítése és megosztása után a kliensek, vagyis a CUPS által kínált szolgáltatásokat elérni kívánó gépek beállítása következik. Ha csupán egyetlen gépünk van, amely egyszerre szerver és kliens, akkor az itt szereplõ információk nagy részére nem lesz szükségünk. &unix; kliensek A &unix; kliensek esetében is a CUPS használatára lesz szükségünk. Miután rájuk is telepítettük, a CUPS által hálózaton megosztott nyomtatókat maguktól fel is ismerik a különbözõ munkakörnyezetek, például a GNOME vagy KDE nyomtatókezelõi. Emellett a szerverhez hasonlóan a kliensen is el tudjuk érni a címen a CUPS helyi felhasználói felületét, ahol az Administration menüben az Add Printer gombbal tudunk felvenni a szervernél tapasztalt módon hasonlóhoz. Amikor viszont megjelenik a Device legördülõ menü, akkor válasszuk az automatikusan felismert hálózati CUPS nyomtatót, vagy az ipp és http elemek valamelyikén keresztül adjuk meg a hálózati CUPS nyomtató IPP vagy HTTP alapú egységes forrásazonosítóját (URI) a következõ formák valamelyikében: ipp://szervernév-vagy-ip/printers/nyomtatónév http://szervernév-vagy-ip:631/printers/nyomtatónév Ha a CUPS kliensek valamiért nem látnák a hálózaton megosztott nyomtatókat, akkor próbáljuk meg hozzáadni a /usr/local/etc/cups/client.conf állományhoz a következõ sort: ServerName szerver-ip Ahol a szerver-ip helyére írjuk be a hálózatunkon található CUPS szerver helyi IP-címét. &windows; kliensek A &windows; XP elõtti változatai nem képesek együttmûködni a hálózaton megosztott IPP alapú nyomtatókkal. A &windowsxp; rendszertõl kezdõdõen azonban már rendelkeznek a szükséges támogatással, ezért itt már nagyon könnyû beállítani a CUPS nyomtatókat. Ehhez rendszeradminisztrátorként futtassuk a &windows; a nyomtatók hozzáadásához tartozó varázslóját, ahol válasszuk a Hálózati nyomtató típust, majd a következõ formában töltsük ki az eszköz forrásazonosítóját: http://szervernév-vagy-ip:631/printers/nyomtatónév Ha az IPP támogatását még nem tartalmazó régebbi &windows; változatunk van, akkor a CUPS szolgáltatásait a net/samba3 szerveren keresztül tudjuk elérhetõvé tenni, azonban ennek bemutatásával itt most nem foglalkozunk. Hibakeresés A CUPS használata során tapasztalható problémák többségét az engedélyek helytelen beállítása okozza. Elõször tehát, ha valami nem mûködik rendesen, akkor ellenõrizzük újra az elõbb felvázolt &man.devfs.8; beállításokat. Ezután gyõzõdjünk meg arról is, hogy az állományrendszerben ténylegesen keletkezõ eszközök engedélyei megfelelõek. Továbbá segíthet megoldani a problémát, ha felvesszük a felhasználónkat a korábban tárgyalt cups csoportba. Ha a CUPS felhasználói felületének Administration képernyõjén található beállítások látszólag hatástalanok, akkor érdemes úgy próbálkoznunk, hogy elõször készítünk egy bizonsági másolatot a /usr/local/etc/cups/cupsd.conf állományról és kézzel módosítgatva kísérletezünk különféle konfigurációs lehetõségek kombinációival. Ehhez találhatunk itt egy példát. Ezzel kapcsolatban azonban megjegyezzük, hogy a bemutatott cupsd.conf állomány inkább áttekinthetõ mintsem biztonságos módon tárgyalja a lehetõségeket. Ezért javasoljuk, hogy miután sikerült elérnünk a CUPS szervert és beállítani a klienseket, nézzük át alaposan a mintául szolgáló opciókat és korlátozzuk le minél jobban a hozzáférést. # Általános információk naplózása. Ha hibát keresünk, írjuk az # "info" helyett a "debug" értéket. LogLevel info # A rendszergazdák csoportja. SystemGroup wheel # A 631-es porton várjuk a kliensek kapcsolódását. Port 631 #Listen localhost:631 Listen /var/run/cups.sock # A helyi hálózaton megosztott nyomtatók mutatása. Browsing On BrowseOrder allow,deny #BrowseAllow @LOCAL BrowseAllow 192.168.1.* # Adjuk meg a helyi hálózatunkat. BrowseAddress 192.168.1.* # Adjuk meg a helyi hálózatunkat. # Alapértelmezett hitelesítési módszer, amikor szükség van rá. DefaultAuthType Basic DefaultEncryption Never # Vegyük ki ezt a sort, ha titkosítani akarunk. # A szervert a helyi hálózaton bármelyik gép elérheti. <Location /> Order allow,deny #Allow localhost Allow 192.168.1.* # Adjuk meg a helyi hálózatunkat. </Location> # A helyi hálózatról el tudjuk érni az adminisztrációs felületet. <Location /admin> #Encryption Required Order allow,deny #Allow localhost Allow 192.168.1.* # Adjuk meg a helyi hálózatunkat. </Location> # A helyi hálózatunkról el tudjuk érni a konfigurációs állományt. <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny #Allow localhost Allow 192.168.1.* # Adjuk meg a helyi hálózatunkat. </Location> # Az alapértelmezett nyomtatási és feladatkezelési házirendek. <Policy default> # A feladatokat kizárólag csak a tulajdonosaik vagy a rendszergazda # képesek elvégezni. <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs \ Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription \ Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job \ CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> # A karbantartást csak megfelelõ hitelesítés után végezhetünk. <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer \ Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs \ Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer \ Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class \ CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> AuthType Basic Require user @SYSTEM Order deny,allow </Limit> # A feladatokat csak a tulajdonosaik és a rendszergazda tudják törölni. <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> <Limit All> Order deny,allow </Limit> </Policy> A CUPS portok finomhangolása Ha a CUPS lesz az elsõdlegesen használt nyomtatási rendszer, akkor az /etc/make.conf állományban érdemes lehet még további olyan változókat beállítanunk, amelyek elõtérbe helyezik a CUPS használatát a többi nyomtatási lehetõséggel szemben. Ezek közül most szót ejtünk néhányról: WITH_CUPS=YES CUPS_OVERWRITE_BASE=YES WITHOUT_LPR=YES Elsõként a WITH_CUPS látható, amely hatására a portok telepítésük során lehetõség szerint a CUPS megoldásaira fognak építkezni. Másodikként a CUPS_OVERWRITE_BASE szerepel, amely megadásával a telepítés során a &os; alapértelmezett nyomtatási rendszere, az LPR szimbolikus linkjei és állományai cserélõdnek le, illetve megakadályozza, hogy ez visszaforduljon a rendszer egy késõbbi frissítésekor. A harmadik, a WITHOUT_LPR az LPR használatának mellõzésére utasítja az érintett portokat. + +
diff --git a/hu_HU.ISO8859-2/books/fdp-primer/book.xml b/hu_HU.ISO8859-2/books/fdp-primer/book.xml index 2a729e7d53..99be957cb7 100644 --- a/hu_HU.ISO8859-2/books/fdp-primer/book.xml +++ b/hu_HU.ISO8859-2/books/fdp-primer/book.xml @@ -1,310 +1,308 @@ %chapters; ]> A &os; Dokumentációs Projekt irányelvei kezdõknek A &os; Dokumentációs Projekt 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 DocEng $FreeBSD$ $FreeBSD$ &legalnotice; Köszönjük a részvételt a &os; Dokumentációs Projektben! Minden segítség nagyon fontos számunkra. Ebben az ismertetõben megtalálható a &os; Dokumentációs Projekt munkáját segítõ (kötelezõ és ajánlott) szoftverek és segédeszközök leírásától kezdõdõen a Dokumentációs Projekt mögött álló elképzelések bemutatásáig minden olyan hasznos információ, amelyre szükségünk lehet a munkánk megkezdéséhez. A leíráson folyamatosan dolgozunk, nem tekinthetõ még véglegesnek. A befejezetlen szakaszokat a címükben csillaggal jelöltük meg. Fordította: Páli Gábor, utolsó ellenõrzés: 2010.11.28. Bevezetés Parancssori promptok A következõ táblázatban láthatjuk a rendszer alapértelmezett promptját és a rendszeradminisztrátor promptját. A példákban ilyen elemek segítségével fogjuk jelezni, hogy milyen felhasználóként kell azokat lefuttatni. Felhasználó Prompt Egyszerû felhasználó &prompt.user; Rendszeradminisztrátor &prompt.root; Szedési szabályok Az alábbi táblázatban röviden összefoglaljuk a könyvben alkalmazott szedési irányelveket. Leírás Példa Parancsok A ls -l használatával listázzuk ki az összes állományt. Állománynevek Nyissuk meg a .login állományt. Képernyõn megjelenõ üzenetek You have mail. Felhasználói parancsok &prompt.user; su Password: Hivatkozások man oldalakra A &man.su.1; használatával váltsunk felhasználót. Felhasználói- és csoportnevek Ezt kizárólag csak a root felhasználó végezheti el. Kiemelések Ezt meg kell csinálni. Parancssori változók: helyettesítsük egy valódi névvel vagy változóval Az állomány törléséhez adjuk ki az rm állománynév parancsot. Környezeti változók A $HOME a saját felhasználói könyvtárunkat tartalmazza. Megjegyzések, tanácsok, fontosabb információk, figyelmeztetések és példák A szövegben elõfordulhatnak megjegyzések, figyelmeztetések és példák. Így jelennek meg a megjegyzések és általában ránk hatással levõ információkat tartalmaznak, amelyeket érdemes figyelembe vennünk. Így jelennek meg a gyakorta hasznos tanácsok, amelyek esetenként egy másik, gyakran egyszerûbb megoldást mutatnak be. Így jelennek meg a fontosabb információk. Általában még további elvégzendõ lépéseket adnak meg. Így jelennek meg a figyelmeztetések. Határozottan érdemes rájuk figyelni, mert ha nem követjük pontosan a bennük megadott utasításokat, akkor azzal kárt okozhatunk a rendszerünkben. Ez lehet fizikai, tehát a hardvereszközeink sérülését okozó probléma, vagy nem fizikai, tehát például egy fontos állomány akartlan törlése. Mintapélda Így jelennek meg a példák, amelyek jellemzõen valaminek a részletes bemutatását vagy egy konkrét mûvelet eredményét tartalmazzák. Köszönetnyilvánítás Szeretnénk megköszönni Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn és Christopher Maden munkáját, akik kellõ fordítottak idõt arra, hogy átolvassák a könyv kezdeti változatait, majd azt számos értékes megjegyzéssel és javaslattal gazdagítsák. &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/hu_HU.ISO8859-2/books/handbook/Makefile b/hu_HU.ISO8859-2/books/handbook/Makefile index abc2388059..ecb9d9d2ca 100644 --- a/hu_HU.ISO8859-2/books/handbook/Makefile +++ b/hu_HU.ISO8859-2/books/handbook/Makefile @@ -1,315 +1,313 @@ # # The FreeBSD Documentation Project # The FreeBSD Hungarian Documentation Project # $FreeBSD$ # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile # %SRCID% 1.113 # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES = advanced-networking/isdn-bus.eps IMAGES+= advanced-networking/isdn-twisted-pair.eps IMAGES+= advanced-networking/natd.eps IMAGES+= advanced-networking/net-routing.pic IMAGES+= advanced-networking/static-routes.pic IMAGES+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES+= mail/mutt1.scr IMAGES+= mail/mutt2.scr IMAGES+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES+= mail/pine3.scr IMAGES+= mail/pine4.scr IMAGES+= mail/pine5.scr IMAGES+= install/example-dir1.eps IMAGES+= install/example-dir2.eps IMAGES+= install/example-dir3.eps IMAGES+= install/example-dir4.eps IMAGES+= install/example-dir5.eps IMAGES+= security/ipsec-network.pic IMAGES+= security/ipsec-crypt-pkt.pic IMAGES+= security/ipsec-encap-pkt.pic IMAGES+= security/ipsec-out-pkt.pic IMAGES+= vinum/vinum-concat.pic IMAGES+= vinum/vinum-mirrored-vol.pic IMAGES+= vinum/vinum-raid10-vol.pic IMAGES+= vinum/vinum-raid5-org.pic IMAGES+= vinum/vinum-simple-vol.pic IMAGES+= vinum/vinum-striped-vol.pic IMAGES+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/hu_HU.ISO8859-2/books/handbook/chapters.ent b/hu_HU.ISO8859-2/books/handbook/chapters.ent index 3703f274c4..4a8283610e 100644 --- a/hu_HU.ISO8859-2/books/handbook/chapters.ent +++ b/hu_HU.ISO8859-2/books/handbook/chapters.ent @@ -1,75 +1,75 @@ %pgpkeys; - + "> diff --git a/it_IT.ISO8859-15/books/handbook/Makefile b/it_IT.ISO8859-15/books/handbook/Makefile index 185b307110..4ea1fc4e5c 100644 --- a/it_IT.ISO8859-15/books/handbook/Makefile +++ b/it_IT.ISO8859-15/books/handbook/Makefile @@ -1,289 +1,287 @@ # # $FreeBSD$ # Original revision: 1.108 # # Crea il Manuale di FreeBSD. # # ------------------------------------------------------------------------ # # Variabili specifiche del Manuale # # WITH_PGPKEYS La versione stampata del manuale riporta solo i # fingerprints PGP di base. Se vuoi visualizzare # le chiavi intere, allora setta questa variabile. # Questa opzione non ha effetto sui formati HTML. # # Targets specifici del Manuale # # pgpkeyring Questo target leggerà il contenuto del file # pgpkeys/chapter.xml ad estrarrà tutte le chiavi # pgp sullo standard output. Questo output può # quindi essere rediretto su un file e distribuito # come un keyring pubblico degli sviluppatori di # FreeBSD che può essere facilmente importato in # PGP/GPG. # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= ale@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png # Immagini dalla libreria per tutti i documenti IMAGES_LIB = callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lista i singoli files XML che compongono il documento. Modifiche # a qualunque di questi files obbligano la ricreazione # # Contenuto XML SRCS = book.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= audit/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Attiva tutti i capitoli. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Variabili specifiche del Manuale # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/it_IT.ISO8859-15/books/handbook/chapters.ent b/it_IT.ISO8859-15/books/handbook/chapters.ent index ddec590e01..1ce18398b1 100644 --- a/it_IT.ISO8859-15/books/handbook/chapters.ent +++ b/it_IT.ISO8859-15/books/handbook/chapters.ent @@ -1,73 +1,73 @@ %pgpkeys; - + "> diff --git a/ja_JP.eucJP/articles/contributing/article.xml b/ja_JP.eucJP/articles/contributing/article.xml index d249b475d1..627295fc20 100644 --- a/ja_JP.eucJP/articles/contributing/article.xml +++ b/ja_JP.eucJP/articles/contributing/article.xml @@ -1,597 +1,599 @@
FreeBSD ¤Ø¤Î¹×¸¥ ¤³¤Îʸ½ñ¤Ï¡¢¸Ä¿Í¤äÃÄÂΤ¬ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤¹¤ë¤¿¤á¤Î¤¤¤¯¤Ä¤«¤ÎÊýË¡¤Ë¤Ä¤¤¤ÆÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£ Jordan Hubbard ´ó¹Æ: &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ¹×¸¥ ¤¢¤Ê¤¿¤â FreeBSD ¤Î¤¿¤á¤Ë¹×¸¥¤·¤¿¤¯¤Ê¤ê¤Þ¤·¤¿¤«? ÁÇÀ²¤é¤·¤¤! FreeBSD ¤ÏÀ¸¤­»Ä¤ë¤¿¤á¤Ë¥æ¡¼¥¶¥Ù¡¼¥¹¤Î¹×¸¥¤ËÍê¤Ã¤Æ¤¤¤Þ¤¹¡£ ¤¢¤Ê¤¿¤Î¹×¸¥¤Ï´¶¼Õ¤µ¤ì¤ë¤À¤±¤Ç¤Ï¤Ê¤¯¡¢FreeBSD ¤¬À®Ä¹¤·Â³¤±¤ë¤¿¤á¤Ë¶Ë¤á¤Æ½ÅÍפʤâ¤Î¤Ê¤Î¤Ç¤¹! °ìÉô¤Î¿Í㤬ȯ¸À¤·¤Æ¤¤¤ë¤Î¤È¤ÏÈ¿ÂФˡ¢ ¹×¸¥¤ò¼õ¤±ÉÕ¤±¤Æ¤â¤é¤¦¤¿¤á¤ËÏÓÍø¤­¤Î¥×¥í¥°¥é¥Þ¡¼¤Ë¤Ê¤ë¤È¤« FreeBSD ¥³¥¢¥Á¡¼¥à¤Î¿Í¤È¿Æͧ¤Ë¤Ê¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ ¿¤¯¤Î¤½¤·¤Æ±×¡¹Áý²Ã¤¹¤ëÀ¤³¦Ãæ¤Î¹×¸¥¼Ô㤬 FreeBSD ¤ò³«È¯¤·¤Æ¤ª¤ê¡¢ Èà¤é¤ÎǯÎð¡¢ÀìÌçµ»½ÑʬÌî¤Ï¿´ô¤ËÅϤäƤ¤¤Þ¤¹¡£ ¼ê¤Î¶õ¤¤¤Æ¤¤¤ë¿Í¤è¤ê¤âÀ®¤¹¤Ù¤­»Å»ö¤ÎÊý¤¬Â¿¤¯¡¢ ¤ª¼êÅÁ¤¤¤Ï¤¤¤Ä¤Ç¤â´¿·Þ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ï¥«¡¼¥Í¥ë¤ä»¶ºß¤·¤Æ¤¤¤ë¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤è¤ê¤â¡¢ ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à´Ä¶­¤ËÂФ·¤ÆÀÕǤ¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£ »ä¤¿¤Á¤Î TODO ¥ê¥¹¥È¤Ë¤Ïʸ½ñÀ°È÷¡¢¥Ù¡¼¥¿¥Æ¥¹¥È¡¢ ¥¤¥ó¥¹¥È¡¼¥é¤äÀìÌç²½¤µ¤ì¤¿¥¿¥¤¥×¤Î¥«¡¼¥Í¥ë³«È¯¤Î¹¥Îã¤ò¾Ò²ð¤¹¤ë¤Ê¤ÉÈó¾ï¤Ë¹­¤¤ÈϰϤκî¶È¤¬¤¢¤ê¤Þ¤¹¡£ ¤¢¤Ê¤¿¤Îµ»Ç½¥ì¥Ù¥ë¤äʬÌî¤Ë´Ø¤ï¤é¤º¡¢ ¥×¥í¥¸¥§¥¯¥È¤ò»Ù±ç¤Ç¤­¤ë¤³¤È¤¬É¬¤º²¿¤«¤¢¤ê¤Þ¤¹! FreeBSD ´ØÏ¢¤Î»ö¶È¤Ë·È¤ï¤ë¾¦¶ÈÃÄÂΤ¬»ä¤¿¤Á¤Ë¥³¥ó¥¿¥¯¥È¤¹¤ë¤³¤È¤â´¿·Þ¤·¤Æ¤¤¤Þ¤¹¡£ ¤¢¤Ê¤¿¤ÎÀ½Éʤò (FreeBSD ¾å¤Ç) Æ°ºî¤µ¤»¤ë¤Ë¤Ï¡¢ ÆÃÊ̤ʳÈÄ¥¤¬É¬ÍפǤϤ¢¤ê¤Þ¤»¤ó¤«? ¤¢¤Þ¤ê¤Ë¤âÉ÷ÊѤï¤ê¤ÊÍ×µá¤Ç¤Ê¤±¤ì¤Ð¡¢ ¤½¤ì¤ò¼õ¤±Æþ¤ì¤ëÍÑ°Õ¤¬»ä¤¿¤Á¤Ë¤¢¤ë¤È¤ï¤«¤ë¤Ï¤º¤Ç¤¹¡£ ÉղòÁÃͤΤ¢¤ëÀ½ÉʤǤ¹¤«? »ä¤¿¤Á¤ËÃΤ餻¤Æ¤¯¤À¤µ¤¤! ¿ʬ»ä¤¿¤Á¤Ï¡¢ ¤¢¤ëÌ̤ˤª¤¤¤Æ¶¦Æ±¤·¤Æºî¶È¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£ ¥Õ¥ê¡¼¥½¥Õ¥È¥¦¥§¥¢³¦¤Ï¡¢ ¥½¥Õ¥È¥¦¥§¥¢¤¬¤É¤Î¤è¤¦¤Ë³«È¯¤µ¤ì¡¢ ÈÎÇ䤵¤ì¡¢Êݼ餵¤ì¤Æ¤¤¤¯¤«¤Ë¤Ä¤¤¤Æ¡¢´û¸¤Î²¾Àâ¤ËÄ©À路¤Æ¤¤¤Þ¤¹¡£ ¾¯¤Ê¤¯¤È¤â¤â¤¦°ìÅÙ¹Íθ¤·¤Æ¤ß¤ë¤³¤È¤ò»ä¤¿¤Á¤Ï¶¯¤¯¤ª¾©¤á¤·¤Þ¤¹¡£ ²¿¤¬É¬Í×? ¼¡¤Î²ÝÂê¤È¥µ¥Ö¥×¥í¥¸¥§¥¯¥È¤Î°ìÍ÷¤Ï¡¢¿§¡¹¤Ê TODO ¥ê¥¹¥È¤È¥æ¡¼¥¶¤«¤é¤ÎÍ×µá¤ò¹ç¤ï¤»¤¿¤â¤Î¤Ç¤¹¡£ ¿Ê¹ÔÃæ¤ÎÈó¥×¥í¥°¥é¥Þ¸þ¤±¤Î²ÝÂê FreeBSD ¤Ë´Ø¤ï¤Ã¤Æ¤¤¤ëÃæ¤Ë¤Ï¡¢¥×¥í¥°¥é¥Þ¤Ç¤Ï¤Ê¤¤¿Í¤¬¤¿¤¯¤µ¤ó¤¤¤Þ¤¹¡£ ¥×¥í¥¸¥§¥¯¥È¤Ë¤Ï¡¢Ê¸½ñ¤ò½ñ¤¯¿Í¡¢Web ¥Ç¥¶¥¤¥Ê¡¢¥µ¥Ý¡¼¥È¤ò¹Ô¤¦¿Í¤¬¤¤¤Þ¤¹¡£ ¹×¸¥¤¹¤ë¤Î¤ËɬÍפʤΤϡ¢»þ´Ö¤ÎÅê»ñ¤È³Ø¤Ö°ÕÍߤǤ¹¡£ Äê´üŪ¤Ë FAQ ¤È¥Ï¥ó¥É¥Ö¥Ã¥¯¤òÄ̤·¤ÆÆɤó¤Ç¤ß¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¤Þ¤º¤¤ÀâÌÀ¤ä¸Å¤¤»öÊÁ¤ä´°Á´¤Ë´Ö°ã¤Ã¤Æ¤¤¤ë¤³¤È¤Ê¤É¤¬¤¢¤ì¤Ð»äã¤Ë¶µ¤¨¤Æ¤¯¤À¤µ¤¤¡£ ¤µ¤é¤ËÎɤ¤¤Î¤Ï²æ¡¹¤Ë½¤Àµ°Æ¤òÁ÷¤ë¤³¤È¤Ç¤¹ (Docbook ¤Ï³Ø¤Ö¤Î¤Ë¤½¤ì¤Û¤ÉÆñ¤·¤¯¤¢¤ê¤Þ¤»¤ó¤¬¡¢ ¥×¥ì¥¤¥ó¥Æ¥­¥¹¥È¤Ç¤âÌäÂê¤Ï¤¢¤ê¤Þ¤»¤ó)¡£ FreeBSD ¤Îʸ½ñ¤ò¼«Ê¬¤ÎÊì¹ñ¸ì¤ËËÝÌõ¤¹¤ë¤Î¤ò¼êÅÁ¤Ã¤Æ¤¯¤À¤µ¤¤¡£ ʸ½ñ¤¬¤¹¤Ç¤Ë¸ºß¤¹¤ì¤Ð¡¢¤â¤Ã¤Èʸ½ñ¤òËÝÌõ¤·¤¿¤ê¡¢ ¤½¤ÎËÝÌõ¤¬ºÇ¿·¤Î¾õÂÖ¤«¤É¤¦¤«³Îǧ¤¹¤ë¤Î¤ò¼êÅÁ¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ ¤Þ¤º FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥ÈÆþÌç¤Î ËÝÌõ¤Ë´Ø¤¹¤ë FAQ (¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤ÎÅú¤¨) ¤ò°ìÆɤ·¤Æ¤¯¤À¤µ¤¤¡£ ¤È¤Ï¤¤¤Ã¤Æ¤â¡¢ ¤½¤¦¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¤¢¤Ê¤¿¤¬¤¹¤Ù¤Æ¤Î FreeBSD ʸ½ñ¤ÎËÝÌõ¤Ë·È¤ï¤ë¤è¤¦¤Ë¤Ê¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¤Ç¤¹¤«¤é¤Í¡£ — ¥Ü¥é¥ó¥Æ¥£¥¢¤È¤·¤Æ¡¢ ¿¾¯¤Ë´Ø¤ï¤é¤º¡¢¼«Ê¬¤¬¤ä¤í¤¦¤È»×¤¦¤À¤±¤ä¤Ã¤Æ¤¯¤À¤µ¤¤¡£ ¤¤¤Ã¤¿¤ó狼¤¬ËÝÌõ¤ò»Ï¤á¤¿¤é¡¢ ¤¿¤¯¤µ¤ó¤Î¿Í㤬¤¤¤Ä¤À¤Ã¤Æ¶¨ÎϤ·¤Æ¤¯¤ì¤Þ¤¹¤«¤é¡£ ¤â¤·ËÝÌõ¤ËÈñ¤¹»þ´Ö¤ä¥¨¥Í¥ë¥®¡¼¤¬¸Â¤é¤ì¤Æ¤¤¤ë¤Ê¤é¡¢ ¤Þ¤º¥¤¥ó¥¹¥È¡¼¥ëÊýË¡¤ÎËÝÌõ¤«¤é¤ª´ê¤¤¤·¤Þ¤¹ (ÌõÃí: ¤Ê¤¼¤Ê¤é¡¢ ¤â¤Ã¤È¤âɬÍפȤµ¤ì¤Æ¤¤¤ëʸ½ñ¤¬¤½¤ì¤À¤«¤é¤Ç¤¹)¡£ ¤¿¤Þ¤Ë (¤â¤·¤¯¤ÏÄê´üŪ¤Ë) &a.questions; ¤ä &ng.misc; ¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£ ¤³¤ì¤Ï¡¢¤¢¤Ê¤¿¤Î»ý¤Ã¤Æ¤¤¤ëÀìÌçÃ챤ò¶¦Í­¤·¤¿¤ê¡¢ 狼¤¬Êú¤¨¤Æ¤¤¤ëÌäÂê¤ò²ò·è¤¹¤ë¤Î¤ËÈó¾ï¤ËÍ­¸ú¤Ê¤â¤Î¤Ë¤Ê¤êÆÀ¤ë¤³¤È¤Ç¤¹¡£ »þ¤Ë¤Ï¤¢¤Ê¤¿¼«¿È¤Ç¿·¤·¤¤¤³¤È¤ò³Ø¤Ö¤³¤È¤µ¤¨¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤³¤ì¤é¤Î¥Õ¥©¡¼¥é¥à¤Ï¤ä¤ë¤Ù¤­¤³¤È¤Î¥¢¥¤¥Ç¥£¥¢¤Î¸»¤Ë¤â¤Ê¤êÆÀ¤ë¤Î¤Ç¤¹¡£ ¿Ê¹ÔÃæ¤Î¥×¥í¥°¥é¥Þ¸þ¤±¤Î²ÝÂê ¤³¤Î¥»¥¯¥·¥ç¥ó¤Çµó¤²¤ë²ÝÂê¤ÏËÄÂç¤Ê»þ´Ö¤ÎÅê»ñ¤Þ¤¿¤Ï FreeBSD ¤Î¥«¡¼¥Í¥ë¤Ë´Ø¤¹¤ë¿¼¤¤Ãμ±¡¢¤â¤·¤¯¤ÏξÊý¤òɬÍפȤ·¤Þ¤¹¡£ ¤·¤«¤·¤Ê¤¬¤é¡¢½µËö¥Ï¥Ã¥«¡¼ ¤ËŬ¤·¤¿Î©ÇɤʲÝÂê¤â¿ô¿¤¯¤¢¤ê¤Þ¤¹¡£ FreeBSD-CURRENT ¤ò±¿ÍѤ·¤Æ¤ª¤ê¡¢ ¾õÂÖ¤ÎÎɤ¤¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÀܳ¤¬¤¢¤ë¤Ê¤é¤Ð¡¢ current.FreeBSD.org ¤È¤¤¤¦°ìÆü¤Ë°ì²ó¥Õ¥ë¥ê¥ê¡¼¥¹¤ò¹Ô¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤¬¤¢¤ê¤Þ¤¹ — »þ¤ª¤êºÇ¿·¤Î¥ê¥ê¡¼¥¹¤ò¤½¤³¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢ ¤½¤Î²áÄø¤Ç²¿¤«ÌäÂ꤬¤¢¤ë¤Ê¤éÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ &a.bugs; ¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£ ¤½¤³¤Ç¤Ï¤¢¤Ê¤¿¤¬·úÀßŪ¤Ê¥³¥á¥ó¥È¤òÉÕ¤±¤¿¤ê¥Æ¥¹¥È¤Ç¤­¤ë¥Ñ¥Ã¥Á¤¬Ä󶡤µ¤ì¤Æ¤¤¤ë¤è¤¦¤ÊÌäÂ꤬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤â¤·¤¯¤Ï¤½¤ì¤é¤ÎÌäÂê¤Î°ì¤Ä¤ò¤¢¤Ê¤¿¼«¿È¤Ç½¤Àµ¤¹¤ë¤³¤È¤µ¤¨¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ -CURRENT ¤ËÀµ¤·¤¯Åö¤Æ¤é¤ì¤ë¤¬¤·¤Ð¤é¤¯·Ð¤Ã¤Æ¤â (Ä̾ï¤Ï 2, 3 ½µ´Ö) -STABLE ¤Ë¼è¤ê¹þ¤Þ¤ì¤Æ¤Ê¤¤¤è¤¦¤Ê¥Ð¥°¥Õ¥£¥Ã¥¯¥¹¤¬¤¢¤ë¤Ê¤é¤Ð¥³¥ß¥Ã¥¿¡¼¤ËÃúÇ«¤Ë»×¤¤½Ð¤µ¤»¤Æ¤¯¤À¤µ¤¤¡£ ´ó£¥½¥Õ¥È¥¦¥§¥¢¤ò¥½¡¼¥¹¥Ä¥ê¡¼¤Î src/contrib ¤Ë°ÜÆ°¤µ¤»¤Æ¤¯¤À¤µ¤¤¡£ src/contrib °Ê²¼¤Î¥³¡¼¥É¤¬ºÇ¿·¤Î¤â¤Î¤Ç¤¢¤ë¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ ·Ù¹ð¤ò¾ÜºÙ¤ËÊó¹ð¤¹¤ë¤è¤¦¤Ë¤·¤Æ¥½¡¼¥¹¥Ä¥ê¡¼Á´ÂÎ (¤â¤·¤¯¤Ï¤½¤Î°ìÉô) ¤ò¹½ÃÛ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ ¤½¤·¤Æ·Ù¹ð¤¬½Ð¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ports ¤Ç¡¢gets() ¤ò»È¤Ã¤Æ¤¤¤ë¤È¤« malloc.h ¤ò¥¤¥ó¥¯¥ë¡¼¥É¤·¤Æ¤¤¤ë¤Ê¤É¤È¤¤¤Ã¤¿·Ù¹ð¤¬½Ð¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¤Ê¤ó¤é¤«¤Î ports ¤Ë´Ø¤ï¤Ã¤Æ¤¤¤Æ¡¢ &os; ¤Ë¸ÇÍ­¤ÎÊѹ¹¤¬É¬ÍפǤ¢¤ì¤Ð¡¢ ¤¢¤Ê¤¿¤Î¥Ñ¥Ã¥Á¤òºî¼Ô¤Ë¥Õ¥£¡¼¥É¥Ð¥Ã¥¯¤·¤Æ¤¯¤À¤µ¤¤ (¼¡¤Î¥Ð¡¼¥¸¥ç¥ó¤¬½Ð¤¿»þ¤Ë¤¢¤Ê¤¿¤¬³Ú¤Ë¤Ê¤ê¤Þ¤¹)¡£ &posix; ¤Î¤è¤¦¤Ê¸ø¼°É¸½à¤Î¼Ì¤·¤òÆþ¼ê¤·¤Æ¤¯¤À¤µ¤¤¡£FreeBSD C99 & POSIX ɸ½àŬ¹ç¥×¥í¥¸¥§¥¯¥È¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Ë¡¢ ¤½¤¦¤¤¤Ã¤¿É¸½à¤Ø¤Î¥ê¥ó¥¯¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£ FreeBSD ¤ÎµóÆ°¤òɸ½à¤¬Í׵᤹¤ë¤â¤Î¤ÈÈæ³Ó¤·¤Æ¤¯¤À¤µ¤¤¡£µóÆ°¤¬°Û¤Ê¤ë¾ì¹ç¡¢ Æäˤ½¤ì¤¬»ÅÍͤμè¤ë¤Ë­¤é¤Ê¤«¤Ã¤¿¤êʬ¤«¤ê¤Ë¤¯¤¤ºÙ¤«¤¤Éôʬ¤Ê¤é¡¢ ¾ã³²Êó¹ð¤òÄó½Ð¤·¤Æ¤¯¤À¤µ¤¤¡£¤Ç¤­¤ì¤Ð¤É¤¦½¤Àµ¤¹¤Ù¤­¤«ÌÀ¤é¤«¤Ë¤·¤Æ¡¢ ¾ã³²Êó¹ð¤Ë¥Ñ¥Ã¥Á¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£É¸½à¤¬´Ö°ã¤Ã¤Æ¤¤¤ë¤È´¶¤¸¤¿¤é¡¢ ɸ½à²½ÃÄÂΤˤ½¤Îµ¿Ìä¤òäý¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤³¤Î°ìÍ÷¤ËÄɲ乤ë²ÝÂê¤òÄó°Æ¤·¤Æ¤¯¤À¤µ¤¤! ¾ã³²Êó¹ð (PR; Problem Report) ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¤ª¤±¤ëºî¶È ¾ã³²Êó¹ð (PR) ¥Ç¡¼¥¿¥Ù¡¼¥¹ FreeBSD ¾ã³²Êó¹ð°ìÍ÷¤Ç¤Ï¡¢¸½ºßÌäÂê¤È¤Ê¤Ã¤Æ¤¤¤ë¾ã³²Êó¹ð¤È¡¢ FreeBSD ¤ÎÍøÍѼԤˤè¤Ã¤ÆÄó½Ð¤µ¤ì¤¿²þÎɤÎÍ×˾¤¹¤Ù¤Æ¤Î°ìÍ÷¤ò¸ø³«¤·¤Æ¤¤¤Þ¤¹¡£ ¾ã³²Êó¹ð¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¤Ï¡¢ ¥×¥í¥°¥é¥Þ¸þ¤±¤ÈÈó¥×¥í¥°¥é¥Þ¸þ¤±¤Î²ÝÂ꤬¶¦¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ open ¾õÂ֤ξ㳲Êó¹ð¤ò¸«¤Æ¡¢¶½Ì£¤ò°ú¤¯¤â¤Î¤¬¤¢¤ë¤«³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£ ¤Ê¤«¤Ë¤Ï¡¢¾ã³²Êó¹ð¤ËÂФ¹¤ë½¤Àµ¤¬Å¬Àڤʤâ¤Î¤Ç¤¢¤ë¤«¤É¤¦¤«Ã±¤Ë¥Á¥§¥Ã¥¯¤¹¤ë¤À¤±¤Î¤È¤Æ¤â´Êñ¤Êºî¶È¤â¤¢¤ë¤Ç¤·¤ç¤¦¤·¡¢ ¤º¤Ã¤ÈÊ£»¨¤Ê¤â¤Î¤ä¡¢½¤Àµ¤¬´Þ¤Þ¤ì¤Æ¤¹¤é¤¤¤Ê¤¤¤â¤Î¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£ ¤Þ¤º¡¢¤Þ¤Àï¤Ë¤â³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤Ê¤¤¾ã³²Êó¹ð¤«¤éºî¶È¤ò»Ï¤á¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¡¢Ã¯¤«Â¾¤Î¿Í¤Ë³ä¤êÅö¤Æ¤¬·è¤Þ¤Ã¤Æ¤¤¤ë¤±¤ì¤É¤â¼«Ê¬¤¬ºî¶È²Äǽ¤À¡¢ ¤È¤¤¤¦¾ã³²Êó¹ð¤¬¤¢¤ì¤Ð¡¢ºî¶È¤¬¤Ç¤­¤ë¤«¤É¤¦¤«¡¢ ³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë¿Í¤ËÅŻҥ᡼¥ë¤ÇÌ䤤¹ç¤ï¤»¤Æ¤¯¤À¤µ¤¤¡£— ´û¤Ë¥Æ¥¹¥ÈÍѥѥåÁ¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤·¡¢ ¤è¤ê¿Ê¤ó¤À¹Í¤¨¤Ë´Ø¤·¤ÆµÄÏÀ¤¬¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ <quote>¥¢¥¤¥Ç¥£¥¢</quote>¥Ú¡¼¥¸¤Î¹àÌÜ &os; ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤¿¤¤¿Í¤Î¤¿¤á¤Ë ¥Ü¥é¥ó¥Æ¥£¥¢¤Î¤¿¤á¤Î &os; ¤Î¥×¥í¥¸¥§¥¯¥È¤È¥¢¥¤¥Ç¥£¥¢°ìÍ÷ ¤âÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ ¤³¤Î°ìÍ÷¤Ï¾ï¤Ë¹¹¿·¤µ¤ì³¤±¤Æ¤ª¤ê¡¢¤½¤ì¤¾¤ì¤Î¥×¥í¥¸¥§¥¯¥È¤Ë¤Ä¤¤¤Æ¡¢ ¥×¥í¥°¥é¥Þ¤ÈÈó¥×¥í¥°¥é¥ÞξÊý¤Ë¸þ¤±¤¿¹àÌܤ¬¤¢¤ê¤Þ¤¹¡£ ¹×¸¥¤Î»ÅÊý °ìÈÌŪ¤Ë¡¢¥·¥¹¥Æ¥à¤Ø¤Î¹×¸¥¤Ï¼¡¤Î 5 ¤Ä¤Î¥«¥Æ¥´¥ê¤Î 1 ¤Ä°Ê¾å¤ËʬÎव¤ì¤Þ¤¹: ¥Ð¥°Êó¹ð¤È°ìÈÌŪ¤ÊÏÀɾ °ìÈÌŪ¤Êµ»½ÑŪ´Ø¿´»ö¤Ë´Ø¤¹¤ë¥¢¥¤¥Ç¥¢¤äÄó°Æ¤Ï &a.hackers; ¤Ø¥á¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£Æ±Íͤˡ¢¤³¤Î¤è¤¦¤Ê»öÊÁ¤Ë¶½Ì£¤Î¤¢¤ë (¤½¤·¤ÆËÄÂç¤Ê¥á¡¼¥ë! ¤ËÂѤ¨¤é¤ì¤ë) ¿Í¤Ï¡¢ &a.hackers; ¤Ë»²²Ã¤¹¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£ ¤³¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ä¾¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥Ð¥°¤òȯ¸«¤·¤¿¤êÊѹ¹¤òÁ÷ÉÕ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¾ì¹ç¤Ï &man.send-pr.1; ¥×¥í¥°¥é¥à¤« ¥¦¥§¥Ö¥Ù¡¼¥¹¤Î send-pr ¤ò»ÈÍѤ·¤ÆÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥Ð¥°¥ì¥Ý¡¼¥È¤Î³Æ¹àÌܤòËä¤á¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£65KB ¤òĶ¤¨¤ë¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢ ¥ì¥Ý¡¼¥ÈÃæ¤ËľÀܥѥåÁ¤òÆþ¤ì¤Æ¤¯¤À¤µ¤Ã¤Æ·ë¹½¤Ç¤¹¡£ ¥Ñ¥Ã¥Á¤¬¥½¡¼¥¹¥Ä¥ê¡¼¤Ë¤¹¤°Å¬ÍѤǤ­¤ë¤â¤Î¤Ê¤é¤Ð¡¢ Êó¹ð¤Î³µÍ×¤Ë [PATCH] ¤È½ñ¤¤¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£ ¥Ñ¥Ã¥Á¤òÆþ¤ì¤ë¾ì¹ç¡¢¥«¥Ã¥È&¥Ú¡¼¥¹¥È¤Ï¤·¤Ê¤¤¤Ç ¤¯¤À¤µ¤¤¡£ ¥«¥Ã¥È&¥Ú¡¼¥¹¥È¤Ç¤Ï¥¿¥Ö¤¬¥¹¥Ú¡¼¥¹¤ËŸ³«¤µ¤ì¤Æ¥Ñ¥Ã¥Á¤¬»È¤¤Êª¤Ë¤Ê¤é¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ ¥Ñ¥Ã¥Á¤¬ 20KB ¤òĶ¤¨¤ë¾ì¹ç¤Ï¡¢ ¤½¤ì¤é¤ò (&man.gzip.1; ¤ä &man.bzip2.1; ¤Ç) °µ½Ì¤·¡¢ °µ½Ì¤·¤¿¥Ñ¥Ã¥Á¤ò &man.uuencode.1; ¤ò»È¤Ã¤Æ¥Ð¥°Êó¹ð¤Ë´Þ¤á¤ë¤³¤È¤â¸¡Æ¤¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥ì¥Ý¡¼¥È¤¬¥Õ¥¡¥¤¥ê¥ó¥°¤µ¤ì¤ì¤Ð¡¢ ¥Ð¥°Êó¹ð¤Î³Îǧ¤È¥È¥é¥Ã¥­¥ó¥°ÈÖ¹æ¤ò¥á¡¼¥ë¤Ç¼õ¤±¼è¤ë¤Ï¤º¤Ç¤¹¡£ ¤³¤Î¥È¥é¥Ã¥­¥ó¥°ÈÖ¹æ¤ò³Ð¤¨¤Æ¤ª¤­¡¢ÌäÂê¤Ë´Ø¤¹¤ë¾ÜºÙ¾ðÊó¤ò &a.bugfollowup; ¤Ë¥á¡¼¥ë¤ÇÁ÷¤Ã¤Æ¹¹¿·¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£¤¿¤È¤¨¤Ð "Re: kern/3377" ¤Î¤è¤¦¤Ë¡¢ ¤³¤ÎÈÖ¹æ¤ò¥µ¥Ö¥¸¥§¥¯¥È¹Ô¤Ë»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ ¤¹¤Ù¤Æ¤Î¥Ð¥°¥ì¥Ý¡¼¥È¤ÎÄɲþðÊó¤Ï¡¢ ¤³¤ÎÊýË¡¤ÇÁ÷ÉÕ¤µ¤ì¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ ¤â¤·¥¿¥¤¥à¥ê¡¼¤Ë (¤¢¤Ê¤¿¤ÎÅŻҥ᡼¥ëÀܳ·ÁÂ֤ˤâ¤è¤ê¤Þ¤¹¤¬¡¢ 3 Æü¤«¤é 1 ½µ´Ö) ³Îǧ¤ò¼õ¤±¤È¤ì¤Ê¤¤¤È¤«¡¢²¿¤é¤«¤ÎÍýͳ¤Ç &man.send-pr.1; ¥³¥Þ¥ó¥É¤¬»ÈÍѤǤ­¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢&a.bugs; ¤Ø¥á¡¼¥ë¤òÁ÷¤ê¡¢ 狼Âå¤ê¤Ë¥Ð¥°Êó¹ð¤òÁ÷ÉÕ¤·¤Æ¤â¤é¤¦¤è¤¦¤¿¤º¤Í¤Æ¤¯¤À¤µ¤¤¡£ Îɤ¤¾ã³²Êó¹ð¤ò½ñ¤¯ÊýË¡¤Ë¤Ä¤¤¤Æ¤Ï¤³¤Îʸ½ñ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ʸ½ñ¤ÎÊѹ¹ ʸ½ñ¤Ë´Ø¤¹¤ëÄó°Æ ʸ½ñ¤ÎÊѹ¹¤Ï &a.doc; ¤¬´ÆÆĤ·¤Æ¤¤¤Þ¤¹¡£ ´°Á´¤ÊÀâÌÀ¤Ï¡¢FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥ÈÆþÌç¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ¥Ð¥°Êó¹ð¤È°ìÈÌŪ¤ÊÏÀɾ ¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë &man.send-pr.1; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¡¢Äó°Æ¤äÊѹ¹ (¤É¤ó¤Êº³ºÙ¤Ê¤â¤Î¤Ç¤â´¿·Þ¤·¤Þ¤¹!) ¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£ ¸½Â¸¤Î¥½¡¼¥¹¥³¡¼¥É¤ÎÊѹ¹ FreeBSD-CURRENT ¸½Â¸¤Î¥½¡¼¥¹¥³¡¼¥É¤Ø¤ÎÄɲäޤ¿¤ÏÊѹ¹¤Ï¡¢ ¤¤¤¯¤é¤«¥È¥ê¥Ã¥­¡¼¤Ê»Å»ö¤Ç¤¢¤ê¡¢FreeBSD ³«È¯¤Î¸½¾õ¤Ë¤¢¤Ê¤¿¤¬¤É¤ì¤À¤±Ä̤¸¤Æ¤¤¤ë¤«¤ËÂ礭¤¯°Í¸¤·¤Þ¤¹¡£ FreeBSD-CURRENT ¤È¤·¤ÆÃΤé¤ì¤ë FreeBSD ¤ÎÆÃÊ̤ʷѳŪ¥ê¥ê¡¼¥¹¤¬¤¢¤ê¤Þ¤¹¡£FreeBSD-CURRENT ¤Ï³«È¯¼Ô¤ÎÀѶËŪ¤Ê³èÆ°¤ÎÊص¹¤Î¤¿¤á¤Ë¡¢ ¿§¡¹¤ÊÊýË¡¤ÇÍøÍѲÄǽ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£FreeBSD-CURRENT ¤ÎÆþ¼ê¤È»ÈÍÑÊýË¡¤Ë¤Ä¤¤¤Æ¤Î¾Ü¤·¤¤¾ðÊó¤Ë¤Ä¤¤¤Æ¤ÏFreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯ ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ ¸Å¤¤¥½¡¼¥¹¤ò¤â¤È¤Ëºî¶È¤¹¤ë¤È¡¢ »ÄÇ°¤Ê¤¬¤é¤¢¤Ê¤¿¤ÎÊѹ¹¤¬»þ¤È¤·¤Æ»þÂåÃÙ¤ì¤â¤·¤¯¤ÏÂ礭¤¯°Û¤Ê¤ë¤â¤Î¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤Æ¡¢ FreeBSD ¤ËºÆÅý¹ç¤¹¤ë¤Î¤Ïº¤Æñ¤Ë¤Ê¤ë¶²¤ì¤¬¤¢¤ê¤Þ¤¹¡£ ¥·¥¹¥Æ¥à¤Î¸½¾õ¤Ë´Ø¤¹¤ëµÄÏÀ¤¬¤ª¤³¤Ê¤ï¤ì¤Æ¤¤¤ë &a.announce; ¤È &a.current; ¤Ø»²²Ã¤¹¤ì¤Ð¡¢¤³¤Î²ÄǽÀ­¤òºÇ¾®¸Â¤Ë¤Ç¤­¤Þ¤¹¡£ ½½Ê¬¿·¤·¤¤¥½¡¼¥¹¤òÊѹ¹¤Î¥Ù¡¼¥¹¤Ë¤Ç¤­¤ë¤³¤È¤¬³Î¼Â¤Ë¤Ê¤Ã¤¿¤È²¾Äꤷ¤Æ¡¢ ¼¡¤Î¥¹¥Æ¥Ã¥×¤Ï FreeBSD ¤ÎÊݼéôÅö¼Ô¤ØÁ÷¤ëº¹Ê¬¥Õ¥¡¥¤¥ë¤ÎÀ¸À®¤Ç¤¹¡£¤³¤ì¤Ï &man.diff.1; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¤ª¤³¤Ê¤¤¤Þ¤¹¡£ º¹Ê¬¥Õ¥¡¥¤¥ë¤ÎÄó½Ð¤Ë¤ª¤¤¤Æ¹¥¤Þ¤·¤¤ &man.diff.1; ¤Î·Á¼°¤Ï¡¢ diff -u ¤Ë¤è¤êÀ¸À®¤µ¤ì¤ë unified diff ·Á¼°¤Ç¤¹¡£ diff &prompt.user; diff -u oldfile newfile ¤Þ¤¿¤Ï¡¢ &prompt.user; diff -u -r -N olddir newdir ¤Ç¡¢»ØÄꤵ¤ì¤¿¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Þ¤¿¤Ï¥Ç¥£¥ì¥¯¥È¥ê³¬ÁؤËÂФ¹¤ë unified diff ·Á¼°¤Îº¹Ê¬¤¬À¸À®¤µ¤ì¤Þ¤¹¡£ ¾Ü¤·¤¤ÀâÌÀ¤Ï &man.diff.1; ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ º¹Ê¬¥Õ¥¡¥¤¥ë (&man.patch.1; ¥³¥Þ¥ó¥É¤Ç¥Æ¥¹¥È¤Ç¤­¤Þ¤¹) ¤òºî¤Ã¤¿¤é¡¢¤½¤ì¤é¤ò FreeBSD ¤Ë´Þ¤á¤Æ¤â¤é¤¦¤è¤¦¥á¡¼¥ë¤ÇÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£¥Ð¥°Êó¹ð¤È°ìÈÌŪ¤ÊÏÀɾ ¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë &man.send-pr.1; ¥³¥Þ¥ó¥É¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£º¹Ê¬¥Õ¥¡¥¤¥ë¤À¤±¤ò &a.hackers; ¤ØÁ÷¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£¸«²á¤´¤µ¤ì¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£ ¤¢¤Ê¤¿¤ÎÄó°Æ¤ÏÂç´¿·Þ¤Ç¤¹ (¤³¤ì¤Ï¥Ü¥é¥ó¥Æ¥£¥¢¤Î¥×¥í¥¸¥§¥¯¥È¤Ç¤¹!)¡£ »ä¤¿¤Á¤Ï¿˻¤Ê¤Î¤Ç¤¹¤°¤Ë¼è¤ê¤«¤«¤ì¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢ ¤½¤ì¤Þ¤Ç PR ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë»Ä¤Ã¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£ Êó¹ð¤Î³µÍ×¤Ë [PATCH] ¤È½ñ¤¤¤Æ¤¢¤Ê¤¿¤ÎÄó°Æ¤òɽÌÀ¤·¤Æ¤¯¤À¤µ¤¤¡£ uuencode ¤¢¤Ê¤¿¤¬¤½¤¦¤·¤¿Êý¤¬¤¤¤¤¤È»×¤¦¾ì¹ç (¤¿¤È¤¨¤Ð¡¢ ¥Õ¥¡¥¤¥ë¤ÎÄɲᢺï½ü¤Þ¤¿¤Ï̾¾ÎÊѹ¹¤Ê¤É)¡¢Êѹ¹¤ò tar ¥Õ¥¡¥¤¥ë¤Ë¤Þ¤È¤á¡¢&man.uuencode.1; ¥×¥í¥°¥é¥à¤Ë¤«¤±¤Æ¤¯¤À¤µ¤¤¡£&man.shar.1; ¥¢¡¼¥«¥¤¥Ö¤â´¿·Þ¤·¤Þ¤¹¡£ ¤¿¤È¤¨¤Ð¡¢ºÆÇÛÉÛ¤ËŬÍѤµ¤ì¤ëÃøºî¸¢¤ÎÌäÂê¤Ë¼«¿®¤¬¤Ê¤¤¤È¤¤¤Ã¤¿¡¢ ¤¢¤Ê¤¿¤ÎÊѹ¹¤¬Èù̯¤ÊÀ­¼Á¤Î¤â¤Î¤Ç¤¢¤ë²ÄǽÀ­¤¬¤¢¤ì¤Ð¡¢ &man.send-pr.1; ¤ÇÄó½Ð¤¹¤ë¤è¤ê¤à¤·¤íľÀÜ &a.core; ¤ØÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£&a.core; °¸¤Î¥á¡¼¥ë¤Ï¡¢ Æü¡¹¤Î»Å»ö¤Î¤«¤Ê¤ê¤Î³ä¹ç¤ò FreeBSD ¤Ë³ä¤¤¤Æ¤¤¤ë¿Í¤¿¤Á¤Î¡¢ ¤è¤ê¾®¤µ¤Ê¥°¥ë¡¼¥×¤ËÆϤ­¤Þ¤¹¡£ ¤³¤Î¥°¥ë¡¼¥×¤â¤Þ¤¿¤È¤Æ¤âË»¤·¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¡¢ ËÜÅö¤ËɬÍפʾì¹ç¤À¤±¥³¥¢¥Á¡¼¥à¤Ë¥á¡¼¥ë¤òÁ÷¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥³¡¼¥Ç¥£¥ó¥°¥¹¥¿¥¤¥ë¤Ë´Ø¤·¤Æ &man.intro.9; ¤ª¤è¤Ó &man.style.9; ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£¥³¡¼¥É¤òÄó½Ð¤¹¤ëÁ°¤Ë¤Ï¡¢ ¾¯¤Ê¤¯¤È¤â¤³¤Î¾ðÊó¤ò°Õ¼±¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤ë¤è¤¦¤ª´ê¤¤¤·¤Þ¤¹¡£ ¿·¤¿¤Ê¥³¡¼¥É¤ä¤­¤ï¤á¤ÆÉղòÁÃͤι⤤¥Ñ¥Ã¥±¡¼¥¸ Â礭¤ÊʬÎ̤κî¶ÈÀ®²Ì¤Î¹×¸¥¤ä¡¢½ÅÍפʿ·¤·¤¤µ¡Ç½¤ò FreeBSD ¤ËÄɲ乤ë¾ì¹ç¤Ë¤Ï¡¢ÂçÄñ¡¢Êѹ¹ÅÀ¤ò tar ¥Õ¥¡¥¤¥ë¤Ë¤Þ¤È¤á¤Æ uuencode ¤·¤ÆÁ÷¤ë¤«¡¢¥¦¥§¥Ö¥µ¥¤¥È¤ä FTP ¥µ¥¤¥È¤Ø¥¢¥Ã¥×¥í¡¼¥É¤·¤Æ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ web ¤ä FTP ¥µ¥¤¥È¤¬ÍøÍѤǤ­¤Ê¤±¤ì¤Ð¡¢Å¬ÀÚ¤Ê FreeBSD ¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç狼¤½¤ÎÊѹ¹¤ò¤ª¤¯¥µ¥¤¥È¤òÄ󶡤·¤Æ¤¯¤ì¤ë¤è¤¦Íê¤ó¤Ç¤¯¤À¤µ¤¤¡£ ÂçÎ̤Υ³¡¼¥É¤ò°·¤Ã¤Æ¤¤¤ë»þ¤Ï¡¢ ¾ï¤ËÃøºî¸¢¤Ë´Ø¤¹¤ëÈù̯¤ÊÌäÂ꤬½Ð¤Æ¤­¤Þ¤¹¡£ FreeBSD ¤Ë´Þ¤á¤ë¥³¡¼¥É¤ÎÃøºî¸¢¤È¤·¤Æ¼õ¤±Æþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ï¡¢ °Ê²¼¤ÎÆó¤Ä¤Ç¤¹¡£ BSD copyright BSD ¥³¥Ô¡¼¥é¥¤¥È¡£ ¤³¤Î¥³¥Ô¡¼¥é¥¤¥È¤Ï ¸¢Íø¤ËÇû¤é¤ì¤Ê¤¤ À­³Ê¤È¾¦ÍÑ´ë¶È¤Ë¤È¤Ã¤Æ°ìÈÌŪ¤ÊÌ¥ÎϤò¤â¤Ä¤¿¤á¤ËºÇ¤â¹¥¤Þ¤ì¤Þ¤¹¡£ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ï¾¦ÍÑÍøÍѤòÁˤó¤À¤ê¤»¤º¡¢²¿¤«¤ò FreeBSD ¤ØÅê»ñ¤¹¤ëµ¤¤Ë¤Ê¤Ã¤¿¾¦¶È´Ø·¸¼Ô¤Ë¤è¤ë»²²Ã¤òÀѶËŪ¤Ë¾©Î夷¤Þ¤¹¡£ GPL GNU General Public License GNU General Public License GNU°ìÈ̸øÍ­»ÈÍѵöÂú¡¢¤Þ¤¿¤Ï GPL¡£ ¤³¤Î¥é¥¤¥»¥ó¥¹¤Ï¥³¡¼¥É¤ò¾¦ÍÑÌÜŪ¤Ë»ÈÍѤ¹¤ë¾ì¹ç¤Ë;ʬ¤ÊÅØÎϤ¬µá¤á¤é¤ì¤ë¤¿¤á¡¢ »ä¤¿¤Á¤Ë¤¢¤Þ¤êɾȽ¤¬Îɤ¤¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤·¤«¤·¡¢ »ä¤¿¤Á¤Ï´û¤Ë GPL ²¼¤Î¹âÉʼÁ¤Ê¥³¡¼¥É (¥³¥ó¥Ñ¥¤¥é¡¢¥¢¥»¥ó¥Ö¥é¡¢¥Æ¥­¥¹¥È¥Õ¥©¡¼¥Þ¥Ã¥¿Åù) ¤ÎÄ󶡤ò¼õ¤±¤Æ¤ª¤ê¡¢»ä¤¿¤Á¤Ï¸½ºß¤½¤ì¤òɬÍפȤ·¤Æ¤¤¤Þ¤¹¡£¤½¤Î¤¿¤á¡¢ ¤³¤Î¥é¥¤¥»¥ó¥¹¤Ë¤è¤ë¿·¤¿¤Ê¹×¸¥¤òµñÀ䤹¤ë¤È¤¤¤¦¤Î¤Ï¶ò¤«¤Ê¤³¤È¤Ç¤·¤ç¤¦¡£GPL ²¼¤Î¥³¡¼¥É¤Ï¥½¡¼¥¹¥Ä¥ê¡¼¤ÎÊ̤ÎÉôʬ¡¢¸½ºß¤Î¤È¤³¤í /sys/gnu ¤« /usr/src/gnu ¤ËÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£ ¤½¤Î¤¿¤á¡¢GPL ¤¬ÌäÂê¤È¤Ê¤ë¤è¤¦¤Ê¿Í¤Ï¡¢ ï¤Ç¤â´Êñ¤Ë¤½¤ì¤È¤ï¤«¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ ¤³¤ì°Ê³°¤Î¥¿¥¤¥×¤ÎÃøºî¸¢¤Ë¤è¤ë´ó£¤Ï¡¢FreeBSD ¤Ø´Þ¤á¤ë¤³¤È¤ò¹Íθ¤¹¤ëÁ°¤ËÃí°Õ¿¼¤¤¥ì¥Ó¥å¡¼¤ò¼õ¤±¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ Æä˸ÂÄêŪ¤Ê¾¦ÍѤÎÃøºî¸¢¤¬Å¬ÍѤµ¤ì¤ë´ó£¤Ï°ìÈ̤˵ñÈݤµ¤ì¤Þ¤¹¡£¤·¤«¤·¡¢ ºî¼Ô¤¬Æȼ«¤Î·ÐÏ©¤Ç¤½¤Î¤è¤¦¤ÊÊѹ¹¤òÇÛÉÛ¤¹¤ë¤³¤È¤Ï¾ï¤Ë¾©Î夵¤ì¤Æ¤¤¤Þ¤¹¡£ ¤¢¤Ê¤¿¤ÎºîÉÊ¤Ë BSD ¥¹¥¿¥¤¥ë ¤ÎÃøºî¸¢¤òÉÕ¤±¤ë¤Ë¤Ï¡¢ Êݸ¤¿¤¤¥½¡¼¥¹¥³¡¼¥É¥Õ¥¡¥¤¥ë¤¹¤Ù¤Æ¤Î°ìÈֺǽé¤Ë°Ê²¼¤Î¥Æ¥­¥¹¥È¤òÆþ¤ì¤Æ¡¢ %% ¤Î´Ö¤òŬÀڤʾðÊó¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£ Copyright (c) %%ŬÀÚ¤Êǯ%% %%¤¢¤Ê¤¿¤Î̾Á°%%, %%¤¢¤Ê¤¿¤Î½£%% %%͹ÊØÈÖ¹æ%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%¤¢¤Ê¤¿¤Î̾Á°%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%¤¢¤Ê¤¿¤Î̾Á°%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $&os;$ Êص¹¤ò¤Ï¤«¤ë¤¿¤á¡¢ ¤³¤Î¥Æ¥­¥¹¥È¤Î¥³¥Ô¡¼¤Ï¼¡¤Î¾ì½ê¤ËÃÖ¤¤¤Æ¤¢¤ê¤Þ¤¹¡£ /usr/share/examples/etc/bsd-style-copyright ÌõÃí °Ê²¼¤Ï¿ÀÅÄÉÒ¹­»á¤è¤ê´ó£¤µ¤ì¤¿ bsd-style-copyright ¤ÎÆüËܸìÌõ¤Ç¤¹¡£ ¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Ë´Þ¤á¤ë¤â¤Î¤Ï¸¶Ê¸¤ÎÊý¤Ç¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤´ÍøÍѤ¯¤À¤µ¤¤¡£ ¤Þ¤¿¡¢¸¶Ê¸¤È¤Î´Ö¤Ë¼ñ»Ý¤Îº¹°Û¤¬À¸¤¸¤¿¾ì¹ç¡¢ ¸¶Ê¸¤ÎÆâÍƤ¬ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Î°Õ»×¤Ç¤¢¤ë¤â¤Î¤È¤·¤Þ¤¹¡£ Copyright (C) [ǯ] [¤¢¤Ê¤¿¤Î̾Á°] All rights reserved. ¥½¡¼¥¹¤È¥Ð¥¤¥Ê¥ê·Á¼°¤ÎºÆÇÛÉÛ¤ª¤è¤Ó»ÈÍѤϡ¢Êѹ¹¤Î̵ͭ¤Ë¤«¤«¤ï¤é¤º°Ê²¼¤Î ¾ò·ï¤òËþ¤¿¤¹¾ì¹ç¤Ë¸Â¤êµö²Ä¤µ¤ì¤ë: 1. ¥½¡¼¥¹¥³¡¼¥É¤ÎºÆÇÛÉۤϡ¢¾åµ­¤ÎÃøºî¸¢É½¼¨¡¦¤³¤Î¾ò·ï¤Î¥ê¥¹¥È¡¦²¼µ­¤Î ÈÝǧÀ¼ÌÀʸ¤òÊÝ»ý¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£ 2. ¥Ð¥¤¥Ê¥ê·Á¼°¤ÎºÆÇÛÉۤϾ嵭¤ÎÃøºî¸¢É½¼¨¡¦¤³¤Î¾ò·ï¤Î¥ê¥¹¥È¡¦²¼µ­¤Î ÈÝǧÀ¼ÌÀʸ¤ò¡¢ÇÛÉÛʪ¤È¶¦¤ËÄ󶡤µ¤ì¤ëʸ½ñ¤ª¤è¤Ó/¤Þ¤¿¤Ï¾¤Î»ñÎÁ¤ÎÃæ¤Ë ´Þ¤á¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£ (ÌõÃí:¤³¤³¤«¤é¡ÖÈÝǧÀ¼ÌÀʸ¡×¤Ç¤¹) ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Ï[¤¢¤Ê¤¿¤Î̾Á°]¤ª¤è¤Ó¹×¸¥¼Ô¤Ë¤è¤Ã¤Æ ``¤¢¤ë¤¬¤Þ¤Þ¤Î¾õÂÖ'' ¤ÇÄ󶡤µ¤ì¡¢¾¦ÉÊÀ­¤ÈÆÃÄê¤ÎÌÜŪ¤ËÂФ¹¤ëŬ¹çÀ­¤Ë¤Ä¤¤¤Æ¤Î°ÅÌÛ¤ÎÊݾڤËα¤Þ ¤é¤º¡¢¤¤¤«¤Ê¤ëÌÀ¼¨¤ª¤è¤Ó°ÅÌÛ¤ÎÊݾڤòǧ¤á¤Ê¤¤¡£[¤¢¤Ê¤¿¤Î̾Á°]¤ª¤è¤Ó¹×¸¥ ¼Ô¤Ï¡¢¤¢¤é¤æ¤ëľÀÜŪ¡¦´ÖÀÜŪ¡¦¶öȯŪ¡¦ÆüìŪ¡¦Åµ·¿Åª¡¦É¬Á³Åª¤Ê»³² (Âå ÂØÀ½Éʤޤ¿¤ÏÂåÂØ¥µ¡¼¥Ó¥¹¤Î³ÍÆÀÈñ; ¸úÍÑ¡¦¥Ç¡¼¥¿¡¦Íø±×¤ÎÁÓ¼º; ¤Þ¤¿¤Ï¶È̳ ÃæÃǤò´Þ¤ß¡¢¤Þ¤¿¤½¤ì¤À¤±¤Ëα¤Þ¤é¤Ê¤¤Â»³²) ¤ËÂФ·¤Æ¡¢¤¿¤È¤¨¤É¤Î¤è¤¦¤Ë¤· ¤ÆÀ¸¤¸¤¿¤È¤·¤Æ¤â¡¢¤½¤·¤Æ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Î»ÈÍѤˤè¤Ã¤Æ¤É¤Î¤è¤¦¤Ë¤Ç¤¢¤ì À¸¤¸¤ë¡¢·ÀÌó¾å¤Ç¤¢¤í¤¦¤È¡¢¸·Ì©¤ÊÀÕǤÆâ¤Ç¤¢¤í¤¦¤È¡¢¤¢¤ë¤¤¤ÏÉÔÀµ¹Ô°Ù (²á ¼º¤ä¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤ò´Þ¤à) ¤Ë¤ª¤±¤ë¾ì¹ç¤Ç¤¢¤í¤¦¤È¤â¡¢¤¤¤«¤Ê¤ëÀÕǤÏÀ¾å¤â¡¢ ¤¿¤È¤¨¤½¤Î¤è¤¦¤Ê»³²¤Î²ÄǽÀ­¤¬Í½¸«¤µ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢°ìÀÚ¤ÎÀÕǤ¤ò»ý¤¿ ¤Ê¤¤¡£ ËÝÌõ: ¿ÀÅÄÉÒ¹­ ¸æ¶¨ÎÏ (¸Þ½½²»½ç¡¦·É¾Îά): ÃÓÅĸ¦Æó¡¢ÆâÀî ´î¾Ï¡¢Æ£Â¼ ±Ñ¼£¡¢¤à¤é¤¿¤·¤å¤¦¤¤¤Á¤í¤¦ ÌÝÌî ²í°ì¡¢²£ÅÄ¡÷±§Å﵆ ¶âÁ¬¡¢¥Ï¡¼¥É¥¦¥§¥¢¤Þ¤¿¤Ï¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥¢¥¯¥»¥¹ »ä¤¿¤Á¤Ï FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ÎÌÜŪ¤ò¿Ê¤á¤ë¤¿¤á¤Î´óÉÕ¤ò¾ï¤Ë´î¤ó¤Ç¼õ¤±Æþ¤ì¤Æ¤¤¤Þ¤¹¡£ »ä¤¿¤Á¤Î¤è¤¦¤Ê¥Ü¥é¥ó¥Æ¥£¥¢³èÆ°¤Ç¤Ï¡¢ ¤Á¤ç¤Ã¤È¤·¤¿¤³¤È¤¬Â礤¤ËÌòΩ¤Ä¤Î¤Ç¤¹! ¤Þ¤¿°ìÈÌŪ¤Ë¡¢»ä¤¿¤Á¤Ï¼«Á°¤Ç¼þÊÕµ¡´ï¤òÇ㤦»ñ¶â¤¬ÉÔ­¤·¤Æ¤¤¤ë¤¿¤á¡¢ ¼þÊÕµ¡´ï¤Î¥µ¥Ý¡¼¥È¤ò½¼¼Â¤µ¤»¤ë¤Î¤Ë¥Ï¡¼¥É¥¦¥§¥¢¤Î´óÉդϤȤƤâ½ÅÍפǤ¹¡£ <anchor id="donations"/>»ñ¶â¤Î´óÉÕ The FreeBSD Foundation ¤Ï¡¢ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ÎÌÜɸ¤ò¿ä¿Ê¤¹¤ë¤¿¤á¤ËÀßΩ¤µ¤ì¤¿¡¢ Èó±ÄÍø¤Î¡¢ÀǶâ¤òÌȽü¤µ¤ì¤¿ºâÃĤǤ¹¡£501(c)3 ¤ËŬ¹ç¤¹¤ëÃÄÂΤȤ·¤Æ¡¢ Foundation ¤Ï¥¢¥á¥ê¥«¹ç½°¹ñϢˮ½êÆÀÀǤʤé¤Ó¤Ë ¥³¥í¥é¥É½£½êÆÀÀǤò°ìÈ̤ËÌȽü¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ÌÈÀÇÃÄÂΤؤδóÉդϡ¢ ¿¤¯¤Î¾ì¹çϢˮÀ¯ÉܤβÝÀÇÂоݽêÆÀ¤«¤é¹µ½ü¤Ç¤­¤Þ¤¹¡£ ´óÉդϾ®ÀÚ¼ê¤Ç°Ê²¼¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
¤Þ¤¿¡¢´óÉդμõ¤±ÉÕ¤±¤ò PayPal ¤òÄ̤¸¤Æ web ·Ðͳ¤Ç¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ ´óÉÕ¤ò¤¹¤ë¤Ë¤Ï¡¢The FreeBSD Foundation ¤Î web ¥µ¥¤¥È¤ò¤¼¤Ò¤´Í÷¤¯¤À¤µ¤¤¡£ The FreeBSD Foundation ¤Ë´Ø¤¹¤ë¤³¤ì°Ê¾å¤Î¾ðÊó¤Ï The FreeBSD Foundation -- an Introduction ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£ Foundation ¤Ø¤Î email ¤Ç¤ÎÏ¢Íí¤Ï bod@FreeBSDFoundation.org ¤Ø¤É¤¦¤¾¡£ ¥Ï¡¼¥É¥¦¥§¥¢¤Î´ó£ ´ó£ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ÏŬÀڤʻȤ¤Æ»¤Î¤¢¤ë¥Ï¡¼¥É¥¦¥§¥¢¤Î´óÉÕ¤ò´î¤ó¤Ç¼õ¤±Æþ¤ì¤Æ¤¤¤Þ¤¹¡£ ¥Ï¡¼¥É¥¦¥§¥¢¤ò´ó£¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Ê¤é¡¢ ´ó£ÉʼõÉÕ»ö̳¶É¤ËÏ¢Íí¤·¤Æ¤¯¤À¤µ¤¤¡£ + +
diff --git a/ja_JP.eucJP/articles/contributors/article.xml b/ja_JP.eucJP/articles/contributors/article.xml index 9ae2885a74..91c47b335b 100644 --- a/ja_JP.eucJP/articles/contributors/article.xml +++ b/ja_JP.eucJP/articles/contributors/article.xml @@ -1,431 +1,433 @@ %contrib.ent; ]>
FreeBSD ¤Ø¤Î¹×¸¥¼Ô &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ¤³¤Îʸ½ñ¤Ï FreeBSD ¤Ë¹×¸¥¤·¤¿¸Ä¿Í¤äÁÈ¿¥¤òÎóµ­¤·¤¿¤â¤Î¤Ç¤¹¡£ ´ó£¼Ô¥®¥ã¥é¥ê¡¼ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ï¼¡¤Î´ó£¼Ô¤Ë²¸µÁ¤ò¼õ¤±¤Æ¤ª¤ê¡¢ ¤³¤³¤Ë¸øɽ¤·¤Æ´¶¼Õ¤Î°Õ¤òɽ¤·¤¿¤¤¤È»×¤¤¤Þ¤¹¡£ ¥»¥ó¥È¥é¥ë¥µ¡¼¥Ð¥×¥í¥¸¥§¥¯¥È¤Ø¤Î´ó£¼Ô: ¼¡¤Ë¤¢¤²¤ë¸Ä¿Í¤ª¤è¤Ó´ë¶È¤«¤é¤Ï¡¢ ¿·¤·¤¤¥»¥ó¥È¥é¥ë¥µ¡¼¥Ð¥Þ¥·¥ó¤Î¤¿¤á¤ÎÉôÉʤδó£¤ò夭¤Þ¤·¤¿¡£ ¤³¤ì¤Ë¤è¤ê¡¢freefall.FreeBSD.org ¤ò¥ê¥×¥ì¡¼¥¹¤·¤Æ¡¢¿·¤·¤¤ FreeBSD ¥µ¡¼¥Ð¥Þ¥·¥ó¤ò ¹½ÃÛ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤·¤¿¡£ &a.mbarkah.email; ¤ÈÈà¤Î½ê°¤¹¤ë Hemisphere Online ¤Ï¡¢Pentium Pro (P6) 200MHz CPU ¤ò´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ ASA Computers ¤Ï¡¢Tyan 1662 ¥Þ¥¶¡¼¥Ü¡¼¥É ¤ò´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ ViaNet Communications ¤Î Joe McGuckin joe@via.net ¤Ï¡¢Kingston ¥¤¡¼¥µ¥Í¥Ã¥È¥³¥ó¥È¥í¡¼¥é ¤ò´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Jack O'Neill jack@diamond.xtalwind.net ¤Ï¡¢ NCR 53C875 SCSI ¥³¥ó¥È¥í¡¼¥é¥«¡¼¥É ¤ò´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Alameda Networks ¤Î Ulf Zimmermann ulf@Alameda.net ¤Ï¡¢128 MB ¤Î¥á¥â¥ê¡¢¤½¤·¤Æ 4 GB ¤Î¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤È¶©ÂÎ ¤ò´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ ľÀÜŪ¤Ê»ñ¶âÄó¶¡ ¼¡¤Ë¤¢¤²¤ë¸Ä¿Í¤ª¤è¤Ó´ë¶È¤«¤é¤Ï FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ËÂФ¹¤ëľÀÜŪ¤Ê »ñ¶âÄ󶡤ò夤¤Æ¤¤¤Þ¤¹¡£ Annelise Anderson ANDRSN@HOOVER.STANFORD.EDU &a.dillon.email; Blue Mountain Arts Epilogue Technology Corporation &a.sef.email; Global Technology Associates, Inc Don Scott Wilde Gianmarco Giovannelli gmarco@masternet.it Josef C. Grosch joeg@truenorth.org Robert T. Morris &a.chuckr.email; Imaginary Landscape, LLC. ¤Î Kenneth P. Stox ken@stox.sa.enteract.com Dmitry S. Kohmanyuk dk@dog.farm.org ÆüËܤΠLaser5 ¤Ï¡¢¤µ¤Þ¤¶¤Þ¤Ê¼ïÎà¤Î FreeBSD CD ¤ÎÈÎÇäÍø±×¤Î°ìÉô¤ò ´óÉÕ¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£ Éù½ÐÈÇ ¤Ï¡¢¤Ï¤¸¤á¤Æ¤Î FreeBSD ¤ÎÇä¤ê¾å¤²¤Î°ìÉô¤ò FreeBSD ¥×¥í¥¸¥§¥¯¥ÈµÚ¤Ó XFree86 ¥×¥í¥¸¥§¥¯¥È¤Ø´óÉÕ¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£ ¥¢¥¹¥­¡¼ ¤Ï FreeBSD ´ØÏ¢¤Î½ñÀÒ¤ÎÇä¤ê¾å¤²¤Î°ìÉô¤ò FreeBSD ¥×¥í¥¸¥§¥¯¥È¤ª¤è¤Ó FreeBSD ͧ¤Î²ñ¤Ø´óÉÕ¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£ ²£²ÏÅŵ¡³ô¼°²ñ¼Ò ¤«¤é¤Ï FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ø¿Âç¤Ê´óÉÕ¤ò¤¤¤¿¤À¤­¤Þ¤·¤¿¡£ BuffNET Pacific Solutions Siemens AG, Andre Albsmeier andre.albsmeier@mchp.siemens.de Chris Silva ras@interaccess.com ¥Ï¡¼¥É¥¦¥§¥¢¤Î´ó£¼Ô ¼¡¤Ë¤¢¤²¤ë¸Ä¿Í¤ª¤è¤Ó´ë¶È¤«¤é¤Ï¡¢ ¥Æ¥¹¥È¤ä¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Î³«È¯ / ¥µ¥Ý¡¼¥È ¤Î¤¿¤á¤Î¥Ï¡¼¥É¥¦¥§¥¢¤Î´ó£¤ò夤¤Æ¤¤¤Þ¤¹¡£ BSDi ¤Ï¡¢ ¥Í¥Ã¥È¥ï¡¼¥¯¤Ø¤Î¥¢¥¯¥»¥¹¤ª¤è¤Ó ¾¤Î¥Ï¡¼¥É¥¦¥§¥¢¥ê¥½¡¼¥¹¤Î´ó£¤Ï¤¤¤¦¤Þ¤Ç¤â¤Ê¤¯¡¢ ³«È¯¤Ë»È¤¦¤¿¤á¤Î Pentium P5-90 ¤È 486/DX2-66 EISA/VL ¤Î¥·¥¹¥Æ¥à¿ôÂæ¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Compaq ¤«¤é¡¢¤µ¤Þ¤¶¤Þ¤Ê¼ïÎà¤Î Alpha ¥·¥¹¥Æ¥à¤ò FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë´ó£¤·¤Æ¤¤¤¿¤À¤­¤Þ¤·¤¿¡£ ¤³¤ÎË­É٤ʴó£ÉʤÎÃæ¤Ë¤Ï AlphaStation DS10 4 Âæ¡¢AlphaServer DS20 1 Âæ¡¢ AlphaServer 2100 ¿ôÂæ¡¢AlphaServer 4100 1 Âæ¡¢ 500Mhz ¤Î CPU ¤òÅëºÜ¤·¤¿¥Ñ¡¼¥½¥Ê¥ë¥ï¡¼¥¯¥¹¥Æ¡¼¥·¥ç¥ó 8 Âæ¡¢ 433Mhz ¤Î CPU ¤òÅëºÜ¤·¤¿¥Ñ¡¼¥½¥Ê¥ë¥ï¡¼¥¯¥¹¥Æ¡¼¥·¥ç¥ó 4 Â椬´Þ¤Þ¤ì¡¢ ¤½¤ì°Ê³°¤Ë¤â¿ô¡¹¤Î»Ù±ç¤ò¤¤¤¿¤À¤­¤Þ¤·¤¿¡£ ¾åµ­¤Î¥Þ¥·¥ó¤Ï¡¢FreeBSD/Alpha ¤Ë¤ª¤±¤ë ¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°ºî¶È¡¢package ¹½ÃÛ¡¢SMP ¤Î³«È¯¡¢ ¤½¤·¤Æ°ìÈÌŪ¤Ê³«È¯¤ËÍøÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£ TRW Financial Sysytems ¼Ò¤Ï¡¢PC 130 Âæ¡¢68 GB ¤Î¥Õ¥¡¥¤¥ë¥µ¡¼¥Ð 3 Âæ¡¢12 ¤Î¥¤¡¼¥µ¥Í¥Ã¥È¡¢ ¥Ç¥£¥¹¥¯¥ì¥¹¥³¡¼¥É¤Î¥Ç¥Ð¥Ã¥°¤ò¤ª¤³¤Ê¤¦¤¿¤á¤Î ¥ë¡¼¥¿ 2ÂæµÚ¤Ó ATM ¥¹¥¤¥Ã¥Á¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£¤Þ¤¿¡¢ Èà¤é¤Ï 2¡¢3 ¿Í¤Î FreeBSD ¥Ï¥Ã¥«¡¼¤ò¸Û¤Ã¤Æ¡¢FreeBSD ¤ËÀìÇ°¤µ¤»¤Æ¤¯¤À¤µ¤Ã¤Æ¤ª¤ê¤Þ¤¹¡£ ¤¢¤ê¤¬¤È¤¦¤´¤¶¤¤¤Þ¤¹! Dermot McDonnell ¤Ï¡¢Åì¼Ç XM3401B CD-ROM ¥É¥é¥¤¥Ö¤ò ´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£¤½¤Î CD-ROM ¥É¥é¥¤¥Ö¤Ï¸½ºß freefall ¤Ç»ÈÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£ Chuck Robey chuckr@glue.umd.edu ¤Ï¡¢¼Â¸³ÍѤΥեí¥Ã¥Ô¡¼¥Æ¡¼¥×¥¹¥È¥ê¡¼¥Þ¤ò ´óÉÕ¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Larry Altneu larry@ALR.COM ¤È &a.wilko.email;¤Ï¡¢wt ¥É¥é¥¤¥Ð¤ò²þÎɤ¹¤ë¤¿¤á¤Ë Wangtek ¤È Archive ¤Î QIC-02 ¥Æ¡¼¥×¥É¥é¥¤¥Ö¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Ernst Winter ewinter@lobo.muc.de ¤Ï¡¢ ¤³¤Î¥×¥í¥¸¥§¥¯¥È¤Ø 2.88 MB ¤Î¥Õ¥í¥Ã¥Ô¡¼¥É¥é¥¤¥Ö¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ ¤¦¤Þ¤¯¤¤¤±¤Ð¡¢ ¤³¤ì¤Ç¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ð¤ò½ñ¤­Ä¾¤¹¤¿¤á¤Î ¥×¥ì¥Ã¥·¥ã¡¼¤¬Áý¤¨¤ë¤Ç¤·¤ç¤¦¡£ Tekram Technologies ¤Ï NCR ¥É¥é¥¤¥Ð¤ä AMD ¥É¥é¥¤¥Ð¤È¼«¼Ò¤Î¥«¡¼¥É¤ÎµÕ¹Ô¥Æ¥¹¥È¤Î¤¿¤á FAST/ULTRA SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿ DC-390¡¢DC-390U¡¢DC-390F ¤ò ³Æ£±ËçÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£¤Þ¤¿¡¢¥Õ¥ê¡¼¤Ê OS ¤Î¤¿¤á¤Î¥É¥é¥¤¥Ð¤Î ¥½¡¼¥¹¤ò¼«¼Ò¤Î FTP ¥µ¡¼¥Ð ¤Ç¸ø³«¤µ¤ì¤Æ¤¤¤ë¤³¤È¤â¾Î»¿¤ËÃͤ¹¤ë¤Ç¤·¤ç¤¦¡£ Larry M. Augustin ¤Ï Symbios Sym8751S SCSI ¥«¡¼¥É¤ò´ó£¤·¤Æ¤¯¤À¤µ¤Ã¤¿¤À¤±¤Ç¤Ê¤¯¡¢Ultra-2 ¤ä LVD ¤ò¥µ¥Ý¡¼¥È¤¹¤ë¼¡´ü¥Á¥Ã¥× Sym53c895 ¤Î¤â¤Î¤ò´Þ¤à ¥Ç¡¼¥¿¥Ö¥Ã¥¯¤Î¥»¥Ã¥È¤È¡¢ºÇ¿·¤Î Symbios SCSI ¥Á¥Ã¥×¤¬»ý¤ÄÀè¿ÊŪµ¡Ç½¤ò°ÂÁ´¤Ë»È¤¦ÊýË¡¤Ë¤Ä¤¤¤Æ½ñ¤«¤ì¤¿ ºÇ¿·¤Î¥×¥í¥°¥é¥ß¥ó¥°¥Þ¥Ë¥å¥¢¥ë¤â´ó£¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ ËÜÅö¤Ë¤¢¤ê¤¬¤È¤¦¤´¤¶¤¤¤Þ¤¹! &a.kuku.email; ¤Ï¡¢IDE CD-ROM ¥É¥é¥¤¥Ð³«È¯ÍѤΠFX120 12 ÇÜ® Mitsumi CD-ROM ¥É¥é¥¤¥Ö¤òÄ󶡤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£ Mike Tancsa mike@sentex.ca ¤Ï¡¢ ³ÈÄ¥¥«¡¼¥É¤ÎÂбþ¤È¡¢netatm ATM ¥¹¥¿¥Ã¥¯¤Î³«È¯ºî¶È¤Î¤¿¤á¤Ë 4 Ëç¤Î ATM PCI ¥«¡¼¥É¤ò´ó£¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£ ÆÃÉ®¤¹¤Ù¤­´ó£¼Ô BSDi (¤«¤Ä¤Æ¤Î Walnut Creek CDROM) ¤Ï¡¢ ¸À¤¤É½¤»¤Ê¤¤¤Û¤É¿¤¯¤Î´óÉÕ¤ò¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿ (¾ÜºÙ¤Ï FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î ¡ÖFreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë¤Ä¤¤¤Æ¡×¤Î¾Ï¤ò¤´Í÷¤¯¤À¤µ¤¤)¡£ Æäˡ¢»ä¤¿¤Á¤Î¤â¤È¤â¤È¤Î¥×¥é¥¤¥Þ¥ê³«È¯¥Þ¥·¥ó¤Ç¤¢¤ë freefall.FreeBSD.org¡¢ ¥Æ¥¹¥È¤ª¤è¤Ó¥Ó¥ë¥É¥Þ¥·¥ó¤Ç¤¢¤ë thud.FreeBSD.org ¤Ç»ÈÍѤ·¤Æ¤¤¤ë¥Ï¡¼¥É¥¦¥§¥¢¤ËÂФ·´¶¼Õ¤·¤¿¤¤¤È»×¤¤¤Þ¤¹¡£ ¤Þ¤¿Èà¤é¤Ë¤Ï¡¢¿ôǯ¤Ë¤ï¤¿¤ë¿§¡¹¤Ê¹×¸¥¼Ô¤Ø¤Î»ñ¶âÄ󶡤䡢 ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ø¤Î T1 ¥³¥Í¥¯¥·¥ç¥ó¤Î̵À©¸Â»ÈÍѤòÄ󶡤·¤Æ 夤¤¿²¸µÁ¤¬¤¢¤ê¤Þ¤¹¡£ interface business GmbH, Dresden ¤Ï¡¢&a.joerg.email; ¤òº¬µ¤¤è¤¯¥µ¥Ý¡¼¥È¤·¤Æ¤¯¤À¤µ¤¤¤Þ¤·¤¿¡£Èà¤ÏËÜ¿¦¤è¤ê FreeBSD ¤Î»Å»ö¤ò¹¥¤ß¤¬¤Á¤Ç¤¢¤ê¡¢Èà¸Ä¿Í¤ÎÀܳ¤¬¤¢¤Þ¤ê¤Ë ÃÙ¤¯¤Ê¤Ã¤¿¤êÅÓÀڤ줿¤ê¤·¤Æ»Å»ö¤Ë¤Ê¤é¤Ê¤¤»þ¤Ïɬ¤º interface business ¤Î (Èó¾ï¤Ë¹â²Á¤Ê) EUnet ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÀܳ¤ËÍê¤Ã¤¿¤â¤Î¤Ç¤¹¡Ä¡£ Berkeley Software Design, Inc. ¤Ï¡¢Æ±¼Ò¤Î DOS ¥¨¥ß¥å¥ì¡¼¥¿¤Î¥³¡¼¥É¤ò BSD ¥³¥ß¥å¥Ë¥Æ¥£Á´ÂΤËÂФ·¤ÆÄ󶡤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£¤³¤Î¥³¡¼¥É¤Ï¡¢ doscmd ¥³¥Þ¥ó¥É¤ËÍøÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£ FreeBSD ¤Î³«È¯¼Ô¤¿¤Á (CVS ¤Î) commit¤¹¤ë¸¢Íø¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢FreeBSD ¤Î¥½¡¼¥¹¥Ä¥ê¡¼¤Ë¤Ä¤¤¤Æ ºî¶È¤ò¤ª¤³¤Ê¤Ã¤Æ¤¤¤ë¿Í¡¹¤¬¤¤¤Þ¤¹¡£ ¤¹¤Ù¤Æ¤Î¥³¥¢¥Á¡¼¥à¤Î¥á¥ó¥Ð¤Ï¤Þ¤¿³«È¯¼Ô¤Ç¤â¤¢¤ê¤Þ¤¹¡£ (À«¤Ç¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç) &contrib.committers; ¥³¥¢¥Á¡¼¥à¤Î´¶ÈÀ¸ ¥³¥¢¥Á¡¼¥à (core team) ¼¡¤Ë¤¢¤²¤ë¿Í¡¹¤Ï () ¤Çµ­¤·¤¿´ü´Ö¡¢FreeBSD ¥³¥¢¥Á¡¼¥à¤Î¥á¥ó¥Ð¡¼¤Ç¤·¤¿¡£FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë¤ª¤±¤ëÈà¤é¤ÎÅØÎϤ˴¶¼Õ¤Î°Õ¤òɽ¤·¤Þ¤¹¡£ ¤À¤¤¤¿¤¤¤ÎµÕǯÂå½ç &contrib.corealumni; ³«È¯¥Á¡¼¥à¤Î´¶ÈÀ¸ ³«È¯¥Á¡¼¥à (development team) ¼¡¤Ë¤¢¤²¤ë¤Î¤Ï¡¢¤«¤Ä¤Æ FreeBSD ³«È¯¥Á¡¼¥à¤Î°ì°÷¤À¤Ã¤¿¿Í¡¹¤Ç¤¹¡£ FreeBSD ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤Æ¤¯¤À¤µ¤Ã¤¿Èà¤é¤Ë´¶¼Õ¤·¤Þ¤¹¡£ ¤Û¤ÜµÕǯÂå½ç¤Ë: &contrib.develalumni; BSD ÇÉÀ¸¥½¥Õ¥È¥¦¥§¥¢¤Ø¤Î¹×¸¥¼Ô ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤ÏºÇ½é¤Ï William F. Jolitz ¤Î 386BSD release 0.1 ¤«¤éÇÉÀ¸¤·¤Þ¤·¤¿¤¬¡¢¥ª¥ê¥¸¥Ê¥ë¤Î 386BSD ¤Ë¸ÇÍ­¤Î¥³¡¼¥É¤Ï¤Û¤È¤ó¤É»Ä¤Ã¤Æ¤¤¤Þ¤»¤ó¡£ ¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Ï´ðËÜŪ¤Ë¤Ï¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø ¥Ð¡¼¥¯¥ì¥¤¹»¤Î Computer Science Research Group (CSRG) ¤È¤½¤Î¶¦Æ±¸¦µæ¼Ô ¤¿¤Á¤Ë¤è¤ë 4.4BSD-Lite ¥ê¥ê¡¼¥¹¤«¤éºÆ¼ÂÁõ¤µ¤ì¤Þ¤·¤¿¡£ ¤Þ¤¿¡¢NetBSD ¤ä OpenBSD ¤Î°ìÉô¤â FreeBSD ¤Ë¼è¤ê¹þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£¤·¤¿¤¬¤Ã¤Æ»ä¤¿¤Á¤Ï NetBSD ¤È OpenBSD ¤Ø¹×¸¥¤·¤¿¿Í¡¹¤¹¤Ù¤Æ¤Ë´¶¼Õ¤·¤Þ¤¹¡£ ¤½¤Î¾¤Î FreeBSD ¤Ø¤Î¹×¸¥¼Ô (̾Á°¤Ç¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç) &contrib.additional; 386BSD ¥Ñ¥Ã¥Á¥­¥Ã¥È¤Ø¤Î¥Ñ¥Ã¥ÁÄó¶¡¼Ô (̾Á°¤Ç¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç): &contrib.386bsd; + +
diff --git a/ja_JP.eucJP/articles/problem-reports/article.xml b/ja_JP.eucJP/articles/problem-reports/article.xml index b34a1ba53f..322bc0a12c 100644 --- a/ja_JP.eucJP/articles/problem-reports/article.xml +++ b/ja_JP.eucJP/articles/problem-reports/article.xml @@ -1,1328 +1,1330 @@
&os; ¾ã³²Êó¹ð¤Î½ñ¤­Êý &tm-attrib.freebsd; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ¤³¤Îµ­»ö¤Ç¤Ï¡¢ÌÀÎƤʾ㳲Êó¹ð (Problem Report: PR) ¤ò &os; ¥×¥í¥¸¥§¥¯¥È¤ËÄó½Ð¤¹¤ëÊýË¡¤ò²òÀ⤷¤Þ¤¹¡£ Dag-Erling Smørgrav ´ó¹Æ: Mark Linimon ¾ã³²Êó¹ð
¤Ï¤¸¤á¤Ë ¥½¥Õ¥È¥¦¥§¥¢¤ÎÍøÍѼԤȤ·¤Æ·Ð¸³¤¹¤ë¤â¤Ã¤È¤â¤¤¤é¤¿¤À¤·¤¤¤³¤È¤Î°ì¤Ä¤Ï¡¢ ¤½¤ì¤Ï¥Ð¥°¤¸¤ã¤Ê¤¤¡¢¤Ò¤É¤¤¾ã³²Êó¹ð¤À ¤Ê¤É¤Î¤è¤¦¤Ê¤½¤Ã¤±¤Ê¤¯Íý²ò¤ÎÌò¤ËΩ¤¿¤Ê¤¤ÀâÌÀ¤Ë¤è¤Ã¤Æ¡¢ ¾ã³²Êó¹ð¤¬¤¢¤Ã¤µ¤êÊÒÉÕ¤±¤é¤ì¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤¹¡£ ƱÍͤˡ¢¥½¥Õ¥È¥¦¥§¥¢³«È¯¼Ô¤¬·Ð¸³¤¹¤ë¤â¤Ã¤È¤â¤¤¤é¤À¤¿¤·¤¤¤³¤È¤Î°ì¤Ä¤Ï¡¢ ¼ÂºÝ¤Ï¾ã³²Êó¹ð¤Ç¤Ï¤Ê¤¤Ã±¤Ê¤ë¥µ¥Ý¡¼¥ÈÍ×µá¤ä ²¿¤¬ÌäÂê¤Ç¤É¤Î¤è¤¦¤ËºÆ¸½¤¹¤ë¤«¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤¬ Ë³¤·¤¤¤Þ¤¿¤Ï·çÍ¤Æ¤¤¤ë¾ã³²Êó¹ð¤¬»¦Åþ¤¹¤ë¤³¤È¤Ç¤¹¡£ ¤³¤Îµ­»ö¤Î¤Í¤é¤¤¤Ï¡¢¾å¼ê¤Ê¾ã³²Êó¹ð¤Î½ñ¤­Êý¤Ë¤Ä¤¤¤ÆÀâÌÀ¤¹¤ë¤³¤È¤Ç¤¹¡£ ¾å¼ê¤Ê¾ã³²Êó¹ð¤È¤Ï¤É¤¦¤¤¤¦¤â¤Î¤Ç¤·¤ç¤¦¤«? ¤½¤¦¤Ç¤¹¤Í¡¢Ã±ÅáľÆþ¤ËÍ×ÅÀ¤ò¸À¤¨¤Ð¡¢ ¾å¼ê¤Ê¾ã³²Êó¹ð¤È¤Ï¡¢¿×®¤Ë²òÀϤò¿Ê¤á½èÍý¤ò¹Ô¤¦¤³¤È¤¬¤Ç¤­¡¢ ÍøÍѼԤȳ«È¯¼Ô¤¬¤ª¸ß¤¤¤ËËþ­¤Ç¤­¤ë¤â¤Î¤Ç¤¹¡£ ¤³¤Îµ­»ö¤Ç¤Ï¼ç¤È¤·¤Æ &os; ¤Î¾ã³²Êó¹ð¤Ë¾ÇÅÀ¤ò¹Ê¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢ ¾¤Î¥½¥Õ¥È¥¦¥§¥¢¥×¥í¥¸¥§¥¯¥È¤Ç¤â¿¤¯¤ÎÉôʬ¤¬Åö¤Æ¤Ï¤Þ¤ë¤Ç¤·¤ç¤¦¡£ ¤³¤Îµ­»ö¤Ï¥Æ¡¼¥ÞÊ̤ËÀ°Íý¤µ¤ì¤Æ¤ª¤ê¡¢½çÈÖ¤ËÆɤá¤ë¤è¤¦¤Ë¤Ï¤Ê¤Ã¤Æ¤¤¤Þ¤»¤ó¡£ ¤½¤Î¤¿¤á¡¢Ãʳ¬¤òƧ¤ó¤À¥Á¥å¡¼¥È¥ê¥¢¥ë¤È¤·¤ÆÍøÍѤ¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢ ¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ëÁ°¤ËÁ´ÂΤòÄ̤·¤ÆÆɤà¤Ù¤­¤Ç¤¹¡£
¤¤¤Ä¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ì¤Ð¤è¤¤¤Î¤« ÌäÂê¤Ë¤Ï¤µ¤Þ¤¶¤Þ¤Ê¼ïÎब¤¢¤ê¤Þ¤¹¤¬¡¢ ¤½¤ì¤é¤¹¤Ù¤Æ¤¬¾ã³²Êó¹ð¤ËÃͤ¹¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤â¤Á¤í¤ó¡¢Ã¯¤·¤â¤¬´°àú¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¡¢ ¼ÂºÝ¤Ï¥³¥Þ¥ó¥É¤Î¹½Ê¸¤ò´ª°ã¤¤¤·¤Æ¤¤¤¿¤ê¡¢ ÀßÄê¥Õ¥¡¥¤¥ë¤ò½ñ¤­´Ö°ã¤¨¤Æ¤¤¤ë¤Î¤Ë¡¢ ¥×¥í¥°¥é¥à¤Ë¥Ð¥°¤ò¸«¤Ä¤±¤¿! ¤È»×¤¤¹þ¤ó¤Ç¤·¤Þ¤¦¤³¤È¤¬¤¢¤ë¤Ç¤·¤ç¤¦ (¤È¤Ï¸À¤Ã¤Æ¤â¡¢¤½¤ì¼«¿È¡¢Ê¸½ñ¤¬Å¬Àڤ˵­½Ò¤µ¤ì¤Æ¤¤¤Ê¤«¤Ã¤¿¤ê¡¢ ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥¨¥é¡¼½èÍý¤¬´Å¤¤¤³¤È¤ò°Å¼¨¤·¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹)¡£ ¤½¤ì°Ê³°¤Ë¤â¡¢¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ë¤³¤È¤¬Àµ¤·¤¤¹ÔÆ°¤Ç¤Ï¤Ê¤¯¡¢ ¤¢¤Ê¤¿¤ä³«È¯¼Ô¤¿¤Á¤ËÉÔËþ¤òÊú¤«¤»¤ë¤À¤±¤È¤¤¤¦¾ì¹ç¤¬¤¢¤ê¤Þ¤¹ (ÌõÃí: ¤Ï¤Ã¤­¤ê¤ÈÇÄ°®¤·¤Æ¤¤¤Ê¤¤¤³¤È¤òÊó¹ð¤¹¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ Í×ÎΤòÆÀ¤Ê¤¤¾ã³²Êó¹ð¤Ï°·¤¤¤Ë¤¯¤¤¤â¤Î¤Ç¤¹)¡£ µÕ¤Ë¡¢¥Ð¥°¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ë¤Î¤Ë¤Õ¤µ¤ï¤·¤¤¾ì¹ç¤â¤¢¤ê¤Þ¤¹ — ¤¿¤È¤¨¤Ð¡¢´û¸µ¡Ç½¤Î³ÈÄ¥¤ä¿·¤·¤¤µ¡Ç½¤ÎÅëºÜ¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤¹¡£ ¤Ç¤Ï¡¢²¿¤¬¥Ð¥°¤Ç²¿¤¬¥Ð¥°¤Ç¤Ê¤¤¤Î¤«¡¢ ¤É¤Î¤è¤¦¤Ë¤·¤Æ·è¤á¤ì¤ÐÎɤ¤¤Ç¤·¤ç¤¦¤«? ´Êñ¤Ê·Ð¸³Â§¤Ç¤Ï¡¢¤½¤ì¤ò¼ÁÌä¤È¤·¤Æ (¤è¤¯¤¢¤ë¤Î¤Ï ¤É¤¦¤¹¤ì¤Ð X ¤Ç¤­¤Þ¤¹¤«? ¤ä Y ¤Ï¤É¤³¤Ç¸«¤Ä¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤«? ¤Î¤è¤¦¤Ê·Á¼°¤Ç) ɽ¸½¤Ç¤­¤ë¤Ê¤é¡¢¤¢¤Ê¤¿¤ÎÌäÂê¤Ï¥Ð¥°¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤¤¤Ä¤âÇò¹õ¤¬¤Ä¤±¤é¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢ ¤³¤Î¼ÁÌ䵬§¤ÏÂçȾ¤Î¾ì¹ç¤Ë¤¢¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£ ¤â¤·¡¢¤³¤Î¤è¤¦¤Ê¼ÁÌä¤ËÂФ¹¤ëÅú¤¨¤òµá¤á¤Æ¤¤¤ë¤Î¤Ê¤é¡¢ &a.questions; ¤Ç¼ÁÌ䤷¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ ÌõÃí &a.questions; ¤Ø¤Î¥á¡¼¥ë¤Ï±Ñ¸ì¤Ç¤ª´ê¤¤¤·¤Þ¤¹¡£ ÆüËܸì¤Ç¤Î¼ÁÌä¤Ï¡¢&a.jp.users-jp; ¤ä FreeBSD-beginners-jp ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È ¤Ê¤É¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£ ¥Ð¥°¤Ç¤Ï¤Ê¤¤¤â¤Î¤Ë´Ø¤¹¤ë¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ë¤³¤È¤¬Å¬Àڤȹͤ¨¤é¤ì¤ë¤Î¤Ï¡¢ °Ê²¼¤Î¤è¤¦¤Ê¾ì¹ç¤Ç¤¹¡£ ³°Éô¤Ç´ÉÍý¤µ¤ì¤Æ¤¤¤ë¥½¥Õ¥È¥¦¥§¥¢¤Î¹¹¿·ÄÌÃÎ (¼ç¤Ë ports ¤Î¤³¤È¤Ç¤¹¤¬¡¢BIND ¤ä¤µ¤Þ¤¶¤Þ¤Ê GNU ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Î¤è¤¦¤Ê³°Éô¤Ç°Ý»ý¤µ¤ì¤Æ¤¤¤ë¡¢ ¥·¥¹¥Æ¥à¤Î´ðÁäò¹½À®¤¹¤ë¥½¥Õ¥È¥§¥¢¤â´Þ¤Þ¤ì¤Þ¤¹)¡£ ¥á¥ó¥Æ¥Ê¥ó¥¹¤µ¤ì¤Æ¤¤¤Ê¤¤ ports (MAINTAINER ¤¬ ports@FreeBSD.org ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹) ¤Ç¤Ï¡¢¤³¤Î¼ê¤Î¹¹¿·ÄÌÃΤ϶½Ì£¤òÊú¤¤¤¿ committer ¤¬¼è¤ê¾å¤²¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤·¡¢¤¢¤Ê¤¿¤¬¤½¤Î port ¤ò¹¹¿·¤¹¤ë¥Ñ¥Ã¥Á¤òÄó½Ð¤¹¤ë¤³¤È¤¬µá¤á¤é¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤¢¤é¤«¤¸¤á¥Ñ¥Ã¥Á¤òÄó½Ð¤¹¤ì¤Ð¡¢port ¤¬¤¿¤À¤Á¤Ë¹¹¿·¤µ¤ì¤ë²ÄǽÀ­¤¬Èó¾ï¤Ë¹â¤¯¤Ê¤ê¤Þ¤¹¡£ port ¤¬¥á¥ó¥Æ¥Ê¥ó¥¹¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ °ì¼¡ÇÛÉÛ¸µ¤«¤é¿·¤¿¤Ê¥Ð¡¼¥¸¥ç¥ó¤¬¥ê¥ê¡¼¥¹¤µ¤ì¤¿¤³¤È¤òÄÌÃΤ¹¤ë¾ã³²Êó¹ð¤Ï committer ¤Ë;ʬ¤Êºî¶È¤ò¤µ¤»¤ë¤À¤±¤Ç¤¢¤Þ¤êÌò¤ËΩ¤¿¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤Þ¤¿¡¢¥á¥ó¥Æ¥Ê¤Ï¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤¬½Ð¤¿¤³¤È¤ò¤¹¤Ç¤ËÃΤäƤ¤¤ë²ÄǽÀ­¤¬¹â¤¤¤Ç¤¹¡£ ¤â¤·¤«¤¹¤ë¤È¡¢³«È¯¼Ô¤È°ì½ï¤Ëºî¶È¤·¤Æ¤¤¤Æ¡¢ Âà¹Ô¤·¤¿¤È¤³¤í¤¬¤Ê¤¤¤«¤Ê¤É¤ò¥Æ¥¹¥È¤·¤Æ¤¤¤ë¤È¤³¤í¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤¤¤º¤ì¤Î¾ì¹ç¤â¡¢Port ºîÀ®¼Ô¤Î¤¿¤á¤Î¥Ï¥ó¥É¥Ö¥Ã¥¯ ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¼ê½ç¤¬¤â¤Ã¤È¤â¤è¤¤·ë²Ì¤ò¤â¤¿¤é¤·¤Þ¤¹ ( Contributing to the FreeBSD Ports Collection ¤È¤¤¤¦Ê¸½ñ¤âÆɤó¤Ç¤ß¤¿¤¤¤È»×¤ï¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤Í)¡£ ºÆ¸½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¥Ð¥°¤Ï¡¢¤á¤Ã¤¿¤Ëľ¤¹¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£ ¤â¤·¡¢¥Ð¥°¤¬°ìÅÙ¤À¤±È¯À¸¤·¤Æ¤½¤ì¤¬ºÆ¸½¤Ç¤­¤Ê¤¤¤â¤Î¤Ç¡¢ ¤Ê¤ª¤«¤Ä¾¤Î¿Í¤Î¥·¥¹¥Æ¥à¤Ç¤âµ¯¤³¤é¤Ê¤¤¤è¤¦¤Ç¤¢¤ì¤Ð¡¢ ³«È¯¼Ô¤¬¤½¤ì¤òºÆ¸½¤Ç¤­¤ë²ÄǽÀ­¤â¡¢ ²¿¤¬°­¤¤¤Î¤«¤ï¤«¤ë²ÄǽÀ­¤â¤¢¤ê¤Þ¤»¤ó¡£ ¤³¤ì¤Ï¥Ð¥°¤¬µ¯¤³¤é¤Ê¤«¤Ã¤¿¤³¤È¤ò°ÕÌ£¤¹¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤·¤«¤·¡¢¤³¤Î¤è¤¦¤Ê¾õ¶·¤Ç¤Ï¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤¬¥Ð¥°¤Î½¤Àµ¤Ë ¤Ä¤Ê¤¬¤ë¸«¹þ¤ß¤ÏÈó¾ï¤ËÇö¤¤¤â¤Î¤Ç¤¹¡£ ¤ª¤Þ¤±¤Ë¡¢¤³¤Î¼ê¤Î¥Ð¥°¤Ï¼ÂºÝ¤Ï¸Î¾ã¤·¤¿¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ä²áÇ®¤·¤¿ CPU ¤¬¸¶°ø¤Çµ¯¤­¤Æ¤¤¤ë¤³¤È¤¬Â¿¤¤¤Î¤Ç¤¹ (¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ëÁ°¤Ë¤Ïɬ¤º¡¢²Äǽ¤Ê¤é¡¢ ¤³¤¦¤·¤¿¸¶°ø¤òÇÓ½ü¤¹¤ë¤è¤¦Åؤá¤ë¤Ù¤­¤Ç¤¹)¡£ ¼¡¤Ë¡¢Ã¯¤Ë¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ë¤«·è¤á¤Þ¤¹¡£ ¤½¤Î¤¿¤á¤Ë¤Ï¡¢&os; ¤ò¹½À®¤¹¤ë¥½¥Õ¥È¥¦¥§¥¢¤¬¤µ¤Þ¤¶¤Þ¤ÊÍ×ÁǤǹ½À®¤µ¤ì¤Æ¤¤¤ë¤³¤È¤òÃΤäƤª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ ¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¥³¡¼¥É¤Ç¡¢&os; ¤Ø¤Î¹×¸¥¼Ô¤Ë¤è¤Ã¤Æ½ñ¤«¤ì¡¢°Ý»ý¤µ¤ì¤Æ¤¤¤ë¤â¤Î¡£ ¤¿¤È¤¨¤Ð¡¢¥«¡¼¥Í¥ë¡¢C ¥é¥¤¥Ö¥é¥ê¤ä¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð (kern ¤ËʬÎव¤ì¤Æ¤¤¤ë¤â¤Î)¡¢ ¥Ð¥¤¥Ê¥ê¥æ¡¼¥Æ¥£¥ê¥Æ¥£ (bin)¡¢ ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤äʸ½ñ (docs) ¤ä¥¦¥§¥Ö¥Ú¡¼¥¸ (www) ¤¬¤¢¤ê¤Þ¤¹¡£ ¤³¤ÎÎΰè¤Î¥Ð¥°¤ÏÁ´¤Æ &os; ³«È¯¼Ô¤ËÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤½¤ì°Ê³°¤Î¿Í¤Ë¤è¤Ã¤Æ½ñ¤«¤ì¡¢°Ý»ý¤µ¤ì¤Æ¤¤¤ë¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¥³¡¼¥É¤Ç¡¢ &os; ¤Ë¼è¤ê¹þ¤Þ¤ì¡¢&os; ¤Ë¹ç¤ï¤»¤ÆÊѹ¹¤µ¤ì¤Æ¤¤¤ë¤â¤Î¡£ ¤¿¤È¤¨¤Ð¡¢bind, &man.gcc.1; ¤ä &man.sendmail.8; ¤¬¤¢¤ê¤Þ¤¹¡£ ¤³¤ÎÎΰè¤Î¥Ð¥°¤Î¤Û¤È¤ó¤É¤Ï &os; ³«È¯¼Ô¤ËÊó¹ð¤¹¤Ù¤­¤Ç¤¹¤¬¡¢ ÌäÂ꤬ &os; ÆÃÍ­¤Ç¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢ ¤ª¤ª¤â¤È¤Îºî¼Ô¤ËÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ Ä̾ï¤Ï¡¢¤³¤ì¤é¤Î¥Ð¥°¤Ï bin ¤Þ¤¿¤Ï gnu ¥«¥Æ¥´¥ê¤ËʬÎव¤ì¤Þ¤¹¡£ ¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Ç¤Ï¤Ê¤¯ &os; Ports Collection (ports ¥«¥Æ¥´¥ê) ¤Î°ìÉô¤Ç¤¢¤ë¸ÄÊ̤Υ¢¥×¥ê¥±¡¼¥·¥ç¥ó¡£ ¤½¤Î¤Û¤È¤ó¤É¤Ï &os; ¤¬½ñ¤¤¤¿¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ &os; ¤¬Ä󶡤·¤Æ¤¤¤ë¤Î¤Ï¡¢ ñ¤Ê¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëÏÈÁȤߤǤ¹¡£ ¤·¤¿¤¬¤Ã¤Æ¡¢ÌäÂ꤬ &os; ÆÃÍ­¤Ç¤¢¤ë¤È¿®¤¸¤é¤ì¤ë¾ì¹ç¤Ë¤À¤± &os; ³«È¯¼Ô¤ËÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤½¤ì°Ê³°¤Ï¡¢¤½¤Î¥½¥Õ¥È¥¦¥§¥¢¤Î³«È¯¼Ô¤ËÏ¢Íí¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤½¤ì¤«¤é¡¢ÌäÂ꤬»þµ¹¤òÆÀ¤¿¤â¤Î¤«³Îǧ¤¹¤Ù¤­¤Ç¤¹¡£ ´û¤Ë½¤Àµ¤·¤¿¥Ð¥°¤Ë´Ø¤¹¤ë¾ã³²Êó¹ð¤ò¼õ¤±¤È¤ë¤³¤È¤Û¤É³«È¯¼Ô¤òǺ¤Þ¤»¤ë¤â¤Î¤Ï¤Þ¤º¤¢¤ê¤Þ¤»¤ó¡£ ¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤ÎÌäÂê¤Ç¡¢&os; ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ä¤¤¤Æ¤è¤¯Ê¬¤«¤Ã¤Æ¤¤¤Ê¤¤¤Ê¤é¡¢¤Þ¤º FAQ ¤Î &os; ¥Ð¡¼¥¸¥ç¥ó¤Ë´Ø¤¹¤ëÀá¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£ &os; ¤Ç¤Ï¡¢ ¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¤¤¤¯¤Ä¤«¤ÎºÇ¿·¥Ö¥é¥ó¥Á°Ê³°¤Ï½¤Àµ¤Ç¤­¤Þ¤»¤ó¡£ ¤½¤Î¤¿¤á¡¢¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ä¤¤¤Æ¾ã³²Êó¹ð¤òÄó½Ð¤·¤Æ¤â¡¢ ³«È¯¼Ô¤«¤éÌäÂ꤬¤Þ¤Àµ¯¤­¤ë¤«³Îǧ¤¹¤ë¤¿¤á¤Ë¡¢ ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¥Ð¡¼¥¸¥ç¥ó¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¤è¤¦¤Ë´«¤á¤é¤ì¤ë¤À¤±¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¥»¥­¥å¥ê¥Æ¥£¥ª¥Õ¥£¥µ¥Á¡¼¥à¤¬¡¢ ¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¥Ð¡¼¥¸¥ç¥ó¤Î°ìÍ÷ ¤ò´ÉÍý¤·¤Æ¤¤¤Þ¤¹¡£ ¤¢¤ë port ¤ËÌäÂ꤬¤¢¤ë¾ì¹ç¡¢¤Þ¤º¤Ï¤¸¤á¤Ë Ports Collection ¤ÎºÇ¿·ÈǤ˥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤Æ¡¢¤Þ¤ÀÌäÂ꤬¤¢¤ë¤«¸«¤Æ¤¯¤À¤µ¤¤¡£ ¤³¤ì¤é¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ï®¤¤¥Ú¡¼¥¹¤ÇÊѹ¹¤µ¤ì¤ë¤¿¤á¡¢ &os; ¤Ç´°Á´¤ÊºÇ¿·Èǰʳ°¤ËÂбþ¤¹¤ë¤Î¤ÏÉÔ²Äǽ¤Ç¤¹¡£ ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Ë¤¢¤ëÌäÂê¤Ï¡¢ ľ¤·¤è¤¦¤¬¤¢¤ê¤Þ¤»¤ó¡£
½àÈ÷ ½¾¤¦¤Ù¤­Îɤ¤µ¬Â§¤Ï¡¢ ¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ëÁ°¤Ë¾ï¤ËÌäÂê¤ÎÇطʤòÄ´¤Ù¤ë¤³¤È¤Ç¤¹¡£ ¤¢¤Ê¤¿¤ÎÌäÂê¤Ï¤¹¤Ç¤ËÊó¹ð¤µ¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤Þ¤¿¡¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ÇµÄÏÀ¤µ¤ì¤Æ¤¤¤ëºÇÃ椫¡¢ ºÇ¶áµÄÏÀ¤µ¤ì¤Æ¤¤¤¿¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤¢¤Ê¤¿¤¬Æ°¤«¤·¤Æ¤¤¤ë¤â¤Î¤è¤ê¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Ç¡¢ ´û¤Ë½¤ÀµºÑ¤ß¤È¤¤¤¦¤³¤È¤¹¤é¤¢¤ê¤¨¤Þ¤¹¡£ ¤Ç¤¹¤«¤é¡¢¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ëÁ°¤Ë¼«ÌÀ¤Ê¾ì¤ò¤¹¤Ù¤Æ³Îǧ¤¹¤Ù¤­¤Ç¤¹¡£ &os; ¤Ë¤Ä¤¤¤Æ¤Ï¡¢°Ê²¼¤Î¤È¤³¤í¤Ë¤Ê¤ê¤Þ¤¹¡£ &os; ¤Î ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤ÎÅú¤¨ (FAQ) °ìÍ÷¡£ FAQ ¤Ï¡¢ ¥Ï¡¼¥É¥¦¥§¥¢¸ß´¹À­¡¢ ¥æ¡¼¥¶¥¢¥×¥ê¥±¡¼¥·¥ç¥ó ¤ä ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó ¤È¤¤¤Ã¤¿¤³¤È¤Ë´Ø¤¹¤ë¹­¤¤ÈϰϤμÁÌä¤ËÂФ·¤ÆÅú¤ò¼¨¤½¤¦¤È¤·¤Æ¤¤¤Þ¤¹¡£ ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¡£ — ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ò¹ØÆɤ·¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ &os; ¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Ë¤¢¤ë ¥¢¡¼¥«¥¤¥Ö¸¡º÷¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¡¢¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ÇµÄÏÀ¤¬¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ ¼«Ê¬¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¤Î¥á¥Ã¥»¡¼¥¸¤òÁ÷¤Ã¤Æ¤ß¤Æ¡¢ ¸«Íî¤È¤·¤¿ÅÀ¤ò狼¤¬¸«¤Ä¤±¤Æ¤¯¤ì¤ë¤«¤É¤¦¤« ¿ôÆü´ÖÂԤäƤߤë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£ ¥¦¥§¥ÖÁ´ÂΤò¸¡º÷¤¹¤ë (Ǥ°Õ)¡£— ¤¢¤Ê¤¿¤ÎÌäÂê¤Ë´Ø·¸¤¹¤ëÏÃÂ꤬¤Ê¤¤¤« ¤¢¤Ê¤¿¤Î¤ªµ¤¤ËÆþ¤ê¤Î¸¡º÷¥¨¥ó¥¸¥ó¤ò»È¤Ã¤Æõ¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤¢¤Ê¤¿¤¬ÃΤê¤â¤·¤Ê¤«¤Ã¤¿¤«¡¢ ¸¡º÷¤·¤è¤¦¤È¹Í¤¨¤Ê¤«¤Ã¤¿¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ä¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×¤Î¥¢¡¼¥«¥¤¥Ö¤Ë¤¢¤¿¤ë¤³¤È¤â¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¼¡¤Ë¡¢¸¡º÷²Äǽ¤Ê &os; ¾ã³²Êó¹ð¥Ç¡¼¥¿¥Ù¡¼¥¹ (GNATS) ¤¬¤¢¤ê¤Þ¤¹¡£ ¤¢¤Ê¤¿¤ÎÌäÂ꤬¿·¤·¤¤¤â¤Î¤Ç¤âÉÔÌÀÎƤǤâ¤Ê¤±¤ì¤Ð¡¢ ´û¤ËÊó¹ð¤µ¤ì¤Æ¤¤¤ë²ÄǽÀ­¤¬¤«¤Ê¤ê¹â¤¤¤Ç¤¹¡£ ²¿¤è¤ê¤â¤Þ¤º¡¢ ¸µ¤È¤Ê¤ë¥½¡¼¥¹¥³¡¼¥ÉÆâ¤Î¥É¥­¥å¥á¥ó¥È¤Ç¡¢ ¤¢¤Ê¤¿¤ÎÌäÂ꤬¿¨¤ì¤é¤ì¤Æ¤¤¤Ê¤¤¤«Ä´¤Ù¤Æ¤ß¤ë¤Ù¤­¤Ç¤¹¡£ &os; ¤Î´ðËÜÉôʬ¤Î¥³¡¼¥É¤Ë¤Ä¤¤¤Æ¤Ï¡¢ ¥·¥¹¥Æ¥à¤Î /usr/src/UPDATING ¥Õ¥¡¥¤¥ë¤ÎÆâÍƤ«¡¢ ¤Ë¤¢¤ëºÇ¿·ÈǤò¤è¤¯Ä´¤Ù¤ë¤Ù¤­¤Ç¤¹ (¤¢¤ë¥Ð¡¼¥¸¥ç¥ó¤«¤éÊ̤ΥС¼¥¸¥ç¥ó¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð —ÆÃ¤Ë -current ¥Ö¥é¥ó¥Á¤Ë¾å¤²¤è¤¦¤È¤·¤Æ¤¤¤ë¤Ê¤é¡¢ ¤³¤ì¤ÏÈó¾ï¤Ë½ÅÍפʾðÊó¤Ç¤¹)¡£ ¤·¤«¤·¡¢ÌäÂ꤬ &os; Ports Collection ¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿¤â¤Î¤Ë¤¢¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ /usr/ports/UPDATING (¸ÄÊ̤Πports) ¤Þ¤¿¤Ï /usr/ports/CHANGES (Ports Collection Á´ÂΤ˱ƶÁ¤¹¤ëÊѹ¹) ¤ò»²¾È¤¹¤Ù¤­¤Ç¤¹¡£ ¤È ¤Ï svnweb ¤«¤é¤â»²¾È¤Ç¤­¤Þ¤¹¡£
¾ã³²Êó¹ð¤Î½ñ¤­Êý ÌäÂ꤬¾ã³²Êó¹ð¤ò¹Ô¤¦¤ËÃͤ¹¤ë¤È·ëÏÀ¤ò½Ð¤·¡¢ ¤½¤·¤Æ¤½¤ì¤¬ &os; ¤ÎÌäÂêÅÀ¤Ç¤¢¤ë¤ÈȽÃǤ·¤¿¤é¡¢ ¼ÂºÝ¤Ë¾ã³²Êó¹ð¤ò¼¹É®¤¹¤ë»þ¤Ç¤¹¡£ ¾ã³²Êó¹ð¤òºîÀ®¤·¤ÆÁ÷¿®¤¹¤ë¥×¥í¥°¥é¥à¤Î»ÅÁȤߤËÆþ¤ëÁ°¤Ë¡¢ ¾ã³²Êó¹ð¤ò¤â¤Ã¤È¤â¸ú²ÌŪ¤Ê¤â¤Î¤Ë¤¹¤ë¤³¤Ä¤ò¤¤¤¯¤Ä¤«¾Ò²ð¤·¤Þ¤·¤ç¤¦¡£
¤è¤¤¾ã³²Êó¹ð¤ò½ñ¤¯¤³¤Ä Synopsis(³µÍ×) ¹Ô¤ò¶õ¤Î¤Þ¤Þ¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¾ã³²Êó¹ð¤Ï¡¢À¤³¦Ãæ¤ËÇÛÉÛ¤µ¤ì¤ë¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤ËÁ÷¤é¤ì¤ë (¤½¤³¤Ç¤Ï¡¢Synopsis (³µÍ×) ¤Ï Subject: ¹Ô¤Ë»È¤ï¤ì¤Þ¤¹) ¤È¶¦¤Ë¡¢ ¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¤âÆþ¤ì¤é¤ì¤Þ¤¹¡£¸å¤Ç¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò synopsis (³µÍ×) ¤Ç»²¾È¤¹¤ë¿Í¤Ï¡¢Â꤬¤Ä¤¤¤Æ¤¤¤Ê¤¤¾ã³²Êó¹ð¤Ïñ¤Ë̵»ë¤¹¤ë¤³¤È¤Ç¤·¤ç¤¦¡£ ¤³¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÅÐÏ¿¤µ¤ì¤¿¾ã³²Êó¹ð¤Ï¡¢ 狼¤¬ÂбþºÑ¤Ë¤¹¤ë¤Þ¤Ç¤Ï»Ä¤Ã¤Æ¤¤¤ë¤³¤È¤ò˺¤ì¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ÆâÍÆÉÔÌÀ¤Î¤â¤Î¤ÏÂçÄñ»¨²»¤ËËä¤â¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ ¤ï¤«¤ê¤Ë¤¯¤¤Synopsis (³µÍ×) ¹Ô¤ÏÈò¤±¤Þ¤·¤ç¤¦¡£ ¤¢¤Ê¤¿¤¬Äó½Ð¤·¤¿¾ã³²Êó¹ð¤òÆɤà¿Í¤¬¤É¤¦¤¤¤¦¾õ¶·¤«Ê¬¤«¤Ã¤Æ¤¤¤ë¤È²¾Äꤹ¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤Ç¤­¤ë¤À¤±¾Ü¤·¤¯½ñ¤­¤Þ¤·¤ç¤¦¡£ ¤¿¤È¤¨¤Ð¡¢¤½¤ÎÌäÂê¤Ï¥·¥¹¥Æ¥à¤Î¤É¤ÎÉôʬ¤Ë¤¢¤Æ¤Ï¤Þ¤ë¤Î¤Ç¤·¤ç¤¦¤«¡£ ¥¤¥ó¥¹¥È¡¼¥ëÃæ¤Ë¤·¤«ÌäÂê¤ËÅö¤¿¤é¤Ê¤¤¤Î¤«¡¢¤½¤ì¤È¤â²ÔƯÃæ¤ËÅö¤¿¤ë¤Î¤«¡£ ¶ñÂÎŪ¤ÊÎã¤Ç¤¤¤¦¤Ê¤é¡¢ Synopsis: portupgrade is broken (³µÍ×: portupgrade ¤¬¤ª¤«¤·¤¤) ¤Ç¤Ï¤Ê¤¯¡¢ ¼¡¤Î¤è¤¦¤Ë½ñ¤¤¤¿¤é¤É¤ì¤À¤±ÅÁ¤ï¤ê¤ä¤¹¤¤¤«¹Í¤¨¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ Synopsis: port ports-mgmt/portupgrade coredumps on -current (³µÍ×: sysutils/portupgrade port ¤¬ -current ¤Ç¥³¥¢¥À¥ó¥×¤·¤Þ¤¹)¡£(ports ¤Î¾ì¹ç¤Ï¡¢ Synopsis (³µÍ×) ¹Ô¤ËʬÎà¤È̾Á°¤òÆþ¤ì¤ë¤È¡¢ ¤È¤Æ¤â½õ¤«¤ê¤Þ¤¹)¡£ ¥Ñ¥Ã¥Á¤¬¤¢¤ë¤Ê¤é¡¢¤½¤¦½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ ¥Ñ¥Ã¥Á¤¬¤Ä¤¤¤Æ¤¤¤ë¾ã³²Êó¹ð¤Ï¡¢ ¤Ä¤¤¤Æ¤¤¤Ê¤¤¤â¤Î¤è¤ê¤â¸«¤Æ¤â¤é¤¨¤ë²ÄǽÀ­¤¬¹â¤¤¤Ç¤¹¡£¥Ñ¥Ã¥Á¤ò¤Ä¤±¤ë¾ì¹ç¤Ï¡¢ Synopsis (³µÍ×) ¹Ô¤ÎÀèƬ¤Ë [patch] ¤È¤¤¤¦Ê¸»úÎó (³Ñ³ç¸Ì¤ò´Þ¤ß¤Þ¤¹) ¤ò¤¤¤ì¤Æ²¼¤µ¤¤¡£ (¤³¤ÎÄ̤ê½ñ¤«¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢ ´·½¬¤È¤·¤Æ¤³¤Îʸ»úÎó¤¬ÍѤ¤¤é¤ì¤Æ¤¤¤Þ¤¹)¡£ ¤¢¤Ê¤¿¤¬¥á¥ó¥Æ¥Ê¤Ê¤é¡¢¤½¤¦½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ ¥½¡¼¥¹¥³¡¼¥É¤Î°ìÉô (¤¿¤È¤¨¤Ð¡¢¤¢¤ë port) ¤ò¥á¥ó¥Æ¥Ê¥ó¥¹¤·¤Æ¤¤¤ë¤Ê¤é¡¢³µÍ×¹Ô¤ÎÀèƬ¤Ë [maintainer update] ¤È¤¤¤¦Ê¸»úÎó (³Ñ³ç¸Ì¤ò´Þ¤ß¤Þ¤¹) ¤ò¤Ç¤­¤ì¤Ð¤¤¤ì¤Æ¡¢¾ã³²Êó¹ð¤Î Class ¤òɬ¤º maintainer-update ¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£¤³¤¦¤¹¤ì¤Ð¡¢committer ¤¬¤½¤Î¾ã³²Êó¹ð¤ò°·¤¦ºÝ¤Ë¡¢¤¤¤Á¤¤¤Á³Îǧ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤»¤ó¡£ ¶ñÂÎŪ¤Ë½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ ¤¢¤Ê¤¿¤¬Êú¤¨¤Æ¤¤¤ëÌäÂê¤Ë¤Ä¤¤¤Æ¿¤¯¤Î¾ðÊó¤ò½Ð¤¹¤Û¤É¡¢ ²óÅú¤·¤Æ¤â¤é¤¨¤ë²ÄǽÀ­¤Ï¹â¤¯¤Ê¤ê¤Þ¤¹¡£ &os; ¤Î¥Ð¡¼¥¸¥ç¥ó (¤³¤ì¤òµ­ºÜ¤¹¤ë¾ì½ê¤¬¤¢¤ê¤Þ¤¹¡£¸å½Ò¤·¤Þ¤¹) ¤È¡¢¤É¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤ÇÆ°¤«¤·¤Æ¤¤¤ë¤Î¤«¤ò½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ Æ°¤«¤·¤Æ¤¤¤ë¤Î¤¬ (CDROM ¤«¤é¡¢¤Þ¤¿¤Ï¥À¥¦¥ó¥í¡¼¥É¤·¤ÆÆþ¤ì¤¿) ¥ê¥ê¡¼¥¹¤Ç¤Ê¤Î¤«¡¢¤½¤ì¤È¤â Subversion ¤Ç¥á¥ó¥Æ¥Ê¥ó¥¹¤·¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ç¤Ê¤Î¤« (¤½¤¦¤À¤È¤·¤¿¤é¡¢ºÇ¸å¤Ë¹¹¿·¤·¤¿¤Î¤Ï¤¤¤Ä¤«) ¤â½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£¤¢¤Ê¤¿¤¬ &os.current; ¥Ö¥é¥ó¥Á¤òÄɤ¤¤«¤±¤Æ¤¤¤¿¤é¡¢¤½¤ì¤ò¿¿¤ÃÀè¤Ëʹ¤«¤ì¤ë¤Ç¤·¤ç¤¦¡£ ¤Ê¤¼¤Ê¤é¡¢&os.current; ¤Ç¤Ï (ÃíÌܤòÍá¤Ó¤ëÌäÂê¤ÏÆäË) ½¤Àµ¤¬¤¹¤°¤ËÆþ¤ë·¹¸þ¤¬¤¢¤ê¡¢&os.current; ¤Î¥æ¡¼¥¶¤Ï¤½¤ì¤Ë¤Ä¤¤¤Æ¹Ô¤¯¤³¤È¤¬µá¤á¤é¤ì¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£ make.conf ¤Ë¡¢¤É¤Î¥°¥í¡¼¥Ð¥ë¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤¿¤«½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£ Ãí°Õ: &man.gcc.1; ¤Ë -O2 °Ê¾å¤òÀßÄꤹ¤ë¤Î¤Ï¡¢Â¿¤¯¤Î¾ì¹ç¤Ë¥Ð¥°¤¬¤¢¤ë¤³¤È¤¬Ê¬¤«¤Ã¤Æ¤¤¤Þ¤¹¡£ &os; ³«È¯¼Ô¤Ï¥Ñ¥Ã¥Á¤ò¼õ¤±¼è¤ë¤Ç¤·¤ç¤¦¤¬¡¢ ñ½ã¤Ë»þ´Ö¤È¥Ü¥é¥ó¥Æ¥£¥¢¤¬¾¯¤Ê¤¤¤¿¤á¡¢ ¤½¤Î¤è¤¦¤ÊÌäÂê¤ÏÄ̾ïÄ´ºº¤·¤¿¤¬¤é¤º¡¢ ¤¿¤ÀÂбþ¤·¤Æ¤¤¤Ê¤¤¤À¤±¤À¤ÈÅú¤¨¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ ÌäÂ꤬Íưפ˺Ƹ½¤Ç¤­¤ë¤è¤¦¤Ç¤¢¤ì¤Ð¡¢ ³«È¯¼Ô¤¬¼«¿È¤ÇºÆ¸½¤Ç¤­¤ë¤è¤¦¤Ë¾ðÊó¤ò´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¡¢ÆÃÊ̤ÊÆþÎϤ¬¹Ô¤ï¤ì¤¿»þ¤ËÌäÂ꤬µ¯¤­¤ë¤è¤¦¤Ç¤¢¤ì¤Ð¡¢ ²Äǽ¤Ç¤¢¤ì¤Ð¡¢¤½¤ÎÆþÎÏÎã¤òÆþ¤ì¤Æ¤¯¤À¤µ¤¤¡£¤Þ¤¿¡¢ ¼ÂºÝ¤Î½ÐÎϤäͽÁÛ¤µ¤ì¤ë½ÐÎϤâ´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¡¢¥Ç¡¼¥¿¤¬Â礭¤«¤Ã¤¿¤ê¡¢¸ø³«¤Ç¤­¤Ê¤¤¤â¤Î¤Ç¤¢¤ì¤Ð¡¢ Ʊ¤¸ÌäÂê¤òɽ¤ï¤¹¤è¤¦¤ÊºÇ¾®¸Â¤Î¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¡¢ ¾ã³²Êó¹ð¤Ë´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£ ¥«¡¼¥Í¥ë¤ÎÌäÂê¤Ê¤é¡¢ ¼¡¤Î¾ðÊó¤òÅϤ»¤ë¤è¤¦¤Ë¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤ (¤Ï¤¸¤á¤«¤éÆþ¤ì¤ë¤Î¤Ïñ¤Ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò°ìÇդˤ¹¤ë¤À¤±¤Ê¤Î¤ÇɬÍפ¢¤ê¤Þ¤»¤ó¤¬¡¢ ´Ø·¸¤¬¤¢¤ë¤È»×¤¦Éôʬ¤ÎÈ´¿è¤ÏÆþ¤ì¤ë¤Ù¤­¤Ç¤¹)¡£ ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó (¤É¤Î¥Ï¡¼¥É¥¦¥§¥¢¥Ç¥Ð¥¤¥¹¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤«¤â´Þ¤à) (WITNESS ¤Ê¤É¤Î) ¥Ç¥Ð¥Ã¥°¥ª¥×¥·¥ç¥ó¤òÍ­¸ú¤Ë¤·¤Æ¤¤¤ë¤«¡¢ ¤·¤Æ¤¤¤ë¤Ê¤é¡¢ ¤½¤Î¥ª¥×¥·¥ç¥ó¤òÊѹ¹¤·¤Æ¤âÌäÂê¤ÏÊѤï¤é¤Ê¤¤¤« ¤â¤·À¸À®¤·¤Æ¤¤¤ë¤Ê¤é¡¢¥Ð¥Ã¥¯¥È¥ì¡¼¥¹¡¢ ¥Ñ¥Ë¥Ã¥¯¤ä¾¤Î¥³¥ó¥½¡¼¥ë¤Î½ÐÎÏ¡¢¤Þ¤¿¤Ï¡¢/var /log/messages ¤Î¤¹¤Ù¤Æ¤Î¥Æ¥­¥¹¥È ÌäÂ꤬¥Ï¡¼¥É¥¦¥§¥¢¤Î¤¢¤ëÉôʬ¤Ë´ØÏ¢¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ pciconf -l ¤ª¤è¤Ó dmesg ½ÐÎϤδØÏ¢¤¹¤ëÉôʬ src/UPDATING ¤ÏÆɤó¤À¤«¡¢¤½¤³¤Ë¤¢¤Ê¤¿¤ÎÌäÂ꤬µó¤¬¤Ã¤Æ¤¤¤Ê¤¤¤« (´Ö°ã¤¤¤Ê¤¯Ê¹¤«¤ì¤Þ¤¹) ÂåÂؤȤ·¤ÆÆ°¤«¤»¤ë¥«¡¼¥Í¥ë¤¬Â¾¤Ë¤Ê¤¤¤« (¤³¤ì¤Ï¡¢¸Î¾ã¤·¤¿¥Ç¥£¥¹¥¯¤ä²áÇ®¤·¤¿ CPU ¤Ê¤É¤Î¥Ï¡¼¥É¥¦¥§¥¢¤Ë´ØÏ¢¤·¤¿ÌäÂê¤Ç¡¢ ¥«¡¼¥Í¥ë¤ÎÌäÂê¤Ë¸«¤¨¤ë¤â¤Î¤ò½ü³°¤¹¤ë¤¿¤á¤Ç¤¹) Ports ¤ÎÌäÂê¤Ç¤¢¤ì¤Ð¡¢ ¼¡¤Î¾ðÊó¤òÅϤ»¤ë¤è¤¦¤Ë¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤ (¤Ï¤¸¤á¤«¤éÆþ¤ì¤ë¤Î¤Ïñ¤Ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò°ìÇդˤ¹¤ë¤À¤±¤Ê¤Î¤ÇɬÍפ¢¤ê¤Þ¤»¤ó¤¬¡¢ ´Ø·¸¤¬¤¢¤ë¤È»×¤¦Éôʬ¤ÎÈ´¿è¤ÏÆþ¤ì¤ë¤Ù¤­¤Ç¤¹)¡£ ¤É¤Î ports ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤Î¤« PORTSDIR ¤Ê¤É¡¢bsd.port.mk ¤Î¥Ç¥Õ¥©¥ë¥È¤ò¾å½ñ¤­¤¹¤ë´Ä¶­ÊÑ¿ô¤¹¤Ù¤Æ ports/UPDATING ¤ÏÆɤó¤À¤«¡¢¤½¤³¤Ë¤¢¤Ê¤¿¤ÎÌäÂ꤬µó¤¬¤Ã¤Æ¤¤¤Ê¤¤¤« (´Ö°ã¤¤¤Ê¤¯Ê¹¤«¤ì¤Þ¤¹) ÇùÁ³¤Èµ¡Ç½¤òÍ׵᤹¤ë¤Î¤Ï¤ä¤á¤Þ¤·¤ç¤¦¡£ 狼¤³¤¦¤¤¤¦¤³¤È¤¹¤ë¤â¤Î¤ò¼ÂÁõ¤¹¤Ù¤­¤À ¤È¤¤¤¦·Á¤Î¾ã³²Êó¹ð¤Ï¡¢¾ÜºÙ¤ÊÍ×˾¤ËÈæ¤Ù¤ÆÀ®²Ì¤òÆÀ¤Ë¤¯¤¤¤â¤Î¤Ç¤¹¡£ ¥½¡¼¥¹¥³¡¼¥É¤Ïï¤Ç¤âÍøÍѤǤ­¤ë¤Î¤Ç¤¹¤«¤é¡¢²¿¤«µ¡Ç½¤¬Íߤ·¤±¤ì¤Ð¡¢ ¤½¤ì¤ò¤¤¤ì¤ëºÇÁ±¤Î¼êÃʤϺî¶È¤Ë¤È¤ê¤«¤«¤ë¤³¤È¤Ç¤¹¡£ ¤Þ¤¿¾å½Ò¤·¤¿¤è¤¦¤Ë¡¢¤³¤¦¤¤¤¦¤³¤È¤Ï¿¤¯¤Î¾ì¹ç¡¢ ¾ã³²Êó¹ð¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÅÐÏ¿¤¹¤ë¤è¤ê¤â freebsd-questions ¤ÇµÄÏÀ¤·¤¿Êý¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£ 狼¤¬´û¤Ë»÷¤¿¤è¤¦¤Ê¾ã³²Êó¹ð¤òÄó½Ð¤·¤Æ¤¤¤Ê¤¤¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤³¤ì¤Ï¡¢´û¤Ë½Ò¤Ù¤¿¤³¤È¤Ç¤Ï¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤³¤Ç·«¤êÊÖ¤·¤Æ¤ª¤¯¤ËÃͤ¹¤ë¤Ç¤·¤ç¤¦¡£ Web ¥Ù¡¼¥¹¤Î¸¡º÷¥¨¥ó¥¸¥ó ¤ÇÄ´¤Ù¤ë¤Î¤Ï 1, 2 ʬÄøÅÙ¤·¤«¤«¤«¤ê¤Þ¤»¤ó¡£ (¤â¤Á¤í¤ó¡¢Ã¯¤â¤¬¤È¤­¤É¤­¤³¤ì¤ò˺¤ì¤Æ¤·¤Þ¤¦¤È¤¤¤¦ºá¤òÈȤ·¤Æ¤¤¤Þ¤¹)¡£ ¤Ò¤È¤Ä¤Î¾ã³²Êó¹ð¤Ë¤Ï¤Ò¤È¤Ä¤ÎÌäÂê¤òÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤¡£ 2 ¤Ä°Ê¾å¤ÎÌäÂê¤Ï¡¢´Ø·¸¤¬¤Ê¤±¤ì¤ÐƱ¤¸¾ã³²Êó¹ð¤Ë´Þ¤á¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¥Ñ¥Ã¥Á¤òÄó½Ð¤¹¤ëºÝ¤Ë¤Ï¡¢°ì¤Ä¤Î¾ã³²Êó¹ð¤ËÊ£¿ô¤Îµ¡Ç½¤äÊ£¿ô¤Î¥Ð¥°¤ò¡¢ ¤½¤ì¤é¤¬¶Ë¤á¤Æ´Ø·¸¤·¤Æ¤Ê¤±¤ì¤Ð¡¢´Þ¤á¤ë¤³¤È¤ÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£ ¤½¤Î¤è¤¦¤Ê¾ã³²Êó¹ð¤Ï¡¢²ò·è¤¹¤ë¤Î¤Ë¤è¤ê¿¤¯¤Î»þ´Ö¤¬¤«¤«¤ê¤Þ¤¹¡£ °ÛÏÀ¤Î¤¢¤ëÍ×˾¤Ï½Ð¤µ¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤·¤ç¤¦¡£ ¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤¬¤«¤Ä¤ÆÏÀÁè¤Ë¤Ê¤Ã¤¿Ê¬Ìî¤Ë´Ø¤¹¤ë¤â¤Î¤Ç¤¢¤Ã¤¿¤é¡¢ ¥Ñ¥Ã¥Á¤òÄó½Ð¤¹¤ë¤À¤±¤Ç¤Ê¤¯¡¢¤½¤Î¥Ñ¥Ã¥Á¤¬ ÀµÅö¤Ê¤â¤Î¤Ç¤¢¤ë º¬µò¤âÄó½Ð¤·¤¿¤Û¤¦¤¬¤è¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¤É¤Î¾ì¹ç¤Ç¤â¾å½Ò¤Î¤è¤¦¤Ë ¤Ç¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Î¥¢¡¼¥«¥¤¥Ö¤ò¸¡º÷¤·¤ÆÈ÷¤¨¤ë¤Î¤Ï¤è¤¤¤³¤È¤Ç¤·¤ç¤¦¡£ Îéµ·Àµ¤·¤¯¤·¤Þ¤·¤ç¤¦¡£ ¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤Ë¤Ä¤¤¤Æºî¶È¤¹¤ë¿Í¤Ï¡¢ ¤Û¤È¤ó¤ÉÁ´°÷¤¬¥Ü¥é¥ó¥Æ¥£¥¢¤Ç¤¹¡£ ¶âÁ¬Åª¼ýÆþ°Ê³°¤ÎÆ°µ¡¤«¤é¹Ô¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò¡¢ ¤ä¤ì¤ÈÌ¿Îᤵ¤ì¤ë¤Î¤Ïï¤â¹¥¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¥ª¡¼¥×¥ó¥½¡¼¥¹¥×¥í¥¸¥§¥¯¥È¤Ë´Ø¤·¤Æ¤Ï¡¢ ¤³¤ì¤ò¾ï¤ËǰƬ¤Ë¤ª¤¤¤Æ¤ª¤¯¤È¤è¤¤¤Ç¤·¤ç¤¦¡£
»Ï¤á¤ëÁ°¤Ë &man.send-pr.1; ¥×¥í¥°¥é¥à¤ò»È¤¦¤Ê¤é¡¢´Ä¶­ÊÑ¿ô VISUAL (¤â¤· VISUAL ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð EDITOR) ¤¬°ÕÌ£¤Î¤¢¤ë¤â¤Î¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤«³Îǧ¤·¤Þ¤·¤ç¤¦¡£ ¤Þ¤¿¡¢¥á¡¼¥ëÇÛÁ÷¥½¥Õ¥È¥¦¥§¥¢¤¬Àµ¾ï¤ËÆ°ºî¤¹¤ë¤³¤È¤â³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ &man.send-pr.1; ¤Ï¾ã³²Êó¹ð¤ÎÄó½Ð¤ÈÄÉÀפ˥᡼¥ë¤òÍøÍѤ·¤Þ¤¹¡£ &man.send-pr.1; ¤òÆ°¤«¤¹¥Þ¥·¥ó¤«¤é¥á¡¼¥ë¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤È¡¢ ¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤Ï GNATS ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÆϤ­¤Þ¤»¤ó¡£ &os; ¤Ë¤ª¤±¤ë¥á¡¼¥ë¤ÎÀßÄê¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï &os; ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î ÅŻҥ᡼¥ë ¤Î¾Ï ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ¤¢¤Ê¤¿¤¬»È¤Ã¤Æ¤¤¤ë¥á¡¼¥é¤¬ GNATS ¤ËÁ÷¤ë¥á¥Ã¥»¡¼¥¸¤Ë¼ê¤ò²Ã¤¨¤Ê¤¤¤³¤È¤ò³Î¤«¤á¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£ Æäˡ¢¥á¡¼¥é¤¬¼«Æ°¤Ç²þ¹Ô¤·¤¿¤ê¡¢¥¿¥Ö¤ò¥¹¥Ú¡¼¥¹¤ËÊѹ¹¤·¤¿¤ê¡¢ ²þ¹Ôʸ»ú¤ò¥¨¥¹¥±¡¼¥×¤·¤¿¤ê¤¹¤ë¤È¡¢ Äó½Ð¤·¤¿¥Ñ¥Ã¥Á¤Ï»È¤¨¤Ê¤¤¤â¤Î¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ ¤â¤Ã¤È¤â¡¢¥Æ¥­¥¹¥ÈÉô¤Ë¤Ä¤¤¤Æ¤Ï¾ã³²Êó¹ð¤ò web ¤Çɽ¼¨¤·¤¿»þ¤ËÆɤߤ䤹¤¤¤è¤¦¤Ë¡¢ 70 ʸ»úÁ°¸å¤Ç²þ¹Ô¤òÆþ¤ì¤ë¤³¤È¤ò¤ª´ê¤¤¤·¤Æ¤¤¤Þ¤¹¡£ &man.send-pr.1; ¤ÎÂå¤ï¤ê¤Ë web ¥Ù¡¼¥¹¤Î¾ã³²Êó¹ðÄó½Ð¥Õ¥©¡¼¥à ¤òÍøÍѤ¹¤ë¾ì¹ç¤â¡¢Æ±ÍͤÎÇÛθ¤¬É¬ÍפǤ¹¡£ ¥«¥Ã¥È¥¢¥ó¥É¥Ú¡¼¥¹¥ÈÁàºî¤Ï¥Æ¥­¥¹¥È¤ò¥Õ¥©¡¼¥Þ¥Ã¥È¤¹¤ë¤Î¤ËÉûºîÍѤ¬¤¢¤ë¾ì¹ç¤¬¤¢¤ë¤Î¤Çµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£ ¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢¥Ñ¥Ã¥Á¤¬Êѹ¹¤µ¤ì¤º¤ËÆϤ¯¤è¤¦¤Ë¡¢&man.uuencode.1; ¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ºÇ¸å¤Ë¡¢Äó½Ðʪ¤¬Ä¹¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¦¤Ê¤é¡¢ Äó½Ð»þ¤ËÌäÂ꤬µ¯¤­¤Æ¼º¤ï¤ì¤Æ¤·¤Þ¤¦¤³¤È¤Î¤Ê¤¤¤è¤¦¤Ë¡¢ ¥ª¥Õ¥é¥¤¥ó¤Ç½àÈ÷¤·¤Æ¤ª¤­¤Þ¤·¤ç¤¦¡£ ¤³¤ì¤ÏÆÃ¤Ë web ¥Õ¥©¡¼¥à ¤ÇÌäÂê¤Ë¤Ê¤ê¤Þ¤¹¡£
¥Ñ¥Ã¥Á¤ä¥Õ¥¡¥¤¥ë¤òźÉÕ¤¹¤ë °Ê²¼¤Ï¡¢¾ã³²Êó¹ð¤òÅŻҥ᡼¥ë¤ÇÄó½Ð¤¹¤ë¾ì¹ç¤Ë¤¢¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£ &man.send-pr.1; ¥×¥í¥°¥é¥à¤Ï¡¢ ¾ã³²Êó¹ð¤Ë¥Õ¥¡¥¤¥ë¤òźÉÕ¤¹¤ëµ¡Ç½¤òÈ÷¤¨¤Æ¤¤¤Þ¤¹¡£ ¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤Î´ðËÜ̾¾Î (¤¹¤Ê¤ï¤Á¡¢¥Ñ¥¹¤ò½ü¤¤¤¿¥Õ¥¡¥¤¥ë¤½¤Î¤â¤Î¤Î̾Á°) ¤¬°ì°Õ¤Ç¤¢¤ê¤µ¤¨¤¹¤ì¤Ð¡¢¹¥¤­¤Ê¤À¤±ÅºÉդǤ­¤Þ¤¹¡£ ¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó ¤ÇźÉÕ¤¹¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£ &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors źÉÕ¤¹¤ë¥Õ¥¡¥¤¥ë¤¬¥Ð¥¤¥Ê¥ê¤Ç¤¢¤Ã¤Æ¤â¿´ÇÛ¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¥á¡¼¥ë¥¨¡¼¥¸¥§¥ó¥È¤¬º®Í𤷤ʤ¤¤è¤¦¤Ë¡¢¼«Æ°Åª¤ËÉä¹ç²½¤µ¤ì¤Þ¤¹¡£ ¥Ñ¥Ã¥Á¤Ï context ·Á¼°¤« unified ·Á¼°¤Îº¹Ê¬¤ò &man.diff.1; ¤Î ¤« ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤ÆºîÀ®¤·¤Æ¤¯¤À¤µ¤¤ (unified ·Á¼°¤ÎÊý¤¬¹¥¤Þ¤ì¤Þ¤¹)¡£ ¥Ñ¥Ã¥Á¤òźÉÕ¤¹¤ë¾ì¹ç¡¢ ³«È¯¼Ô¤¬¤¢¤Ê¤¿¤ÎÊó¹ð¤òÆɤó¤Ç´Êñ¤Ë¥Ñ¥Ã¥Á¤òŬÍѤǤ­¤ë¤è¤¦¤Ë¡¢ ½¤Àµ¤·¤¿¥Õ¥¡¥¤¥ë¤ÎÀµ³Î¤Ê SVN ¤Î¥ê¥Ó¥¸¥ç¥óÈֹ椬ÆÃÄê¤Ç¤­¤ë¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥«¡¼¥Í¥ë¤ä¥Ù¡¼¥¹¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ë´Ø¤·¤Æ¤Ï¡¢¿·¤·¤¤¥³¡¼¥É¤Ï¤¹¤Ù¤Æ &os.current; (SVN ¤Î HEAD ¥Ö¥é¥ó¥Á) ¤Ç¥Æ¥¹¥È¤¹¤ë¤Ù¤­¤Ê¤Î¤Ç¡¢¤½¤ì¤ËÂФ¹¤ë¥Ñ¥Ã¥Á¤¬Ë¾¤Þ¤·¤¤¤Ç¤¹¡£ ŬÀÚ¤«½½Ê¬¤Ê¥Æ¥¹¥È¤¬¹Ô¤Ê¤ï¤ì¤¿¤é¡¢¤½¤Î¥³¡¼¥É¤Ï &os.stable; ¥Ö¥é¥ó¥Á¤Ë¥Þ¡¼¥¸¤Þ¤¿¤Ï°Ü¿¢¤µ¤ì¤Þ¤¹¡£ ¥Ñ¥Ã¥Á¤òźÉÕ¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯ËÜʸÃæ¤Ë´Þ¤á¤ë¾ì¹ç¡¢ ¤â¤Ã¤È¤â¤¢¤ê¤¬¤Á¤ÊÌäÂê¤Ï¡¢ ÅŻҥ᡼¥ë¥×¥í¥°¥é¥à¤Ë¤è¤Ã¤Æ¤Ï¥¿¥Ö¤ò¥¹¥Ú¡¼¥¹¤ËÊѹ¹¤·¤Æ¤·¤Þ¤¤¡¢ Makefile ¤Ë´Þ¤á¤ë¤Ä¤â¤ê¤À¤Ã¤¿¤â¤Î¤òÂæ̵¤·¤Ë¤·¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤¹¡£ ¥Ñ¥Ã¥Á¤ò Content-Transfer-Encoding: quoted-printable ¤òÍøÍѤ·¤¿ÅºÉÕ¥Õ¥¡¥¤¥ë¤È¤·¤ÆÁ÷¤é¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤³¤ì¤Ïʸ»ú¤ò¥¨¥¹¥±¡¼¥×¤·¤Æ¤·¤Þ¤¤¡¢ ¥Ñ¥Ã¥ÁÁ´ÂΤ¬»È¤¤Êª¤Ë¤Ê¤é¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£ ¤Þ¤¿¡¢¾ã³²Êó¹ð¤ÎÃæ¤Ë¾®¤µ¤Ê¥Ñ¥Ã¥Á¤ò´Þ¤á¤ë¤Î¤Ï (¤È¤ê¤ï¤±ÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¾ã³²¤ò½¤Àµ¤¹¤ë¾ì¹ç¤Ï) ÂçÄñÌäÂê¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢ Â絬ÌϤʥѥåÁ¤ä¿·¤·¤¤¥³¡¼¥É¤Î¾ì¹ç¤Ï½½Ê¬¤ÊººÆɤò¹Ô¤Ê¤Ã¤¿¸å¤Ë¥³¥ß¥Ã¥È¤¹¤Ù¤­¤Ç¤¢¤ë¤¿¤á¡¢ ¥Ñ¥Ã¥Á¤ò Web ¤ä FTP ¥µ¡¼¥Ð¤ËÃÖ¤­¡¢¤½¤Î URL ¤ò¾ã³²Êó¹ð¤Ë½ñ¤¯¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ÅŻҥ᡼¥ë¤Ë´Þ¤á¤¿¥Ñ¥Ã¥Á¤Ï¥µ¥¤¥º¤¬Â礭¤¤¤Èʬ³ä¤µ¤ì¤ë·¹¸þ¤Ë¤¢¤ê (¤È¤ê¤ï¤± GNATS ¤¬½èÍý¤Ë´Ø¤ï¤ë¤È¤­¤Ï¤½¤¦¤Ê¤ê¤Þ¤¹)¡¢ ¥Ñ¥Ã¥Á¤¬Â礭¤¤¤Û¤É¶½Ì£¤ò¤â¤Ã¤¿¿Í¤¬¤Ä¤Ê¤®Ä¾¤¹¤Î¤¬ÌÌÅݤˤʤê¤Þ¤¹¡£ ¤Þ¤¿¡¢Web ¤Ë¥Ñ¥Ã¥Á¤ò¤ª¤±¤Ð¡¢ ¸µ¤Î¾ã³²Êó¹ð¤Ø¤Î¥Õ¥©¥í¡¼¥¢¥Ã¥×¤È¤·¤Æ¥Ñ¥Ã¥ÁÁ´ÂΤòºÆÄó½Ð¤·¤Ê¤¯¤Æ¤âÊѹ¹¤Ç¤­¤Þ¤¹¡£ ºÇ¸å¤Ë¡¢Â礭¤Ê¥Ñ¥Ã¥Á¤Ï¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥µ¥¤¥º¤ò¤È¤Ë¤«¤¯Áý¤ä¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ ÊĤ¸¤é¤ì¤¿¾ã³²Êó¹ð¤Ï¼ÂºÝ¤Ë¾Ã¤µ¤ì¤ë¤³¤È¤Ï¤Ê¤¯¡¢ ÊÝ»ý¤µ¤ì¤¿¤Þ¤Þ closed ¤È¤¤¤¦°õ¤ò¤Ä¤±¤é¤ì¤ë¤À¤±¤À¤«¤é¤Ç¤¹¡£ ¤Þ¤¿¡¢¾ã³²Êó¹ð¤«¥Ñ¥Ã¥Á¼«ÂΤËÌÀ³Î¤Ë»ØÄ꤬¤Ê¤±¤ì¤Ð¡¢ ¤¢¤Ê¤¿¤¬Äó½Ð¤·¤¿¥Ñ¥Ã¥Á¤Ï½¤Àµ¤·¤¿¸µ¤Î¥Õ¥¡¥¤¥ë¤ÈƱ¤¸¾ò·ï¤Î ¥é¥¤¥»¥ó¥¹²¼¤Ë¤¢¤ë¤â¤Î¤È²¾Äꤵ¤ì¤ë¤³¤È¤Ëα°Õ¤·¤Æ¤ª¤¯¤Ù¤­¤Ç¤¹¡£
¥Æ¥ó¥×¥ì¡¼¥È¤Ëµ­Æþ¤¹¤ë ¼¡¤ÎÀá¤ÏÅŻҥ᡼¥ëÊý¼°¤Ë¤Î¤ß¤¢¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£ &man.send-pr.1; ¤òÆ°¤«¤¹¤È¥Æ¥ó¥×¥ì¡¼¥È¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ ¥Æ¥ó¥×¥ì¡¼¥È¤ÏÆÃÄê¤Î¹àÌܤ«¤éÀ®¤êΩ¤Ã¤Æ¤ª¤ê¡¢ ¤½¤Î°ìÉô¤Ë¤Ï¤¢¤é¤«¤¸¤áËä¤á¤é¤ì¤Æ¤¤¤¿¤ê¡¢ ¤½¤Î¹àÌܤÎÌÜŪ¤Î²òÀâ¤ä¤½¤³¤Ëµ­Æþ¤Ç¤­¤ëÃͤΰìÍ÷¤¬µ­ºÜ¤µ¤ì¤Æ¤¤¤¿¤ê¤·¤Þ¤¹¡£ ¥³¥á¥ó¥È¤ÎÉôʬ¤Ï¡¢¼«Ê¬¤ÇÊѹ¹¡¦ºï½ü¤·¤Ê¤¯¤Æ¤â¡¢ ¼«Æ°Åª¤Ëºï½ü¤µ¤ì¤Þ¤¹¤Î¤Ç¿´ÇÛ¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ ¥Æ¥ó¥×¥ì¡¼¥È¤ÎÀèƬ¤Ë¤¢¤ë SEND-PR: ¤È½ñ¤«¤ì¤Æ¤¤¤ë¹Ô¤Î²¼¤¬ÅŻҥ᡼¥ë¤Î¥Ø¥Ã¥À¤Ç¤¹¡£ Ä̾¤³¤ÎÉôʬ¤òÊѹ¹¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¤¬¡¢ ¾ã³²Êó¹ð¤òÁ÷¿®¤¹¤ëµ¡³£¤ä¥¢¥«¥¦¥ó¥È¤Ç ¥á¡¼¥ë¤ò½Ð¤¹¤³¤È¤Ï¤Ç¤­¤Æ¤â¼õ¤±¤È¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤¾ì¹ç¡¢ From: ¤È Reply-To: ¤Ë¼ÂºÝ¤Î¥á¡¼¥ë¥¢¥É¥ì¥¹¤òÀßÄꤹ¤Ù¤­¤Ç¤¹¡£ ¤Þ¤¿¡¢¼«Ê¬ (¤ä¾¤Î狼) ¤Ë¾ã³²Êó¹ð¤ÎÊ£À½¤òÁ÷¤ê¤¿¤¤¾ì¹ç¤Ï¡¢ ÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò Cc: ¥Ø¥Ã¥À¤ËÄɲ䷤Ƥ¯¤À¤µ¤¤¡£ ÅŻҥ᡼¥ë¤Î¿÷·¿¤Ë¤Ï¡¢¼¡¤Î 2 ¤Ä¤Î°ì¹Ô¥Õ¥£¡¼¥ë¥É¤¬¤¢¤ê¤Þ¤¹¡£ ÌõÃí ¥Õ¥£¡¼¥ë¥É¤Î°ÕÌ£¤¬Ê¬¤«¤ê°×¤¤¤è¤¦¤Ë ¥Õ¥£¡¼¥ë¥É̾¤òÌõ¤·¤Æ¤¤¤Þ¤¹¤¬¡¢ ¥Õ¥£¡¼¥ë¥É¤ÎÃͤâ´Þ¤á¤Æ ¼ÂºÝ¤Î¥Õ¥£¡¼¥ë¥É̾¤Ï±Ñʸ»ú¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ Submitter-Id (Äó½Ð¼Ô-Id): ¤³¤ì¤ÏÊѹ¹¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¤¢¤Ê¤¿¤¬ &os.stable; ¤òÆ°¤«¤·¤Æ¤¤¤ë¾ì¹ç¤Ç¤â¡¢´ûÄêÃͤǤ¢¤ë current-users ¤¬Àµ¤·¤¤¤Î¤Ç¤¹¡£ Confidential (µ¡Ì©): ¤³¤ì¤Ï no ¤Ç´û¤ËËä¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£ µ¡Ì©°·¤¤¤Î &os; ¾ã³²Êó¹ð¤È¤¤¤¦¤â¤Î¤Ï¤Ê¤¤¤¿¤á¡¢ Êѹ¹¤¹¤ë¤³¤È¤Ë°ÕÌ£¤Ï¤¢¤ê¤Þ¤»¤ó¡£— ¾ã³²Êó¹ð¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï¡¢À¤³¦Åª¤ËÇÛÉÛ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ ¼¡¤ÎÀá¤Ç¤Ï¡¢ÅŻҥ᡼¥ë¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤È web ¥¤¥ó¥¿¥Õ¥§¡¼¥¹ ¤ÎξÊý¤Ë¶¦Ä̤ʥե£¡¼¥ë¥É¤Ë¤Ä¤¤¤ÆÀâÌÀ¤·¤Þ¤¹¡£ Originator (¤¢¤Ê¤¿¤Î̾Á°): ¤¢¤Ê¤¿¤ÎËÜ̾¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£ ¤ª¹¥¤ß¤Ç¡¢Ì¾Á°¤Î¸å¤í¤ËÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò »³³ç¸Ì (< ¤È > ¤Î¤³¤È) ¤ÇÊĤ¸¤ÆÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ ÅŻҥ᡼¥ë¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ç¤Ï¡¢¤³¤ì¤ÏÉáÄÌ¡¢¸½ºß¥í¥°¥¤¥ó¤·¤Æ¤¤¤ë¥æ¡¼¥¶¤Î gecos ¥Õ¥£¡¼¥ë¥É¤ò»È¤Ã¤Æ´û¤ËËä¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£ »ØÄꤷ¤¿ÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ï¸ø³«¾ðÊó¤È¤Ê¤ê¡¢ ¥¹¥Ñ¥Þ¡¼¤ËÍøÍѤµ¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ ¥¹¥Ñ¥àÂкö¤ò»È¤¨¤ë¤è¤¦¤Ë¤·¤Æ¤ª¤¯¤«¡¢ °ì»þŪ¤Ê¥á¡¼¥ë¥¢¥«¥¦¥ó¥È¤òÍøÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ ¤·¤«¤·¡¢¤¢¤Ê¤¿¤¬Í­¸ú¤ÊÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò½ñ¤«¤Ê¤¤¤È¡¢ ¤ï¤¿¤·¤¿¤Á¤Ï¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤ËÂФ·¤Æ¼ÁÌä¤Ç¤­¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£ ÌõÃí ¤¿¤È¤¨¤Ð¡¢°Ê²¼¤Î¤è¤¦¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ From: FreeBSD Taro <FreeBSD-Taro@example.org> Organization (½ê°ÁÈ¿¥): ¤¢¤Ê¤¿¤Î¹¥¤­¤Ê¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤³¤Î¥Õ¥£¡¼¥ë¥É¤Ï²¿¤é¤«¤Î¿¼¤¤°ÕÌ£¤Ç»È¤ï¤ì¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£ Synopsis (³µÍ×): ÌäÂê¤Ë¤Ä¤¤¤Æ¤Î´Ê¤Ë¤·¤ÆÍפòÆÀ¤¿ÀâÌÀ¤ò½ñ¤­¹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£ ³µÍפϾ㳲Êó¹ð¥á¡¼¥ë¤Î¥µ¥Ö¥¸¥§¥¯¥È¤È¤·¤ÆÍøÍѤµ¤ì¤Æ¤ª¤ê¡¢ °ìÍ÷¤äÍ׻ݤˤâ»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£ ³µÍפ¬ÉÔÌÀÎƤʾ㳲Êó¹ð¤Ï̵»ë¤µ¤ì¤ë·¹¸þ¤¬¤¢¤ê¤Þ¤¹¡£ ¾å½Ò¤·¤¿¤è¤¦¤Ë¡¢¾ã³²Êó¹ð¤Ë¥Ñ¥Ã¥Á¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤Ê¤é¡¢ ³µÍפÎÀèƬ¤Ë [patch] (³Ñ³ç¸Ì¤ò´Þ¤ß¤Þ¤¹) ¤È½ñ¤¤¤Æ²¼¤µ¤¤¡£ Ports ¤Ë´Ø¤¹¤ë¾ã³²Êó¹ð¤Ç¡¢¤¢¤Ê¤¿¤¬¥á¥ó¥Æ¥Ê¤Ê¤é¡¢ [maintainer update] (³Ñ³ç¸Ì¤ò´Þ¤ß¤Þ¤¹) ¤òÄɲ䷤ơ¢ ¾ã³²Êó¹ð¤Î Class ¤ò maintainer-update ¤Ë¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ Severity (½ÅÍ×ÅÙ): non-critical (½ÅÍפǤϤʤ¤)¡¢ serious (½ÅÍ×)¡¢ critical (Ã×̿Ū) ¤Î¤É¤ì¤«¤Ç¤¹¡£ ½ÅÍ×ÅÙ¤ò²áÂç¤Ëɾ²Á¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¤¢¤Ê¤¿¤ÎÌäÂ꤬ËÜÅö¤ËÃ×̿Ū (¤¿¤È¤¨¤Ð¡¢ ¥Ç¡¼¥¿¤¬²õ¤ì¤¿¤ê¡¢-CURRENT ¤Ç°ÊÁ°¤ËÈæ¤Ù¤Æµ¡Ç½¤¬Â礭¤¯Âಽ¤·¤¿¤Ê¤É) ¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢ critical ¤ËʬÎह¤ë¤Î¤ò¡¢¤Þ¤¿Â¿¤¯¤Î¿Í¤Ë±Æ¶Á¤¹¤ë (¥«¡¼¥Í¥ë¤¬¥Ñ¥Ë¥Ã¥¯¤·¤¿¤ê¥Õ¥ê¡¼¥º¤¹¤ë¡¢ ¤Þ¤¿¤ÏÆÃÄê¤Î¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤ä¥·¥¹¥Æ¥à¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ËÌäÂ꤬¤¢¤ë) ¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢serious ¤ËʬÎह¤ë¤Î¤ò¹µ¤¨¤Æ¤¯¤À¤µ¤¤¡£ ¤Þ¤Ã¤¿¤¯Æ±¤¸¤³¤È¤ò¤ä¤Ã¤¿¿Í¤¬¤¢¤Þ¤ê¤Ë¿¤¤¤¿¤á¡¢ ÌäÂê¤Î½ÅÍ×À­¤ò¿åÁý¤·¤·¤Æ¤â¡¢É¬¤º¤·¤â &os; ³«È¯¼Ô¤¬¤½¤ÎÌäÂê¤ËÁ᤯¤È¤ê¤«¤«¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ — ¼ÂºÝ¡¢ ¤½¤ì¤¬Íýͳ¤Ç¤³¤Î¥Õ¥£¡¼¥ë¥É¤Ë¤Û¤È¤ó¤ÉÃí°Õ¤òʧ¤ï¤Ê¤¤³«È¯¼Ô¤â¤¤¤Þ¤¹¡£ GNATS ¤Î¾ðÊó¤Ï¤¹¤Ù¤Æ¸ø³«¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ ½ÅÍפʥ»¥­¥å¥ê¥Æ¥£¾å¤ÎÌäÂê¤Ï GNATS ¤ËÄó½Ð¤¹¤ë¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤½¤Î¤è¤¦¤ÊÌäÂê¤Ï¡¢ ¥»¥­¥å¥ê¥Æ¥£¥ì¥Ý¡¼¥È¥¬¥¤¥É¥é¥¤¥ó ¤Ë¤·¤¿¤¬¤Ã¤ÆÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£ Priority (Í¥Àè½ç°Ì): low (Ä㤤)¡¢ medium (Ãæ´Ö)¡¢ high (¹â¤¤) ¤Î¤É¤ì¤«¤Ç¤¹¡£ high (¹â¤¤) ¤Ï¼Â¼ÁŪ¤Ë¤¹¤Ù¤Æ¤Î &os; ¥æ¡¼¥¶¤Ë±Æ¶Á¤¹¤ë¤â¤Î¡¢ medium (Ãæ´Ö) ¤Ï¿¤¯¤Î¥æ¡¼¥¶¤Ë±Æ¶Á¤¹¤ë¤â¤Î¤Ë¸ÂÄꤹ¤Ù¤­¤Ç¤¹¡£ ¤³¤Î¥Õ¥£¡¼¥ë¥É¤Ï¤¢¤Þ¤ê¤Ë¤âÍðÍѤµ¤ì¤¿¤¿¤á¡¢ ¤¤¤Þ¤ä¤Û¤È¤ó¤É°ÕÌ£¤¬¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£ Category (ʬÎà): ŬÀÚ¤ÊʬÎà¤òÁª¤ó¤Ç¤¯¤À¤µ¤¤¡£ ¤Þ¤ººÇ½é¤Ë¹Ô¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Î¤Ï¡¢ ¤¢¤Ê¤¿¤ÎÌäÂ꤬¥·¥¹¥Æ¥à¤Î¤É¤ÎÉôʬ¤Ë´ØÏ¢¤·¤Æ¤¤¤ë¤«¤ò·è¤á¤ë¤³¤È¤Ç¤¹¡£ &os; ¤Ï´°Á´¤Ê¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ê¤Î¤Ç¡¢ ¥«¡¼¥Í¥ë¡¢É¸½à¥é¥¤¥Ö¥é¥ê¤ÎξÊý¡¢¤ª¤è¤Ó¡¢ ¼þÊեɥ饤¥Ð¡¢Â¿¤¯¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£ (¥Ù¡¼¥¹¥·¥¹¥Æ¥à) ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£ ¤µ¤é¤Ë¡¢Ports Collection ¤Ë¤Ï¿ô¿¤¯¤ÎÄɲäΥ¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ ¤½¤Î¤¿¤á¡¢ºÇ½é¤ËȽÃǤ·¤Ê¤¯¤Æ¤Ê¤é¤Ê¤¤¤Î¤Ï¡¢ ÌäÂ꤬¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Ë´ØÏ¢¤·¤Æ¤¤¤ë¤Î¤«¡¢ ¤½¤ì¤È¤â Ports Collection ¤«¤é¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿²¿¤«¤Ë´Ø·¸¤·¤Æ¤¤¤ë¤Î¤«¡¢ ¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ °Ê²¼¤Ï¥á¥¸¥ã¡¼¤Ê¥«¥Æ¥´¥ê¤Ë¤Ä¤¤¤Æ¤ÎÀâÌÀ¤Ç¤¹¡£ ¤â¤·¡¢ÌäÂ꤬¥«¡¼¥Í¥ë¡¢(ɸ½à C ¥é¥¤¥Ö¥é¥ê libc) ¥é¥¤¥Ö¥é¥ê¡¢¤Þ¤¿¤Ï¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¼þÊեɥ饤¥Ð¤Çµ¯¤³¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ Ä̾ï¤Ï kern ¥«¥Æ¥´¥ê¤ò»È¤¦¤È¤è¤¤¤Ç¤·¤ç¤¦ (²¼µ­¤ËÀâÌÀ¤¹¤ë¤è¤¦¤Ë¤¤¤¯¤Ä¤«¤ÎÎã³°¤¬¤¢¤ê¤Þ¤¹)¡£ °ìÈÌŪ¤Ë¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó 2, 3 ¤â¤·¤¯¤Ï 4 ¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¤è¤¦¤Ê¤â¤Î¤¬¤³¤³¤ËʬÎव¤ì¤Þ¤¹¡£ ÌäÂ꤬ &man.sh.1; ¤ä &man.mount.8; ¤Î¤è¤¦¤Ê¥Ð¥¤¥Ê¥ê¥×¥í¥°¥é¥à¤Çµ¯¤­¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ ¤Þ¤ººÇ½é¤Ë¡¢¤½¤ì¤é¤Î¥×¥í¥°¥é¥à¤¬¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¤â¤Î¤«¡¢ ¤â¤·¤¯¤Ï Ports Collection ¤«¤éÄɲ䵤줿¤â¤Î¤Ê¤Î¤«¤òȽÃǤ·¤Æ¤¯¤À¤µ¤¤¡£ ¤è¤¯¤ï¤«¤Ê¤é¤±¤ì¤Ð¡¢ whereis programname ¤È¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ &os; ¤Î Ports Collection ¤Î´·Îã¤Ç¤Ï¡¢ (¥·¥¹¥Æ¥à´ÉÍý¼Ô¤Ï¡¢¤³¤ÎÀßÄê¤òÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬) ¤¹¤Ù¤Æ¤Î¤â¤Î¤Ï /usr/local °Ê²¼¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£ ¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¡¢ports ¥«¥Æ¥´¥ê¤ò»È¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹ (¤â¤·¡¢¤½¤Î port ¤Î¥«¥Æ¥´¥ê¤¬ www ¤Ç¤¢¤Ã¤Æ¤âÅö¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£ÀâÌÀ¤¬²¼¤Ë¤¢¤ê¤Þ¤¹)¡£ ¤â¤·¡¢¥³¥Þ¥ó¥É¤Î¾ì½ê¤¬ /bin, /usr/bin, /sbin ¤â¤·¤¯¤Ï /usr/sbin ¤Ç¤¢¤ì¤Ð¡¢ ¤½¤ì¤Ï¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î°ìÉô¤Ç¤¹¤Î¤Ç¡¢ bin ¥«¥Æ¥´¥ê¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤ (&man.gcc.1; ¤Î¤è¤¦¤Ê¤¤¤¯¤Ä¤«¤Î¥×¥í¥°¥é¥à¤Ç¤Ï¡¢gnu ¥«¥Æ¥´¥ê¤ò»È¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢º£¤Î»þÅÀ¤Ç¤Ïµ¤¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤)¡£ ¤³¤Î¥«¥Æ¥´¥ê¤Ë¤Ï¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó 1 ¤Þ¤¿¤Ï 8 ¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¤¹¤Ù¤Æ¤¬Ê¬Îव¤ì¤Þ¤¹¡£ ¤â¤·¡¢¥¨¥é¡¼¤¬¥¹¥¿¡¼¥È¥¢¥Ã¥× (rc) ¥¹¥¯¥ê¥×¥È¤Çµ¯¤­¤Æ¤¤¤ë¡¢¤Þ¤¿¤Ï¾¤ÎÈó¼Â¹Ô·Á¼°¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ë´ØÏ¢¤·¤¿¤è¤¦¤Ê¤â¤Î¤¢¤ì¤Ð¡¢ conf (configuration) ¤¬Å¬Àڤʥ«¥Æ¥´¥ê¤Ç¤·¤ç¤¦¡£ ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó 5 ¤Ë½ñ¤«¤ì¤Æ¤¤¤ëÆâÍƤ¬¤³¤³¤ËʬÎव¤ì¤Þ¤¹¡£ ÌäÂ꤬¥É¥­¥å¥á¥ó¥È (article, book ¤â¤·¤¯¤Ï¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸) ¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢docs ¤¬Å¬Àڤʥ«¥Æ¥´¥ê¤Ç¤¹¡£ ÌäÂ꤬ FreeBSD ¥¦¥§¥Ö¥Ú¡¼¥¸ ¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢www ¤òÁªÂò¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤â¤·¡¢ÌäÂ꤬ www/someportname ¤È¤¤¤¦Ì¾Á°¤Î port ¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤Ã¤Æ¤â¡¢ ports ¥«¥Æ¥´¥ê¤òÁªÂò¤·¤Æ¤¯¤À¤µ¤¤¡£ ¤µ¤é¤Ë¤¤¤¯¤Ä¤«¤ÎÆÃÊ̤ʥ«¥Æ¥´¥ê¤¬¤¢¤ê¤Þ¤¹¡£ ÌäÂ꤬ kern ¤ËʬÎव¤ì¤ë¤è¤¦¤Ê¤â¤Î¤Ç¤â¡¢ USB ¥µ¥Ö¥·¥¹¥Æ¥à¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢usb ¤¬Å¬Àڤʥ«¥Æ¥´¥ê¤Ç¤¹¡£ ÌäÂ꤬ kern ¤ËʬÎव¤ì¤ë¤è¤¦¤Ê¤â¤Î¤Ç¤â¡¢ ¥¹¥ì¥Ã¥É¤Î¥é¥¤¥Ö¥é¥ê¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢threads ¤¬Å¬Àڤʥ«¥Æ¥´¥ê¤Ç¤¹¡£ ÌäÂ꤬¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤ËʬÎव¤ì¤ë¤è¤¦¤Ê¤â¤Î¤Ç¤â¡¢ &posix; ¤Î¤è¤¦¤Êɸ½à¤Ø¤Î½àµò¤Ë´ØÏ¢¤·¤¿¤â¤Î¤Ç¤¢¤ì¤Ð¡¢ standards ¤¬Å¬Àڤʥ«¥Æ¥´¥ê¤Ç¤¹¡£ ¤½¤Î¾¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¤Ï¡¢°Ê²¼¤Î¥«¥Æ¥´¥ê¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ ÌäÂ꤬¡¢¤¢¤Ê¤¿¤Î»È¤Ã¤Æ¤¤¤ë¥×¥í¥»¥Ã¥µ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤Î¤ßµ¯¤³¤ë¤È³Î¿®¤Ç¤­¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¸ÇÍ­¤Î¥«¥Æ¥´¥ê¤«¤éÁª¤ó¤Ç¤¯¤À¤µ¤¤¡£ Îɤ¯»È¤ï¤ì¤Æ¤¤¤ë 32-bit ¥â¡¼¥É¤Î Intel ¸ß´¹¥³¥ó¥Ô¥å¡¼¥¿¤Ï i386, 64-bit ¥â¡¼¥É¤ÇÆ°ºî¤¹¤ë AMD ¥Þ¥·¥ó¤Î¾ì¹ç¤Ï amd64 (¤³¤ÎʬÎà¤Ë¤Ï¡¢EMT64 ¥â¡¼¥É¤ÇÆ°ºî¤¹¤ë Intel ¸ß´¹¤Î¥³¥ó¥Ô¥å¡¼¥¿¤â´Þ¤Þ¤ì¤Þ¤¹) ¤òÁªÂò¤·¤Æ¤¯¤À¤µ¤¤¡£ Ä̾ï¤Ï¤¢¤Þ¤ê¤è¤¯»È¤ï¤ì¤Ê¤¤¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ë¤Ï¡¢ arm, ia64, powerpc ¤ª¤è¤Ó sparc64 ¤¬¤¢¤ê¤Þ¤¹¡£ ¤³¤ì¤é¤Î¥«¥Æ¥´¥ê¤Ï¡¢¤è¤¯¤ï¤«¤é¤Ê¤¤ ÌäÂê¤ËÂФ·¤Æ´Ö°ã¤Ã¤Æ¤è¤¯»È¤ï¤ì¤Þ¤¹¡£ ¤È¤ê¤¢¤¨¤º¿ä¬¤ÇÁª¤ó¤Ç¤·¤Þ¤¦¤Î¤Ç¤Ï¤Ê¤¯¡¢¤½¤Î¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï misc ¤òÁª¤ó¤Ç¤¯¤À¤µ¤¤¡£ ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¥«¥Æ¥´¥ê¤ÎÀµ¤·¤¤»È¤¤Êý ¤¢¤Ê¤¿¤Ï°ìÈÌŪ¤Ê PC ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Î¥Þ¥·¥ó¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢ ÆÃÄê¤Î¥Á¥Ã¥×¥»¥Ã¥È¤äÆÃÄê¤Î¥Þ¥¶¡¼¥Ü¡¼¥É¤ÎÌäÂê¤Ë¤Ö¤Ä¤«¤Ã¤¿¤è¤¦¤Ç¤¹¡£ ¤³¤Î¾ì¹ç¤Ï¡¢i386 ¤¬¤Õ¤µ¤ï¤·¤¤Ê¬Îà¤Ë¤Ê¤ê¤Þ¤¹¡£ ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¥«¥Æ¥´¥ê¤ÎÀµ¤·¤¯¤Ê¤¤»È¤¤Êý Îã: °ìÈÌŪ¤Ê¥Ð¥¹ÍѤÎÄɲäμþÊÕ¥«¡¼¥É¤ä¡¢ ÆÃÄê¤Î¼ïÎà¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ÇÌäÂ꤬¤¢¤ê¤Þ¤¹¡£ ¤³¤Î¾ì¹ç¤Ï¡¢Ê£¿ô¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ë±Æ¶Á¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¡¢ kern ¤¬¤Õ¤µ¤ï¤·¤¤Ê¬Îà¤Ë¤Ê¤ê¤Þ¤¹¡£ ¤â¤·¡¢ÌäÂê¤ò¤É¤ÎʬÎà¤Ëʬ¤±¤ì¤Ð¤è¤¤¤Î¤«¤ï¤«¤é¤Ê¤±¤ì¤Ð (¾å¤ÇÀâÌÀ¤·¤¿¤â¤Î¤ËÅö¤Æ¤Ï¤Þ¤é¤Ê¤±¤ì¤Ð)¡¢ misc ¥«¥Æ¥´¥ê¤òÁª¤ó¤Ç¤¯¤À¤µ¤¤¡£ ¤³¤Î¥«¥Æ¥´¥ê¤òÁªÂò¤¹¤ëÁ°¤Ë¡¢¤Þ¤ººÇ½é¤Ë &a.questions; ¤Ç¡¢ ½õ¤±¤òµá¤á¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ ¸ºß¤¹¤ë¥«¥Æ¥´¥ê¤ÎÃ椫¤éËÜÅö¤ËÁªÂò¤¹¤Ù¤­¤â¤Î¤ò¥¢¥É¥Ð¥¤¥¹¤µ¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ °Ê²¼¤Ë¸½ºß¤ÎʬÎà°ìÍ÷¤ò¼¨¤·¤Þ¤¹ ( ¤«¤é¤â¤Ã¤Æ¤­¤Æ¤¤¤Þ¤¹)¡£ advocacy: &os; ¤ÎÀ¤´ÖŪ¤Ê¥¤¥á¡¼¥¸¤Ë´Ø¤¹¤ëÌäÂê¡£ ¤â¤Ï¤äÍѤ¤¤é¤ì¤Þ¤»¤ó¡£ amd64: AMD64 ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ arm: ARM ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ bin: ´ðËÜ¥·¥¹¥Æ¥à¤Ë´Þ¤Þ¤ì¤ë¥æ¡¼¥¶¥é¥ó¥É¥×¥í¥°¥é¥à¤Ë´Ø¤¹¤ëÌäÂê¡£ conf: ÀßÄê¥Õ¥¡¥¤¥ë¤ä¡¢´ûÄêÃͤʤɤ˴ؤ¹¤ëÌäÂê¡£ docs: ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¡¢¥ª¥ó¥é¥¤¥óʸ½ñ¤Ë´Ø¤¹¤ëÌäÂê¡£ gnu: &man.gcc.1; ¤ä &man.grep.1; ¤Ê¤É¤Î¡¢¼è¤ê¹þ¤Þ¤ì¤¿ GNU ¥½¥Õ¥È¥¦¥§¥¢¤Ë´Ø¤¹¤ëÌäÂê¡£ i386: &i386; ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ ia64: ia64 ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ java: &java; ²¾ÁÛ¥Þ¥·¥ó¤Ë´Ø¤¹¤ëÌäÂê¡£ kern: ¥«¡¼¥Í¥ë¡¢(ÆÃÄê¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥àÍѤǤϤʤ¤) ¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤ä¡¢ ¥Ù¡¼¥¹¥·¥¹¥Æ¥à¤Î¥é¥¤¥Ö¥é¥ê¤Ë¤Ë´Ø¤¹¤ëÌäÂê¡£ misc: ¤³¤ì¤é¤ÎʬÎà¤ËŬ¹ç¤·¤Ê¤¤¤½¤Î¾¤ÎʬÎà¡£(¤Ê¤ª¡¢ ËÜÅö¤Ë¤³¤³¤ËʬÎव¤ì¤ë¤Ù¤­¤â¤Î¤Ï¡¢ ¥ê¥ê¡¼¥¹¤ª¤è¤Ó¥Ó¥ë¥É¤Î¤¿¤á¤Î´ðÈפò¤Î¤¾¤±¤Ð¡¢ ¤Û¤È¤ó¤É¤¢¤ê¤Þ¤»¤ó¡£HEAD ¤Ë¤ª¤±¤ë°ì»þŪ¤Ê¥Ó¥ë¥É¤Î¼ºÇԤϤ³¤³¤ËʬÎह¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ ¤Þ¤¿¡¢¤³¤³¤ËʬÎह¤ë¤È¸«¼º¤ï¤ì¤ä¤¹¤¤¤Ç¤¹)¡£ ports: Ports Collection ¤Ë´Ø¤¹¤ëÌäÂê¡£ powerpc: &powerpc; ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ sparc64: &sparc64; ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤ÎÌäÂê¡£ standards: ɸ½àµ¬³Ê¤Ø¤ÎŬ¹çÌäÂê¡£ threads: &os; ¤Î¥¹¥ì¥Ã¥É¼ÂÁõ (ÆÃ¤Ë &os.current; ¾å¤Î¤â¤Î) ¤Ë´Ø¤¹¤ëÌäÂê¡£ usb: &os; ¤Î USB ¼ÂÁõ¤Ë´Ø¤¹¤ëÌäÂê¡£ www: &os; ¥¦¥§¥Ö¥µ¥¤¥È¤Ø¤ÎÊѹ¹¤È²þÁ±¡£ Class: °Ê²¼¤«¤é°ì¤Ä¤òÁª¤ó¤Ç¤¯¤À¤µ¤¤¡£ sw-bug: ¥½¥Õ¥È¥¦¥§¥¢¤Î¥Ð¥°¡£ doc-bug: ʸ½ñÃæ¤Î´Ö°ã¤¤¡£ change-request: µ¡Ç½¤ÎÄɲä䡢´û¸¤Îµ¡Ç½¤ÎÊѹ¹¤Ë¤Ä¤¤¤Æ¤ÎÍ×˾¡£ update: ports ¤ä¤½¤Î¾¤Î´ó£¥½¥Õ¥È¥¦¥§¥¢¤ËÂФ¹¤ë¹¹¿·¡£ maintainer-update: ¤¢¤Ê¤¿¤¬Êݼ餷¤Æ¤¤¤ë ports ¤Î¹¹¿·¡£ Release: ¤¢¤Ê¤¿¤¬Æ°ºî¤µ¤»¤Æ¤¤¤ë &os; ¤Î¥Ð¡¼¥¸¥ç¥ó¡£ ¤³¤ì¤Ï &man.send-pr.1; ¤ò»È¤¦¤È¼«Æ°Åª¤Ë½ñ¤­¹þ¤Þ¤ì¤Þ¤¹¤¬¡¢ ¤¢¤Ê¤¿¤¬¾ã³²¤¬µ¯¤­¤Æ¤¤¤ë¤â¤Î¤È°ã¤¦¥·¥¹¥Æ¥à¤«¤é¾ã³²Êó¹ð¤òÁ÷¿®¤¹¤ë¾ì¹ç¤Ë¸Â¤ê¡¢ Êѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ ºÇ¸å¤Ë¡¢°ìÏ¢¤ÎÊ£¿ô¹Ô¥Õ¥£¡¼¥ë¥É¤¬¤¢¤ê¤Þ¤¹¡£ Environment (´Ä¶­): ÌäÂ꤬ȯÀ¸¤·¤¿´Ä¶­¤ò²Äǽ¤Ê¸Â¤êÀµ³Î¤Ëµ­½Ò¤¹¤Ù¤­¤Ç¤¹¡£ ¤³¤³¤Ë¤Ï¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ð¡¼¥¸¥ç¥ó¡¢ ÆÃÄê¤Î¥×¥í¥°¥é¥à¤Î¥Ð¡¼¥¸¥ç¥ó¤Þ¤¿¤ÏÌäÂ꤬¤¢¤ë¥Õ¥¡¥¤¥ë¡¢ ¤½¤·¤Æ¥·¥¹¥Æ¥à¤ÎÀßÄê¤Ê¤É¤Î¤è¤¦¤Ê´Ø·¸¤¹¤ë¹àÌÜ¡¢ ÌäÂê¤Ë±Æ¶Á¤òµÚ¤Ü¤¹¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤½¤Î¾¤Î ¥½¥Õ¥È¥¦¥§¥¢¤Ê¤É¤¬´Þ¤Þ¤ì¤Þ¤¹¡£— ¼êû¤Ë¤¤¤¦¤Ê¤é¡¢¤½¤ÎÌäÂ꤬À¸¤¸¤ë´Ä¶­¤òºÆ¹½ÃÛ¤¹¤ë¤¿¤á¤Ë¡¢ ³«È¯¼Ô¤¬ÃΤé¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤¹¤Ù¤Æ¤Ç¤¹¡£ Description: ¤¢¤Ê¤¿¤¬·Ð¸³¤·¤¿ÌäÂê¤Î´°Á´¤ÇÀµ³Î¤ÊÀâÌÀ¡£ ³«È¯¼Ô¤¬¸í²ò¤·¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Ê¤¤¤Î¤Ç¡¢ ÌäÂê¤Î¸¶°ø¤Ë¤Ä¤¤¤ÆÀµ¤·¤¯ÄÉÀפ¬¤Ç¤­¤¿¤È³Î¿®¤·¤Æ¤¤¤Ê¤¤¸Â¤ê ¿ä¬¤ÏÈò¤±¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ How-To-Repeat: ÌäÂê¤òºÆ¸½¤µ¤»¤ë¤¿¤á¤Ë¼è¤ëɬÍפΤ¢¤ë¹ÔÆ°¤Î³µÍס£ Fix: ¤Ç¤­¤ì¤Ð¥Ñ¥Ã¥Á¤«¡¢¾¯¤Ê¤¯¤È¤â²óÈòÊýË¡¤òµ­½Ò¤¹¤ë (Ʊ¤¸ÌäÂê¤ò²óÈò¤¹¤ëÊýË¡¤È¤·¤Æ¾¤Î¿Íã¤Î½õ¤±¤Ë¤Ê¤ë¤À¤±¤Ç¤Ï¤Ê¤¯¡¢ ³«È¯¼Ô¤¬ÌäÂê¤Î¸¶°ø¤òÍý²ò¤¹¤ëÌò¤ËΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó) ¤Ù¤­¤Ç¤¹¤¬¡¢ ¤Ï¤Ã¤­¤ê¤È¤·¤¿¥¢¥¤¥Ç¥¢¤¬¤Ê¤±¤ì¤Ð³«È¯¼Ô¤¬»×º÷¤ò¤á¤°¤é¤¹¤¿¤á¤Ë¡¢ ¤³¤Î¥Õ¥£¡¼¥ë¥É¤Ï¶õ¤Ë¤·¤Æ¤ª¤±¤ÐÎɤ¤¤Ç¤·¤ç¤¦¡£
¾ã³²Êó¹ð¤òÁ÷¿®¤¹¤ë &man.send-pr.1; ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç ¥Æ¥ó¥×¥ì¡¼¥È¤òËä¤á¡¢Êݸ¤·¤Æ¥¨¥Ç¥£¥¿¤ò½ªÎ»¤¹¤ë¤È¡¢ &man.send-pr.1; ¤Ï s)end, e)dit or a)bort? ¤Èɽ¼¨¤·¤Æ»Ø¼¨¤òµá¤á¤Þ¤¹¡£ s ¤ò²¡¤»¤Ð¾ã³²Êó¹ð¤ÎÄó½Ð¤Ë¿Ê¤á¤Þ¤¹¤·¡¢ e ¤À¤È¥¨¥Ç¥£¥¿¤¬ºÆ¤Ó¼Â¹Ô¤µ¤ì¡¢ ¤Ò¤­¤Ä¤Å¤­ÊÔ½¸¤Ç¤­¤Þ¤¹¡£ a ¤Ê¤éºî¶È¤òÃæ»ß¤·¤Þ¤¹¡£ abort ¤òÁªÂò¤·¤¿¾ì¹ç¡¢¤¤¤Þ¤Þ¤Ç½ñ¤¤¤Æ¤¤¤¿¾ã³²Êó¹ð¤Ï¥Ç¥£¥¹¥¯¤Ë»Ä¤ê¤Þ¤¹¤Î¤Ç (&man.send-pr.1; ¤Ï½ªÎ»Á°¤Ë¤½¤Î¥Õ¥¡¥¤¥ë̾¤ò¼¨¤·¤Þ¤¹)¡¢ ²Ë¤Ê»þ¤Ë¤½¤ì¤òÊÔ½¸¤·¤¿¤ê¡¢¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï ¤è¤ê¥Í¥Ã¥È¥ï¡¼¥¯ÀܳÀ­¤Î¤è¤¤¥·¥¹¥Æ¥à¤Ë»ý¤Ã¤Æ¤¤¤¯¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£ ¤³¤Îºî¶È¥Õ¥¡¥¤¥ë¤Ï¡¢&man.send-pr.1; ¤Î ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤ÆÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ &prompt.user; send-pr -f ~/my-problem-report ¾åµ­¤ÎÁàºî¤Ç¤Ï¡¢»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤ß¡¢ ½ñ¼°¤¬Àµ¤·¤¤¤«¸¡¾Ú¤·¡¢¥Õ¥¡¥¤¥ëÃæ¤Î¥³¥á¥ó¥ÈÉôʬ¤ò¼è¤ê½ü¤¤¤Æ¡¢ ¾ã³²Êó¹ð¤¬Á÷¿®¤µ¤ì¤Þ¤¹¡£ Web ¥Õ¥©¡¼¥à ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç submit ¤ò²¡¤¹Á°¤Ë¡¢ ¤½¤Î¥Ú¡¼¥¸¤Ë²èÁü¤Çɽ¼¨¤µ¤ì¤Æ¤¤¤ë¥Æ¥­¥¹¥È¤ò¥Õ¥£¡¼¥ë¥É¤Ëµ­Æþ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ ¤³¤ÎÉÔ¹¬¤Ê¼ê½ç¤Ï¼«Æ°²½¤µ¤ì¤¿¥·¥¹¥Æ¥à¤ä¡¢ ¸í¤ê¤ò¶µ¤¨¤é¤ì¤¿¿Í¤¿¤Á¤Ë¤è¤ë¸íÍѤ¬¤¢¤Ã¤¿¤¿¤á¤ËƳÆþ¤µ¤ì¤Þ¤·¤¿¡£ ¤³¤ì¤Ï¡¢Ã¯¤â¤¬·ù¤¦É¬Í×°­¤Ê¤Î¤Ç¤¹¡£ ¤ª´ê¤¤¤Ç¤¹¤«¤é¡¢¤³¤ì¤ò¼è¤ê½ü¤¯¤è¤¦¤ËÍ×˾¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ ¤Ê¤ª¡¢submit ¤ò²¡¤¹Á°¤Ë¡¢ ¤É¤³¤«¤Ë¤¢¤Ê¤¿¤¬½ñ¤¤¤¿ÆâÍƤòÊݸ¤·¤Æ¤ª¤¯¤³¤È¤ò ¶¯¤¯¾©¤á¤Þ¤¹¡£ ¥æ¡¼¥¶¤¬¤è¤¯½Ð¤¯¤ï¤¹ÌäÂê¤Ë¡¢web ¥Ö¥é¥¦¥¶¤¬¡¢ ¥­¥ã¥Ã¥·¥å¤«¤é̵¸ú¤Ë¤Ê¤Ã¤¿²èÁü¤òɽ¼¨¤·¤Æ¤·¤Þ¤¦¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ ¤¢¤Ê¤¿¤¬¤½¤¦¤¤¤¦ÌܤËÁø¤Ã¤Æ¤·¤Þ¤Ã¤¿¤é¡¢ ¤¢¤Ê¤¿¤ÎÊó¹ð¤ÏµñÈݤµ¤ì¤Æ¤·¤Þ¤¤¡¢ ½ñ¤¤¤¿¤â¤Î¤ò¼º¤Ã¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£ ²¿¤é¤«¤ÎÍýͳ¤Ç²èÁü¤¬¸«¤é¤ì¤º¡¢¤Þ¤¿ &man.send-pr.1; ¤â»È¤¨¤Ê¤¤¾ì¹ç¤Ï¡¢¤´ÌÂÏǤò¤ª¤«¤±¤·¤ÆÂçÊÑ¿½¤·Ìõ¤¢¤ê¤Þ¤»¤ó¤¬¡¢ ¾ã³²Êó¹ð¤ò bugbuster ¥Á¡¼¥à¤Ë freebsd-bugbusters@FreeBSD.org °¸¤ÇÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
¥Õ¥©¥í¡¼¥¢¥Ã¥× ¾ã³²Êó¹ð¤òÄó½Ð¤¹¤ë¤È¡¢ ¾ã³²Êó¹ð¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿ÄÉÀ×ÍѤÎÈÖ¹æ¤È¾õ¶·¤ò³Îǧ¤¹¤ë¤¿¤á¤ËÍøÍѤ¹¤ë URL ¤ò´Þ¤à¡¢³Îǧ¤Î¤¿¤á¤ÎÅŻҥ᡼¥ë¤¬Á÷¤é¤ì¤Æ¤¯¤ë¤Ç¤·¤ç¤¦¡£ ¤Á¤ç¤Ã¤Ô¤ê±¿¤¬¤è¤±¤ì¤Ð¡¢ 狼¤¬¤¢¤Ê¤¿¤ÎÌäÂê¤Ë¶½Ì£¤ò»ý¤Ã¤Æ¤½¤ì¤Ë¼è¤êÁȤ⤦¤È¤¹¤ë¤Ç¤·¤ç¤¦¤·¡¢ ¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¤Ê¤¼¤½¤ì¤¬ÌäÂê¤Ç¤Ê¤¤¤«ÀâÌÀ¤·¤Æ¤¯¤ì¤ë¤Ç¤·¤ç¤¦¡£ ¾õ¶·¤Ë²¿¤«¤ÎÊѹ¹¤¬¤¢¤ë¤È¡¢ 狼¤¬¤¢¤Ê¤¿¤Î¾ã³²Êó¹ð¤ò¿³ººÄÉÀ×¾õÂ֤ˤ·¤Æ¡¢ ²¿¤é¤«¤Î¥³¥á¥ó¥È¤«¥Ñ¥Ã¥Á¤ÎÄÌÃΤò¼«Æ°Åª¤Ë¼õ¤±¤È¤ë¤Ç¤·¤ç¤¦¡£ 狼¤¬¤¢¤Ê¤¿¤ËÄɲþðÊó¤òµá¤á¤¿¤ê¡¢ ºÇ½é¤ÎÊó¹ð¤ÎÃæ¤Ç¸ÀµÚ¤·¤Ê¤«¤Ã¤¿¤â¤Î¤ò»×¤¤½Ð¤·¤¿¤êȯ¸«¤·¤¿¤é¡¢ ¼¡¤Î 2 ¤Ä¤ÎÊýË¡¤Î¤É¤Á¤é¤«¤Ç¡¢¥Õ¥©¥í¡¼¥¢¥Ã¥×¤òÄó½Ð¤·¤Æ¤¯¤À¤µ¤¤¡£ °ìÈֳڤʤΤϡ¢ ¡¡ ¾ã³²Êó¹ð¸¡º÷¥Ú¡¼¥¸ ¤«¤é¹Ô¤±¤ë¡¢¤½¤ì¤¾¤ì¤Î¾ã³²Êó¹ð¤Î web ¥Ú¡¼¥¸¤Î¥Õ¥©¥í¡¼¥¢¥Ã¥×¥ê¥ó¥¯¤òÍøÍѤ¹¤ë¤³¤È¤Ç¤¹¡£ ¤³¤Î¥ê¥ó¥¯¤ò¥¯¥ê¥Ã¥¯¤¹¤ë¤È¡¢ (¥Ö¥é¥¦¥¶¤¬¤½¤¦¤¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð) Àµ¤·¤¤ To: ¤ª¤è¤Ó Subject: ¹Ô¤òËä¤á¤¿ÅŻҥ᡼¥ë²èÌ̤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ ¤Þ¤¿¤Ï¡¢ ¥Ð¥°ÄÉÀ×¥·¥¹¥Æ¥à¤¬¤É¤Î¾ã³²Êó¹ð¤Ë²Ã¤¨¤ì¤Ð¤è¤¤¤«È½ÃǤǤ­¤ë¤è¤¦¤Ë¡¢ ·ï̾¤ËÄÉÀ×Èֹ椬´Þ¤Þ¤ì¤Æ¤¤¤ë¤«³Î¤«¤á¤Æ &a.bugfollowup; ¤Ë¥á¡¼¥ë¤òÁ÷¤ë¤À¤±¤Ç¤â¹½¤¤¤Þ¤»¤ó¡£ ÄÉÀ×ÈÖ¹æ¤ò ´Þ¤á¤Ê¤¤ ¤È¡¢ GNATS ¤Ïº®Í𤷤ơ¢¿·µ¬¤Ë¾ã³²Êó¹ð¤òÀ¸À®¤·¤Æ¡¢¤½¤ì¤ò GNATS ´ÉÍý¼Ô¤Ë³ä¤êÅö¤Æ¤Þ¤¹¡£ ¤½¤¦¤Ê¤ë¤È¡¢Ã¯¤«¤¬¥´¥ß¤òÊÒÉÕ¤±¤Ë¤¯¤ë¤Þ¤Ç¡¢ ²¿Æü¤Þ¤¿¤Ï²¿½µ´Ö¤â¸«¼º¤ï¤ì¤¿¤Þ¤Þ¤Ë¤Ê¤ê¤Þ¤¹¡£ ´Ö°ã¤Ã¤¿¤ä¤êÊý Subject: that PR I sent Àµ¤·¤¤¤ä¤êÊý Subject: Re: ports/12345: compilation problem with foo/bar ÌäÂ꤬¤Ê¤¯¤Ê¤Ã¤¿¤Î¤Ë¾ã³²Êó¹ð¤Î½èÍý¤¬´°Î»¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ ¤Ç¤­¤ì¤Ð¡¢¤É¤Î¤è¤¦¤Ë¡¢¤¤¤Ä¡¢ÌäÂê¤ò²ò·è¤Ç¤­¤¿¤«¤ÎÀâÌÀ¤òź¤¨¤Æ¡¢ ¤³¤Î¾ã³²Êó¹ð¤ÏµÄÏÀ¤ò½ªÎ»¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡¢¤È (Á°½Ò¤ÎÊýË¡¤Ç) ¥Õ¥©¥í¡¼¥¢¥Ã¥×¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
ÌäÂ꤬µ¯¤­¤¿¤é ¤Û¤È¤ó¤É¤Î¾ã³²Êó¹ð¤Ï¥·¥¹¥Æ¥à¤Ç½èÍý¤µ¤ì¡¢ ¤¿¤À¤Á¤Ë¼õ¤±ÉÕ¤±¤é¤ì¤Þ¤¹¡£¤·¤«¤·¡¢GNATS ¤Î½èÍý¤¬ÃÙ¤ì¤Æ¡¢ 10 ʬ°Ê¾å³Îǧ¤ÎÅŻҥ᡼¥ë¤¬ÆϤ«¤Ê¤¤¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ ¤·¤Ð¤é¤¯¤ªÂÔ¤Á¤¯¤À¤µ¤¤¡£ ¤µ¤é¤Ë¡¢GNATS ¤ÏÆþÎϤò¤¹¤Ù¤ÆÅŻҥ᡼¥ë¤Ç¼õ¤±¼è¤ë¤Î¤Ç¡¢ &os; ¤¬ÅϤµ¤ì¤¿¥á¡¼¥ë¤ò¤¹¤Ù¤Æ spam ¥Õ¥£¥ë¥¿¤ËÄ̤·¤Æ¤â±Æ¶Á¤¬½Ð¤Þ¤¹¡£ 1, 2 »þ´Ö¤ÇÊÖÅú¤ò¼õ¤±¼è¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ spam ¥Õ¥£¥ë¥¿¤Ë°ú¤Ã¤«¤«¤Ã¤¿²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ ¤½¤Î¾ì¹ç¤Ï¡¢bugmeister@FreeBSD.org ¤Ë¥á¡¼¥ë¤òÁ÷¤Ã¤Æ GNATS ´ÉÍý¼Ô¤Î½õÎϤò¤â¤È¤á¤Æ¤¯¤À¤µ¤¤¡£ spam ¤ÎȽÃÇ´ð½à¤Ë¡¢(¾ã³²Êó¹ð¤Ë HTML ¤ò¤¤¤ì¤ëɬÍפϤʤ¤¤Ë¤â¤«¤«¤ï¤é¤º) spam ¤Ë¤è¤¯¤ß¤é¤ì¤ë HTML ¥á¡¼¥ë¤Ç¤¢¤ë¤«¤É¤¦¤«¸«¤ë¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ ¾ã³²Êó¹ð¤òÁ÷¤ëºÝ¤Ë¤Ï¡¢HTML ¥á¡¼¥ë¤Ë¤·¤Ê¤¤¤³¤È¤ò¶¯¤¯¿ä¾©¤·¤Þ¤¹¡£ ¥Õ¥£¥ë¥¿¤Ë¤Ò¤Ã¤«¤«¤ë²ÄǽÀ­¤¬¹â¤¤¤À¤±¤Ç¤Ê¤¯¡¢ ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¤´¤Á¤ã¤´¤Á¤ã¤Ë¤·¤Æ¤·¤Þ¤¦¤À¤±¤È¤¤¤¦²ÄǽÀ­¤¬¹â¤¤¤«¤é¤Ç¤¹¡£ ÀΤʤ¬¤é¤Î¥Æ¥­¥¹¥È¥á¡¼¥ë¤ÎÊý¤¬¤º¤Ã¤È¤è¤¤¤Ç¤·¤ç¤¦¡£ ¤Þ¤ì¤Ë¡¢¾ã³²Êó¹ð¤¬¼õ¤±ÉÕ¤±¤é¤ì¡¢ÄÉÀ×Èֹ椬ÉÕ¤¤¤¿¤Î¤Ë¡¢ web ¤Î¸¡º÷¥Ú¡¼¥¸¤Î¤É¤Î°ìÍ÷¤Ë¤âɽ¼¨¤µ¤ì¤Ê¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ ¤½¤Î¾ì¹ç¡¢¤ª¤½¤é¤¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Îº÷°ú¤¬¥Ç¡¼¥¿¥Ù¡¼¥¹¤½¤Î¤â¤Î¤È Ʊ´ü¤¬³°¤ì¤Æ¤·¤Þ¤Ã¤¿¤Î¤À¤È»×¤ï¤ì¤Þ¤¹¡£ ËÜÅö¤Ë¤½¤¦¤«³Îǧ¤¹¤ëÊýË¡¤Ï¡¢ ÆÃÄê¤Î¾ã³²Êó¹ð¤ò¸«¤ë¥Ú¡¼¥¸¤Ë¤¤¤Ã¤Æ¡¢ ¾ã³²Êó¹ð¤¬½Ð¤Æ¤¯¤ë¤«³Îǧ¤¹¤ë¤³¤È¤Ç¤¹¡£ ¾ã³²Êó¹ð¤¬Â¸ºß¤¹¤ë¤Ê¤é¡¢bugmeister@FreeBSD.org ¤Ë¥á¡¼¥ë¤ò½Ð¤·¤Æ GNATS ´ÉÍý¼Ô¤ËÃΤ餻¤Æ¤¯¤À¤µ¤¤¡£ ¤¿¤À¤·¡¢Äê´üŪ¤Ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤òºÆ¹½ÃÛ¤¹¤ë cron ¥¸¥ç¥Ö¤¬Áö¤Ã¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢µÞ¤¤¤Ç¤¤¤ë¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢ Æäˤʤˤ⤹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
¤µ¤é¤Ê¤ëÆɤߤâ¤Î ´°Á´¤Ê¤â¤Î¤È¤Ï¤¤¤¨¤Þ¤»¤ó¤¬¡¢ ŬÀڤʾ㳲Êó¹ð¤Î½ñ¤­Êý¤È¼ê½ç¤Ë¤Ä¤¤¤Æ´ØÏ¢¤¹¤ë»ñÎÁ¤ò¼¨¤·¤Þ¤¹¡£ ¸ú²ÌŪ¤Ë¥Ð¥°¤òÊó¹ð¤¹¤ë¤Ë¤Ï ( ÆüËܸìÌõ) — Simon G. Tatham »á¤Ë¤è¤ë¡¢(&os; ¤Ë¸Â¤é¤Ê¤¤) Ìò¤ËΩ¤Ä¾ã³²Êó¹ð¤ÎºîÀ®¤Ë¤Ä¤¤¤Æ¤Î¤¹¤°¤ì¤¿¥¨¥Ã¥»¥¤¡£ ¾ã³²Êó¹ð ¼è¤ê°·¤¤¥¬¥¤¥É¥é¥¤¥ó — ¾ã³²Êó¹ð¤¬ &os; ¤Î³«È¯¼Ô¤Ë¤è¤Ã¤Æ¤É¤Î¤è¤¦¤Ë°·¤ï¤ì¤ë¤«¤Ë¤Ä¤¤¤Æ Í­±×¤Ê¸«¼±¤ò¤Þ¤È¤á¤¿µ­»ö¡£
+ +
diff --git a/ja_JP.eucJP/books/fdp-primer/book.xml b/ja_JP.eucJP/books/fdp-primer/book.xml index 62c69bfe09..3ed35d5f5d 100644 --- a/ja_JP.eucJP/books/fdp-primer/book.xml +++ b/ja_JP.eucJP/books/fdp-primer/book.xml @@ -1,281 +1,279 @@ %chapters; ]> ¿·¤·¤¤¹×¸¥¼Ô¤Î¤¿¤á¤Î FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥ÈÆþÌç FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È 1998 1999 2000 2001 2002 2003 2004 DocEng $FreeBSD$ $FreeBSD$ &bookinfo.legalnotice; FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤Ë»²²Ã¤·¤Æ¤¯¤À¤µ¤Ã¤Æ¤¢¤ê¤¬¤È¤¦¤´¤¶¤¤¤Þ¤¹¡£ ¤¢¤Ê¤¿¤Î¹×¸¥¤ÏÈó¾ï¤Ë²ÁÃͤΤ¢¤ë¤³¤È¤Ç¤¹¡£ ¤³¤ÎÆþÌç¤Ç¤Ï FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤Ø¤Î¹×¸¥¤ò»Ï¤á¤ë¤Ë¤¢¤¿¤Ã¤ÆÍý²ò¤¹¤ëɬÍפΤ¢¤ë¤³¤È¡¢ ¤¹¤Ê¤ï¤Á(ɬ¿Ü¤Î¤â¤Î¤À¤±¤Ç¤Ê¤¯¡¢¿ä¾©¤µ¤ì¤ë¤â¤Î¤â´Þ¤á¤¿)¥Ä¡¼¥ë¤ä¥½¥Õ¥È¥¦¥§¥¢¤Î»È¤¤Êý¤«¤é¡¢ ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥È¤ÎÊý¿Ë¤Ë¤ï¤¿¤ëÆâÍƤΤ¹¤Ù¤Æ¤ò°·¤Ã¤Æ¤¤¤Þ¤¹¡£ ¤³¤Îʸ½ñ¤ÏȯŸÅÓ¾å¤Ë¤¢¤ê¡¢¤Þ¤À´°À®¤·¤Æ¤¤¤Þ¤»¤ó¡£ ¤Þ¤À´°À®¤·¤Æ¤¤¤Ê¤¤Àá¤Î̾Á°¤Ë¤Ï *(¥¢¥¹¥¿¥ê¥¹¥¯) ¤¬ÉÕ¤±¤Æ¤¢¤ê¤Þ¤¹¡£ ¤Þ¤¨¤¬¤­ ¥·¥§¥ë¥×¥í¥ó¥×¥È °Ê²¼¤Îɽ¤Ï¡¢ ɸ½à¤Î¥·¥¹¥Æ¥à¥×¥í¥ó¥×¥È¤È¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¤Î¥×¥í¥ó¥×¥È¼¨¤·¤Æ¤¤¤Þ¤¹¡£ ¤³¤Îʸ½ñ¤Ç¤¢¤²¤ë¼ÂÎã¤Ç¤Ï¡¢ ¤É¤Á¤é¤Î¥æ¡¼¥¶¤Ç¤½¤ÎÎã¤ò¼Â¹Ô¤¹¤Ù¤­¤«¼¨¤¹¤¿¤á¤Ë¤³¤ì¤é¤Î¥×¥í¥ó¥×¥È¤ò»ÈÍѤ·¤Þ¤¹¡£ ¥æ¡¼¥¶ ¥×¥í¥ó¥×¥È Ä̾ï¥æ¡¼¥¶ &prompt.user; root &prompt.root; ɽµ­¾å¤Î´·Îã ²¼¤Îɽ¤Ï¡¢ ¤³¤Îʸ½ñ¤Ç»È¤ï¤ì¤ëɽµ­¾å¤Î´·Îã¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£ °ÕÌ£ Îã ¥³¥Þ¥ó¥É¡¢¥Õ¥¡¥¤¥ë¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤ª¤è¤Ó¡¢ ¥³¥ó¥Ô¥å¡¼¥¿²èÌ̤ؤνÐÎÏ ¤¢¤Ê¤¿¤Î .login ¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Æ¤¯¤À¤µ¤¤¡£ ¥Õ¥¡¥¤¥ë¤Î°ìÍ÷¤òɽ¼¨¤¹¤ë¤Ë¤Ï ls -a ¤ò»È¤¤¤Þ¤¹¡£ You have mail. ¥³¥ó¥Ô¥å¡¼¥¿¤Î²èÌ̤Ëɽ¼¨¤µ¤ì¤ë¤â¤Î¤È¡¢ ¤¢¤Ê¤¿¤¬ÆþÎϤ¹¤ë¤â¤Î¤ò¶èÊ̤¹¤ë¾ì¹ç &prompt.user; su Password: ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î»²¾È ¥æ¡¼¥¶Ì¾¤òÊѹ¹¤¹¤ë¤Ë¤Ï su 1 ¤ò»È¤¤¤Þ¤¹¡£ ¥æ¡¼¥¶Ì¾¤È¥°¥ë¡¼¥×̾ ¤³¤ì¤¬¹Ô¤Ê¤¨¤ë¤Î¤Ï root ¤À¤±¤Ç¤¹¡£ ¶¯Ä´Éôʬ ɬ¤º¤³¤ì¤ò¹Ô¤Ê¤ï¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ ¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë½ñ¤«¤ì¤ë°ú¿ô¡£ ¤³¤ì¤Ï¼ÂºÝ¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë̾¤äÊÑ¿ô̾¤Ê¤É¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£ ¥Õ¥¡¥¤¥ë¤ò¾Ãµî¤¹¤ë¤Ë¤Ï¡¢ rm ¥Õ¥¡¥¤¥ë̾ ¤ÈÆþÎϤ·¤Þ¤¹¡£ ´Ä¶­ÊÑ¿ô $HOME¤Ï¡¢ ¤¢¤Ê¤¿¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¹¡£ Ãíµ­¡¢Tips¡¢½ÅÍפʾðÊó¡¢·Ù¹ð¡¢Î㼨 Ãíµ­¤ä·Ù¹ð¡¢Î㼨¤ÏËÜʸÃæ¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£ Ãíµ­¤Ï¤³¤Î¤è¤¦¤Ê´¶¤¸¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ ¤³¤ì¤Ë¤Ï¡¢ÆɼԤ¬¹Ô¤Ê¤¦Áàºî¤Ë´ØÏ¢¤·¤Æ Ãí°Õ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤òÅÁ¤¨¤ë¤¿¤á¤ÎÆâÍƤ¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ Tips ¤Ï¤³¤Î¤è¤¦¤Ê´¶¤¸¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ ¤³¤ì¤Ë¤Ï¡¢ÆɼԤÎÌò¤ËΩ¤Ä¤«¤â¤·¤ì¤Ê¤¤¾ðÊó¤ä¡¢ ²¿¤«¤ò¤¹¤ë¤Î¤Ë¤è¤ê°×¤·¤¤ÊýË¡¤Ø¤ÈƳ¤¤¤Æ¤¯¤ì¤ë¤è¤¦¤Ê¼ê¤¬¤«¤ê¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ ½ÅÍפʾðÊó¤Ï¤³¤Î¤è¤¦¤Ê´¶¤¸¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ °ìÈÌŪ¤Ë¤ÏÆɼԤ¬Äɲ䷤ƹԤï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¼ê½ç¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£ ·Ù¹ð¤Ï¡¢¤³¤Î¤è¤¦¤Ê´¶¤¸¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ ¤³¤ì¤Ë¤Ï¡¢¼ê½ç¤Ë½¾¤ï¤Ê¤¤¾ì¹ç¤Ë²¿¤é¤«¤Î»³²¤òÈï¤ë²ÄǽÀ­¤¬¤¢¤ë¤³¤È¤ò ÅÁ¤¨¤ëÆâÍƤ¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ ¤½¤Î»³²¤Ï¥Ï¡¼¥É¥¦¥§¥¢¤äÁàºî¼Ô¤ËÂФ¹¤ëʪÍýŪ¤Ê¤â¤Î¤«¤âÃΤì¤Þ¤»¤ó¤·¡¢ ÉÔÃí°Õ¤Ç½ÅÍפʥե¡¥¤¥ë¤¬ºï½ü¤µ¤ì¤Æ¤·¤Þ¤¦¤è¤¦¤ÊÈóʪÍýŪ¤Ê¤â¤Î¤«¤âÃΤì¤Þ¤»¤ó¡£ Î㼨¤Î¥µ¥ó¥×¥ë Î㼨¤Ï¡¢¤³¤Î¤è¤¦¤Ê´¶¤¸¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ ¤³¤ì¤Ë¤ÏÄ̾ÆɼԼ«¿È¤¬»î¤¹É¬ÍפΤ¢¤ëÎã¤ä¡¢ ¤¢¤ëÁàºî¤¬¤É¤Î¤è¤¦¤Ê·ë²Ì¤ò¤â¤¿¤é¤¹¤Î¤«¡¢ ÆɼԤ˼¨¤¹¤¿¤á¤ÎÎ㤬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ ¼Õ¼­ Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn, Christopher Maden ¤Ï¤³¤Îʸ½ñ¤Î½é¹Æ¤òÆɤà»þ´Ö¤ò³ä¤¤¤Æ¡¢ ¤¿¤¯¤µ¤ó¤ÎÍ­±×¤Ê¥³¥á¥ó¥È¤äÈãɾ¤òÁ÷¤Ã¤Æ¤¯¤ì¤Þ¤·¤¿¡£ ¤³¤³¤Ë´¶¼Õ¤Î°Õ¤òɽ¤·¤Þ¤¹¡£ &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/ja_JP.eucJP/books/handbook/Makefile b/ja_JP.eucJP/books/handbook/Makefile index 683c12b036..4ec5ac667c 100644 --- a/ja_JP.eucJP/books/handbook/Makefile +++ b/ja_JP.eucJP/books/handbook/Makefile @@ -1,354 +1,352 @@ # # $FreeBSD$ # # Build the FreeBSD Handbook (Japanese). # # Original revision: r42118 # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic #IMAGES_EN+= advanced-networking/pxe-nfs.png IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps #IMAGES_EN+= security/ipsec-network.pic #IMAGES_EN+= security/ipsec-crypt-pkt.pic #IMAGES_EN+= security/ipsec-encap-pkt.pic #IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content #SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml #SRCS+= dtrace/chapter.xml #SRCS+= freebsd-glossary.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml #SRCS+= firewalls/chapter.xml #SRCS+= filesystems/chapter.xml #SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml #SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml #SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml #SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml #SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent # Japanese only SRCS+= jcontrib/chapter.xml SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml ${DOC}.parsed.xml @${XSLTPROC} ${XSLPGP} ${DOC}.parsed.xml # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/ja_JP.eucJP/books/handbook/chapters.ent b/ja_JP.eucJP/books/handbook/chapters.ent index b1ee8ab0c9..29c0971c49 100644 --- a/ja_JP.eucJP/books/handbook/chapters.ent +++ b/ja_JP.eucJP/books/handbook/chapters.ent @@ -1,74 +1,74 @@ %pgpkeys; - + "> diff --git a/mn_MN.UTF-8/books/handbook/Makefile b/mn_MN.UTF-8/books/handbook/Makefile index 7485ab93cd..be27f99454 100644 --- a/mn_MN.UTF-8/books/handbook/Makefile +++ b/mn_MN.UTF-8/books/handbook/Makefile @@ -1,359 +1,357 @@ # $FreeBSD$ # # The FreeBSD Mongolian Documentation Project # # Original revision 39022 # # Build the FreeBSD Handbook. # # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/pxe-nfs.png IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/mn_MN.UTF-8/books/handbook/chapters.ent b/mn_MN.UTF-8/books/handbook/chapters.ent index b82b00701b..49e1ee8a6e 100644 --- a/mn_MN.UTF-8/books/handbook/chapters.ent +++ b/mn_MN.UTF-8/books/handbook/chapters.ent @@ -1,77 +1,77 @@ %pgpkeys; - + "> diff --git a/nl_NL.ISO8859-1/articles/contributing-ports/article.xml b/nl_NL.ISO8859-1/articles/contributing-ports/article.xml index 4464bcffff..c2618632b1 100644 --- a/nl_NL.ISO8859-1/articles/contributing-ports/article.xml +++ b/nl_NL.ISO8859-1/articles/contributing-ports/article.xml @@ -1,873 +1,875 @@
Bijdragen aan de &os; Portscollectie Abstract Dit artikel beschrijft de manieren waarop een individu kan bijdragen aan de &os; Portscollectie. Vertaald door René Ladan. Sam Lawrance Mark Linimon &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ bijdragen aan ports Introductie De Portscollectie is een eeuwig werk-in-uitvoering. We willen onze gebruikers een reservoir van software van derde partijen bieden dat gemakkelijk te gebruiken, bijgewerkt, en van hoge kwaliteit is. We hebben mensen nodig die wat tijd en moeite investeren om ons dit doel te helpen bereiken. Iedereen kan erin betrokken raken, en er zijn vele manieren om dat te doen. Bijdragen aan ports is een uitstekende manier om te helpen om iets aan het project terug te geven. Of u nu op zoek bent naar een blijvende rol, of naar een uitdaging voor een regenachtige dag, wij stellen uw hulp zeer op prijs! Als een vrijwilliger kunt u doen en laten wat u wilt. We vragen echter wel dat u op de hoogte bent van wat andere leden van de &os;-gemeenschap van u verwachten. U doet er goed aan om dit te overwegen voordat u besluit om vrijwilliger te worden. Wat u kunt doen om te helpen Er zijn een aantal gemakkelijke manieren waarop u bij kunt dragen om de portsboom actueel en in een goede toestand te houden: Zoek wat leuke of nuttige software en creëer er een port voor. Er is een groot aantal niet-onderhouden ports. Wordt een onderhouder en adopteer een port. Als u een port gecreëerd of geadopteerd heeft, dient u op de hoogte te zijn van wat u als onderhouder moet doen. Als u op zoek bent naar een snelle uitdaging zou u een bug of een kapotte port kunnen repareren. Een nieuwe port creëeren Er is een apart document beschikbaar om u door het creëeren (en bijwerken) van een port te loodsen genaamd het Porter's Handbook. Het Porter's Handbook is het beste naslagwerk wat betreft het werken met het portssysteem. Het noemt details over hoe het portssysteem werkt en bespreekt aangeraden praktijken. Een niet-onderhouden port adopteren Een niet-onderhouden port kiezen Het beheer overnemen van ports die niet onderhouden worden is een uitstekende manier om betrokken te raken. Niet-onderhouden ports worden alleen bijgewerkt en gerepareerd wanneer iemand zich aanbiedt om eraan te werken. Er is een groot aantal ports dat niet onderhouden wordt. Het is een goed idee om met het adopteren van een port te beginnen die u regelmatig gebruikt. Voor niet-onderhouden ports staat de MAINTAINER op ports@FreeBSD.org. Een lijst van ports die niet onderhouden wordt en hun huidige fouten en probleemrapporten kan worden bekeken op het &os; Ports Monitoring System. Sommige ports beïnvloeden een groot aantal anderen vanwege afhankelijkheden en relaties als slaafport. Over het algemeen wensen we dat mensen wat ervaring hebben voordat ze zulke ports onderhouden. U kunt uitzoeken of een port wel of geen afhankelijkheden of slaafpoorten heeft door in een hoofdindex van ports genaamd INDEX te kijken. (De naam van het bestand varieert naar gelang de uitgave van &os;; bijvoorbeeld INDEX-8.) Sommige ports hebben conditionele afhankelijkheden die niet standaard in een bouw van INDEX worden opgenomen. We verwachten dat u zulke ports kunt herkennen door naar de Makefile van andere ports te kijken. Hoe een port te adopteren Zorg eerst dat u uw verantwoordelijkheden als onderhouder begrijpt. Lees ook het Porter's Handbook. Neem alstublieft niet meer werk op u dan dat u op een comfortabele manier aankunt. U kunt zo snel als u wilt het beheer van een niet-onderhouden port aanvragen. Stel MAINTAINER in op uw emailadres en stuur een PR (probleemrapport) in met de verandering. Als de port bouwfouten bevat of moet worden bijgewerkt, dan kunt u deze veranderingen in hetzelfde PR opnemen. Dit helpt omdat veel committers minder bereid zijn om beheer aan iemand toe te kennen die geen bekende geschiedenis met &os; heeft. Het insturen van PR's die bouwfouten repareren of ports bijwerken zijn de beste manier om er een op te bouwen. Stuur uw PR in met categorie ports en klasse change-request. Een committer zal uw PR nakijken, de veranderingen committen, en uiteindelijk het PR sluiten. Soms kan dit proces even duren (committers zijn ook vrijwilligers). De uitdaging voor port-onderhouders Deze sectie geeft u een idee waarom ports onderhouden moeten worden en schetst de verantwoordelijkheden van een onderhouder van een port. Waarom ports onderhoud nodig hebben Een port creëeren is een eenmalige taak. Er zeker van zijn dat een port actueel is en blijft bouwen en draaien is een voortdurende inspanning. Onderhouders zijn mensen die wat van hun tijd wijden aan het vervullen van deze doelen. De voornaamste reden waarom ports onderhoud nodig hebben is om het nieuwste en beste van software van derde partijen aan de &os;-gemeenschap te geven. Een aanvullende uitdaging is om individuele ports werkend te houden binnen het evoluerende raamwerk van de Portscollectie. Als onderhouder zult u de volgende uitdagingen moeten aangaan: Nieuwe versies en updates van software. Nieuwe versies en updates van bestaande geporteerde software komen continu beschikbaar, en moeten in de Portscollectie worden verwerkt om actuele software aan te bieden. Veranderingen aan afhankelijkheden. Als er significante wijzigingen zijn gemaakt aan de afhankelijkheden van uw port, kan het zijn dat de port moet worden bijgewerkt zodat het correct blijft werken. Veranderingen die afhankelijke ports beïnvloeden. Als andere ports afhankelijk zijn van een port die u onderhoudt, kan het zijn om veranderingen aan uw port met andere onderhouders te coördineren. Interactie met andere gebruikers, onderhouders, en ontwikkelaars. Een gedeelte van een onderhouder zijn is het vervullen van een ondersteunende rol. Er wordt niet van u verwacht dat u algemene ondersteuning biedt (maar we juichen het toe als u dat doet). U dient een centraal punt voor &os;-specifieke zaken met betrekking tot uw ports te bieden. Bugs oplossen. Een port kan vatbaar zijn voor bugs die specifiek zijn voor &os;. U dient deze bugs te onderzoeken en te repareren wanneer ze worden gerapporteerd. Het grondig testen van een port om problemen te identificeren voordat ze in de Portscollectie terechtkomen is nog beter. Veranderingen aan portsinfrastructuur en beleid. Af en toe worden die systemen die gebruikt worden om ports en pakketten te bouwen bijgewerkt of wordt er een nieuwe aanbeveling met betrekking tot de infrastructuur gemaakt. U dient van deze veranderingen op de hoogte te zijn indien ze betrekking hebben op uw ports en ze bijgewerkt moeten worden. Veranderingen aan het basissysteem. &os; is constant in ontwikkeling. Veranderingen aan software, bibliotheken, de kernel, of zelfs beleidsveranderingen kunnen noodzakelijke veranderingen aan ports veroorzaken. Verantwoordelijkheden als onderhouder Houd uw ports actueel Deze sectie schetst het proces dat gevolgd wordt om uw ports actueel te houden. Dit is een overzicht. Meer informatie over het bijwerken van een port is beschikbaar in het Porter's Handbook. Kijk uit naar updates Houd de stroomopwaartse leverancier in de gaten wat betreft nieuwe versies, updates, en beveiligingsreparaties voor de software. Mailinglijsten met aankondigingen of webpagina's met nieuws zijn hiervoor handig. Soms zullen gebruikers contact met u opnemen en vragen wanneer uw port wordt bijgewerkt. Als u het druk hebt met andere dingen of u het om enige andere reden niet nu kunt bijwerken, vraag ze dan om u te helpen door een update te sturen. U kunt ook geautomatiseerde email van de &os; Ports Version Check ontvangen die u informeert of er een nieuwe versie van het distributiebestand van uw port beschikbaar is. Meer informatie over dat systeem (inclusief hoe toekomstige emails te stoppen) staat in het bericht. Verwerk veranderingen Verwerk veranderingen in de port wanneer ze beschikbaar komen. U dient een patch aan te kunnen maken tussen de originele port en uw bijgewerkte port. Herzie en test Herzie en test uw veranderingen grondig: Bouw, installeer, en test uw port op zoveel mogelijk platforms en architecturen. Het is gebruikelijk dat een port op één tak of platform werkt maar faalt op een ander. Zorg dat de afhankelijkheden van uw port compleet zijn. De aangeraden manier om dit te doen is door uw eigen tinderbox voor ports te installeren. Bekijk bronnen voor meer informatie. Controleer of de pakketlijst actueel is. Dit omvat het toevoegen van nieuwe bestanden en mappen en het verwijderen van ongebruikte regels. Verifieer uw port met &man.portlint.1; als gids. Bekijk bronnen voor belangrijke informatie over het gebruik van portlint. Overweeg of veranderingen aan uw port andere ports zouden kunnen kapotmaken. Bespreek de veranderingen met de onderhouders van die ports als dit het geval is. Dit is speciaal van belang als uw update de versie van de gedeelde bibliotheek verandert; in dit geval dienen de afhankelijke ports minstens een verhoging van de PORTREVISION te krijgen zodat ze automatisch worden bijgewerkt door geautomatiseerde gereedschappen als portmaster of &man.portupgrade.1;. Stuur veranderingen in Verzend uw update door een PR met een uitleg van de veranderingen en een patch die de verschillen tussen de originele port en de bijgewerkte port bevat in te sturen. Bekijk alstublieft Probleemrapporten voor &os; schrijven voor informatie over hoe een echt goed PR te schrijven. Stuur alstublieft geen &man.shar.1;-archief van de gehele port; gebruik in plaats daarvan &man.diff.1; -ruN. Op deze manier kunnen committers veel gemakkelijker zien welke veranderingen er precies gemaakt worden. De sectie in het Porter's Handbook over Upgrading bevat meer informatie hierover. Wacht Op een gegeven moment zal een committer uw PR behandelen. Dit kan minuten, maar ook weken duren — ben dus alstublieft geduldig. Geef feedback Als een committer een probleem vindt in uw veranderingen zullen ze het waarschijnlijk aan u terugkoppelen. Een snel antwoord helpt om uw PR sneller gecommit te krijgen, en is beter voor het behouden van een discussie wanneer er geprobeerd wordt om problemen op te lossen. En ten slotte Uw veranderingen zullen gecommit worden en uw port zal bijgewerkt zijn. Het PR wordt vervolgens door de committer gesloten. Dat is alles! Zorg ervoor dat uw ports correct blijven bouwen Deze sectie gaat over het ontdekken en oplossen van problemen die verhinderen dat uw ports correct bouwen. &os; garandeert alleen dat de Portscollectie op de -STABLE-takken werkt. U dient 7-STABLE of 8-STABLE te draaien, bij voorkeur de laatste. In theorie zou het voldoende moeten zijn om de nieuwste uitgave van elke STABLE-tak te draaien (aangezien de ABI's niet horen te veranderen), maar als u die tak kunt draaien is dat beter. Aangezien de meerderheid van &os;-installaties op PC-compatibele machines draait (wat wordt aangeduid als de i386-architectuur), verwachten wij van u dat u de port op die architectuur werkend houdt. We prefereren dat de ports ook op de amd64-architectuur draaien. Het is prima om hulp te vragen als u een van deze machines niet heeft. De gebruikelijke manieren om te falen voor niet-i386 machines zijn dat de originele programmeurs aannamen dat, bijvoorbeeld, pointers ints zijn of dat een relatief lakse oudere gcc compiler werd gebruikt. Steeds meer reorganiseren applicatie-auteurs hun code om deze aannames te verwijderen — maar als de auteur de code niet actief onderhoudt, zult u dit zelf moeten doen. Deze taken moet u uitvoeren om ervoor te zorgen dat uw port gebouwd kan worden: Kijk uit naar bouwfouten Controleer regelmatig het geautomatiseerde portbouwcluster, pointyhat, en de scanner voor distributiebestanden om te zien of er ports zijn die u onderhoudt die er niet in slagen om gebouwd of opgehaald te worden (bekijk bronnen voor meer informatie over deze systemen). Rapportages over mislukkingen kunnen ook via email van andere gebruikers of geautomatiseerde systemen tot u komen. Verzamel informatie Als u eenmaal op de hoogte bent van een probleem, verzamel dan informatie die u helpt het op te lossen. Bouwfouten die door pointyhat worden gerapporteerd worden vergezeld door logs die aangeven waar het bouwen mislukte. Als de mislukking door een gebruiker aan u werd gerapporteerd, vraag ze dan om informatie te verzenden die u helpt om het probleem te vast te stellen, zoals: Bouwlogs De commando's en opties die gebruikt werden om de port te bouwen (inclusief opties die in /etc/make.conf zijn ingesteld) Een lijst met op hun systeem geïnstalleerde pakketten als aangegeven door &man.pkg.info.1; De versie van &os; die ze draaien als aangegeven door &man.uname.1; -a Wanneer hun Portscollectie voor het laatst was bijgewerkt Wanneer hun bestand INDEX voor het laatst was bijgewerkt Onderzoek en zoek een oplossing Helaas is er geen rechttoe-rechtaan proces dat gevolgd kan worden om dit te doen. Herinner: vraag om hulp als u vast zit! De &a.ports; is een goede plaats om te starten, en de stroomopwaartse ontwikkelaars zijn vaak zeer behulpzaam. Stuur veranderingen in Net zoals bij het bijwerken van een port, dient u nu de veranderingen te integreren, te herzien en te testen, uw veranderingen als een PR in te sturen, en feedback te geven als dat nodig is. Stuur patches naar de stroomopwaartse auteurs In sommige gevallen moet u patches maken om de port op &os; te laten draaien. Sommige (maar niet alle) stroomopwaartse auteurs zullen zulke patches in hun code accepteren voor de volgende uitgave. Als dit zo is, kan dit zelfs hun gebruikers op andere op BSD-gebaseerde systemen helpen en misschien dubbel werk besparen. Overweeg alstublieft om geschikte patches naar de auteurs te zenden als teken van goede wil. Onderzoek foutrapporten en PR's die aan uw port gerelateerd zijn Deze sectie gaat over het ontdekken en repareren van bugs. &os;-specifieke bugs worden in het algemeen veroorzaakt door aannames over de bouw- en draaiomgevingen die niet voor &os; gelden. U zult zo'n soort fout minder snel aantreffen, maar het kan subtieler en moeilijker zijn om het vast te stellen. De onderstaande taken moet u uitvoeren om ervoor te zorgen dat uw port als bedoeld blijft werken: Reageer op bugrapporten Bugs kunnen per email via de GNATS Probleemrapportendatabase aan u worden gerapporteerd. Bugs kunnen ook direct door gebruikers aan u gerapporteerd worden. U dient binnen 14 dagen op PR's en andere rapporten te reageren, probeer hier alstublieft niet zo lang over te doen. Probeer zo snel mogelijk te reageren, zelfs als het alleen maar is om te zeggen dat u wat meer tijd nodig heeft voordat u aan het PR kan werken. Als u niet na 14 dagen heeft gereageerd, mag elke committer via een maintainer-timeout uit een PR committen waarop u niet heeft gereageerd. Verzamel informatie Als degene die de bug heeft gerapporteerd niet ook een reparatie heeft aangeleverd, zult u informatie moeten verzamelen die u in staat stelt om er een te genereren. Als de bug reproduceerbaar is, kunt u zelf de meeste vereiste informatie verzamelen. Zo niet, vraag dan degene die de bug rapporteerde om de informatie voor u te verzamelen, zoals: Een gedetailleerde beschrijving van hun acties, verwacht gedrag en eigenlijk gedrag van het programma Kopiën van invoergegevens die de bug aanzwengelden Informatie over hun bouw- en uitvoeromgeving — bijvoorbeeld een lijst van geïnstalleerde pakketten en de uitvoer van &man.env.1; Coredumps Stacktraces Elimineer onjuiste rapporten Sommige bugrapporten kunnen onjuist zijn. De gebruiker kan het programma simpelweg verkeerd gebruikt hebben; of hun geïnstalleerde pakketten kunnen verouderd zijn en bijgewerkt moeten worden. Soms is een gerapporteerde fout niet specifiek voor &os;. Rapporteer in dit geval de bug naar de stroomopwaartse ontwikkelaars. Als u de bug kunt repareren, kunt u de port ook patchen zodat de reparatie is toegepast voor de volgende stroomopwaartse uitgave. Vind een oplossing Net als met bouwfouten dient u een oplossing voor het probleem te vinden. Nogmaals, vraag om hulp als u vastzit! Stuur veranderingen in of keur ze goed Net als bij het bijwerken van een port, dient u nu de veranderingen te integreren, ze te herzien en te testen, en ze in een PR op te sturen (of een vervolg te verzenden als er al een PR voor het probleem bestaat). Als een andere gebruiker veranderingen in het PR heeft ingezonden, kunt u ook een vervolg sturen waarin u zegt of u de veranderingen wel of niet goedkeurt. Ondersteuning bieden Deel van een onderhouder zijn is ondersteuning bieden — niet noodzakelijk voor de software in het algemeen — maar voor de port en alle &os;-specifieke rariteiten en problemen. Gebruikers kunnen contact met u opnemen voor vragen, suggesties, problemen, en patches. Meestal zal hun correspondentie specifiek voor &os; zijn. Af en toe zult u uw diplomatieke vaardigheden moeten gebruiken, en gebruikers die algemene ondersteuning zoeken vriendelijk naar de geschikte bronnen verwijzen. Minder vaak zult u iemand tegenkomen die vraagt waarom de RPMs niet actueel zijn of hoe ze de software onder Foo Linux kunnen draaien. Grijp deze kans om ze te vertellen dat uw port actueel is (als het dat is, uiteraard!) en stel voor dat ze &os; uitproberen. Soms zullen gebruikers en ontwikkelaars besluiten dat u een druk persoon bent wiens tijd waardevol is en wat werk van u overnemen. Ze kunnen bijvoorbeeld: een PR insturen of u patches toesturen om uw port bij te werken, een PR onderzoeken en er misschien een reparatie voor aanleveren, of op andere wijze veranderen aan uw port insturen. In deze gevallen is uw hoofdplicht om op tijd te reageren. Nogmaals, de timeout voor niet-reagerende onderhouders is 14 dagen. Na deze periode mogen niet-goedgekeurde veranderingen gecommit worden. Ze hebben de moeite genomen om dit voor u te doen; dus probeer tenminste op tijd te reageren. Daarna dient u zo snel mogelijk hun veranderingen te herzien, goed te keuren, te wijzigen, of met hen te bediscussiëren. Als u ervoor kunt zorgen dat ze het gevoel hebben dat hun bijdrage gewaardeerd wordt (wat zo hoort te zijn), dan heeft u een grotere kans om ze te overtuigen om in de toekomst meer voor u te doen :-). Een kapotte port vinden en repareren Er zijn twee zeer goede plaatsen om een port te vinden die wat aandacht nodig heeft. U kunt de webinterface voor de probleemrapportdatabase gebruiken om onopgeloste PR's te doorzoeken en ze te bekijken. De meerderheid van port-PR's zijn updates, maar met een beetje zoeken door en uitkammen van de samenvattingen zou u iets moeten kunnen vinden wat interessant is om aan te werken (de klasse sw-bug is een goede plaats om te beginnen). De andere plaats is het &os; Ports Monitoring System. Zoek in het bijzonder naar niet-onderhouden ports met bouwfouten en ports die als BROKEN zijn gemerkt. Het is ook goed om veranderingen voor een onderhouden port te versturen, maar denk eraan om de onderhouder te vragen in het geval dat ze al aan het probleem werken. Als u eenmaal een bug of probleem heeft gevonden, verzamel dan informatie, onderzoek, en repareer het! Als er een bestaand PR is, ga daar dan mee verder. Maak anders een nieuw PR aan. Uw veranderingen zullen worden herzien en, als alles goed is, gecommit. Wanneer het tijd wordt om te stoppen Wanneer uw interesses en toewijdingen veranderen, zult u erachter komen dat u niet langer tijd heeft om sommige van (of al) uw ports-bijdragen voort te zetten. Dat is prima! Laat ons weten als u een port niet langer gebruikt of om andere redenen de tijd of interesse heeft verloren om ports te onderhouden. Op deze manier kunnen we verder gaan en andere mensen toestaan om te proberen om aan bestaande problemen met de port te werken zonder op uw antwoord te wachten. Herinner dat &os; een vrijwilligersproject is, dus als het onderhouden van een port niet langer leuk is, is het waarschijnlijk tijd om iemand anders het te laten doen! In elk geval houdt het Ports Management Team (portmgr) zich het recht voor om u als onderhouder te wissen als u uw port voor enige tijd niet actief heeft onderhouden. (Momenteel is dit 3 maanden.) Hiermee bedoelen we dat er onopgeloste problemen of wachtende updates zijn waaraan binnen die tijd niet gewerkt is. Bronnen voor onderhouders en vrijwilligers voor ports Het Porter's Handbook is uw overlevingsgids voor het portssysteem. Houd het in de buurt! Probleemrapporten voor &os; schrijven beschrijft hoe het beste een PR geformuleerd en ingezonden kan worden. In 2005 werden er meer dan elfduizend port-PR's ingestuurd! Het volgen van dit artikel helpt ons enorm om de tijd te verkorten die nodig is om uw PR's te behandelen. De Probleemrapportendatabase. Pointyhat is het bouwcluster voor ports. U kunt Pointyhat gebruiken om bouwlogs van ports over alle architecturen en grote uitgaven te controleren. Het &os; Ports Monitoring System kan u kruislingse informatie over ports zoals bouwfouten en probleemrapporten laten zien. Als u een onderhouder bent kunt u het gebruiken om de bouwstatus van uw ports te controleren. Als een vrijwilliger kunt u het gebruiken om kapotte en niet-onderhouden ports te vinden die gerepareerd moeten worden. De scanner voor distributiebestanden voor &os; ports kan u ports laten zien waarvoor de distributiebestanden niet kunnen worden opgehaald. U kunt uw eigen ports controleren of u kunt het gebruiken om ports te vinden waarvan de MASTER_SITES moet worden bijwerkt. De tinderbox voor ports is de meest grondige manier om een port door de gehele cyclus van installatie, inpakken, en deïnstallatie te halen. Het biedt een opdrachtregelinterface maar kan ook via een webinterface worden beheerd. Meer informatie staat op de marcuscom tinderbox homepage. &man.portlint.1; is een applicatie die gebruikt kan worden om te verifiëren dat uw port zich aan vele belangrijke stilistische en functionele richtlijnen houdt. portlint is een eenvoudige heuristieke applicatie, dus dient u het alleen als gids te gebruiken. Als portlint veranderingen voorstelt die onredelijk lijken, raadpleeg dan het Porter's Handbook of vraag om advies. De &a.ports; dient voor algemene ports-gerelateerde discussies. Het is een goede plaats om hulp te vragen. U kunt zich aanmelden, of de lijstarchieven lezen en doorzoeken. Het lezen van de archieven van de &a.ports-bugs; en de &a.cvs-ports; kan ook interessant zijn. + +
diff --git a/nl_NL.ISO8859-1/articles/contributing/article.xml b/nl_NL.ISO8859-1/articles/contributing/article.xml index 52e07d8212..ddde72f27e 100644 --- a/nl_NL.ISO8859-1/articles/contributing/article.xml +++ b/nl_NL.ISO8859-1/articles/contributing/article.xml @@ -1,562 +1,564 @@
Bijdragen aan &os; Vertaald door René Ladan. Dit artikel beschrijft de verschillende manieren waarop een individu of organisatie kan bijdragen aan het &os; Project. Jordan Hubbard Bijgedragen door &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ bijdragen Dus u wilt bijdragen aan &os;? Dat is mooi! &os; bouwt op de bijdragen van zijn gebruikers om te overleven. Uw bijdragen worden niet alleen gewaardeerd, ze zijn van vitaal belang voor de aanhoudende groei van &os;. In tegenstelling tot wat sommige mensen u laten geloven, hoeft u geen doorgewinterde programmeur of een goede vriend van het coreteam van &os; te zijn opdat uw bijdragen geaccepteerd worden. Een groot en groeiend aantal internationale bijdragende vrijwilligers, van een grote variëteit aan leeftijden en technische expertisegebieden, ontwikkelen &os;. Er is altijd meer werk te doen dan dat er mensen zijn om het uit te voeren, en meer hulp wordt altijd gewaardeerd. Het &os; project is verantwoordelijk voor een complete omgeving van een besturingssysteem, en niet slechts voor alleen een kernel of een paar verspreide gereedschappen. Hierom staan op onze TODO-lijsten een groot aantal verschillende taken: van documentatie, beta-testing en -presentatie, tot de systeeminstaller en ver gespecialiseerde soorten van kernelontwikkeling. Mensen van alle niveaus op bijna alle gebieden kunnen zeer waarschijnlijk meehelpen aan het project. Commerciële entiteiten die betrokken zijn in &os;-gerelateerde ondernemingen worden ook aangemoedigd om contact met ons op te nemen. Heeft u een speciale uitbreiding nodig om uw product te laten werken? U zult zien dat wij ontvankelijk zijn voor uw verzoeken, op de voorwaarde dat ze niet te vreemdsoortig zijn. Werkt u aan een product met toegevoegde waarde? Laat het ons weten! Misschien kunnen we op sommige punten samenwerken. De wereld van vrije software heeft te maken met vele bestaande aannamen over hoe software wordt ontwikkeld, verkocht, en onderhouden, en we verzoeken u om er op zijn minst nog eens naar te kijken. Wat is er nodig De onderstaande lijst van taken en deelprojecten representeert een soort amalgaam van verschillende TODO-lijsten en verzoeken van gebruikers. Voortdurende taken voor niet-programmeurs Veel mensen die betrokken zijn bij &os; zijn geen programmeurs. Het Project omvat documentatieschrijvers, Webontwerpers, en mensen ter ondersteuning. Deze mensen hoeven alleen een tijdsinvestering en een wil om te leren bij te dragen. Lees regelmatig de FAQ en het Handboek door. Laat het ons weten als er iets slecht is uitgelegd, is verlopen of gewoon helemaal verkeerd is. Of stuur een reparatie in (Docbook is niet moeilijk te leren, maar er is geen bezwaar tegen inzendingen in ASCII). Help bij het vertalen van &os;-documentatie in uw eigen taal. Als er al documentatie in uw taal bestaat, kunt u helpen door aanvullende documenten te vertalen of te controleren dat de vertalingen up-to-date zijn. Kijk eerst op Translations FAQ in de &os; Documentation Project Primer. U bindt zich niet aan het vertalen van elk &os;-document door dit te doen — als vrijwilliger kunt u zo veel of zo weinig vertalen als u wilt. Als iemand eenmaal begint te vertalen, sluiten andere mensen zich hier bijna altijd bij aan. Als u slechts de tijd of energie heeft om één document te vertalen, vertaal dan alstublieft de installatie-instructies. Lees af en toe (of regelmatig) de &a.questions; en &ng.misc;. Het kan veel voldoening geven om uw expertise te delen en mensen helpen met het oplossen van hun problemen; soms leert u zelf misschien iets nieuws! Deze fora kunnen ook een inspiratiebron zijn voor dingen om aan te werken. Voortdurende taken voor programmeurs Voor de meeste van de hier genoemde taken is een aanzienlijke tijdsinvestering, of diepe kennis van de kernel van &os;, of beide nodig. Er zijn echter ook vele nuttige taken die geschikt zijn voor weekend hackers. Als u &os;-CURRENT draait en een goede Internetverbinding heeft, dan is er een machine current.FreeBSD.org die elke dag een volledige uitgave bouwt—probeer zo nu en dan om de nieuwste uitgave ervan te installeren en rapporteer alle fouten in het proces. Lees de &a.bugs;. Er kunnen problemen zijn waarop u constructief commentaar kunt geven of waarvoor u testbare patches kunt geven. U kunt zelfs proberen om een van de problemen zelf op te lossen. Als u bugfixes weet die succesvol op -CURRENT zijn toegepast maar nog niet na een redelijk interval naar -STABLE zijn samengevoegd (normaliter een aantal weken), stuur de committer dan een beleefde herinnering. Verplaats bijgedragen software naar src/contrib in de broncodeboom. Verzeker dat de code in src/contrib up-to-date is. Bouw de broncodeboom (of slechts een gedeelte ervan) met extra waarschuwingen aangezet en ruim de waarschuwingen op. Repareer waarschuwingen voor ports die verouderde dingen zoals gets() of malloc.h gebruiken. Als u ports heeft bijgedragen en u &os;-specifieke veranderingen moest maken, stuur dan uw patches terug naar de originele auteurs (dit maakt het gemakkelijker voor u wanneer ze de volgende versie uitbrengen). Verkrijg kopieën van formele standaarden zoals &posix;. Enkele links over deze standaarden staan op de website van het &os; C99 & POSIX Standards Conformance Project. Vergelijk het gedrag van &os; met dat wat de standaard voorschrijft. Als het gedrag verschilt, met name in subtiele of obscure gedeelten van de specificatie, stuur er dan een PR over op. Indien mogelijk, zoek uit hoe het te repareren en voeg een patch bij het PR. Als u meent dat de standaard verkeerd is, vraag dan het standaardorgaan om de vraag te overwegen. Suggereer verdere taken voor deze lijst! Spit de PR-database door probleemrapportdatabase De &os; PR-lijst laat alle huidige actieve probleemrapportages en verzoeken voor verrijkingen zien die door gebruikers van &os; zijn ingestuurd. De PR-database bevat zowel taken voor programmeurs als voor niet-programmeurs. Bekijk de open PR's, en kijk of iets uw interesse wekt. Sommige van deze kunnen heel simpele taken zijn waarvoor gewoon een extra paar ogen nodig is om te bevestigen dat de reparatie in de PR een goede is. Andere kunnen veel complexer zijn, of bevatten in het geheel geen reparatie. Begin met de PR's die nog niet aan iemand anders zijn toegekend. Als een PR aan iemand anders is toegekend, maar het eruit ziet als iets wat u aankunt, stuur dan een email naar de persoon waaraan het is toegekend en vraag of u eraan kunt werken —ze kunnen al een patch hebben die klaar is om getest te worden, of verdere ideeën hebben die u met ze kan bespreken. Kies een van de punten van de <quote>Ideeën</quote> pagina De &os;-lijst van projecten en ideeën voor vrijwilligers is ook beschikbaar voor mensen die aan het &os;-project willen bijdragen. Deze lijst wordt regelmatig bijgewerkt en bevat punten voor zowel programmeurs als niet-programmeurs met informatie over elk project. Hoe bij te dragen Bijdragen aan het systeem vallen over het algemeen in één of meer van de volgende 5 categoriën: Foutrapportages en algemeen commentaar Een idee of suggestie van algemene technische aard dient naar &a.hackers; gemaild te worden. Evenzo kunnen mensen die in dit soort dingen geïnteresseerd zijn (en een tolerantie voor grote hoeveelheden mail hebben!) zich abonneren op de &a.hackers;. Zie Het &os; Handboek voor meer informatie over deze en andere mailinglijsten. Als u een bug vindt of een specifieke verandering opstuurt, gebruik dan alstublieft het programma &man.send-pr.1; of het webgebaseerde equivalent om het te rapporteren. Probeer om elk veld van het bugrapport in te vullen. Voeg patches direct bij het rapport tenzij ze 65kB overschrijden. Als de patch geschikt is om op de broncodeboom te worden toegepast, vermeld dan [PATCH] in het overzicht van het rapport. Wanneer u patches bijvoegt, gebruik dan geen knippen-en-plakken omdat knippen-en-plakken tabs in spaties omzet en de patches onbruikbaar maakt. Overweeg wanneer patches veel groter zijn dan 20 kB om ze te comprimeren (bijvoorbeeld met &man.gzip.1; of &man.bzip2.1;) en &man.uuencode.1; te gebruiken om hun gecomprimeerde vorm in uw probleemrapport op te nemen. Na het opsturen van een rapport dient u een bevestiging met daarbij een volgnummer te krijgen. Bewaar dit volgnummer zodat u ons op de hoogte kunt houden met details over het probleem door mail te sturen naar &a.bugfollowup;. Gebruik het nummer als het berichtonderwerp, bijvoorbeeld "Re: kern/3377". Aanvullende informatie voor elk foutrapport dient op deze manier opgestuurd te worden. Als u geen bevestiging ontvangt binnen een redelijke tijd (3 dagen tot een week, afhankelijk van uw emailverbinding) of als u, om enige reden, het commando &man.send-pr.1; niet kunt gebruiken, dan kunt u iemand vragen om het voor u op te sturen door mail te sturen naar de &a.bugs;. Zie ook dit artikel over het schrijven van goede probleemrapporten. Veranderingen aan de documentatie documentatie-inzendingen Veranderingen aan de documentatie worden overzien door de &a.doc;. Bekijk de &os; Documentation Primer voor volledige instructies. Stuur bijdragen en veranderingen (zelfs kleine zijn welkom!) door &man.send-pr.1; te gebruiken zoals beschreven is in Foutrapportages en algemeen commentaar. Veranderingen aan bestaande broncode &os;-CURRENT Een toevoeging of verandering aan de bestaande broncode is een iets lastigere zaak en hangt in grote mate af van hoe ver u achterloopt met de huidige toestand van &os;-ontwikkelingen. Er is een speciale doorgaande uitgave van &os; die bekend staat als &os;-CURRENT die op verscheidene manieren beschikbaar wordt gesteld voor het gemak van ontwikkelaars die actief aan het systeem werken. Zie Het &os; Handboek voor meer informatie over het verkrijgen en gebruiken van &os;-CURRENT. Het werken met oudere broncode betekent helaas dat uw veranderingen soms te verouderd of te ver afgedwaald zijn om eenvoudig in &os; gerëintegreerd te worden. De kansen hierop kunnen enigszins geminimaliseerd worden door een abonnement te nemen op de &a.announce; en de &a.current; lijsten, waar discussies over de huidige toestand van het systeem plaatsvinden. Aannemende dat u in staat bent om redelijk recente broncode veilig te stellen om uw veranderingen op te baseren, is de volgende stap het produceren van een verzameling diffs om naar de onderhoudsmensen van &os; te sturen. Dit wordt gedaan met het commando &man.diff.1;. Het geprefereerde &man.diff.1;-formaat voor het opsturen van patches is het verenigde uitvoerformaat gegenereerd door diff -u. diff &prompt.user; diff -u oudbestand nieuwbestand of &prompt.user; diff -u -r -N oudemap nieuwemap zouden een verzameling van verenigde diffs genereren voor het gegeven bronbestand of maphiërarchie. Zie &man.diff.1; voor meer details. Als u eenmaal een verzameling aan diffs heeft (welke u kunt testen met het commando &man.patch.1;), dient u ze op te sturen voor opname in &os;. Gebruik het programma &man.send-pr.1; zoals beschreven in Foutrapportages en algemeen commentaar. Stuur de diffs niet alleen naar de &a.hackers; op omdat ze dan verloren raken! We stellen uw toezending erg op prijs (dit is een vrijwilligersproject!); omdat we het druk hebben kan het zijn dat we het niet direct kunnen behandelen, maar het blijft in de PR-database totdat we het doen. Geef uw toezending aan door [PATCH] in het overzicht van het rapport op te nemen. uuencode Als u het geschikt acht (bijvoorbeeld als u bestanden toegevoegd, verwijderd, of hernoemd heeft), bundelt u uw veranderingen in een tar-bestand en draait u het programma &man.uuencode.1; erop. Archieven die met &man.shar.1; zijn aangemaakt zijn ook welkom. Als uw verandering mogelijk gevoelig van aard is, bijvoorbeeld als u onzeker bent over copyright-zaken die de verdere distributie ervan dicteren, dan dient u het direct naar &a.core; te sturen in plaats van het met &man.send-pr.1; op te sturen. Het &a.core; bereikt een veel kleinere groep mensen die veel dagelijks werk op &os; doen. Merk op dat deze groep het ook erg druk heeft, daarom dient u alleen mail naar hen te sturen als dit echt noodzakelijk is. Bekijk alstublieft &man.intro.9; en &man.style.9; voor wat informatie over de codeerstijl. We zouden het op prijs stellen als u op zijn minst op de hoogte bent van deze informatie voordat u code opstuurt. Nieuwe code of grote pakketten met toegevoegde waarde In het geval van een significante bijdrage van een grote bijdrage aan werk, of van een belangrijke nieuwe mogelijkheid aan &os;, is het bijna altijd nodig om de veranderingen als uuencoded tar-bestanden te versturen of ze naar een web- of FTP-site up te loaden zodat andere mensen ze kunnen benaderen. Als u geen toegang heeft tot een web- of FTP-site, vraag dan een geschikte &os;-mailinglijst om iemand de veranderingen voor u te laten hosten. Bij het werken met grote hoeveelheden code komt het gevoelige onderwerp van copyright ook altijd naar voren. Acceptabele copyrights voor code voor opname in &os; zijn: Het BSD-copyrightBSD-copyright. Dit copyright wordt het meeste verkozen wegens zijn natuur van geen voorwaarden en de algemene aantrekkelijkheid voor commerciële ondernemingen. Ver van het ontmoedigen van dit soort commercieel gebruik, moedigt het &os; Project zulke participatie door commerciële interesses actief aan die uiteindelijk geneigd kunnen zijn om zelf iets in &os; te investeren. De GNU General Public LicenseGNU General Public License, of GPLGPLGNU General Public License. Deze licentie is niet zo populair bij ons wegens de extra hoeveelheid moeite die gevraagd wordt van iedereen die de code voor commerciële doeleinden gebruikt, maar vanwege de grote hoeveelheid aan ge-GPL-de code die we momenteel nodig hebben (compiler, assembler, tekstopmaker, enz.) zou het dom zijn om aanvullende bijdragen onder deze licentie te verwerpen. Code onder de GPL gaat ook naar een ander deel van de boom, namelijk /sys/gnu of /usr/src/gnu, en is daardoor eenvoudig te herkennen voor iedereen voor wie de GPL problemen geeft. Bijdragen die onder een ander soort copyright vallen moeten zorgvuldig worden herzien voordat hun opname in &os; wordt overwogen. Bijdragen waarvoor nogal beperkende commerciële copyrights gelden worden over het algemeen verworpen, alhoewel de auteurs altijd worden aangemoedigd om zulke veranderingen via hun eigen kanalen beschikbaar te maken. Om een copyright in BSD-stijl op uw werk te plaatsen, dient u de volgende tekst aan het uiterste begin van elk broncodebestand te plaatsen dat u wilt beschermen, en daarbij de tekst tussen de %% door de juiste informatie te vervangen: Copyright (c) %%juiste_jaren_hier%% %%uw_naam_hier%%, %%uw_staat%% %%uw_postcode%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%uw_naam_hier%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%uw_naam_hier%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ Voor uw gemak staat een kopie van deze tekst in /usr/share/examples/etc/bsd-style-copyright. Geld, hardware, of Internettoegang We accepteren altijd graag donaties om het &os; Project verder te verspreiden en in een vrijwilligersonderneming zoals het onze kan een klein beetje een groot verschil maken! Hardwaredonaties zijn ook erg belangrijk om onze lijst van ondersteunde randapparatuur uit te breiden aangezien ons het over het algemeen aan de middelen ontbreekt om zelf zulke dingen te kopen. <anchor id="donations"/>Geld doneren De &os; Foundation is een non-profit, belastinguitgesloten stichting die opgericht is om de doelen van het &os; Project verder te verspreiden. Als een 501(c)3-entiteit is de Foundation over het algemeen uitgesloten van inkomstenbelasting van de overheid van de Verenigde Staten alsook van inkomstenbelasting van de staat Colorado. Donaties aan een entiteit die van belasting is uitgesloten zijn vaak aftrekbaar van het belastbaar overheidsinkomen. Donaties kunnen als check verstuurd worden aan:
The FreeBSD Foundation P.O. Box 20247 Boulder, CO 80308 USA
De &os; Foundation is nu in staat om donaties via het web met PayPal te ontvangen. Om een donatie te maken bezoekt u de website van de Foundation. Meer informatie over de &os; Foundation kan gevonden worden in The FreeBSD Foundation -- an Introduction. Om de Foundation per email te bereiken, schrijft u naar bod@FreeBSDFoundation.org. Hardware doneren Het &os; Project accepteert graag hardwaredonaties die het goed kan gebruiken. Als u geïnteresseerd bent in het donerendonaties van hardware, neem dan contact op met het Donations Liaison Office. + +
diff --git a/nl_NL.ISO8859-1/articles/problem-reports/article.xml b/nl_NL.ISO8859-1/articles/problem-reports/article.xml index 9ac460b2eb..d5496e3d05 100644 --- a/nl_NL.ISO8859-1/articles/problem-reports/article.xml +++ b/nl_NL.ISO8859-1/articles/problem-reports/article.xml @@ -1,1361 +1,1363 @@
Probleemrapporten voor &os; schrijven &tm-attrib.freebsd; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Dit artikel beschrijft hoe een probleemrapport het beste geformuleerd en naar het &os; Project verzonden kan worden. Vertaald door René Ladan. Dag-Erling Smørgrav Bijgedragen door Mark Linimon probleemrapporten
Introductie Eén van de meest frustrerende ervaringen die een gebruiker van software kan hebben is om een probleemrapport in te sturen om het vervolgens afgehandeld te zien met een korte en onbehulpzame uitleg als geen bug of fout PR. Evenzo is één van de meest frustrerende ervaringen als ontwikkelaar van software om overspoeld te worden met probleemrapporten die niet echt een probleemrapport zijn maar ondersteuningsverzoeken, of die weinig tot geen informatie bevatten over wat het probleem is en hoe het te reproduceren. Dit document poogt te beschrijven hoe goede probleemrapporten te schrijven. Wat is een goed probleemrapport? Kort door de bocht is een goed probleemrapport een rapport dat geanalyseerd kan worden en waar snel mee kan worden omgegaan, voor de wederzijdse voldoening van zowel de gebruiker als de ontwikkelaar. Hoewel de nadruk van dit artikel ligt op probleemrapporten voor &os;, zou het meeste ook in sterke mate op andere softwareprojecten van toepassing moeten zijn. Merk op dat dit artikel thematisch in plaats van chronologisch is ingedeeld, dus u dient het hele document te lezen alvorens een probleemrapport in te sturen, en het niet als een stapsgewijze tutorial te behandelen.
Wanneer een probleemrapport te versturen Er zijn vele soorten problemen, die niet allemaal geschikt zijn voor een probleemrapport. Natuurlijk is niemand perfect dus zal het soms voorkomen dat u overtuigd bent dat u een bug in een programma heeft gevonden terwijl u in feite de syntaxis voor een commando verkeerd begrepen heeft of een typefout in een instellingenbestand gemaakt heeft (hoewel dat soms zelf al op slechte documentatie of slechte foutafhandeling in de applicatie kan wijzen). Er zijn nog steeds veel gevallen waarin het insturen van een probleemrapport duidelijk niet de juiste handeling is, en het alleen tot frustratie bij uzelf en de ontwikkelaars leidt. Omgekeerd zijn er gevallen waarin het juist kan zijn om een probleemrapport in te sturen over iets anders dan een bug—bijvoorbeeld voor een verbetering of een nieuwe mogelijkheid. Dus hoe wordt bepaald of iets wel of niet een bug is? Een eenvoudige vuistregel is dat uw probleem geen bug is als het als een vraag kan worden uitgedrukt (meestal van de vorm Hoe doe ik X? of Waar kan ik Y vinden?). Het is niet altijd zo zwart-wit, maar de vraagregel gaat in de meeste gevallen op. Overweeg, als u een antwoord zoekt, om uw vraag aan de &a.questions; te stellen. Enkele gevallen waar het juist kan zijn om een probleemrapport in te sturen over iets dat geen bug is zijn: Meldingen van updates aan extern onderhouden software (over het algemeen ports, maar ook extern onderhouden componenten van het basissysteem zoals BIND of verscheidene gereedschappen van GNU). Voor onbeheerde ports (MAINTAINER bevat ports@FreeBSD.org) kan zo'n updatemelding opgepakt worden door een geïnteresseerde committer, of u kunt gevraagd worden om een patch aan te leveren om de port bij te werken; door dit van te voren aan te bieden verhoogt u in sterke mate de kans dat de port binnen een redelijk tijdsbestek wordt bijgewerkt. Als de port beheerd wordt, zijn PR's die nieuwe stroomopwaartse uitgaven aankondigen niet erg nuttig aangezien ze aanvullend werk voor de committers genereren, en waarschijnlijk weet de beheerder al dat er een nieuwe versie uit is, ze hebben er waarschijnlijk met de ontwikkelaars aan gewerkt, ze zijn waarschijnlijk regressietesten aan het uitvoeren, enzovoorts. In beide gevallen zal het volgen van het proces zoals beschreven in het Porters Handboek tot de beste resultaten leiden. (U bent misschien ook geïnteresseerd in Bijdragen aan de &os; Portscollectie.) Een bug die niet reproduceerbaar is kan zelden gerepareerd worden. Als een bug slechts eenmalig voorkwam en u deze niet kunt reproduceren, en het bij niemand anders lijkt voor te komen, dan bestaat de kans dat geen van de ontwikkelaars het kan reproduceren of kan uitzoeken wat er mis is. Dit betekent niet dat het niet gebeurde, maar wel dat de kans dat uw probleemrapport ooit tot een reparatie leidt erg klein is. Om het allemaal erger te maken, worden dit soort bugs vaak veroorzaakt door falende harde schijven of oververhitte processoren — u dient altijd te proberen om deze oorzaken, indien mogelijk, uit te sluiten voordat u een PR instuurt. Vervolgens, om te besluiten aan wie u uw probleemrapport dient te sturen, moet u weten dat de software waaruit &os; bestaat uit verschillende elementen is opgebouwd: Code in het basissysteem die geschreven is en onderhouden wordt door &os;-vrijwilligers, zoals de kernel, de C-bibliotheek, en de apparaatstuurprogramma's (gecategoriseerd als kern); de binaire hulpmiddelen (bin); de handleidingpagina's en documentatie (docs); en de webpagina's (www). Alle bugs in deze gebieden dienen aan de &os;-ontwikkelaars gerapporteerd te worden. Code in het basissysteem die geschreven is en onderhouden wordt door anderen, en in &os; is geïmporteerd en aangepast. Voorbeelden zijn bind, &man.gcc.1;, en &man.sendmail.8;. De meeste bugs in deze gebieden dienen aan de &os;-ontwikkelaars gerapporteerd te worden; maar in sommige gevallen kan het zijn dat ze aan de originele auteurs gerapporteerd moeten worden als de problemen niet specifiek voor &os; zijn. Gewoonlijk vallen deze bugs in ofwel de categorie bin ofwel de categorie gnu. Individuele applicaties die niet in het basissysteem zitten maar in plaats daarvan deel zijn van de Portscollectie van &os; (categorie ports). De meeste van deze applicaties zijn niet geschreven door &os;-ontwikkelaars; wat &os; biedt is slechts een raamwerk om de applicatie te installeren. Daarom dient u alleen een probleem aan de &os;-ontwikkelaars te rapporteren als u gelooft dat het probleem specifiek voor &os; is; anders dient u het aan de auteurs van de software te rapporteren. Daarna dient u vast te stellen of het probleem actueel is. Er zijn maar weinig dingen die een ontwikkelaar meer irriteren dan het ontvangen van een probleemrapport over een bug die reeds gerepareerd is. Als het probleem in het basissysteem zit, dient u eerst het FAQ-gedeelte over &os;-versies te lezen als u niet reeds bekend bent met het onderwerp. Het is niet mogelijk voor &os; om problemen in iets anders dan bepaalde recente takken van het basissysteem op te lossen, dus leidt het insturen van een bug-rapport over een oudere versie waarschijnlijk alleen tot het advies van een ontwikkelaar om naar een ondersteunde versie bij te werken om te kijken of het probleem nog steeds voorkomt. Het Security Officer Team onderhoudt de lijst van ondersteunde versies. Als het probleem in een port zit, moet u uw Portscollectie eerst naar de laatste versie bijwerken en kijken of het probleem nog steeds van toepassing is. Wegens de hoge snelheid waarmee deze applicaties veranderen, is het onhaalbaar voor &os; om iets anders dan de allernieuwste versies te ondersteunen, problemen met oudere versies van applicaties kunnen simpelweg niet worden opgelost.
Voorbereidingen Een goede regel is om altijd een vooronderzoek te doen voordat u een probleemrapport ingestuurd. Misschien is uw probleem reeds gerapporteerd; misschien wordt het besproken op de mailinglijsten, of gebeurde dat recentelijk; misschien is het al gerepareerd in een nieuwere versie dan die u draait. Om deze redenen dient u alle voor de hand liggende plaatsen te controleren voordat u uw probleemrapport instuurt. Voor &os; betekent dit: De &os;-lijst van Veelgestelde Vragen (FAQ). De FAQ probeert antwoord te geven op een breed scala aan vragen, zoals vragen die betrekking hebben op compatibiliteit van hardware, gebruikersapplicaties, en kernelconfiguratie. De mailinglijsten—als u niet geabonneerd bent, gebruik dan de doorzoekbare archieven op de &os;-website. Als uw probleem niet op de lijsten bediscussieerd is, kunt u proberen om er een bericht over te posten en enkele dagen wachten om te zien of iemand iets kan zien wat u misschien over het hoofd heeft gezien. Optioneel, het gehele web—gebruik uw favoriete zoekmachine om referenties naar uw probleem te vinden. U kunt zelfs hits krijgen van gearchiveerde mailinglijsten of nieuwsgroepen die u niet kende of waarvan u er niet aan had gedacht om die te doorzoeken. Vervolgens, de doorzoekbare &os; PR-database (GNATS). Tenzij uw probleem recent of obscuur is, bestaat er een redelijke kans dat het reeds gerapporteerd is. Het belangrijkste is dat u probeert te controleren of bestaande documentatie in de bronnen uw probleem bespreekt. Voor de basis-&os;-code dient u zorgvuldig de inhoud van het bestand /usr/src/UPDATING op uw systeem of de laatste versie ervan op te bestuderen. (Dit is essentiële informatie als u van de ene naar een andere versie bijwerkt—in het bijzonder als u naar de tak &os.current; bijwerkt.) Als het probleem echter zit in iets wat als deel van de &os; Portscollectie was geïnstalleerd, dan dient u /usr/ports/UPDATING (voor individuele ports) of /usr/ports/CHANGES (voor veranderingen die de gehele Portscollectie beïnvloeden) te raadplegen. en zijn ook beschikbaar via svnweb.
Het probleemrapport schrijven Nu u besloten heeft dat uw probleem een probleemrapport verdiend, en het een probleem met &os; is, is het tijd om het eigenlijke probleemrapport te schrijven. Voordat het mechanisme van het programma dat gebruikt wordt om PR's aan te maken en in te sturen wordt behandeld, zijn hier wat tips en trucs die ervoor zorgen dat uw PR het meest effectief is.
Tips en trucs voor het schrijven van een goed probleemrapport Laat de regel Synopsis niet leeg. De PR's gaan zowel naar een mailinglijst die over de gehele wereld wordt verspreid (waar de Synopsis wordt gebruikt voor de Onderwerp:-regel), als in een database. Iedereen die later de database op samenvatting doorzoekt, en een PR met een lege onderwerpsregel aantreft, zal het waarschijnlijk gewoon overslaan. Onthoud dat PR's in deze database blijven staan totdat iemand ze sluit; een anoniem PR zal slechts in de massa opgaan. Voorkom het gebruik van een zwakke Synopsis-regel. U mag niet aannemen dat iemand die uw PR leest enige achtergrondkennis van uw inzending heeft, dus des meer u biedt, des te beter. Op welk deel van het systeem heeft het probleem betrekking? Ziet u het probleem alleen tijdens het installeren, of tijdens het draaien? Ter illustratie, in plaats van Synopsis: portupgrade is broken, zie hoeveel informatiever dit lijkt: Synopsis: port pors-mgmt/portupgrade coredumps on -current. (In het geval van ports is het bijzonder behulpzaam om zowel de categorie als de portnaam in de Synopsis-regel te vermelden.) Als u een patch heeft, zeg dat dan. Het is veel waarschijnlijker dat een PR met daarin een patch bekeken wordt dan een PR zonder patch. Als u een patch bijsluit, plaats dan de tekst [patch] (inclusief de haken) aan het begin van de Synopsis. (Alhoewel het niet verplicht is om die exacte tekst te gebruiken, is dat per conventie degene die gebruikt wordt.) Als u een onderhouder bent, zeg dat dan. Als u een deel van de broncode onderhoudt (bijvoorbeeld een port), kunt u overwegen om de tekst [maintainer update] (inclusief de haken) aan het begin van de onderwerpsregel te plaatsen, en dient u zeker de Class van uw PR op maintainer-update te zetten. Op deze manier hoeft de committer die uw PR behandelt dit niet te controleren. Ben specifiek. Des te meer informatie u aanlevert over wat voor probleem u heeft, des te groter is de kans dat u een antwoord krijgt. Vermeld de versie van &os; die u draait (hier is een plaats voor, zie hieronder) en op welke architectuur dat is. U dient aan te geven of u een uitgave draait (bijvoorbeeld een CD-ROM of een download), of een systeem dat met Subversion wordt onderhouden (en zo ja, op welk revisienummer u zit). Als u de tak &os.current; volgt, is dat het allereerste wat iemand zal vragen, omdat reparaties (in het bijzonder voor opvallende problemen) de neiging hebben om snel gecommit te worden, en gebruikers van &os.current; worden geacht om hun zaken bij te houden. Vermeld welke globale opties u in uw make.conf heeft gespecificeerd. Noot: het specificeren van -O2 en hoger aan &man.gcc.1; staat in veel situaties als bug-gevoelig bekend. Hoewel de &os;-ontwikkelaars patches zullen accepteren, zijn ze over het algemeen niet bereid om zulke gevallen te onderzoeken vanwege een simpel gebrek aan tijd en vrijwilligers, en zullen ze in plaats hiervan antwoorden met dat dit gewoon niet ondersteund is. Als het probleem eenvoudig gereproduceerd kan worden, neem dan informatie op die een ontwikkelaar helpt om het probleem zelf te reproduceren. Al een probleem kan worden gedemonstreerd met specifieke invoer, neem dan een voorbeeld van die invoer op indien mogelijk, en neem zowel de eigenlijke als de verwachte uitvoer op. Als deze gegevens groot zijn of niet gepubliceerd kunnen worden, probeer dan om een minimaal bestand te maken dat hetzelfde probleem vertoont en dat in het PR kan worden opgenomen. Als het een probleem met de kernel betreft, reken er dan op om de volgende informatie aan te leveren. (U hoeft deze niet standaard bij te sluiten, wat alleen de database opvult, maar u dient uittreksel bij te sluiten die u relevant acht): uw kernelconfiguratie (inclusief welke hardware-apparaten u heeft geïnstalleerd) of u wel of niet debug-opties aan heeft staan (zoals WITNESS), en zo ja, of het probleem zich blijft voordoen als u de optie omkeert de volledige tekst van elke backtrace, panic of andere console-uitvoer, of regels in /var/log/messages als die waren gegenereerd De uitvoer van pciconf -l en relevante gedeelten van uw uitvoer van dmesg als uw probleem te maken heeft met een bepaald stuk hardware. het feit dat u /usr/src/UPDATING heeft gelezen en dat uw probleem daar niet staat vermeld (iemand gaat er geheid naar vragen) of u wel of niet op het draaien van een andere kernel kunt terugvallen (dit is om problemen gerelateerd aan hardware zoals falende schijven en oververhitte CPU's uit te sluiten, welke zich als kernelprobleem kunnen vermommen) Als het een probleem met de ports betreft, reken er dan op om de volgende informatie aan te leveren. (U hoeft deze niet standaard bij te sluiten, wat alleen de database opvult, maar u dient uittreksels bij te sluiten die u relevant acht): welke ports u heeft geïnstalleerd alle omgevingsvariabelen die de standaardwaarden in bsd.port.mk overschrijven, zoals PORTSDIR het feit dat u /usr/ports/UPDATING heeft gelezen en dat uw probleem daar niet staat vermeld (iemand gaat er geheid naar vragen) Voorkom vage verzoeken voor mogelijkheden. PR's van de vorm iemand moet echt iets dat zus-en-zo doet implementeren leveren minder waarschijnlijk resultaat op dan zeer specifieke verzoeken. Onthoud dat de broncode voor iedereen beschikbaar is, dus als u een mogelijkheid wilt is de beste manier om het erin te krijgen aan het werk te gaan! Neem ook het feit in overweging dat veel van dit soort dingen beter op freebsd-questions besproken kunnen worden dan als een regel in de PR-database, zoals hierboven besproken. Verzeker u ervan dat niemand anders reeds een soortgelijk PR heeft ingestuurd. Alhoewel dit al hierboven genoemd is, is het het herhalen hier waard. Het duurt slechts een minuut of twee om de webgebaseerde zoekmachine op te gebruiken. (Natuurlijk vergeet iedereen dit zo nu en dan.) Rapporteer slechts één zaak per Probleemrapport. Voorkom het bijsluiten van twee of meer problemen in hetzelfde rapport tenzij ze gerelateerd zijn. Voorkom, wanneer patches worden bijgevoegd, het toevoegen van meerdere mogelijkheden of het repareren van meerdere bugs in hetzelfde PR tenzij ze sterk gerelateerd zijn—het oplossen van zulke PR's duurt vaak langer. Voorkom controversiële verzoeken. Als uw PR een gebied behandelt dat in het verleden controversieel was, dient u waarschijnlijk bereid te zijn om niet alleen patches, maar ook een verklaring waarom de patches Het Juiste Ding Om Te Doen zijn aan te leveren. Zoals hierboven vermeld, is het zorgvuldig doorzoeken van de mailinglijsten door gebruik te maken van de archieven op altijd een goede voorbereiding. Ben beleefd. Bijna iedereen die aan uw PR zal werken is een vrijwilliger. Niemand houdt ervan om te horen dat ze iets moeten doen wat ze al aan het doen zijn voor een andere motivatie dan geld. Dit is iets goeds om altijd in de gaten te houden bij Open Source projecten.
Voordat u begint Als u het programma &man.send-pr.1; gebruikt, zorg er dan voor dat uw omgevingsvariabele VISUAL (of EDITOR als VISUAL niet is ingesteld) op iets zinnigs is ingesteld. U dient er ook zeker van te zijn dat het afleveren van mail goed werkt. &man.send-pr.1; gebruikt mailberichten voor het insturen en volgen van probleemrapporten. Als u geen mailberichten kunt posten op de machine waarop u &man.send-pr.1; draait, zal uw probleemrapport de GNATS-database niet bereiken. Zie voor details over het opzetten van mail op &os; het hoofdstuk Elektronische post van het &os; Handboek op . Verzeker u ervan dat uw mailprogramma het bericht onderweg naar GNATS niet vermangelt. In het bijzonder zal elke patch die u instuurt onbruikbaar worden, als uw mailer automatisch regels afbreekt, tabs in spaties verandert, of nieuwe-regel-tekens escapet. Voor de tekstgedeelten vragen wij u echter om handmatig regels rond de 70 tekens af te breken, zodat de webversie van het PR leesbaar is. Dezelfde soort overwegingen gelden als u het webgebaseerde PR-instuurformulier in plaats van &man.send-pr.1; gebruikt. Merk op dat knip-en-plakbewerkingen hun eigen bijwerkingen op tekstopmaak kunnen hebben. In bepaalde gevallen kan het nodig zijn om &man.uuencode.1; te gebruiken om er zeker van te zijn dat patches ongewijzigd aankomen. Ten slotte, als uw inzending lang is, dient u uw werk offline voor te bereiden zodat er niets verloren gaat indien er zich een probleem met het inzenden ervan voordoet. Dit kan in het bijzonder een probleem zijn met het webformulier.
Patches of bestanden bijvoegen Het volgende geldt voor het versturen van PR's via email: Het programma &man.send-pr.1; heeft voorzieningen voor het bijvoegen van bestanden aan een probleemrapport. U kunt zoveel bestanden bijvoegen als u wilt op voorwaarde dat elk bestand een unieke basisnaam (i.e., de naam van het bestand zelf, zonder het pad) heeft. Gebruik de opdrachtregeloptie om de namen van de bij te voegen bestanden te specificeren: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/fouten Maakt u zich geen zorgen over binaire bestanden, deze worden automatisch gecodeerd zodat ze de mail-agent niet verontrusten. Als u een patch bijvoegt, gebruik dan de optie of van &man.diff.1; om een context- of verenigde diff (verenigd is geprefereerd) aan te maken, en zorg ervoor dat u de exacte revisienummers uit SVN specificeert van de bestanden die u heeft gewijzigd zodat de ontwikkelaars die uw rapport lezen ze gemakkelijk kunnen toepassen. Voor problemen met de kernel of de basisgereedschappen is een patch tegen &os.current; (de Subversion-tak HEAD) geprefereerd aangezien alle nieuwe code eerst daar toegepast en getest dient te worden. Nadat het voldoende of substantieel is getest, wordt de code samengevoegd of gemigreerd naar de tak &os.stable;. Als u een patch inline in plaats van als bijlage bijvoegt, merk dan op dat het meest voorkomende probleem de neiging is van sommige email-programma's om tabs als spaties weer te geven, wat alles dat bedoeld was als deel van een Makefile volledig ruineert. Stuur geen patches als bijlagen door gebruik te maken van Content-Transfer-Encoding: quoted-printable. Dit zal karakter-escaping uitvoeren en de gehele patch waardeloos maken. Merk ook op dat hoewel het over het algemeen goed is om kleine patches in een PR op te nemen—in het bijzonder als ze het probleem dat in het PR beschreven is oplossen—grote patches en in het bijzonder nieuwe code waarvoor substantiële review nodig kan zijn voordat het gecommit wordt op een web- of FTP-server geplaatst dient te worden, en de URL in plaats van de patch bij het PR gevoegd dient te worden. Patches in email hebben de neiging om gemangeld te worden, in het bijzonder wanneer GNATS erbij betrokken is, en hoe groter de patch, des te moeilijker het is voor geïnteresseerde partijen om het te ontrafelen. Ook stelt het posten van een patch op het web u in staat om het te wijzigen zonder dat het nodig is om de gehele patch opnieuw in te zenden als een vervolgbericht op het originele PR. Ten slotte vergroten grote patches simpelweg de omvang van de database, aangezien gesloten PR's niet worden verwijderd maar in plaats daarvan worden bewaard en simpelweg als closed worden gemarkeerd. U dient ook te weten dat tenzij u het expliciet in uw PR of in de patch zelf vermeld, dat van alle patches die u instuurt wordt aangenomen dat ze onder dezelfde licentietermen vallen als het originele bestand dat u heeft gewijzigd.
Het sjabloon invullen De volgende sectie heeft alleen betrekking op de email-methode: Wanneer u &man.send-pr.1; draait, wordt er een sjabloon aan u gepresenteerd. Het sjabloon bestaat uit een lijst met velden, waarvan sommige al zijn ingevuld, en waarvan bij anderen staat uitgelegd wat de bedoeling is of wat acceptabele waarden zijn. Maakt u zich geen zorgen over het commentaar, deze worden automatisch verwijderd wanneer u ze niet wijzigt of ze zelf verwijdert. Bovenaan het sjabloon, onder de regels met SEND-PR:, staan de email-koppen. U hoeft deze normaalgesproken niet te wijzigen, tenzij u het probleemrapport vanaf een machine of account verstuurt die wel mail kan versturen maar niet kan ontvangen; in dat geval wilt u waarschijnlijk de velden From: en Reply-To: op uw echte emailadres instellen. U kunt uzelf (of iemand anders) een carbonkopie van het probleemrapport versturen door één of meer emailadressen aan de kop Cc: toe te voegen. Alleen in het email-sjabloon vindt u de volgende velden van één regel: Submitter-Id: Verander dit niet. De standaardwaarde current-users is juist, zelfs als u &os.stable; draait. Confidential: Dit is vooraf ingevuld met no. Het heeft geen zin om dit te veranderen aangezien er geen vertrouwelijk &os; probleemrapport bestaat—de PR-database wordt wereldwijd gedistribueerd. Severity: Eén van non-critical, serious of critical. Overdrijf niet, bestempel uw probleem niet als critical tenzij het dat echt is (bijvoorbeeld gevallen van gegevenscorruptie, serieuze functionele regressie ten opzichte van een vorige -CURRENT) of als serious tenzij het iets is dat vele gebruikers aangaat (kernelpanics of bevroren computers; problemen met bepaalde apparaatstuurprogramma's of systeemgereedschappen). &os;-ontwikkelaars zullen niet noodzakelijk sneller aan uw probleem werken als u de belangrijkheid ervan opblaast aangezien er vele anderen zijn die precies hetzelfde gedaan hebben — in feite schenken sommige ontwikkelaars weinig aandacht aan dit veld vanwege deze redenen. Beveiligingsproblemen dienen niet naar GNATS gestuurd te worden, omdat alle GNATS-informatie publieke kennis is. Stuur zulke problemen alstublieft volgens onze richtlijnen voor beveilingsrapportages.. Priority: Eén van low, medium of high. high dient te worden gereserveerd voor problemen die bijna iedere gebruiker van &os; aangaan en medium voor iets dat vele gebruikers aangaat. Dit veld is zo vaak misbruikt dat het bijna volledig betekenisloos is geworden. De volgende sectie beschrijft velden die zowel in de email-interface als in de webinterface voorkomen: Originator: Specificeer hier alstublieft uw echte naam, eventueel gevolgd door uw emailadres in punthaken. In de email-interface wordt dit normaalgesproken vooraf ingevuld met het gecos-veld van de huidige aangemelde gebruiker. Het emailadres dat u gebruikt wordt publieke informatie en kan in de handen van spammers vallen. U dient òfwel maatregelen te treffen om spam af te handelen, òf een tijdelijk emailaccount te gebruiken. Merk op dat als u een in het geheel ongeldig emailaccount gebruikt, wij u geen vragen over uw PR kunnen stellen. Organization: Alles waarvan u vrolijk wordt. Dit veld wordt niet voor iets significants gebruikt. Synopsis: Vul hier een korte en accurate beschrijving van het probleem in. De samenvatting wordt gebruikt als het onderwerp van de email van het probleemrapport, en wordt gebruikt in lijsten en samenvattingen van probleemrapporten; probleemrapporten met een obscure samenvatting hebben de neiging om genegeerd te worden. Zoals hierboven vermeld, als uw probleemrapport een patch bevat, begin dan alstublieft de samenvatting met [patch] (inclusief de haken); als het een ports-PR is en u de port onderhoudt, overweeg dan om [maintainer update] (inclusief de haken) toe te voegen en de Class van uw PR op maintainer-update te zetten. Category: Kies een geschikte categorie. Het eerste wat u moet doen is beslissen in welk gebied van het systeem uw probleem ligt. Onthoud dat &os; een compleet besturingssysteem is, dat zowel een kernel, de standaardbibliotheken, vele hulpstuurprogramma's, en een groot aantal gereedschappen (het basissysteem) installeert. Er zijn echter duizenden aanvullende applicaties in de Portscollectie. U dient eerst te beslissen of het probleem in het basissysteem zit of dat het in iets dat via de Portscollectie geïnstalleerd is zit. Hier volgt een beschrijving van de grote categoriën: Als er een probleem met de kernel, de bibliotheken (zoals de standaard C-bibliotheek libc), of een hulpstuurprogramma is, gebruikt u in het algemeen de categorie kern. (Er zijn enkele uitzonderingen die hieronder vermeld staan). In het algemeen zijn dat dingen die in sectie 2, 3, of 4 van de handleidingpagina's staan beschreven. Als er een probleem met een binair programma zoals &man.sh.1; of &man.mount.8; is, dient u eerst te bepalen of deze programma's deel zijn van het basissysteem of dat ze via de Portscollectie zijn toegevoegd. Als u het niet zeker weet, kunt u whereis programmanaam uitvoeren. De conventie van &os; voor de Portscollectie is om alles onder /usr/local te installeren, alhoewel dit door een systeembeheerder veranderd kan worden. Voor dezen gebruikt u de categorie ports (zelfs als de categorie van de port www is; zie hieronder). Als de locatie /bin, /usr/bin, /sbin, of /usr/sbin is, dan is het een onderdeel van het basissysteem, en dient u de categorie bin te gebruiken. (Enkele programma's, zoals &man.gcc.1;, gebruiken eigenlijk de categorie gnu, maar daarover hoeft u zich nu geen zorgen te maken.) Dit zijn allemaal programma's die in sectie 1 of 8 van de handleidingpagina's worden beschreven. Als u denkt dat de fout in de opstartscripts (rc) zit, of in een ander type onuitvoerbaar configuratiebestand, dan is de juiste categorie conf (configuratie). Deze dingen worden in sectie 5 van de handleidingpagina's beschreven. Als u een probleem in de documentatie (artikelen, boeken, handleidingpagina's) heeft gevonden, dan is de juiste keuze docs. Als u een probleem heeft met de &os; webpagina's, dan is de juiste www. Als u problemen heeft met iets dat van een port genaamd www/portnaam afkomt, dan hoort dit desalniettemin in de categorie ports thuis. Er zijn nog enkele gespecialiseerde categoriën: Als het probleem in kern gestopt zou worden maar met het USB-subsysteem te maken heeft, dan is de juiste keuze usb. Als het probleem in kern gestopt zou worden maar het met de threading-bibliotheken te maken heeft, dan is de juiste keuze threads. Als het probleem in het basissysteem zit, maar het met onze naleving van standaarden zoals &posix; te maken heeft, dan is de juiste keuze standards. Als het probleem te maken heeft met interne fouten van de &java.virtual.machine; (&jvm;), dan dient u de categorie java te kiezen, zelfs als was &java; vanuit de Portscollectie geïnstalleerd. Meer algemene problemen met &java;-ports horen nog steeds onder ports thuis. Dit laat al het andere achter. Als u ervan overtuigd bent dat het probleem zich alleen voordoet onder de processorarchitectuur die u gebruikt, kies dan één van de architectuurspecifieke categoriën: gewoonlijk i386 voor Intel-compatibele machines in 32-bit-modus; amd64 voor AMD-machines die in 64-bit-modus draaien (dit omvat ook Intel-compatibele machines die in EMT64-modus draaien); en minder gewoonlijk arm, ia64, powerpc, en sparc64. Deze categoriën worden vaak misbruikt voor Ik weet het niet-problemen. Gebruik alstublieft misc, in plaats van te raden. Correct gebruik van een arch-specifieke categorie U heeft een gewone PC-gebaseerde machine, en denkt dat u een probleem bent tegengekomen dat specifiek is voor een bepaalde chipset of een bepaald moederbord: i386 is de juiste categorie. Onjuist gebruik van een arch-specifieke categorie U heeft een probleem met een insteekkaart op een veelvoorkomende bus, of een probleem met een bepaald type harde schijfstation: in dit geval is het waarschijnlijk op meer dan één architectuur van toepassing, en is kern de juiste categorie. Als u echt niet weet waar het probleem zich bevindt (of als de uitleg niet bij een van de bovenstaanden lijkt te passen), gebruik dan de categorie misc. Voordat u dit doet, kunt u eerst hulp vragen aan de &a.questions;. U krijgt dan misschien het advies dat een bestaande categorie echt een betere keuze is. Hier is een actuele lijst van categoriën (van ): advocacy: problemen gerelateerd aan het publieke imago van &os;. Overbodig. amd64: problemen specifiek aan het platform AMD64. arm: problemen specifiek aan het platform ARM. bin: problemen met gebruikersprogramma's in het basissysteem. conf: problemen met configuratiebestanden, standaardwaarden, enzovoorts. docs: problemen met handleidingpagina's of online documentatie. gnu: problemen met geïmporteerde GNU-software zoals &man.gcc.1; of &man.grep.1;. i386: problemen specifiek aan het &i386;-platform. ia64: problemen specifiek aan het ia64-platform. java: problemen gerelateerd aan de &java; Virtual Machine. kern: problemen met de kernel, (platforminspecifieke) apparaatstuurprogramma's, of de basisbibliotheken. misc: alles wat niet in een van de andere categoriën past. (Merk op dat er bijna niets is wat echt in deze categorie past, behalve problemen met de uitgave- en bouwinfrastructuur. Tijdelijke bouwfouten op HEAD horen hier niet thuis. Merk ook op dat dingen in deze categorie gemakkelijk kwijtraken). ports: problemen gerelateerd aan de Portscollectie. powerpc: problemen specifiek voor het &powerpc;-platform. sparc64: problemen specifiek voor het &sparc64;-platform. standards: Zaken met betrekking tot conformatie aan standaarden. threads: problemen gerelateerd aan de implementatie van threads op &os; (in het bijzonder op &os.current;). usb: problemen gerelateerd aan de implementatie van USB op &os;. www: Veranderingen of verbeteringen aan de website van &os;. Class: Kies één van de volgenden: sw-bug: softwarebugs. doc-bug: fouten in documentatie. change-request: verzoeken voor aanvullende mogelijkheden of veranderingen in bestaande mogelijkheden. update: updates aan ports of andere bijgedragen software. maintainer-update: updates aan ports die u onderhoudt. Release: De versie van &os; die u draait. Dit wordt automatisch ingevuld als u &man.send-pr.1; gebruikt en hoeft alleen veranderd te worden als u een probleemrapport verstuurt vanaf een ander systeem dan van hetgene waarop het probleem zich voordoet. Ten slotte zijn er een aantal meerregelige velden: Environment: Dit dient zou nauwkeurig mogelijk de omgeving te beschrijven waarin het probleem is waargenomen. Dit omvat de versie van het besturingssysteem, de versie van het specifieke programma of bestand dat het probleem bevat, en alle andere relevante zaken zoals systeemconfiguratie, andere geïnstalleerde software dat het probleem beïnvloedt, enzovoorts— eigenlijk alles wat een ontwikkelaar moet weten om de omgeving te reconstrueren waarin het probleem optreedt. Description: Een complete en nauwkeurige beschrijving van het probleem dat u ondervindt. Probeer speculaties over de oorzaken van het probleem te vermijden tenzij u zeker weet dat u op het juiste spoor zit, aangezien een ontwikkelaar hierdoor onjuiste aannames over het probleem kan maken. How-To-Repeat: Een samenvatting van de acties die nodig waren om het probleem te reproduceren. Fix: Bij voorkeur een patch, of op zijn minst een tijdelijke oplossing (wat niet alleen andere mensen helpt om het probleem te omzeilen, maar mogelijk ook een ontwikkelaar de oorzaak van het probleem helpt te begrijpen), maar als u hier ook geen echte ideëen over heeft is het beter om dit veld open te laten dan om te speculeren.
Het probleemrapport versturen Als u &man.send-pr.1; gebruikt: Als u klaar bent met het invullen van het sjabloon, het heeft opgeslagen, en uw tekstverwerker verlaten heeft, zal &man.send-pr.1; u de prompt s)end, e)dit or a)bort? tonen. U kunt dan s aanslaan om het probleemrapport in te sturen, e aanslaan om de tekstverwerker te herstarten en verdere wijzigingen te maken, of a aanslaan om te stoppen. Als u het laatste kiest, blijft uw probleemrapport bewaard op schijf (&man.send-pr.1; vertelt u de bestandsnaam voordat het eindigt), zodat u het rustig kunt bewerken, of het misschien over kunt plaatsen naar een systeem met een betere netverbinding, voordat u het met de optie van &man.send-pr.1; verstuurt: &prompt.user; send-pr -f ~/mijn-probleemrapport Dit leest het gespecificeerde bestand, controleert de geldigheid van de inhoud, verwijdert commentaar en verstuurt het. Als u het webformulier gebruikt: Voordat u op submit drukt, moet u een veld invullen waarin tekst staat dat als afbeelding op de pagina wordt weergegeven. Deze ongelukkige maatregel moest worden genomen vanwege het misbruik door geautomatiseerde systemen en enkele kwaadwillige gebruikers. Het is noodzakelijk kwaad dat niemand leuk vindt; vraag ons alstublieft niet om het te verwijderen. Merk op dat u ten zeerste wordt aangeraden om uw werk ergens op te slaan voordat u op submit drukt. Een veelvoorkomend probleem voor gebruikers is dat hun webbrowser een verouderde afbeelding uit de cache laat zien. Als u dit overkomt, wordt uw inzending geweigerd en kan u uw werk verliezen. Als u om een bepaalde reden geen afbeeldingen kunt bekijken, en u ook &man.send-pr.1; niet kunt gebruiken, accepteer dan alstublieft onze verontschuldigingen voor het ongemak en email uw probleemrapport naar het bugbuster-team op freebsd-bugbusters@FreeBSD.org.
Vervolg Als uw probleemrapport eenmaal is ingestuurd, ontvangt u een bevestiging per email waarin het volgnummer dat aan uw probleemrapport was toegewezen en een URL dat u kunt gebruiken om de status te controleren zijn opgenomen. Met een beetje geluk zal iemand interesse in uw probleem tonen en proberen het op te lossen, of, wat het geval kan zijn, uitleggen waarom het geen probleem is. U wordt automatisch op de hoogte gehouden van alle toestandsveranderingen, en u ontvangt kopiën van al het commentaar en patches die iemand aan het controletraject van uw probleemrapport kan koppelen. Als iemand aanvullende informatie van u vraagt, of als u zich iets herinnert of iets ontdekt dat u niet in het initiële rapport noemde, gebruik dan alstublieft één van de twee methoden om uw vervolg in te sturen: De gemakkelijkste manier is om de vervolgkoppeling op de webpagina van het individuele PR te gebruiken, welke u kunt bereiken vanuit de PR-zoekpagina. Het klikken op deze koppeling brengt een email-venster naar voren met daarin de juiste regels voor Aan: en Onderwerp: ingevuld (als uw browser is ingesteld om dit te doen). Als alternatief kunt u het naar &a.bugfollowup; mailen, waarbij het volgnummer in het onderwerp is opgenomen zodat het foutenvolgsysteem weet aan welk probleemrapport het vervolg gekoppeld moet worden. Als u het volgnummer niet opgeeft, raakt GNATS in de war en maakt het een geheel nieuw PR aan welke het vervolgens aan de GNATS-beheerder toekent, en vervolgens raakt uw PR kwijt totdat iemand de rommel opruimt, wat dagen of weken later kan zijn. Verkeerde manier: Onderwerp: that PR I sent Juiste manier: Onderwerp: Re: ports/12345: compilation problem with foo/bar Als het probleemrapport open blijft nadat het probleem is opgelost, stuur dan een vervolg (op de bovenstaande manier) waarin u vertelt dat het probleemrapport gesloten kan worden, en indien mogelijk, uitlegt hoe of wanneer het probleem was opgelost.
Als u problemen heeft De meeste PR's gaan door het systeem en worden snel geaccepteerd; soms loopt GNATS echter achter en kan het zijn dat u uw email-bevestiging pas na 10 minuten of zelfs later ontvangt. Wees alstublieft geduldig. Tevens geldt, omdat GNATS alle invoer via email ontvangt, dat het absoluut noodzakelijk is dat &os; alle inzendingen door spam-filters haalt. Als u binnen een uur of twee geen antwoord krijgt, kan uw PR misschien zijn opgeslokt; als dit zo is, neem dan alstublieft contact op met de GNATS-beheerders op bugmeister@FreeBSD.org en vraag om hulp. Een veelvoorkomende anti-spam-maatregel is het vergelijken met vele vormen van misbruik die in HTML-gebaseerde email voorkomen (alhoewel niet noodzakelijk het slechts opnemen van HTML in een PR). We raden het gebruik van HTML-gebaseerde email voor het versturen van PR's sterk af: niet alleen is het waarschijnlijker dat het niet door de filters komt, het heeft ook de neiging om de database te verstoppen. Oude platte email wordt sterk geprefereerd. In zeldzame gevallen zult een bug in GNATS tegenkomen waarbij een PR geaccepteerd is en een volgnummer toegewezen heeft gekregen maar waarbij het niet op de lijst van PR's van een van de opvraag-webpagina's staat. Het kan zijn gebeurd dat de index van database niet meer met de database zelf is gesynchroniseerd. De manier waarop u dit kunt testen is door de webpagina bekijk een enkel PR op te roepen en te kijken of het PR wordt vermeld. Als dat zo is, stel dan alstublieft de GNATS-beheerders op bugmeister@FreeBSD.org op de hoogte. Merk op dat er een cron-taak is die de database periodiek herbouwt, dus u hoeft geen actie te ondernemen tenzij u haast heeft.
Verdere literatuur Er is een lijst met bronnen die relevant is voor het juist schrijven en verwerken van probleemrapporten. Het is in geen geval compleet. Effectief softwarestoringen melden—een uitstekend essay door Simon G. Tatham over het samenstellen van nuttige (niet-&os;-specifieke) probleemrapporten. Problem Report Handling Guidelines—waardevolle inzichten in hoe probleemrapporten worden afgehandeld door de &os;-ontwikkelaars.
+ +
diff --git a/nl_NL.ISO8859-1/books/handbook/Makefile b/nl_NL.ISO8859-1/books/handbook/Makefile index 7ef0b5d2c6..235967baec 100644 --- a/nl_NL.ISO8859-1/books/handbook/Makefile +++ b/nl_NL.ISO8859-1/books/handbook/Makefile @@ -1,351 +1,349 @@ # # $FreeBSD$ # # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile # %SRCID% 42118 # # Bouw het Nederlandse FreeBSD Handboek. # # ------------------------------------------------------------------------ # # Handboekspecifieke variabelen # # WITH_PGPKEYS De gedrukte verie van het handboek geeft standaard # alleen PGP vingerafdrukken weer. Als het gewenst # is dat de complete sleutel wordt weergegeven dan # dient deze variabele insteld te worden. De optie # heeft geen invloed op de HTML formaten. # # Handboekspecifieke doelen # # pgpkeyring Dit doel leest de inhoud van pgpkeys/chapter.xml # en schrijft dan alle PGP sleutels naar stdout. # De uitvoer kan omgeleid worden naar een bestand # en verspreid worden als een publieke sleutelring # van FreeBSD ontwikkelaars die eenvoudig in # PGP/GPG ingelezen kan worden. # # ------------------------------------------------------------------------ # Om een nieuw hoofdstuk aan het Handboek toe te voegen: # # - Werk deze Makefile, chapters.ent en book.xml bij # - Voeg een beschrijving voor het nieuwe hoofdstuk toe aan preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= remko@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/pxe-nfs.png IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Afbeeldingen van de afbeeldingenbibliotheek IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS-lijsten van de individuele XML-bestanden die het document vormen. # Veranderingen aan een van deze bestanden zal een nieuwe build afdwingen # # XML-inhoud SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entiteiten SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Neem alle hoofdstukken mee. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${XSLTPROC} ${XSLPGP} ${DOC}.parsed.xml # # Handboekspecifieke variablen # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # regels die lijsten met mirrors vanuit de XML-database genereren. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/nl_NL.ISO8859-1/books/handbook/chapters.ent b/nl_NL.ISO8859-1/books/handbook/chapters.ent index c983f6cf3a..5f553b5c7e 100644 --- a/nl_NL.ISO8859-1/books/handbook/chapters.ent +++ b/nl_NL.ISO8859-1/books/handbook/chapters.ent @@ -1,74 +1,74 @@ %pgpkeys; - + "> diff --git a/pl_PL.ISO8859-2/books/handbook/Makefile b/pl_PL.ISO8859-2/books/handbook/Makefile index e1aaa878a6..06f8da187d 100644 --- a/pl_PL.ISO8859-2/books/handbook/Makefile +++ b/pl_PL.ISO8859-2/books/handbook/Makefile @@ -1,257 +1,255 @@ # The FreeBSD Polish Documentation Project # # $FreeBSD$ # Original revision: 1.100 # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/desktop.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= install/xf86setup.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/pl_PL.ISO8859-2/books/handbook/chapters.ent b/pl_PL.ISO8859-2/books/handbook/chapters.ent index 7117d36d11..8127fd135e 100644 --- a/pl_PL.ISO8859-2/books/handbook/chapters.ent +++ b/pl_PL.ISO8859-2/books/handbook/chapters.ent @@ -1,70 +1,70 @@ %pgpkeys; - + "> diff --git a/pt_BR.ISO8859-1/articles/contributing-ports/article.xml b/pt_BR.ISO8859-1/articles/contributing-ports/article.xml index 8bfdb6dbee..190c69dea9 100644 --- a/pt_BR.ISO8859-1/articles/contributing-ports/article.xml +++ b/pt_BR.ISO8859-1/articles/contributing-ports/article.xml @@ -1,1076 +1,1078 @@
Contribuindo para a Coleção de Ports do FreeBSD Sumário Este artigo descreve as formas pelas quais uma pessoa pode contribuir com a Coleção de Ports do FreeBSD. Sam Lawrance Mark Linimon &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Contribuindo com o ports Introdução A Coleção de Ports é um trabalho permanente, em constante evolução. Nós queremos oferecer aos nossos usuários um repositório de softwares de terceiros que seja fácil de utilizar, atualizado e de alta qualidade. Qualquer um pode se envolver, e existem muitas formas diferentes de fazer isso. Contribuir para a coleção de ports é uma excelente forma de ajudar e de devolver algo para o projeto. Não importa se você está à procura de participação contínua, ou apenas um desafio divertido para um dia chuvoso, nós vamos adorar receber a sua ajuda! Como voluntário, o que você faz é limitado apenas pelo que você quer fazer. No entanto, pedimos que você tome conhecimento do que os outros membros da comunidade &os; irão esperar de você. Você pode querer levar isso em conta antes de decidir se voluntariar. O que você pode fazer para ajudar Existem várias maneiras pelas quais você pode contribuir para manter a árvore de Ports atualizada e em boas condições de funcionamento: Encontre algum software legal e útil e crie um port para ele. Existe um grande número de ports que não têm nenhum mantenedor (maintainer). Torne-se um mantenedor e adote um port. Se você tiver criado ou adotado um port, tome conhecimento do que precisa fazer agora que é um mantenedor. Quando você estiver procurando por um desafio rápido você pode corrigir um bug ou um port quebrado. Criando um novo <literal>port</literal> Existe um documento separado, disponível para ajudar e guiá-lo no processo de criação (ou de atualização) de um port, chamado Porter's Handbook. O Porter's Handbook é a melhor fonte de referência para se trabalhar no sistema de ports. Ele fornece detalhes de como o sistema de ports funciona e discute as boas práticas recomendadas. Adotando um <literal>port</literal> sem manutenção Escolhendo um <literal>port</literal> sem manutenção Assumir a responsabilidade pela manutenção de um port que está abandonado é uma excelente forma de se envolver. Ports sem manutenção só são atualizados ou consertados quando alguém se voluntaria à trabalhar neles. Existe um grande número de ports sem manutenção. É uma boa idéia iniciar com a adoção de um port que você usa regularmente. Os ports sem manutenção tem a variável MAINTAINER setada como ports@FreeBSD.org em seu Makefile. A lista dos ports sem manutenção, seus erros atuais, e seus respectivos relatórios de problema , pode ser vista no Sistema de Monitoração de Ports do FreeBSD. Alguns ports afetam um grande número de outros devido as suas dependências e aos ports escravos. Você deve esperar até que tenha alguma experiência antes de se voluntariar para manter um port destes. Você pode descobrir se um port tem ou não dependências ou ports escravos, observando o índice principal de ports chamado INDEX. (O nome do arquivo varia de acordo com a release do &os;; por exemplo, INDEX-8.) Alguns ports têm dependências condicionais que não são incluídas na compilação padrão do INDEX. Esperamos que você seja capaz de identificar estes ports observando os Makefiles dos outros ports. Como adotar um <literal>port</literal> Primeiro certifique-se de que você compreende as suas responsabilidades como um mantenedor. Também leia o Porter's Handbook. Por favor, não se comprometa com mais do que o que você se sente capaz de fazer. Você pode pedir para se tornar o responsável por um port sem manutenção no momento em que desejar. Basta definir o MAINTAINER para o seu próprio email e enviar um PR (relatório de problema) com a mudança. Se o port tiver erros de compilação ou se estiver precisando de atualização, você pode querer enviar quaisquer outras alterações no mesmo PR. Isto irá ajudar porque muitos comitters estão pouco dispostos a designar alguém sem um histórico conhecido junto ao &os; como responsável pela manutenção de um port. Enviar PRs os quais corrigem erros de compilação ou que atualizam ports é a melhor forma de estabelecer um. Envie o seu PR com a categoria ports e a classe change-request. Um comitter irá examinar o seu PR, dar commit das alterações e finalmente fechar o seu PR. Algumas vezes este processo pode demorar um pouco (afinal os comitters também são voluntários). Os desafios dos mantenedores de <literal>ports</literal> Esta seção lhe dará uma idéia de porque os ports precisam ser mantidos e irá apresentar as responsabilidades de um mantenedor de ports. Porque os <literal>ports</literal> precisam de manutenção Criar um port é uma tarefa que demanda esforço uma única vez. Garantir que um port está atualizado e que continua a compilar e a executar é um esforço de manutenção permanente. Os mantenedores (maintainers), são pessoas as quais dedicam uma parte do seu tempo para a realização destes objetivos. A principal razão pela qual o sistema de ports precisa de manutenção é trazer os melhores e mais recentes softwares de terceiros para a comunidade &os;. Um desafio adicional é manter os ports individuais trabalhando com o framework da Coleção de Ports a medida que ele evolui. Como mantenedor, você vai precisar gerenciar os seguintes desafios: Novas versões de software e atualizações. Novas versões e atualizações de softwares que já pertencem ao ports tornam-se disponíveis o tempo todo, e estes têm de ser incorporados a Coleção de Ports a fim de atualizar os softwares disponibilizados por ela. Alterações em dependências. Se forem feitas mudanças significativas nas dependências de seu port, ele pode precisar ser atualizado para que continue a funcionar corretamente. Alterações que afetam <literal>ports</literal> que dependem do seu. Se outros ports dependem de um port que você mantém, alterações em seu port podem demandar coordenação com outros mantenedores. Interação com outros usuários, mantenedores e desenvolvedores. Parte do trabalho de um mantenedor é atuar no suporte. Não esperamos que você ofereça suporte generalizado (mas será bem vindo se você optar por isto). O que você deve oferecer é um ponto de coordenação para questões sobre os seus ports que sejam especificos ao &os;. Caça aos bugs. Um port pode ser afetado por erros que são específicos ao &os;. Você vai precisar investigar, encontrar e corrigir estes erros quando eles forem reportados. Testar exaustivamente um port para identificar problemas antes que eles cheguem na Coleção de Ports é ainda melhor. Alterações na política e na infra-estrutura de <literal>ports</literal>. Ocasionalmente, os sistemas que são utilizados para compilar os ports e os pacotes são atualizados ou uma nova recomendação que afeta esta infra-estrutura é feita. Você deve estar ciente destas alterações para o caso dos seus ports serem afetados e precisarem de atualização. Alterações no sistema base. O &os; está em constante desenvolvimento. Alterações ao software, as bibliotecas, ao kernel ou mesmo alterações na política podem alterar os requisitos de um port. Responsabilidades de um Mantenedor Mantenha seus <literal>ports</literal> atualizados Esta seção descreve o processo que você deve seguir para manter seus ports atualizados. Esta é uma visão geral. Maiores informações sobre o processo de atualização de um port estão disponíveis no Porter's Handbook. Fique atentendo para as atualizações Monitore o desenvolvedor para tomar conhecimento sobre a liberação de novas versões, atualizações, e correções de segurança para o software do seu port. Listas de discussão destinadas a avisos de lançamentos ou páginas web de notícias são úteis para fazer isso. Algumas vezes os usuários irão entrar em contato com você e perguntar quando o seu port será atualizado. Se você está ocupado com outras coisas ou se por qualquer outra razão não pode fazer a atualização naquele momento, pergunte se eles irão ajudá-lo enviando um PR com a atualização. Você também pode receber um email automático do sistema de verificação de ports do &os; informando que uma nova versão do seu port's distfile está disponível. Maiores informações sobre este sistema (incluindo a de como parar emails futuros) serão fornecidas na mensagem. Incorpore as alterações Quando elas se tornarem disponíveis, incorpore as mudanças ao seu port. Você precisa ser capaz de gerar um patch entre o seu port original e o seu port atualizado. Revisão e teste Examine cuidadosamente e teste as suas alterações: Compile, instale e teste o seu port no maior número possível de plataformas e arquiteturas. É comum que um port funcione em um branch ou plataforma e falhe em outra. Certifique-se de que as dependências do seu port estão completas. A melhor forma de fazer isto é instalar a sua própria ports tinderbox. Consulte a seção sobre recursos para maiores informações. Verifique se a lista de empacotamento está atualizada. Isto envolve a adição de novos arquivos e diretórios e a remoção de entradas não utilizadas. Verifique o seu port utilizando o &man.portlint.1; como um guia. Consulte a seção sobre recursos para informações importantes sobre o uso do portlint. Avalie se as alterações no seu port podem levar a quebra de outros ports. Se este for o caso, coordene as alterações com os mantenedores destes ports. Isto é especialmente importante se a sua atualização alterar a versão de uma biblioteca compartilhada; neste caso, no mínimo, os ports que forem dependentes do seu vão precisar atualizar seu PORTREVISION de modo que eles sejam automaticamente atualizados pelas ferramentas de automação tais como o portmaster ou o &man.portupgrade.1;. Envie as alterações Envie sua atualização através da submissão de um PR contendo uma explicação sobre as mudanças e um patch com as diferenças entre o port original e a versão atualizada. Por favor, consulte o artigo Escrevendo Relatórios de Problema para o FreeBSD para maiores informações sobre como escrever um bom PR. Por favor, não envie um arquivo &man.shar.1; com o port inteiro. Em vez disso, utilize &man.diff.1; -ruN. Desta forma, os committers podem ver com muito mais facilidade e precisão quais são as mudanças que estão sendo feitas. A seção Atualizações do Porter's Handbook tem maiores informações. Aguarde Em algum momento um committer vai cuidar do seu PR. Isto pode demorar alguns minutos, ou pode levar semanas — desta forma, por favor, seja paciente. Dê feedbacks Se um committer encontrar um problema nas suas alterações, ele provavelmente irá encaminhá-lo de volta para você. Uma resposta rápida irá ajudá-lo a ter o seu PR resolvido mais rapidamente, e será melhor para manter o fluxo de conversação quando se está tentando resolver qualquer problema. E finalmente... As suas alterações serão aceitas e o seu port estará atualizado. O PR será fechado pelo committer. E é isso! Assegure que os seus <literal>ports</literal> continuem compilando corretamente. Esta seção é sobre descobrir e corrigir problemas que impeçam os seus ports de compilar corretamente. O funcionamendo da Coleção de Ports é garantido pelo &os; apenas no ramo -STABLE do sistema. Você deve estar executando o 8-STABLE ou o 9-STABLE, preferencialmente o último. Em teoria, você deve ser capaz de usá-lo com a última release de cada ramo estável (uma vez que as ABIs não deveriam mudar) mas se você puder executar o ramo -STABLE, isto será ainda melhor. Uma vez que a maioria das instalações do FreeBSD rodam em maquinas PC compatíveis (como é denominada a arquitetura i386), nós esperamos que você mantenha os seus ports funcionando nesta arquitetura. Nós preferimos que os ports também funcionem de forma nativa na arquitetura amd64. É totalmente justo que você peça ajuda se você não possuir uma destas máquinas. As falhas mais usuais na compilação para máquinas não-i386 ocorrem porque o programador original assumiu, por exemplo, que os ponteiros são do tipo int, ou então que uma versão antiga e relativamente mais frouxa do compilador gcc está sendo utilizada. Cada vez mais, os autores de aplicações estão retrabalhando seu código para remover estes pressupostos — mas se o autor não estiver mantendo o código de forma ativa, você pode precisar fazer isto você mesmo. Estas são as tarefas que precisam ser executadas para garantir o seu port pode ser compilado: Esteja atento para falhas de compilação Verifique regularmente o cluster de compilação automatizada de ports, o pointyhat, e o scanner de arquivos de distribuição para ver se algum dos ports que você mantém está falhando na compilação ou no download do código fonte (veja a seção sobre recursos para maiores informações sobre estes sistemas). Relatórios de falha também podem chegar até você por email, vindos de outros usuários ou dos sistemas automatizados. Colete informações Uma vez que você tome conhecimento de um problema, colete informações para ajudá-lo a corrigi-lo. Os erros de compilação reportados pelo pointyhay são acompanhados por logs os quais irão lhe mostrar onde a compilação falhou. Se a falha tiver sido reportada à você por um usuário, peça a ele para lhe enviar informações as quais possam lhe ajudar no diagnóstico do problema, tais como: Logs de compilação Os comandos e as opções que foram utilizadas para compilar o port (incluindo as opções definidas no /etc/make.conf) A lista de aplicativos instalados em seus sistemas, como mostrada pelo &man.pkg.info.1; A versão do &os; que eles estão utilizando, como mostrada pelo &man.uname.1; -a Quando a sua Coleção de Ports foi atualizada pela última vez Quando o seu arquivo INDEX foi atualizado pela última vez Investigue e encontre uma solução Infelizmente não existe um processo simples a ser seguido para fazer isto. Porém lembre-se: Se você estiver sem saber o que fazer, peça ajuda! A &a.ports; é um bom lugar para começar, e os desenvolvedores do software também estão frequentemente dispostos a ajudar. Envie as alterações Assim como na atualização de um port, você agora deve incorporar as alterações, revisá-las, testá-las, e depois submeter um PR com elas, fornecendo feedback, se necessário. Envie <literal>patches</literal> para os desenvolvedores do software Em alguns casos você irá precisar modificar o software do seu port para que ele execute no &os;. Alguns (mas não todos) desenvolvedores irão aceitar incorporar tais patches em seu código para a próxima release. Se eles aceitarem, isto pode até ajudar os seus usuários nos outros sistemas derivados do BSD e talvez evite esforços duplicados. Por favor, considere o envio de qualquer patch aplicável aos desenvolvedores do software como uma cortesia. Investigue os relatórios de bugs e os PRs relacionados ao seu <literal>port</literal> Esta seção é sobre a descoberta e correção de bugs. Os bugs específicos ao &os; são geralmente causados por suposições feitas pelo desenvolvedor sobre o ambiente de compilação e de execução que não se aplicam ao &os;. É pouco provável que você encontre um problema deste tipo, eles são mais sutis e difíceis de diagnosticar. Estas são as tarefas que precisam ser executadas para garantir que o seu port continua funcionando como esperado: Responda os relatórios de bugs Bugs podem ser reportados para você por meio de email através do Banco de Dados de Relatórios de Problema GNATS. Bugs também podem ser reportados diretamente à você pelos usuários. Você deve responder os PRs e demais relatórios no prazo de até 14 dias, mas por favor tente não levar tanto tempo. Tente responder o mais rápido possível, mesmo que seja só para dizer que você precisa de mais algum tempo antes que você possa trabalhar no PR. Se você não responder neste prazo de 14 dias, qualquer committer poderá realizar o commit do PR ao qual você não respondeu baseado na regra de maintainer-timeout. Colete informações Se a pessoa que reportou o bug não tiver fornecido também uma correção, você vai precisar coletar as informações que irão lhe permitir gerar uma. Se o bug pode ser reproduzido, você pode coletar a maioria das informações necessárias você mesmo. Se não conseguir reproduzi-lo, peça para a pessoa que reportou o bug para coletar as informações para você, tais como: Uma descrição detalhada das suas ações, comportamento esperado para o programa e o seu comportamento atual Cópia dos dados que desencadearam o bug Informação sobre o seu ambiente de compilação e execução — como, por exemplo, a lista dos aplicativos instalados e a saída do &man.env.1; Dumps de memória Rastreamento de pilhas Elimine os relatórios incorretos Alguns dos relatórios de bugs podem estar incorretos. Por exemplo, o usuário pode ter simplesmente utilizado o programa de forma errada; ou os aplicativos instalados podem estar desatualizados e precisando de atualização. À vezes, o bug reportado não é específico ao &os;. Neste caso, relate o bug para o desenvolvedor do software. Se a correção do bug estiver dentro da sua capacidade técnica, você também pode aplicar um patch ao seu port, para que a correção seja disponibilizada antes do release da nova versão oficial por parte do desenvolvedor. Encontre uma solução Assim como ocorre com os erros de compilação, você vai precisar encontrar uma correção para o problema. Mais uma vez, lembre-se de pedir ajuda se você estiver sem saber por onde começar! Envie ou aprove as alterações Assim como ocorre na atualização de um port, agora você deve incorporar as alterações, revisá-las, testá-las, e enviar as suas mudanças em um PR (ou enviar um followup se já existir um PR para o problema). Se outro usuário tiver submetido alterações em um PR, você também pode enviar um followup dizendo se aprova ou não estas mudanças. Forneça suporte Faz parte da função de mantenedor prover suporte — não para o software em geral — mas para o port e para qualquer problema ou peculiaridade que seja específica do &os;. Usuários podem contatá-lo com perguntas, sugestões, problemas e patches. Na maior parte do tempo serão mensagens especificas ao &os;. Ocasionalmente você pode precisar usar as suas habilidades diplomáticas para gentilmente direcionar os usuários que buscam suporte geral aos recursos apropriados. Menos frequentemente você irá encontrar pessoas perguntando por que o RPM não está atualizado ou como eles podem fazer o software executar no Linux XYZ. Aproveite a oportunidade para informar que o seu port está atualizado (se ele estiver, é claro) e sugira que eles testem o &os;. À vezes os usuários e desenvolvedores irão decidir que você é um pessoa ocupada, cujo tempo é valioso e irão fazer parte do trabalho para você. Por exemplo, eles podem: Submeter um PR ou enviar um patch para atualizar o seu port, investigar e talvez disponibilizar uma correção para um PT, ou de outra forma, submeter mudanças para o seu port. Nestes casos a sua principal obrigação é responder rapidamente. Mais uma vez, o tempo limite de espera pela resposta de um mantenedor é de 14 dias. Após este período as alterações podem ser processadas sem a sua aprovação. Eles se deram ao trabalho de fazer isto por você, portanto, tente pelo menos responder prontamente. Em seguida analise, aprove, modifique ou discuta as alterações com eles o mais rapidamente possível. Se você puder fazê-los sentir que a contribuição deles é apreciada (e ela deveria ser), você terá melhores chances de persuadi-los a fazer mais coisas para você no futuro :-). Localizando e corrigindo um <literal>port</literal> quebrado. Existem dois lugares muito bons nos quais você pode encontrar ports que precisam de alguma atenção. Você pode utilizar a interface web do banco de dados dos Relatórios de Problema para pesquisar e visualizar os PRs não resolvidos. A maioria dos PRs da categoria ports são referentes a atualizações, mas com um pouco de pesquisa e leitura das sinopses você deverá ser capaz de encontrar algo interessante para trabalhar (a classe sw-bug é um bom ponto de partida). O outro lugar é o Sistema de Monitoração de Ports do &os;. Em especial, procure por ports sem manutenção e com erros de compilação e por ports que estejam marcados como BROKEN (quebrados). É OK enviar alterações para um port que está sendo mantido, mas lembre-se de consultar primeiro o mantenedor para o caso dele já estar trabalhando na solução do problema. Depois que você tiver encontrado um bug ou problema, colete informações, investigue e conserte! Se existir já um PR, envie um followup. Caso contrário, crie um novo PR. Suas alterações serão revisadas e se tudo estiver OK, serão processadas e incorporadas. Saber quando parar A medida que seus interesses e compromissos mudarem, você poderá se ver sem tempo para continuar com algumas (ou com todas) das suas contribuições para os seus ports. Tudo bem! Por favor, nos avise se você não estiver mais utilizando um port, ou se de outra forma você não tem mais tempo ou mesmo interesse para ser um mantenedor. Desta forma, poderemos seguir em frente e permitir que outras pessoas trabalhem com os problemas existentes nestes ports sem ter que aguardar pela sua resposta. Lembre-se, o &os; é um projeto voluntário, se manter um port não é mais divertido, provavelmente está na hora de deixar alguma outra pessoa fazê-lo. De qualquer forma, a Equipe de Gerenciamento do Ports (portmgr) se reserva o direito de revogar a sua condição de mantenedor de um port se você não estiver dando manutenção de forma ativa ao mesmo já há algum tempo (Atualmente, o período limite é de 3 meses). Com isto queremos dizer que existem problemas não resolvidos ou atualizações pendentes as quais não foram trabalhadas durante esse tempo. Recursos para mantenedores de <literal>ports</literal> e colaboradores O Porter's Handbook é o seu guia de mochila para o sistema de ports. Mantenha ele sempre a mão! O artigo Escrevendo Relatórios de Problemas para o FreeBSD descreve as melhores práticas na elaboração e na submissão de um PR. Em 2005 foram submetidos mais de 11 mil relatórios de problema na categoria ports. Ao seguir as recomendações deste artigo você irá nos ajudar a reduzir o tempo necessário para processar o seu PR. O Banco de Dados de Relatórios de Problemas. O Pointyhat é o cluster de compilação do sistema de ports. Você pode utilizar o Pointyhat para verificar os logs de compilação de um port em todas as arquiteturas e releases principais. O Sistema de Monitoração de Ports do &os; pode lhe mostrar informações de referência cruzada sobre um port tais como erros de compilação e relatórios de problema. Se você é um mantenedor você pode utilizá-lo para verificar o status de compilação dos seus ports. Se você é um colaborador você pode utilizá-lo para encontrar ports quebrados e sem manutenção os quais precisam ser corrigidos. O Scanner de Arquivos de Distribuição da Coleção de Ports do FreeBSD pode lhe mostrar ports para os quais não é possível fazer o download do código fonte. Você pode utilizá-lo nos seus próprios ports ou usá-lo para encontrar ports que precisam ter o seu MASTER_SITES atualizado. O ports tinderbox é a forma mais completa de testar um port através de todo o ciclo de instalação, empacotamento, e desinstalação. Ele possui uma interface de linha de comando, mas também pode ser controlado através de uma interface web. Ele está disponível em ports/ports-mgmt/tinderbox. Você irá encontrar maiores informações na Home page do marcuscom sobre o tinderbox. O &man.portlint.1; é um aplicativo o qual pode ser utilizado para verificar se o seu port esta em conformidade com as muitas e importantes diretrizes funcionais e de estilo que se aplicam a um port. O portlint é um aplicação heurística simples, de forma que você deve usá-lo apenas como um guia. Se o portlint sugerir uma alteração que lhe parece ser irracional, consulte o Porter's Handbook ou peça orientação usando os canais apropriados. A &a.ports; destina-se a discussão de assuntos gerais relacionados ao sistema de ports. Ela é um bom lugar para se pedir ajuda. Você pode se inscrever, ou ler e consultar o histórico de mensagens da lista. A leitura do histórico da &a.ports-bugs; e da &a.cvs-ports; também pode ser interessante. + +
diff --git a/pt_BR.ISO8859-1/articles/contributing/article.xml b/pt_BR.ISO8859-1/articles/contributing/article.xml index d8fadee65e..24b79be194 100644 --- a/pt_BR.ISO8859-1/articles/contributing/article.xml +++ b/pt_BR.ISO8859-1/articles/contributing/article.xml @@ -1,688 +1,690 @@
Contribuindo para o FreeBSD Este artigo descreve as diferentes maneiras pelas quais um indivíduo ou uma organização podem contribuir com o projeto FreeBSD. Jordan Hubbard Colaboração de &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Contribuindo Então você quer contribuir com o FreeBSD? Isso é ótimo! O FreeBSD depende das contribuições da sua base de usuários para sobreviver. Suas contribuições não são apenas apreciadas, elas são vitais para que o FreeBSD continue crescendo. Ao contrário do que algumas pessoas podem tentar fazê-lo acreditar, você não precisa ser um programador super experiente ou amigo pessoal de um membro do Core Team do FreeBSD para ter suas contribuições aceitas. Um grande e crescente número de colaboradores internacionais, de idades e de áreas técnicas extremamente variadas desenvolvem o FreeBSD. Há sempre mais trabalho a ser realizado do que pessoas disponíveis para fazê-lo. Toda e qualquer ajuda é sempre bem vinda. O projeto FreeBSD é responsável por todo um sistema operacional, ou seja, é responsável por muito mais que apenas um kernel ou alguns utilitários dispersos. Da forma como está, o nosso TODO, possui tarefas em uma escala muito ampla: da documentação, da realização de beta testes e de apresentação, ao instalador do sistema e desenvolvimento altamente especializado de componentes para o kernel. Pessoas de todos os níveis de habilidade, de qualquer área técnica, certamente podem ajudar o projeto de alguma forma. As instituições comerciais envolvidas em projetos relacionados ao FreeBSD; também, são encorajadas a nos contatar. Você necessita de uma extensão especial para fazer seu produto funcionar? Você irá nos encontrar receptivos aos seus pedidos, desde que eles não sejam demasiadamente descabidos. Você está trabalhando em um produto que agrega valor ao sistema? Por favor, deixe-nos saber! Nós talvez possamos trabalhar em conjunto em algum aspecto dele. O mundo do software livre desafia muitos dos conceitos existentes sobre como um software é desenvolvido, vendido e mantido; e, nós o incitamos a dar ao menos uma segunda olhada. O que é necessário? A seguinte lista de tarefas e sub-projetos representa uma amálgama de várias listas de TODO e solicitações enviadas por usuários. Tarefas em execução por não-programadores. Muitas das pessoas que estão envolvidas com o FreeBSD não são programadores. O projeto inclui autores de documentação, Web designers, e pessoal de suporte. Tudo o que estas pessoas precisam para contribuir é algum tempo livre para investir e vontade de aprender. Leia o FAQ e &a.ptbr.p.handbook; periodicamente. Se algo estiver mal explicado, desatualizado ou mesmo completamente errado; por favor, deixe-nos saber. Ou melhor, envie-nos uma correção. (Docbook não é difícil de aprender, mas não há nenhuma objeção à submissões em formato ASCII). Ajude a traduzir a documentação do FreeBSD para a sua língua nativa. Se a documentação já existir no seu idioma, você pode ajudar a traduzir novos documentos ou verificar se as traduções existentes estão atualizadas. Primeiro, verifique o FAQ sobre traduções no &a.ptbr.p.fdpp;. Você não estará se comprometendo a traduzir todos os documentos do FreeBSD fazendo isto — como um voluntário, você pode traduzir muitos ou poucos documentos, quantos desejar. Uma vez que alguém começa a traduzir, outros quase sempre se juntam ao esforço. Se você somente tiver tempo livre ou energia para traduzir uma pequena parte da documentação; por favor, traduza as instruções de instalação. Leia a &a.questions; e o &ng.misc; ocasionalmente (ou regularmente se possível). Pode ser muito recompensador compartilhar a sua experiência e ajudar outras pessoas a resolverem seus problemas; Muitas vezes apenas este processo o levará à aprender coisas! Estes fóruns também podem ser uma fonte de idéias para assuntos aos quais se dedicar. Tarefas em execução por programadores A maioria das tarefas listadas aqui requerem um investimento considerável de tempo ou conhecimento profundo do kernel do FreeBSD; ou, ambos. Entretanto, também existem muitas tarefas úteis que são apropriadas para os hackers de final de semana. Se você executar o FreeBSD-CURRENT e tiver uma boa conexão Internet, existe uma máquina current.FreeBSD.org que produz um lançamento (release) completo uma vez por dia — tente instalar diariamente o lançamento mais recente gerado e relate todas as falhas encontradas no processo. Leia a &a.bugs;. Pode existir um problema o qual você possa comentar construtivamente ou mesmo uma correção que possa testar. Ou, você pode ainda tentar reparar um dos problemas sozinho. Se você souber de qualquer problema que tenha sido corrigido com sucesso no -CURRENT e cuja correção não tenha sido aplicada ao -STABLE após um intervalo razoável de tempo (normalmente algumas semanas), envie ao committer um lembrete educado. Mova as contribuições de software para src/contrib na árvore do código fonte. Tenha certeza que o código disponível em src/contrib está atualizado. Compile o sistema (ou apenas uma parte dele) com warnings extras habilitados e remova os warnings. Corrija warnings de ports que ainda fazem coisas ultrapassadas tais como utilizar gets() ou incluir malloc.h. Se você contribuiu com algum dos ports, e teve que fazer alguma mudança específica para o &os;, envie suas correções de volta aos autores originais (isto tornará sua vida mais fácil quando eles lançarem a próxima versão). Consiga cópias de padrões formais tais como &posix;. Você pode obter alguns links sobre estes padrões no sítio www FreeBSD C99 & Projeto de Conformidade com Padrões Posix. Compare o comportamento do FreeBSD àquele requerido pelo padrão. Se o comportamento diferir, particularmente em pontos sutis ou obscuros da especificação, envie-nos um PR sobre ele. Se você for capaz, descubra como corrigi-lo e inclua um patch em seu PR. Se você acredita que o padrão está errado, peça ao comitê de padrões que considere a pergunta. Sugira novas tarefas para esta lista! Trabalhe no banco de dados de <literal>PR</literal> (relatório de problemas) base de dados de relatórios de problemas A Lista de PRs do FreeBSD mostra todos os relatórios de problemas ativos no momento e os pedidos de melhoria que foram submetidos pelos usuários do FreeBSD. O banco de dados inclui tarefas para programadores e para não-programadores. Consulte os PRs abertos, e veja se algum deles é de seu interesse. Alguns deles podem ser tarefas muito simples que necessitam apenas que um par extra de olhos olhe para eles e confirme que a correção proposta funciona. Outros podem ser muito mais complexos, ou podem nem ter vindo com uma correção. Comece com os PRs que ainda não foram atribuídos a ninguém. Se um PR estiver atribuído a outra pessoa, mas se parecer com algo que você possa cuidar, envie um e-mail para a pessoa encarregada do mesmo e pergunte se você pode trabalhar nele — ele pode já ter um patch pronto para ser testado, ou você pode discutir novas idéias com ele. Escolha um dos itens da <quote>página de idéias</quote> A lista de projetos do &os; e de idéias para voluntários também está disponível para as pessoas dispostas a contribuir com o projeto &os;. A lista é atualizada regularmente e contém itens sobre cada projeto para programadores e para não programadores. Como contribuir Contribuições para o sistema geralmente caem em uma ou mais das seguintes 5 categorias: Relatórios de Erro e Comentários em Geral Uma idéia ou sugestão técnica de interesse geral deve ser enviada para a &a.hackers;. Da mesma forma, pessoas com interesse neste tipo de assunto (e uma tolerância para um alto volume de mensagens!), devem se inscrever na &a.hackers;. Consulte o &a.ptbr.p.handbook; para maiores informações sobre esta e outras listas de discussão. Se você encontrar um erro ou estiver enviando uma alteração específica; por favor, faça o relatório utilizando o programa &man.send-pr.1; ou a sua interface WWW equivalente. A não ser que ele exceda 65KB, inclua qualquer patch diretamente no relatório. Se o patch é destinado a ser aplicado na árvore de código, coloque a palavra [PATCH] na sinópse do relatório. Quando incluir um patch, não o faça utilizando copiar-e-colar porque ao copiar-e-colar os tabs serão convertidos para espaços, e tornará o patch inutilizável. Quando os patches forem muito maiores que 20KB, considere a possibilidade de comprimi-los (por ex. usando &man.gzip.1; or &man.bzip2.1;) e utilize o &man.uuencode.1; para incluir a versão compactada no seu relatório de problema. Depois de enviar o relatório, voce deve receber uma confirmação junto com um número de registro. Guarde este número de registro, de forma que você possa nos manter atualizados sobre o seu problema enviando um e-mail para &a.bugfollowup;. Coloque o número no assunto da mensagem, por ex. "Re: kern/3377". Informações adicionais sobre qualquer relatório de problema (Problem Report) devem ser submetidas desta forma. Se você não receber a confirmação em prazo razoável (3 dias a 1 semana, dependendo da sua conexão de e-mail), ou está por alguma razão impossibilitado de utilizar o comando &man.send-pr.1; ; então, você pode pedir que alguém o envie para você enviando e-mail para &a.bugs;. Consulte também este artigo sobre como escrever um bom relatório de problema. Alterações na Documentação Envio de documentação Alterações na documentação são administradas pela &a.doc;. Por favor, verifique o &a.ptbr.p.fdpp; para obter instruções detalhadas. Envie suas colaborações e alterações (inclusive as pequenas são bem vindas!) usando o &man.send-pr.1; como descrito no Relatórios de Erro e Comentários em Geral. Alterações no Código Fonte Existente FreeBSD-CURRENT Uma adição ou alteração ao código fonte existente é um caso um pouco mais complicado e depende muito de quão desatualizado você está em relação ao estado atual de desenvolvimento do FreeBSD. Existe um lançamento (release) especial em andamento do FreeBSD conhecido como FreeBSD-CURRENT o qual é disponibilizado em uma grande variedade de formas para a comodidade dos desenvolvedores que trabalham ativamente no sistema. Consulte o &a.ptbr.p.handbook; para maiores informações sobre como obter e utilizar o FreeBSD-CURRENT. Trabalhar com versões antigas do código, infelizmente, muitas vezes significa que as suas alterações serão demasiadamente obsoletas ou muito divergentes para possibilitar uma fácil re-integração ao FreeBSD. As possibilidades de que isso ocorra podem ser minimizadas um pouco através da sua inscrição nas listas &a.announce; e &a.current;, nas quais as discussões sobre o estado atual do sistema ocorrem. Supondo que você consiga obter acesso à código fonte do sistema razoavelmente atualizado para basear as suas alterações nele, o próximo passo é produzir um conjunto de diffs para enviar aos mantenedores do FreeBSD. Isto é feito com o comando &man.diff.1;. O formato preferido do &man.diff.1; para enviar um patch, é o formato de saída unificada gerado por diff -u. diff &prompt.user; diff -u oldfile newfile ou &prompt.user; diff -u -r -N olddir newdir deverá gerar um conjunto de diffs unificados para o arquivo de origem informado ou hierarquia de diretórios. Consulte o manual do &man.diff.1; para maiores informações. Uma vez que você tenha o conjunto de diffs (os quais você pode testar com o comando &man.patch.1;), você deve submetê-los para inclusão no FreeBSD. Utilize o comando &man.send-pr.1; como descrito no Relatórios de Erro e Comentários em Geral. Não envie os diffs apenas para a &a.hackers; ou eles serão perdidos! Nós apreciamos extremamente a sua submissão (este é um projeto voluntário!); porque nós somos ocupados, nós podemos não ter como tratá-la imediatamente, mas ela permanecerá em nosso bando de dados de PRs até que nós o façamos. Marque a sua submissão incluindo a palavra [PATCH] na sinópse do relatório. uuencode Se você sentir que é apropriado (por ex. você adicionou, deletou ou renomeou arquivos), empacote as suas mudanças em um arquivo tar e execute o programa &man.uuencode.1; nele. Arquivos criados com o &man.shar.1; também são bem vindos. Se suas mudanças são de uma natureza potencialmente sensível, tais como você estar inseguro sob quais políticas de direito autoral as novas versões serão distribuídas, então você deve enviá-las diretamente para o &a.core; ao invés de submetê-las com o &man.send-pr.1;. O &a.core; é formado por um grupo muito pequeno de pessoas as quais cuidam de muitas das tarefas diárias de administração do projeto &os;. Observe que este grupo também é muito ocupado e portanto você só deve enviar um e-mail a eles se for realmente necessário. Por favor, consulte a &man.intro.9; e a &man.style.9; para obter alguma informação sobre o estilo de codificação. Nós apreciaríamos se você estivesse ao menos ciente destas informações antes de submeter o seu código. Código Novo ou Pacotes Principais de Valor Adicional (<foreignphrase>Major Value-Added Packages</foreignphrase>) No caso de uma contribuição significativa de um trabalho de grande porte, ou a adição de uma nova característica importante ao FreeBSD, torna-se quase sempre necessário que se envie as alterações em um arquivo tar uuencoded ou então que se faça o upload das mesmas para um servidor WWW ou FTP para que as outras pessoas possam acessá-las. Se você não possui acesso a um servidor WWW ou FTP, pergunte em uma lista de discussão apropriada do FreeBSD se alguém pode hospedar essas alterações para você. Quando se trabalha com grandes quantidades de código, o sensível assunto de direitos autorais invariavelmente vem a tona. Os direitos autorais aceitos para os códigos incluídos no FreeBSD são: Licensa BSD Os direitos autorais BSD. Este tipo de licensa é a mais preferível devido a sua natureza não restritiva e pela sua afinidade com iniciativas comerciais. Longe de desencorajar o uso comercial, o Projeto FreeBSD encoraja ativamente tais participações, uma vez que estes interesses comerciais podem eventualmente se converter em investimentos no próprio FreeBSD. GPLGNU General Public License Licença Pública Geral GNU (GNU General Public License) A licensa pública geral GNU, ou GPL. Esta licensa não é tão popular conosco, devido aos esforços extras que exigem de qualquer pessoa que venha a utilizar o código com finalidades comerciais, mas dada a grande quantidade de código GPL que nós necessitamos atualmente (compilador, montador assembler, formatador de texto, etc) seria tolice recusar contribuições adicionais sob esta licensa. O código sob a GPL também vai para uma parte diferente da árvore, mais especificamente para /sys/gnu ou /usr/src/gnu, de forma que é muito fácil identificá-lo para qualquer um que a GPL representa um problema. As contribuições que vêm sob qualquer outro tipo de licensa devem ser cuidadosamente revisadas antes de sua inclusão no FreeBSD ser considerada. Contribuições com algum tipo de restrição particular ao seu uso comercial são geralmente rejeitadas, embora os autores sejam sempre incentivados a tornarem tais alteração disponíveis por meio de canais próprios. Para colocar o seu trabalho sob licensa estilo-BSD, inclua o texto abaixo no início de cada um dos arquivos que você deseja proteger, substituindo o texto entre %% com as informações apropriadas: Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $&os;$ Para a sua comodidade, uma cópia deste texto pode ser encontrada em /usr/share/examples/etc/bsd-style-copyright . Dinheiro, Hardware ou Acesso Internet Nós ficamos sempre muito felizes em aceitar doações para agregar a causa do Projeto FreeBSD, em um esforço voluntário como o nosso, um pouco pode significar muito! Doações de hardware também são muito importantes para expandir a nossa lista de periféricos suportados, uma vez que normalmente não temos recursos para comprar estes ítens nós mesmos. <anchor id="donations"/>Doando Dinheiro A Fundação FreeBSD é uma entidade sem fins lucrativos e isenta de impostos, estabelecida com o objetivo de promover os objetivos do Projeto FreeBSD. Como uma entidade 501(c)3, a fundação é isenta de recolher as taxas do governo federal, bem como as do Estado do Colorado. As doações para uma entidade isenta de impostos são freqüentemente dedutíveis dos impostos federais. As doações podem ser enviadas através de cheques para:
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO, 80303 USA
A Fundação FreeBSD é agora capaz de receber doações através da web com o PayPal. Para fazer uma doação; por favor, visite o sítio www da Fundação. Maiores informações sobre a Fundação FreeBSD podem ser obtidas no documento A Fundação FreeBSD - Uma introdução. Para contatar a Fundação por e-mail, escreva para bod@FreeBSDFoundation.org. Doando <foreignphrase>Hardware</foreignphrase> doacões O projeto de FreeBSD aceita alegremente doações de hardware para as quais pode encontrar bom uso. Se voce estiver interessado em doar componentes de hardware; por favor, contate o Escritório de Relacionamento com Doadores. + +
diff --git a/pt_BR.ISO8859-1/articles/problem-reports/article.xml b/pt_BR.ISO8859-1/articles/problem-reports/article.xml index ec1f919881..9099749011 100644 --- a/pt_BR.ISO8859-1/articles/problem-reports/article.xml +++ b/pt_BR.ISO8859-1/articles/problem-reports/article.xml @@ -1,1649 +1,1651 @@
Escrevendo Relatórios de Problema no &os; &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ Este artigo descreve qual a melhor forma de formular e de submeter um relatório de problema para Projeto &os;. Dag-Erling Smørgrav Contribuido por Mark Linimon relatório de problema
Introdução Uma das experiências mais frustrantes que alguém pode ter como um usuário de um software é submeter um relatório sobre um problema que está enfrentando apenas para vê-lo ser sumariamente fechado com uma informação curta e pouco útil do tipo isto não é um bug ou ainda este relatório de problema não procede. Da mesma forma, uma das experiências mais frustrantes para um desenvolvedor de software é ser inundado com relatórios de problemas que na verdade não são realmente relatórios de problemas, mas sim solicitações de suporte, ou então que contenham pouca ou nenhuma informação sobre como o problema ocorre e sobre como proceder para reproduzi-lo. Este documento tem por objetivo descrever como escrever bons relatórios de problema. Mas o que vem a ser um bom relatório de problema? Bem, indo direto ao ponto, um bom relatório de problema é aquele que se pode analisar e tratar rapidamente, para a satisfação mútua do usuário e do desenvolvedor. Embora o foco primário deste artigo seja a elaboração de relatórios de problemas no &os;, a maior parte das recomendações deve aplicar-se muito bem a outros projetos de software. Observe que este artigo esta organizado de forma temática, e não de forma cronológica, desta forma você deve ler o documento inteiro antes de enviar um relatório de problema, ao invés de tratá-lo como um tutorial passo-a-passo.
Quando enviar um relatório de problema Existem muitos tipos de problemas, e nem todos eles devem gerar um relatório de problema. É claro, ninguém é perfeito e em algumas ocasiões você terá certeza de que encontrou um bug em um determinado software quando na verdade você compreendeu errado a sintaxe de um comando ou mesmo cometeu um erro de digitação em um arquivo de configuração (o que por sua vez pode indicar uma documentação pouco detalhada ou então um tratamento inadequado do erro por parte da aplicação). Existem ainda muitas outras situações nas quais enviar um relatório de problema claramente não é a melhor ação a ser tomada, e só vai servir para frustrar a você e aos desenvolvedores. Em contrapartida, existem situações nas quais é recomendado que você nos envie um relatório de problema sobre outras coisas que não um bug, como por exemplo para nos enviar uma sugestão de melhoria ou um pedido de uma nova funcionalidade. Então como você irá diferenciar o que é e o que não é um bug? Existe uma regra de ouro que diz que o seu problema não é um bug se ele pode ser expresso como uma pergunta (normalmente na forma Como eu faço X ou Onde eu posso encontrar Y). Na maior parte das vezes não será sempre tão claro desta forma, mas a regra acima cobre a grande maioria dos casos. Se você estiver procurando por uma resposta, considere enviar a sua pergunta para &a.questions;. Veja alguns casos nos quais pode ser apropriado enviar um relatório de problema sobre algo que não é um bug: Pedidos de melhorias nas funcionalidades. Geralmente é uma boa idéia debater estas propostas nas listas de discussão antes de enviá-las em um relatório de problemas. Notificações sobre atualizações de softwares mantidos externamente (principalmente do ports, mas também de componentes do sistema base como, por exemplo, o BIND e vários outros utilitários GNU). Para os ports sem manutenção (aqueles nos quais a variável MAINTAINER contém ports@FreeBSD.org), essas notificações de atualização podem ser capturadas por um committer interessado, ou você pode ser solicitado a fornecer um patch para atualizar o port; disponibilizar este patch antecipadamente irá melhorar de forma significativa as suas chances de ter o port atualizado rapidamente. Se o port possui um mantenedor, o envio de um relatório de problema comunicando sobre o lançamento de uma nova versão geralmente não é muito útil uma vez que eles geram trabalho adicional para os committers, e o mantenedor provavelmente já tem conhecimento de que existe uma nova versão, ele provavelmente já trabalhou com os desenvolvedores para atualizá-lo e está provavelmente executando testes para verificar se não existem problemas, etc. Em ambos os casos, você irá obter melhores resultados se seguir o processo descrito no Porter's Handbook. (Talvez você também queira ler o artigo Contribuindo para a Coleção de Ports do &os;.) Um bug que não pode ser reproduzido, raramente será corrigido. Se o bug ocorreu uma única vez e você não consegue reproduzi-lo, e se aparentemente ele não ocorre com mais ninguém, as chances são de que nenhum dos desenvolvedores será capaz de reproduzir ou de saber o que está errado. Isso não significa que não seja possível, mas significa que a probabilidade do seu relatório de problema resultar na correção do bug é muito pequena. Para piorar a situação, muitas vezes este tipo de erro é, na realidade, causado por falhas nos discos rígidos ou por superaquecimento do processador — sempre que possível você deve tentar excluir estas causas antes de enviar um relatório de problema. Em seguida, para decidir a quem você deve apresentar o seu relatório de problema, você precisa entender que o &os; é composto de vários elementos de software diferentes: Código na base do sistema que é escrito e mantido por colaboradores do &os;, tais como o Kernel, a biblioteca C, os drivers de dispositivos (categorizados como kern); os utilitários binários (bin); as páginas de manual e a documentação (docs); e as páginas web (www). Todos os bugs nestas áreas devem ser reportados para os desenvolvedores do &os; Código na base do sistema que é escrito e mantido por outros, e que foram adaptados e importados no &os;. Exemplos incluen bind, &man.gcc.1;, e &man.sendmail.8;. A maioria dos bugs nestas áreas devem ser reportados para os desenvolvedores do &os;; mas em alguns casos pode ser necessário reportá-los aos autores originais, caso o problema não seja especifico do &os;. Normalmente estes bugs irão ficar sob as categorias bin ou gnu. Os aplicativos individuais que não estão na base do sistema, mas que fazem parte da coleção de Ports do &os; (Categoria ports). A maioria destes aplicativos não são escritos por desenvolvedores do &os;; o que o &os; oferece é apenas um sistema para facilitar a instalação do aplicativo. Portanto, você deve relatar um problema para os desenvolvedores do &os; apenas quando você acreditar que o problema é específico do &os;, caso contrário, você deve reportá-lo aos autores do software. A seguir você deve verificar se o problema é ou não atual. Existem poucas coisas que aborrecem um desenvolvedor mais do que receber um relatório de problema a respeito de um bug que ele já corrigiu. Se o problema está na base do sistema, você deverá primeiro ler a seção do FAQ sobre Versões do &os;, se você não estiver familiarizado com o tema. Não é possível para o &os; corrigir problemas em versões muito antigas do sistema base, desta forma enviar um relatório de problema sobre um bug em uma versão muito antiga vai provavelmente resultar apenas em um desenvolvedor aconselhando que você atualize o seu sistema para uma versão suportada para ver se o problema ainda ocorre. A equipe de Security Officer mantém a lista de versões suportadas. Se o problema está em um port, observe que você deverá primeiro atualizar seu sistema para a versão mais atual da coleção de ports e ver se o problema ainda se aplica. Devido ao ritmo acelerado de mudanças nestas aplicações, é inviável para o &os; suportar qualquer coisa que não seja obrigatoriamente a versão mais recente, e problemas com uma versão antiga do aplicativo simplesmente não podem ser corrigidos.
Preparação Uma boa regra a ser seguida sempre é realizar uma busca a respeito do assunto antes de enviar um relatório de problema. Pode ser que o seu problema já tenha sido reportado anteriormente; pode ser que esteja sendo debatido nas listas de discussão ou que tenha sido recentemente; pode até ser que o problema já tenha sido corrigido em uma versão mais recente do que a que você está utilizando. Você deve portanto verificar em todos os lugares óbvios antes de enviar o relatório de problema. Para o &os;, isto significa: A lista de Perguntas e Respostas mais Frequentes sobre o &os; (FAQ). A FAQ tem por objetivo fornecer respostas para uma grande variedade de perguntas, tais como as que dizem respeito a compatibilidade de hardware, aplicações do usuário, Configuração do kernel, etc. As listas de discussão — se você não está inscrito, utilize a busca do histórico no web site do &os;. Se o seu problema não tiver sido discutido nas listas, você pode tentar enviar uma mensagem sobre ele e aguardar alguns dias para ver se alguém consegue perceber algo que você tenha deixado passar desapercebido. Opcionalmente, na internet inteira — utilize seu mecanismo de busca preferido para localizar referências sobre o seu problema. Você pode encontrar referências a ele em mensagens de listas de discussão ou de grupos de noticias dos quais você nunca ouviu falar ou nos quais sequer pensou em procurar. Na sequência, verifique o banco de dados com os relatórios de problema do &os; (GNATS). A menos que o seu problema seja recente ou muito obscuro, existe uma boa chance dele já ter sido reportado. E o mais importante, você deve verificar se a documentação existente no código base não endereça o seu problema. Para o código base do &os; você deve estudar cuidadosamente o conteúdo do arquivo /usr/src/UPDATING disponível no seu sistema de arquivos ou a sua versão mais recente no Repositório Subversion. (Esta informação é vital se você estiver atualizando de uma versão para outra — especialmente se estiver atualizando para o &os.current;). No entanto, se o problema é com algo que foi instalado como uma parte da coleção de ports do &os; você deve consultar o /usr/ports/UPDATING (para os ports individuais) ou o /usr/ports/CHANGES (para mudanças que afetam a Coleção de Ports inteira). Estes arquivos também estão disponíveis no SVNWeb, nos urls e respectivamente.
Escrevendo o Relatório de Problema Agora que você decidiu que o seu assunto merece um relatório de problema (PR), e que ele é um problema do &os;, é hora de escrever o relatório em si. Mas antes de entrarmos na mecânica do programa utilizado para gerar e enviar os PRs, aqui estão algumas dicas e truques para ajudá-lo a garantir que o seu PR será o mais efetivo possível.
Dicas e truques para escrever um bom relatório de problema. Não deixe a linha de Synopsis (sinopse) em branco. Os PRs são enviados para listas de discussão no mundo todo (nas quais a Synopsis é utilizada como linha de Subject:), além de serem armazenados em um banco de dados. Qualquer pessoa que vier a navegar no banco de dados pelas sinopses, e encontrar um PR com a linha de assunto em branco, tende a pulá-lo. Lembre-se que os PRs permanecem na base de dados até que sejam fechados por alguém; os anônimos normalmente irão desaparecer em meio ao ruído. Evite utilizar uma Synopsis (sinopse) fraca. Você não pode assumir que alguém que esteja lendo o seu PR conheça todo o contexto que motivou o seu envio, desta forma quanto mais informação você fornecer, melhor. Por exemplo, a que parte do sistema o problema se aplica? O problema ocorre durante a instalação ou durante a execução do sistema? Para ilustrar, ao invés de utilizar Synopsis: o portupgrade está quebrado, veja o quão mais claro e mais eficiente seria utilizar Synopsis: port sysutils/portupgrade gerando coredumps no -current. (No caso de um port, é especialmente útil ter a categoria e o nome do port na linha de sinopse.) Se você possui um patch, mencione-o. Um PR que inclui um patch é muito mais provável de ser analisado do que um sem. Se você estiver incluindo um, coloque a palavra [patch] no inicio da linha de sinopse. (Embora não seja obrigatório utilizar exatamente esta palavra, por convenção, é ela que é utilizada.) Se você é um maintainer (mantenedor), diga-o. Se você está mantendo uma parte do código fonte (por exemplo, um port), você deve considerar a possibilidade de incluir as palavras [maintainer update] (incluindo os colchetes) no inicio da linha de sinópse e deve definir a class (classe) do seu PR para maintainer-update. Desta forma qualquer committer que manusear o seu PR não terá de verificar o Makefile do port, para certificar-se de que a atualização foi enviada pelo maintainer. Seja específico. Quanto mais informações você fornecer sobre o problema que você está tendo, melhores serão as suas chances de obter uma resposta. Inclua a versão do &os; que você está utilizando (existe um lugar para colocar esta informação, veja abaixo) e em qual arquitetura. Você incluir a informação se está executando a partir de um Release (e.g. de um CDROM ou Download), ou a partir de um sistema mantido com o &man.cvsup.1; (e neste caso, quando foi atualizado pela ultima vez). Se você estiver utilizando o &os.current;, esta vai ser a primeira coisa que alguém irá lhe perguntar, porque as correções (especialmente para os problemas de alto nível) tendem a serem realizadas muito rapidamente, e espera-se que os usuários do &os.current; mantenham-se atualizados. Inclua quais opções globais você especificou no seu make.conf. Observação: É conhecido que utilizar -O2 (e acima disso) com o &man.gcc.1; gera problemas em muitas situações. Apesar dos desenvolvedores do &os; aceitarem patches, eles normalmente não estão dispostos a investigar este tipo de problema por uma simples falta de tempo e de voluntários, e ao invés disso podem responder apenas que isto não é suportado. Se o problema pode ser reproduzido facilmente, inclua informações para possibilitar que ele seja reproduzido pelos desenvolvedores. Se o problema só pode ser demonstrado com a entrada de um conjunto de dados específico, você deverá incluir um exemplo destas informações, além de informar qual é resultado atual (errado) e qual era o resultado esperado (correto). Se o conjunto de dados for muito grande ou se o mesmo não puder ser tornado público, tente criar um arquivo com o mínimo de informações necessárias para replicar o problema, e que possa ser incluído no seu PR. Se for um problema com o kernel, esteja preparado para fornecer as seguintes informações (Você não precisa fornecer estas informações por padrão, o que só tende a encher o banco de dados, mas você deve incluir os trechos acreditar que são relevantes): A configuração do seu kernel (incluindo quais dispositivos de hardware você tem instalados) Se você tem ou não opções de depuração habilitadas (tais como WITNESS), e em caso afirmativo, se o problema continua ocorrendo quando você altera a lógica de configuração destas opções O texto completo de qualquer backtrace, panic e outras mensagens no console, ou os registros do /var/log/messages, caso tenha sido gerado algum A saída do pciconf -l e as partes relevantes da saída do dmesg se o problema estiver relacionado a um componente de hardware O fato de que você leu o src/UPDATING e que o seu problema não está listado ali (é certeza que alguém vai perguntar) Se você consegue ou não executar outro kernel (Isto é para poder descartar a possibilidade de ser um problema de hardware tais como falha nos discos rígidos e superaquecimento dos processadores, cujos sintomas podem se confundir com problemas no kernel) Se for um problema com um port, esteja preparado para fornecer as seguintes informações (Você não precisa fornecer estas informações por padrão, o que só tende a encher o banco de dados, mas você deve incluir os trechos acreditar que são relevantes): Quais ports você tem instalados As variáveis de ambiente que substituem os padrões do bsd.port.mk, como por exemplo PORTSDIR O fato de que você leu o ports/UPDATING e que o seu problema não está listado ali (é certeza que alguém vai perguntar) Evite pedidos vagos de novas funcionalidades. Os PRs no formato alguém realmente deveria implementar algo que faz isso e aquilo são menos prováveis de obterem uma resposta do que os que são mais específicos. Lembre-se, o código está disponível para todos, de forma que se você deseja uma nova funcionalidade, a melhor maneira de ter certeza de que ela será incluída é começar a trabalhar! Também considere o fato de que muitas destas sugestões fariam mais sentido como um tópico de discussão na freebsd-questions do que como uma entrada no banco de dados de PRs, como discutido acima. Certifique-se de que ninguém tenha submetido um PR semelhante antes. Embora isso já tenha sido mencionado anteriormente, faz sentido repetir aqui. Esta verificação irá lhe tomar apenas 1 ou 2 minutos no uso do mecanismo de busca do banco de dados de PRs. (é claro, todos são culpados de já terem esquecido de fazer isso de uma vez ou outra.) Relate apenas um problema em cada relatório. Evite incluir dois ou mais problemas em um mesmo relatório caso eles não estejam relacionados. Quando você submeter um patch, evite adicionar várias funcionalidades ou corrigir vários bugs em um mesmo PR, a menos que eles sejam estritamente relacionados — Este tipo de PR muitas vezes demanda mais tempo para ser resolvido. Evite solicitações polêmicas. Se o seu PR está relacionado a um tema que foi polêmico no passado, você deve estar preparado para não somente disponibilizar um patch, como também para defender porque o seu patch é a coisa certa a se fazer. Como mencionado acima, realizar uma busca cuidadosa no histórico das listas de discussão é sempre uma boa forma de se preparar. Seja educado. Praticamente todas as pessoas que potencialmente podem trabalhar no seu PR são voluntários. Ninguém gosta de receber ordens para fazer algo que eles já estão fazendo por alguma outra motivação a qual não é a de ganho financeiro. Esta é uma boa coisa para ter sempre em mente num projeto de código aberto.
Antes de você iniciar Antes de executar o programa &man.send-pr.1;, certifique-se que a sua variável de ambiente VISUAL (ou a EDITOR se a VISUAL não estiver definida) está definida com seu editor preferido. Você também deve certificar-se de que o seu sistema de entrega de emails esta funcionando corretamente. O &man.send-pr.1; utiliza mensagens de email para enviar e rastrear um relatório de problema. Se você não pode enviar mensagens de email a partir da máquina na qual está executando o &man.send-pr.1;, os seus relatórios de problema não irão chegar até a base de dados GNATS. Para maiores detalhes de como configurar o sistema de email no &os;, consulte o capítulo sobre Correio Eletrônico no Handbook do FreeBSD. Certifique-se de que o seu sistema de email não irá alterar a formatação da mensagem ao encaminhá-la para o GNATS. Qualquer patch que você enviar será inutilizado, caso o seu sistema de email quebre automaticamente as linhas, troque tabulações por espaços em branco ou altere os caracteres de mudança para uma nova linha, etc. Entretanto, para as seções de texto nós pedimos que você quebre manualmente as linhas próximo dos 70 caracteres, desta forma a versão web do PR poderá ser lida melhor. Considerações similares se aplicam se você estiver utilizando o formulário web de submissão de PR ao invés de utilizar o &man.send-pr.1;. Observe que operações de copiar-e-colar possuem seus próprios efeitos colaterais na formatação do texto. Em certos casos, pode ser necessário usar o &man.uuencode.1; para garantir que os patches cheguem sem modificações. Finalmente, se a sua submissão será longa, você deve preparar o texto do seu relatório offline, desta forma nada será perdido no caso de você ter problemas quando for submetê-lo. Isto pode ser um problema, em especial, se você estiver utilizando o formulário web.
Anexando <literal>patches</literal> ou arquivos As instruções abaixo se aplicam ao envio de PRs por email: O programa &man.send-pr.1; tem a capacidade de anexar arquivos em um relatório de problemas. Você pode anexar quantos arquivos desejar desde que os mesmos possuam nomes únicos (i.e. o nome próprio do arquivo, sem o caminho de diretório). Basta usar a opção na linha de comando para anexar os arquivos desejados: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors Não se preocupe com os arquivos binários, eles serão encodados automaticamente de forma a não perturbar o seu agente de correio. Se você anexar um patch, tenha certeza de utilizar a opção ou no &man.diff.1; para criar um diff contextual ou um diff unificado (o formato unificado é preferido), e tenha certeza de especificar os números de revisão exatos dos arquivos que você modificou, desta forma o desenvolvedor que ler seu relatório terá condições de aplicá-los facilmente. Para problemas com o kernel ou com os aplicativos do sistema base, um patch para o &os.current; (o ramo HEAD do CVS) é preferido uma vez que todo novo código deve ser aplicado e testado primeiro nele. Depois que forem realizados os testes apropriados, o código será fundido ou migrado para o ramo &os.stable;. Se você juntar um patch no corpo do email, em vez de enviá-lo como um arquivo anexo, você estará sujeito a ocorrência de um problema bastante comum ocasionado pela tendência de alguns clientes de email de converter tabs em espaços, o que irá arruinar completamente qualquer coisa que você tenha enviado com intenção de que fosse parte de um Makefile. Não envie patches como anexos usando Content-Transfer-Encoding: quoted-printable . Isto irá realizar character escaping e o patch inteiro estará inutilizado. Observe também que incluir pequenos patches em um PR é normalmente a coisa certa a se fazer — particularmente quando ele corrige o problema descrito no PR — grandes patches e especialmente código novo, que normalmente requerem uma revisão substancial antes de serem incorporados, devem ser colocados em um servidor web ou de FTP, e a url deve ser incluída no PR ao invés do patch propriamente dito. Os patches dentro de um email tendem a se deformar, especialmente quando o GNATS está envolvido, e quanto maior o patch, maior é a dificuldade para ambas as partes em consertá-lo. Além de que, ao colocar o patch na web, você pode modificá-lo sem ter que reenviar o arquivo completo como um followup do PR original. Além disso, os grandes patches simplesmente aumentam o tamanho do banco de dados, uma vez que os relatórios de problema fechados não são deletados, continuando a existir marcados como closed. Você deve observar que a menos que especifique explicitamente no seu PR ou diretamente no seu patch, qualquer correção que você envie será considerada como estando licenciada sob os mesmos termos do arquivo original que você modificou.
Preenchendo o template As instruções abaixo se aplicam apenas ao envio de PRs por email: Quando você executar o programa &man.send-pr.1;, você será apresentado a um template. O template consiste em uma lista de campos, alguns dos quais estarão pré-preenchidos, e alguns irão possuir comentários explicando o seu propósito ou então listando os valores aceitáveis. Não se preocupe com os comentários, eles serão removidos automaticamente se você não modificá-los ou então os remova você mesmo. Na parte superior do template, logo abaixo das linhas SEND-PR:, está o cabeçalho do email. Você normalmente não necessita modificá-lo, a menos que você esteja enviando o relatório de problema a partir de uma máquina ou de uma conta a qual pode enviar, mas não pode receber emails, neste caso você deve configurar manualmente os campos From: e Reply-To: para o seu endereço de email real. Você também pode querer enviar uma cópia do relatório para você mesmo (ou para alguma outra pessoa) através do uso de uma cópia carbono, adicionando um ou mais endereços de email na linha de cabeçalho Cc:. Os campos de linha única descritos abaixo, estão disponíveis apenas no template do email: Submitter-Id: Não altere este campo. O valor padrão é current-users e está correto, mesmo se você estiver executando o &os.stable;. Confidential: Não altere este campo. O valor padrão é no. Não tem sentido alterá-lo já que não existem relatórios de problema confidenciais no &os; — o banco de dados de PR é distribuído mundialmente pelo CVSup. Severity: Escolha uma opção entre non-critical, serious ou critical. Não faça escândalo; abstenha-se de rotular seu problema como critical a menos que ele realmente seja (por ex. questões de corrupção de dados, grave retrocesso de funcionalidade no -CURRENT em relação a versão anterior, etc)ou de serious a menos que seja algo que vai afetar muitos usuários (Kernel panic ou travamentos do sistema; Problemas com algum driver de dispositivo em particular ou com utilitários de sistema). Os desenvolvedores do &os; não irão necessariamente trabalhar no seu problema mais rápido se você inflar sua importância uma vez que existem muitas outras pessoas que fizeram exatamente isso — na verdade, alguns desenvolvedores prestam pouca atenção a este campo por causa disso. Problemas de segurança não devem ser submetidos para o GNATS, pois todas as informações no GNATS são de conhecimento público. Por favor, envie estes problemas seguindo as nossas diretrizes sobre relatórios de segurança. Priority: Escolha uma opção entre low, medium ou high. high deve ser reservada para os problemas que afetam praticamente todos os usuários do &os; e medium para os problemas que vão afetar muitos usuários. Este campo tornou-se tão amplamente abusado que perdeu quase que completamente seu objetivo. A próxima seção descreve os campos que são comuns entre a interface por email e a interface web: Originator: Por favor informe seu nome completo, seguido opcionalmente pelo seu endereço de email entre colchetes. Na interface de email, este campo é normalmente pré-preenchido com o campo gecos do usuário com o qual você está atualmente logado. O endereço de email que você utilizar irá se tornar uma informação pública e pode vir a se tornar disponível para spammers. Você deverá ter um sistema antispam funcional ou então deverá utilizar uma conta temporária de email. Contudo, por favor, lembre-se que se você não utilizar uma conta de email válida, nós não seremos capazes de entrar em contato com você para fazer perguntas sobre o seu PR. Organization: Campo livre para o que você quiser colocar. Este campo não é utilizado para nada significativo. Synopsis: Preencha este campo com uma descrição curta e precisa sobre o seu problema. A synopsis é utilizada como o assunto do email do relatório de problema, e também é utilizada na listagem de relatório de problemas e resumos; relatórios de problema com synopses obscuras tendem a serem ignorados. Como mencionado acima, se o seu relatório de problema inclui um patch, por favor, inicie sua synopsis com [patch] (incluindo os colchetes); se você for um maintainer considere adicionar [maintainer update] (incluindo os colchetes) ao início da sua synopsis e defina a classe do seu PR para maintainer-update. Category: Escolha uma categoria adequada. A primeira coisa que você precisa fazer é decidir em qual parte do sistema o seu problema está. Lembre-se, o &os; é um sistema operacional completo, o qual instala um kernel, as bibliotecas padrão, muitos drivers de dispositivos e um grande número de utilitários (este conjunto recebe o nome de sistema base). No entanto, existem milhares de aplicativos adicionais na Coleção de Ports. Você primeiro precisa decidir se o problema está no sistema base ou se está em algo que foi instalado através da Coleção de Ports. Aqui está uma descrição das principais categorias: Se o problema é com o Kernel, com as bibliotecas (tal como a biblioteca C padrão, libc), ou com um driver de dispositivo do sistema base, em geral você vai usar a categoria kern. (Existem algumas exceções; veja abaixo). Em geral, estas são coisas que estão descritas nas seções 2, 3 ou 4 das páginas de manual. Se o problema é com um programa binário, tal como o &man.sh.1; ou o &man.mount.8;, primeiro você precisa determinar se estes programas pertencem ao sistema base ou se foram adicionados através da coleção de ports. Se você estiver na dúvida, você pode executar um whereis nomedoprograma, no &os; por convenção todos os aplicativos da coleção de ports são instalados sob /usr/local, embora isso possa ser alterado por um administrador de sistemas. Para estes, você irá utilizar a categoria ports (sim, mesmo que a categoria do port seja www; veja abaixo). Se a localização do aplicativo for /bin, /usr/bin, /sbin, ou /usr/sbin, ele faz parte do sistema base, e você deverá utilizar a categoria bin. (Alguns programas, como o &man.gcc.1;, na prática utilizam a categoria gnu, mas não se preocupe com isso por agora.) Todos estes aplicativos estão descritos nas seções 1 ou 8 das páginas de manual. Se você acredita que o erro está no script de inicialização (rc), ou em algum outro tipo de arquivo de configuração não executável, então a categoria indicada será a conf (configuração). Estas são coisas descritas na seção 5 das páginas de manual. Se você encontrou um problema na documentação (artigos, livros, páginas de manual, etc.), a escolha correta para a categoria é a opção docs. Se você está tendo problemas com as páginas web do &os;, a escolha apropriada é www. Independentemente se você está tendo algum problema com um port chamado www/nomedoport, a categoria correta para o mesmo será ports. Existem algumas categorias mais especializadas. Se o problema pode ser classificado na categoria kern, e está relacionado ao subsistema USB, a categoria correta será usb. Se o problema pode ser classificado na categoria kern, e está relacionado com as bibliotecas de threads, a categoria correta será threads. Se o problema está localizado no sistema base, mas está relacionado a nossa aderência a padrões tais como o &posix;, a categoria correta será standards. Se o problema está relacionado a erros internos de uma &java.virtual.machine; (&jvm;), mesmo que o &java; tenha sido instalado a partir da coleção de ports, você deve selecionar a categoria java. Problemas genéricos com o port do &java; devem continuar sendo enviados na categoria ports. Isto deixa tudo mais. Se você está convencido de que o problema irá ocorrer apenas na arquitetura do processador que você está utilizando, selecione uma categoria específica para a sua arquitetura: geralmente i386 para máquinas compatíveis com a arquitetura Intel de 32 bits, amd64 para máquinas AMD executando em modo 64 bits (o que também inclui máquinas compatíveis com a arquitetura Intel executando em modo EMT64); e menos comumente ia64, powerpc, e sparc64. Estas categorias são muitas vezes utilizadas de forma indevida para problemas do tipo Eu não sei. Em vez de tentar adivinhar, por favor, apenas utilize a categoria misc. Uso correto da categoria específica de arquitetura. Você tem um computador comum (PC), e acredita que encontrou um problema específico com um chipset em particular ou com uma placa mãe específica: A categoria correta é i386. Uso incorreto da categoria específica de arquitetura. Você está tendo problemas com uma placa de expansão instalada em um barramento bastante comum, ou um problema com um tipo específico de disco rígido: neste caso, é provável que o problema ocorra em mais de uma arquitetura, e a categoria correta seria kern. Se você realmente não sabe onde está o problema (ou o mesmo não parece se encaixar nas categorias acima), utilize a categoria misc. Mas antes de fazer isto, pode ser uma boa idéia primeiro pedir ajuda na &a.questions;. Você poderá ser orientado à utilizar uma das outras categorias para obter um melhor resultado. Aqui está a lista atual de categorias (retirada do url ): advocacy: problemas relacionados a imagem pública do &os;. Obsoleta. alpha: problemas específicos da plataforma Alpha. amd64: problemas específicos da plataforma AMD64. arm: problemas específicos da plataforma ARM. bin: problemas com os programas de nível de usuário na base do sistema. conf: problemas com os arquivos de configuração, valores padrões, etc. docs: problemas com as páginas de manuais ou com a documentação online. gnu: problemas com softwares GNU, tais como &man.gcc.1; ou &man.grep.1;. i386: problemas específicos da plataforma &i386;. ia64: problemas específicos da plataforma ia64. java: problemas relacionados com a Maquina Virtual &java;. kern: problemas com o kernel, drivers de dispositivo (não específicos à uma plataforma), ou bibliotecas do sistema base. misc: Tudo aquilo que não se encaixa numa das outras categorias. (observe que não existe nada que pertença verdadeiramente a esta categoria, exceto os problemas com a infra estrutura de build e de release. As falhas temporárias de compilação do HEAD não pertencem a esta categoria. Também observe que é fácil para as coisas se perderem nesta categoria). ports: problemas relacionados com a Coleção de Ports. powerpc: problemas específicos da plataforma &powerpc;. sparc64: problemas específicos da plataforma &sparc64;. standards: problemas relacionados a conformidade com os padrões. threads: problemas relacionados a implementação de threads no &os; (especialmente no &os.current;). usb: problemas relacionados a implementação do USB no &os;. www: mudanças e melhorias no web site do &os;. Class: Escolha uma das seguintes opções: sw-bug: bugs de software. doc-bug: erros na documentação. change-request: solicitação de novas funcionalidades ou de alterações em funcionalidades existentes. update: atualizações para o ports ou para outros softwares de terceiros. maintainer-update: atualizações de ports pelos quais você é o responsável. Release: É a versão do &os; que você está utilizando. Este campo é preenchido automaticamente pelo &man.send-pr.1; e só necessita ser alterado se você estiver enviando o relatório de problema de um sistema diferente do que apresenta o problema. Finalmente, há uma série de campos de várias linhas: Environment: Este campo deve descrever, da forma mais precisa possível, o ambiente no qual o problema foi observado. Isto inclui a versão do sistema operacional, a versão do programa ou do arquivo específico que contém o problema, e qualquer outro item relevante tal como a configuração do sistema, outros softwares instalados que tenham influência no problema, etc. — ou seja, simplesmente tudo o que um desenvolvedor precisar saber para reconstruir o ambiente no qual o problema ocorreu. Description: Uma descrição precisa e completa do problema que você esta experimentando. Tente evitar especular sobre as causas do problema a menos que você tenha certeza de que está no caminho certo, do contrário você pode induzir o desenvolvedor a fazer suposições incorretas sobre o problema. How-To-Repeat: Um resumo com as ações que você precisa executar para reproduzir o problema. Fix: Preferencialmente um patch, ou no mínimo um workaround (o que não só ajuda as outras pessoas que estão com o mesmo problema, como também auxilia o desenvolvedor a entender melhor a causa do problema), mas se você não tem nenhuma idéia consistente, é melhor deixar este campo em branco do que especular.
Enviando o relatório de problemas Se você está utilizando o &man.send-pr.1;: Uma vez que você tenha terminado de preencher o template, salve-o, e saia do editor de texto, ao fazer isto o &man.send-pr.1; irá lhe perguntar se você deseja s)end, e)dit or a)bort?. Para ir em frente e enviar o relatório de problema pressione s, caso você queira voltar ao editor para realizar alguma alteração pressione e, ou então pressione a para cancelar o envio. Se você optar por abortar, o seu relatório de problema irá permanecer no seu disco rígido (o &man.send-pr.1; irá lhe informar o nome do arquivo antes de finalizar), assim você poderá editá-lo quando for mais conveniente, ou poderá transferi-lo para um sistema com uma melhor conectividade, no qual poderá enviá-lo usando a opção com o &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report Este comando irá ler o arquivo especificado, validar o seu conteúdo, remover os comentários e enviar o seu PR. Se você está utilizando o formulário web: Antes de pressionar o botão submit para enviar o seu relatório, você terá que preencher um campo com o texto exibido na imagem de captcha exibida no final do formulário. Infelizmente esta medida teve de ser adotada devido ao mau uso do mesmo por sistemas automatizados e por alguns indivíduos mal intencionados. É um mal necessário do qual ninguém gosta. Por favor, não peça para removê-lo. Recomendamos fortemente que você salve o seu trabalho em algum outro lugar antes de pressionar o botão submit. Um problema comum e que ocorre com muitos usuários é a visualização de uma imagem de captcha velha exibida a partir do cache do navegador. Se isso acontecer com você o seu envio será rejeitado e você poderá perder o seu trabalho. Se você, por qualquer motivo, não conseguir visualizar as imagens, e também estiver impossibilitado de utilizar o &man.send-pr.1;, por favor, aceite nossas desculpas por está inconveniência e envie seu relatório de problema por e-mail para a equipe de bugbusters do &os;, no endereço freebsd-bugbusters@FreeBSD.org.
Acompanhamento Depois que seu relatório de problema tiver sido entregue, você receberá uma confirmação por e-mail com o número de rastreamento que foi atribuído ao mesmo e uma URL a qual você poderá utilizar para consultar o status do seu PR. Com um pouco de sorte, alguém irá se interessar pelo seu problema e tentará resolvê-lo, ou, conforme o caso explicar porque não se trata de um problema. Você será notificado automaticamente de qualquer mudança de status, e irá receber uma cópia de qualquer comentário ou correção que alguém venha a anexar à trilha de auditoria do seu relatório de problema. Se alguém lhe requisitar alguma informação adicional, ou se você lembrar de algo ou descobrir algo que você não tenha mencionado no seu relatório inicial, por favor utilize um dos dois métodos abaixo para enviar uma atualização: A forma mais fácil é utilizar o link e followup existente na página web individual de cada PR, a qual pode ser encontrada a partir da página de busca de relatórios. Ao clicar no link será aberta uma janela do seu cliente de e-mail com os campos To: e Subject: já corretamente preenchidos (se o seu navegador estiver configurado corretamente para fazer isto). Alternativamente, você pode apenas enviá-lo para &a.bugfollowup;, certificando-se de que o número de rastreamento está incluso no Subject: de forma que o sistema de acompanhamento de bugs tenha como saber em qual relatório de problema ele deve anexar o material recebido. Se você não incluir o número de rastreamento, o GNATS irá se confundir e criará um relatório de problema completamente novo, o qual será atribuído ao administrador do GNATS, e então o seu followup irá ficar perdido até que alguém tenha tempo de arrumar a bagunça, o que pode levar dias e até mesmo semanas para ocorrer. Forma errada: Subject: Sobre o PR que eu enviei Forma correta: Subject: Re: ports/12345: problemas de compilação do foo/bar Se o relatório de problema permanecer aberto depois que o problema já tiver sido resolvido, basta enviar um follow-up (da forma descrita acima) informando que o PR pode ser fechado, e se possível, explicando como e quando o problema foi corrigido.
Se você está tendo problemas A maioria dos PRs que chegam ao sistema é processada rapidamente; entretanto em alguns momentos o GNATS fica lento e você pode não receber o seu email de confirmação de imediato, levando 10 minutos ou mesmo um pouco mais para recebê-lo. Por favor, tente ser paciente. Além disso, uma vez que o GNATS recebe tudo por email, é absolutamente vital que o &os; processe todas as mensagens que chegam utilizando filtros antispam. Se você não receber o email de confirmação em até duas horas, você pode ter sido barrado por este sistema; Neste caso, por favor, entre em contato com o adminisrador do GNATS no endereço bugmeister@FreeBSD.org e peça ajuda. Dentre as medidas antispam que utilizamos existe uma a qual verifica a aderência da sua mensagem em relação a uma série de abusos comums em emails baseados em HTML (embora o sistema não necessariamente invalide uma mensagem devido a mera inclusão de código HTML no PR). Recomendamos fortemente que você evite utilizar emails no formato HTML quando estiver enviando um PR: Não apenas é provável que a sua mensagem seja bloqueada pelos filtros, como ela também irá prejudicar o banco de dados. O bom e velho email em texto puro é fortemente preferido. Em raras ocasiões você irá se deparar com um bug do GNATS pelo qual um PR será aceito, receberá um número de rastreamento, mas não irá aparecer na lista de PRs em nenhuma consulta realizada no web site. O que pode ter ocorrido é que o índice do banco de dados ficou fora de sincronia com o próprio banco de dados. Uma forma de testar se é isto que esta acontecendo com você é acessar um PR individual qualquer listado a partir do formulário de busca, e substituir o numero do PR na URL pelo seu e verificar se ele carrega normalmente. Se ele carregar, por favor, notifique os administradores do GNATS no endereço bugmeister@FreeBSD.org. Observe que existe uma tarefa agendada no cron que reconstrói periodicamente o banco de dados, de forma que a menos que você esteja com pressa, nenhuma ação será necessária.
Leituras complementares Esta é uma lista com material de referência recomendado sobre boas práticas para se escrever e processar um relatório de problema. Esta lista não tem por objetivo ser uma lista completa. Como reportar bugs de forma efetiva— Um excelente ensaio por Simon G. Tatham sobre a elaboração de relatórios de problemas eficientes (não é especifico sobre o &os;). Guia de como lidar com relatórios de problemas — Uma percepção valiosa sobre como os desenvolvedores do FreeBSD devem lidar com os relatórios de problemas.
+ +
diff --git a/pt_BR.ISO8859-1/books/fdp-primer/book.xml b/pt_BR.ISO8859-1/books/fdp-primer/book.xml index b96fbef5c1..885166984f 100644 --- a/pt_BR.ISO8859-1/books/fdp-primer/book.xml +++ b/pt_BR.ISO8859-1/books/fdp-primer/book.xml @@ -1,298 +1,296 @@ %chapters; ]> &a.ptbr.p.fdpp; para novos colaboradores Projeto de documentação do FreeBSD 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 DocEng $FreeBSD$ $FreeBSD$ &legalnotice; Obrigado por tornar-se parte do Projeto de Documentação do FreeBSD. A sua contribuição é extremamente valiosa. Este &a.ptbr.p.fdpp; cobre tudo o que você precisa saber para começar a contribuir com o Projeto de Documentação do FreeBSD, desde as ferramentas e softwares que você estará utilizando (tanto os obrigatórios quanto os recomendados) à filosofia por trás do projeto de documentação. Este documento é um trabalho em andamento, e não está completo. As sessões que sabemos estarem incompletas estão indicadas com um * no seu nome. Prefácio <foreignphrase>Prompt</foreignphrase> do interpretador de comandos (<foreignphrase>shell</foreignphrase>) A tabela seguinte mostra o prompt padrão do sistema e o prompt do super usuário. Os exemplos irão utilizar estes prompts para indicar com qual usuário o exemplo foi executado. Usuário Prompt Usuário normal &prompt.user; root &prompt.root; Convenções Tipográficas A tabela seguinte descreve as convenções tipográficas utilizadas neste livro. Propósito Exemplos Nome de um comando. Utilize ls -a para listar todos os arquivos. Nome de um arquivo. Edite o seu arquivo .login . Saída (output) de um programa na tela do computador. Você tem email. O que você digita, quando contrastado com a saída (output) do programa na tela do computador. &prompt.user; su Password: Referência a uma página de manual. Utilize o &man.su.1; para assumir outro nome de usuário. Nome de usuário e de grupos de usuários Apenas o root pode fazer isso. Ênfase Você deve fazer isso. Variáveis da linha de comando; Substitua com o nome real ou com a variável. Para deletar um arquivo, digite rm nome_do_arquivo Variáveis de ambiente O $HOME é o seu diretório home. Notas, dicas, informações importantes, avisos e exemplos Ao longo do texto aparecerão notas, avisos e exemplos. Notas são representadas desta forma, e contêm informações para as quais você deveria ficar atento, pois podem afetar o que você faz. Dicas são representadas desta forma, e contêm informações que você pode achar úteis, ou que mostram uma maneira mais fácil de fazer alguma coisa. Informações importantes são representadas desta forma. Normalmente elas destacam passos extras que você pode precisar realizar. Avisos são representados deste modo, e contêm informações de alerta para você sobre possíveis danos se você não seguir as instruções. Estes danos podem ser físicos: para o seu equipamento ou para você; ou, podem ser não-físicos: tal como a deleção inadvertida de arquivos importantes. Uma amostra de exemplo Os exemplos são representados deste modo, e normalmente contêm exemplos que você deve analisar, ou então, mostram como deveriam ser os resultados de uma determinada ação. Agradecimentos Meu muito obrigado a Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn, e Christopher Maden, por terem gasto parte do seu tempo lendo os primeiros rascunhos deste documento e por terem oferecido muitos comentários e críticas construtivas para este trabalho. &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/pt_BR.ISO8859-1/books/handbook/Makefile b/pt_BR.ISO8859-1/books/handbook/Makefile index 69946296b9..9d74af4614 100644 --- a/pt_BR.ISO8859-1/books/handbook/Makefile +++ b/pt_BR.ISO8859-1/books/handbook/Makefile @@ -1,168 +1,166 @@ # # $FreeBSD$ # # Build the FreeBSD Handbook (Brazilian Portuguese). # # The FreeBSD Documentation Project # The FreeBSD Brazilian Portuguese Documentation Project # # Original revision: 1.53 # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ MAINTAINER=lioux@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= #IMAGES = advanced-networking/isdn-bus.eps #IMAGES+= advanced-networking/isdn-twisted-pair.eps #IMAGES+= advanced-networking/natd.eps #IMAGES+= install/userconfig.scr #IMAGES+= install/userconfig2.scr #IMAGES+= install/hdwrconf.scr #IMAGES+= install/probstart.scr #IMAGES+= install/main1.scr #IMAGES+= install/sysinstall-exit.scr #IMAGES+= install/main-doc.scr #IMAGES+= install/docmenu1.scr #IMAGES+= install/main-keymap.scr #IMAGES+= install/keymap.scr #IMAGES+= install/main-options.scr #IMAGES+= install/options.scr #IMAGES+= install/main-std.scr #IMAGES+= install/fdisk-drive1.scr #IMAGES+= install/fdisk-edit1.scr #IMAGES+= install/fdisk-edit2.scr #IMAGES+= install/boot-mgr.scr #IMAGES+= install/fdisk-drive2.scr #IMAGES+= install/disklabel-ed1.scr #IMAGES+= install/disklabel-auto.scr #IMAGES+= install/disklabel-root1.scr #IMAGES+= install/disklabel-root2.scr #IMAGES+= install/disklabel-fs.scr #IMAGES+= install/disklabel-root3.scr #IMAGES+= install/disklabel-ed2.scr #IMAGES+= install/dist-set.scr #IMAGES+= install/dist-set2.scr #IMAGES+= install/media.scr #IMAGES+= install/ed0-conf.scr #IMAGES+= install/ed0-conf2.scr #IMAGES+= install/ftp-anon1.scr #IMAGES+= install/ftp-anon2.scr #IMAGES+= install/nfs-server-edit.scr #IMAGES+= install/security.scr #IMAGES+= install/console-saver1.scr #IMAGES+= install/console-saver2.scr #IMAGES+= install/console-saver3.scr #IMAGES+= install/console-saver4.scr #IMAGES+= install/timezone1.scr #IMAGES+= install/timezone2.scr #IMAGES+= install/timezone3.scr #IMAGES+= install/mouse1.scr #IMAGES+= install/mouse2.scr #IMAGES+= install/mouse3.scr #IMAGES+= install/mouse4.scr #IMAGES+= install/mouse5.scr #IMAGES+= install/mouse6.scr #IMAGES+= install/xf86setup.scr #IMAGES+= install/desktop.scr #IMAGES+= install/pkg-cat.scr #IMAGES+= install/pkg-sel.scr #IMAGES+= install/pkg-install.scr #IMAGES+= install/pkg-confirm.scr #IMAGES+= install/adduser1.scr #IMAGES+= install/adduser2.scr #IMAGES+= install/adduser3.scr #IMAGES+= install/mainexit.scr #IMAGES+= install/disk-layout.eps #IMAGES+= install/edit-inetd-conf.scr # Images from the cross-document image library #IMAGES_LIB= callouts/1.png #IMAGES_LIB+= callouts/2.png #IMAGES_LIB+= callouts/3.png #IMAGES_LIB+= callouts/4.png #IMAGES_LIB+= callouts/5.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= config/chapter.xml SRCS+= boot/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= x11/chapter.xml SRCS+= ports/chapter.xml SRCS+= preface/preface.xml SRCS+= colophon.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} DOC_PREFIX?= ${.CURDIR}/../../.. # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/pt_BR.ISO8859-1/books/handbook/chapters.ent b/pt_BR.ISO8859-1/books/handbook/chapters.ent index fb661ad326..cb59216e97 100644 --- a/pt_BR.ISO8859-1/books/handbook/chapters.ent +++ b/pt_BR.ISO8859-1/books/handbook/chapters.ent @@ -1,69 +1,69 @@ %pgpkeys; - + "> diff --git a/ru_RU.KOI8-R/articles/console-server/article.xml b/ru_RU.KOI8-R/articles/console-server/article.xml index c3b0af53e9..fd67e65863 100644 --- a/ru_RU.KOI8-R/articles/console-server/article.xml +++ b/ru_RU.KOI8-R/articles/console-server/article.xml @@ -1,1556 +1,1558 @@
ëÏÎÓÏÌØÎÙÊ ÓÅÒ×ÅÒ Gregory Bond
gnb@itga.com.au
 áÎÄÒÅÊ úÁÈ×ÁÔÏ× ðÅÒÅ×ÏÄ ÎÁ ÒÕÓÓËÉÊ ÑÚÙË: äÍÉÔÒÉÊ íÏÒÏÚÏ×ÓËÉÊ ðÅÒÅ×ÏÄ ÎÁ ÒÕÓÓËÉÊ ÑÚÙË: &tm-attrib.freebsd; &tm-attrib.cisco; &tm-attrib.intel; &tm-attrib.lantronix; &tm-attrib.microsoft; &tm-attrib.opengroup; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÏÐÉÓÙ×ÁÅÔÓÑ, ËÁË ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ &os;, ÁÐÐÁÒÁÔÎÏÅ É ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ÒÁÂÏÔÁÀÝÅÅ Ó &os;, ÄÌÑ ÐÏÓÔÒÏÅÎÉÑ ËÏÎÓÏÌØÎÏÇÏ ÓÅÒ×ÅÒÁ. ëÏÎÓÏÌØÎÙÍ ÓÅÒ×ÅÒÏÍ ÏÂÙÞÎÏ ÎÁÚÙ×ÁÀÔ ÍÁÛÉÎÕ, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ ÏÔÓÌÅÖÉ×ÁÎÉÑ ËÏÎÓÏÌÅÊ ÍÎÏÇÉÈ ÄÒÕÇÉÈ ÍÁÛÉÎ ×ÍÅÓÔÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÍÎÏÇÉÈ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ÔÅÒÍÉÎÁÌÏ×. ËÏÎÓÏÌØÎÙÊ ÓÅÒ×ÅÒ ðÒÏÂÌÅÍÁ õ ×ÁÓ ÅÓÔØ ËÏÍÐØÀÔÅÒÎÙÊ ÚÁÌ Ó ÍÎÏÖÅÓÔ×ÏÍ &unix;-ÓÅÒ×ÅÒÏ× É ËÏÍÍÕÎÉËÁÃÉÏÎÎÙÍ ÏÂÏÒÕÄÏ×ÁÎÉÅÍ. ëÁÖÄÏÊ ÜÔÏÊ ÍÁÛÉÎÅ ÎÅÏÂÈÏÄÉÍÁ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÁÑ ËÏÎÓÏÌØ. ïÄÎÁËÏ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÔÅÒÍÉÎÁÌÙ ÔÒÕÄÎÏ ÎÁÊÔÉ É ÏÎÉ ÄÏÓÔÁÔÏÞÎÏ ÄÏÒÏÇÉ (ÏÓÏÂÅÎÎÏ ÐÏ ÓÒÁ×ÎÅÎÉÀ Ó ðë, ÏÂÌÁÄÁÀÝÉÍÉ ÇÏÒÁÚÄÏ ÂÏÌØÛÉÍÉ ×ÏÚÍÏÖÎÏÓÔÑÍÉ). é ×Ó£ ÜÔÏ × ËÏÍÐØÀÔÅÒÎÏÍ ÚÁÌÅ ÚÁÎÉÍÁÅÔ ÍÎÏÇÏ ÍÅÓÔÁ. ÷ÁÍ ÎÅÏÂÈÏÄÉÍ ÄÏÓÔÕÐ Ë ËÏÎÓÏÌÉ, ÐÏÔÏÍÕ ÞÔÏ ËÏÇÄÁ ÞÔÏ-ÔÏ ÎÅ ÒÁÂÏÔÁÅÔ, ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ ÎÁÐÒÁ×ÌÑÀÔÓÑ ÔÕÄÁ. é ÎÅËÏÔÏÒÙÅ ÒÁÂÏÔÙ ×ÙÐÏÌÎÑÀÔÓÑ Ó ËÏÎÓÏÌÉ (Ë ÐÒÉÍÅÒÕ, ÐÒÉ ×ÏÚÎÉËÎÏ×ÅÎÉÉ ÐÒÏÂÌÅÍ Ó ÚÁÇÒÕÚËÏÊ ÉÌÉ ÐÒÉ ÕÓÔÁÎÏ×ËÅ ÉÌÉ ÏÂÎÏ×ÌÅÎÉÉ ïó). îÅËÏÔÏÒÙÅ &unix;-ÓÉÓÔÅÍÙ ÐÏÚ×ÏÌÑÀÔ ÐÅÒÅÈÏÄÉÔØ Ó ËÏÎÓÏÌÉ × ÒÅÖÉÍ ÍÏÎÉÔÏÒÁ ðúõ, ËÏÔÏÒÙÊ ÉÎÏÇÄÁ Ñ×ÌÑÅÔÓÑ ÅÄÉÎÓÔ×ÅÎÎÙÍ ÓÐÏÓÏÂÏÍ ÚÁÓÔÁ×ÉÔØ ÆÕÎËÃÉÏÎÉÒÏ×ÁÔØ ÎÅÒÁÂÏÔÁÀÝÕÀ ÍÁÛÉÎÕ. þÁÓÔÏ ÜÔÏ ÏÓÕÝÅÓÔ×ÌÑÅÔÓÑ ÐÏÓÙÌËÏÊ LINE BREAK ÎÁ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÏÒÔ ËÏÎÓÏÌÉ. åÓÌÉ ÍÙ ÓÏÂÉÒÁÅÍÓÑ ÐÏÒÁÂÏÔÁÔØ Ó ËÏÎÓÏÌÑÍÉ, ÔÏ ÂÙÌÏ ÂÙ ×ÅÌÉËÏÌÅÐÎÏ ÏÓÕÝÅÓÔ×ÉÔØ ÅÝ£ ÎÅÓËÏÌØËÏ ×ÅÝÅÊ: õÄÁÌ£ÎÎÙÊ ÄÏÓÔÕÐ. äÁÖÅ × ÏÄÎÏÍ ÐÏÍÅÝÅÎÉÉ ÂÙÌÏ ÂÙ ÎÅÐÌÏÈÏ ÉÍÅÔØ ÄÏÓÔÕÐ ËÏ ×ÓÅÍ ËÏÎÓÏÌÑÍ Ó ×ÁÛÅÇÏ ÒÁÂÏÞÅÇÏ ÍÅÓÔÁ ÂÅÚ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÐÅÒÅÄ×ÉÇÁÔØÓÑ ÐÏ ËÏÍÐØÀÔÅÒÎÏÍÕ ÚÁÌÕ. á ÉÎÏÇÄÁ ÍÁÛÉÎÙ ÒÁÓÐÏÌÏÖÅÎÙ ÇÄÅ-ÔÏ ÄÁÌÅËÏ, ÍÏÖÅÔ ÂÙÔØ, ÄÁÖÅ × ÄÒÕÇÏÊ ÓÔÒÁÎÅ. ðÒÏÔÏËÏÌÉÒÏ×ÁÎÉÅ. åÓÌÉ ÞÔÏ-ÔÏ ÉÄ£Ô ÎÅ ÔÁË, ×ÁÍ ÎÅ ÐÏÍÅÛÁÅÔ ×ÏÚÍÏÖÎÏÓÔØ ÐÏÓÍÏÔÒÅÔØ ÐÒÅÄÙÄÕÝÕÀ ×ÙÄÁÞÕ ÎÁ ËÏÎÓÏÌØ, ÞÔÏÂÙ ÐÏÎÑÔØ ÐÒÏÉÓÈÏÄÑÝÅÅ. ïÂÙÞÎÙÅ ËÏÎÓÏÌØÎÙÅ ÜËÒÁÎÙ ÄÁÀÔ ×ÁÍ ÐÏÓÌÅÄÎÉÅ 25 ÓÔÒÏË. þÅÍ ÔÁËÉÈ ÓÔÒÏË ÂÕÄÅÔ ÂÏÌØÛÅ, ÔÅÍ ÌÕÞÛÅ. îÅÚÁ×ÉÓÉÍÏÓÔØ ÏÔ ÓÅÔÉ. òÅÛÅÎÉÅ ÄÏÌÖÎÏ ÆÕÎËÃÉÏÎÉÒÏ×ÁÔØ ÄÁÖÅ ÐÒÉ ÎÅÒÁÂÏÔÁÀÝÅÊ ÓÅÔÉ. ÷ ËÏÎÃÅ ËÏÎÃÏ×, ÂÏÌØÛÅ ×ÓÅÇÏ ËÏÎÓÏÌÉ ×ÁÍ ÎÕÖÎÙ ÉÍÅÎÎÏ ÐÒÉ ÏÔËÌÀÞÅÎÉÉ ÓÅÔÉ! åÝ£ ÌÕÞÛÅ ÄÏÂÉÔØÓÑ ÎÅÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÓÅÔÉ Ó ×ÏÚÍÏÖÎÏÓÔØÀ ÕÄÁÌ£ÎÎÏÇÏ ÄÏÓÔÕÐÁ. ïÔÓÕÔÓÔ×ÉÅ ÏÄÎÏÊ ÔÏÞËÉ, ËÒÉÔÉÞÎÏÊ ÄÌÑ ÒÁÂÏÔÙ. ëÏÎÓÏÌØÎÁÑ ÓÉÓÔÅÍÁ, ËÏÔÏÒÁÑ ÐÒÉ×ÏÄÉÔ Ë ÎÅÒÁÂÏÔÏÓÐÏÓÏÂÎÏÓÔÉ ×ÓÅÈ ÍÁÛÉÎ ÐÒÉ ÓÂÏÅ, ÎÅ ÎÕÖÎÁ. üÔÏ ÏÓÏÂÅÎÎÏ ×ÁÖÎÏ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ Ó &unix;-ÈÏÓÔÁÍÉ Sun, ÔÁË ËÁË ÏÎÉ ÂÕÄÕÔ ×ÏÓÐÒÉÎÉÍÁÔØ ×ÙËÌÀÞÅÎÉÅ ÔÅÒÍÉÎÁÌÁ ËÁË BREAK É ÂÕÄÕÔ ÐÅÒÅÈÏÄÉÔØ × ÒÅÖÉÍ ROM-ÍÏÎÉÔÏÒÁ. éÎÔÅÒÆÅÊÓ Ó ÐÅÊÄÖÉÎÇÏ×ÙÍ ÉÌÉ ÄÒÕÇÉÍ ÐÏÄÏÂÎÙÍ ÕÓÔÒÏÊÓÔ×ÏÍ ÐÏÄÁÞÉ ÐÒÅÄÕÐÒÅÖÄÁÀÝÉÈ ÓÏÏÂÝÅÎÉÊ. ÷ÏÚÍÏÖÎÏÓÔØ ÕÄÁÌ£ÎÎÏÇÏ ×ÙËÌÀÞÅÎÉÑ É ÐÏ×ÔÏÒÎÏÇÏ ×ËÌÀÞÅÎÉÑ ÍÁÛÉÎ. îÅ ÓÌÉÛËÏÍ ×ÙÓÏËÁÑ ÓÔÏÉÍÏÓÔØ. åÝ£ ÌÕÞÛÅ, ÅÓÌÉ ÓÉÓÔÅÍÁ ÂÕÄÅÔ ÂÅÓÐÌÁÔÎÏÊ! ÷ÏÚÍÏÖÎÙÅ ÒÅÛÅÎÉÑ åÓÌÉ ÄÌÑ ×ÁÛÉÈ ÓÅÒ×ÅÒÏ× ×Ù ÉÓÐÏÌØÚÕÅÔÅ ðë-ÏÂÏÒÕÄÏ×ÁÎÉÅ, ÔÏ ÏÄÎÉÍ ÉÚ ×ÏÚÍÏÖÎÙÈ ÒÅÛÅÎÉÊ Ñ×ÌÑÅÔÓÑ KVM-ÐÅÒÅËÌÀÞÁÔÅÌØ. ôÁËÏÊ KVM-ÐÅÒÅËÌÀÞÁÔÅÌØ ÐÏÚ×ÏÌÑÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÄÎÕ ËÌÁ×ÉÁÔÕÒÕ, ×ÉÄÅÏÍÏÎÉÔÏÒ É ÍÙÛØ Ó ÎÅÓËÏÌØËÉÍÉ ÓÉÓÔÅÍÎÙÍÉ ÂÌÏËÁÍÉ. üÔÏ ÓÎÉÖÁÅÔ ÏÓÔÒÏÔÕ ÐÒÏÂÌÅÍÙ Ó ÆÉÚÉÞÅÓËÉÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ, ÏÄÎÁËÏ ÒÁÂÏÔÁÅÔ ÔÏÌØËÏ Ó ðë-ÏÂÏÒÕÄÏ×ÁÎÉÅÍ (Á ÎÅ Ó ÌÀÂÙÍÉ ÔÉÐÁÍÉ ÉÍÅÀÝÉÈÓÑ ËÏÍÍÕÎÉËÁÃÉÏÎÎÙÈ ÕÓÔÒÏÊÓÔ×), É ÎÅ ÏÂÅÓÐÅÞÉ×ÁÅÔ ÄÏÓÔÕÐ ×ÎÅ ËÏÍÐØÀÔÅÒÎÏÇÏ ÚÁÌÁ. ðÒÉ ÜÔÏÍ ÄÁÖÅ ÏÔÓÕÔÓÔ×ÕÅÔ ÐÒÏËÒÕÔËÁ ÉÓÔÏÒÉÉ ÉÌÉ ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÅ, É ×ÁÍ ÎÕÖÎÏ ÏÒÇÁÎÉÚÏ×Ù×ÁÔØ ÏÐÏ×ÅÝÅÎÉÅ ËÁËÉÍ-ÔÏ ÄÒÕÇÉÍ ÓÐÏÓÏÂÏÍ. âÏÌØÛÉÍ ÍÉÎÕÓÏÍ Ñ×ÌÑÅÔÓÑ ÔÏ, ÞÔÏ ÜÔÏ ÎÅ ÒÁÂÏÔÁÅÔ Ó ÕÓÔÒÏÊÓÔ×ÁÍÉ ÔÏÌØËÏ Ó ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÍ ÉÎÔÅÒÆÅÊÓÏÍ, ÔÁËÉÍ, ËÁË ËÏÍÍÕÎÉËÁÃÉÏÎÎÏÅ ÏÂÏÒÕÄÏ×ÁÎÉÅ. üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÄÁÖÅ × ÚÁÌÅ, ÚÁÐÏÌÎÅÎÎÏÍ ðë-ÓÅÒ×ÅÒÁÍÉ, ×ÁÍ ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÎÕÖÎÙÍ ÄÏÓÔÕÐ Ë ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÊ ËÏÎÓÏÌÉ. îÁ ÓÁÍÏÍ ÄÅÌÅ, Doug Schache ÕËÁÚÁÌ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÎÁÊÔÉ KVM-ÐÅÒÅËÌÀÞÁÔÅÌÉ Ó ÐÏÄÄÅÒÖËÏÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ËÏÎÓÏÌÅÊ ÉÌÉ ÓÏ×ÍÅÓÔÉÍÙÅ ËÁË Ó Sun, ÔÁË É Ó ðë, ÎÏ ÏÎÉ ÄÏÒÏÇÉ. ðÏÓÍÏÔÒÉÔÅ, ÎÁÐÒÉÍÅÒ, ÎÁ ÓÁÊÔÅ Avocent.) ÷Ù ÍÏÖÅÔÅ ÐÏÐÙÔÁÔØÓÑ ÏÂÏÊÔÉÓØ ÂÅÚ ËÏÎÓÏÌØÎÏÇÏ ÔÅÒÍÉÎÁÌÁ, ÏÄÎÁËÏ ËÏÇÄÁ Ô×ÏÒÑÔÓÑ ÓÔÒÁÎÎÙÅ ×ÅÝÉ, ×ÁÍ ÄÅÊÓÔ×ÉÔÅÌØÎÏ ÎÕÖÎÏ ×ÉÄÅÔØ ÐÒÏÉÓÈÏÄÑÝÅÅ ÎÁ ËÏÎÓÏÌÉ. é ×ÁÍ ÎÕÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ËÏÎÓÏÌØ ÄÌÑ ÚÁÇÒÕÚËÉ É ×ÙÐÏÌÎÅÎÉÑ ÔÁËÉÈ ÄÅÊÓÔ×ÉÊ, ËÁË ÕÓÔÁÎÏ×ËÁ ÉÌÉ ÏÂÎÏ×ÌÅÎÉÅ ïó. ÷Ù ÍÏÖÅÔÅ ÐÏÐÙÔÁÔØÓÑ ×ÙÄÅÌÉÔØ ÏÄÉÎ ËÏÎÓÏÌØÎÙÊ ÔÅÒÍÉÎÁÌ É ÐÅÒÅËÌÀÞÁÔØÓÑ ÐÒÉ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÍÅÖÄÕ ÓÅÒ×ÅÒÁÍÉ, ÌÉÂÏ ÐÒÉ ÐÏÍÏÝÉ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÇÏ ÐÅÒÅËÌÀÞÁÔÅÌÑ, ÌÉÂÏ ÐÒÏÓÔÏ ÐÏÄËÌÀÞÁÑ ÅÇÏ Ë ÎÕÖÎÏÊ ÍÁÛÉÎÅ. ðÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÐÅÒÅËÌÀÞÁÔÅÌÉ ÔÁËÖÅ ÔÒÕÄÎÏ ÎÁÊÔÉ É ÏÎÉ ÎŠģÛÅ×Ù, Ë ÔÏÍÕ ÖÅ ÍÏÇÕÔ ÉÍÅÔØ ÐÒÏÂÌÅÍÙ Ó ÐÏÓÙÌËÏÊ ÓÉÇÎÁÌÁ BREAK ÐÒÉ ÐÅÒÅËÌÀÞÅÎÉÉ. é (ÅÓÌÉ ×ÁÛ ËÏÍÐØÀÔÅÒÎÙÊ ÚÁÌ ÐÏÈÏÖ ÎÁ ÎÁÛ) Õ ×ÁÓ ÎÉËÏÇÄÁ ÎÅ ÂÕÄÅÔ ÓÏ×ÐÁÄÁÔØ ËÏÍÂÉÎÁÃÉÑ ËÁÂÅÌÅÊ ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ Ë ÎÕÖÎÏÊ ÍÁÛÉÎÅ, É ÄÁÖÅ ÅÓÌÉ ×ÓÅ ËÁÂÅÌÉ ÎÁ ÍÅÓÔÅ, ×Ù ÎÉËÏÇÄÁ Ó ÔÏÞÎÏÓÔØÀ ÎÅ ÂÕÄÅÔÅ ÚÎÁÔØ, ËÁËÁÑ ÉÍÅÎÎÏ ËÏÍÂÉÎÁÃÉÑ ÏËÏÎÞÁÎÉÊ DTE/DCE ×ÅÄ£Ô Ë ËÏÎËÒÅÔÎÏÍÕ ÏÂÏÒÕÄÏ×ÁÎÉÀ. ôÁË ÞÔÏ ÐÅÒ×ÙÅ 10 ÍÉÎÕÔ ×Ù ÐÏÔÒÁÔÉÔÅ ÎÁ ×ÏÚÎÀ Ó ÉÓÈÏÄÑÝÉÍÉ É ×ÈÏÄÑÝÉÍÉ ÏËÏÎÞÁÎÉÑÍÉ, ÔÏÇÄÁ ËÁË ÓÅÒ×ÅÒ ÎÅ ÒÁÂÏÔÁÅÔ, Á ÐÏÌØÚÏ×ÁÔÅÌÉ ÕÖÅ ËÒÉÞÁÔ. ëÏÎÅÞÎÏ, ÜÔÏ ÎÅ ÕÄÏ×ÌÅÔ×ÏÒÑÅÔ ÔÒÅÂÏ×ÁÎÉÑÍ ÕÄÁÌ£ÎÎÏÇÏ ÐÏÄËÌÀÞÅÎÉÑ Ë ÓÉÓÔÅÍÅ É ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÑ. é ÎÅÉÚÂÅÖÎÏ ËÏÎÓÏÌØ ÏËÁÖÅÔÓÑ ÎÅ ÐÏÄËÌÀÞÅÎÎÏÊ Ë ÎÕÖÎÏÊ ÍÁÛÉÎÅ, ÔÁË ÞÔÏ ×Ù ÐÏÔÅÒÑÅÔÅ ×ÓÅ ËÏÎÓÏÌØÎÙÅ ÓÏÏÂÝÅÎÉÑ, ÍÏÇÕÝÉÅ ÒÁÓÓËÁÚÁÔØ ×ÁÍ Ï ÐÒÏÉÓÈÏÄÑÝÅÍ. ïÄÎÉÍ ÉÚ ÒÁÓÐÒÏÓÔÒÁΣÎÎÙÈ ÒÅÛÅÎÉÊ Ñ×ÌÑÅÔÓÑ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÁÐÐÁÒÁÔÎÏÇÏ ÔÅÒÍÉÎÁÌØÎÏÇÏ ÓÅÒ×ÅÒÁ. ïÂÙÞÎÏ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÐÏÒÔÙ ÐÏÄËÌÀÞÅÎÙ Ë ËÏÎÓÏÌÑÍ ÒÁÚÌÉÞÎÙÈ ÍÁÛÉÎ, É ÎÁÓÔÒÏÅÎÙ ÎÁ ÏÂÒÁÔÎÙÊ telnet-ÄÏÓÔÕÐ. üÔÏ ÚÎÁÞÉÔ, ÞÔÏ ÐÏÌØÚÏ×ÁÔÅÌØ ÍÏÖÅÔ ÐÏÄËÌÀÞÉÔØÓÑ ÐÏ ÐÒÏÔÏËÏÌÕ telnet Ë ÏÐÒÅÄÅÌ£ÎÎÏÍÕ IP/ÐÏÒÔÕ É ÏËÁÚÁÔØÓÑ ÐÏÄËÌÀÞÅÎÎÙÍ Ë ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÊ ËÏÎÓÏÌÉ. üÔÏ ÍÏÖÅÔ ÂÙÔØ ÏÞÅÎØ ÜÆÆÅËÔÉ×ÎÙÍ Ó ÔÏÞËÉ ÚÒÅÎÉÑ ÓÔÏÉÍÏÓÔÉ, ÔÁË ËÁË ÐÏÄÈÏÄÑÝÉÅ ÓÔÁÒÙÅ ÔÅÒÍÉÎÁÌØÎÙÅ ÓÅÒ×ÅÒÙ ÍÏÖÎÏ ÎÁÊÔÉ ÐÏ ÄÏÓÔÁÔÏÞÎÏ ÎÉÚËÏÊ ÃÅÎÅ (ÐÏÌÁÇÁÅÍ, ÞÔÏ ÐÁÒÙ ÔÁËÉÈ Õ ×ÁÓ ÅÝ£ ÎÅÔ). é, ËÏÎÅÞÎÏ, ÏÎÉ ÄÏÓÔÕÐÎÙ ÐÏ ÓÅÔÉ, ÞÔÏ ÐÏÄÈÏÄÉÔ ÄÌÑ ÏÒÇÁÎÉÚÁÃÉÉ ÕÐÒÁ×ÌÅÎÉÑ ÉÚ ÓÅÔÉ. ïÄÎÁËÏ Õ ÎÉÈ ÅÓÔØ ÏÄÉÎ ÂÏÌØÛÏÊ ÎÅÄÏÓÔÁÔÏË: ÅÓÌÉ ÓÅÔØ ÎÅ ÒÁÂÏÔÁÅÔ, ÔÏ ×Ù ÔÅÒÑÅÔÅ ÄÏÓÔÕÐ Ë ÌÀÂÏÊ ËÏÎÓÏÌÉ, ÄÁÖÅ ÅÓÌÉ ÎÁÈÏÄÉÔÅÓØ ÐÒÑÍÏ ÐÅÒÅÄ ÍÁÛÉÎÏÊ. (üÔÏ ÍÏÖÅÔ ÂÙÔØ ÎÅÓËÏÌØËÏ ÎÅ ÔÁË, ÅÓÌÉ Õ ×ÁÓ ÅÓÔØ ÐÏÄÈÏÄÑÝÉÊ ÔÅÒÍÉÎÁÌ, ÐÏÄËÌÀÞÅÎÎÙÊ Ë ÏÄÎÏÍÕ ÉÚ ÐÏÒÔÏ× ÔÅÒÍÉÎÁÌØÎÏÇÏ ÓÅÒ×ÅÒÁ, Ó ËÏÔÏÒÏÇÏ ÍÏÖÎÏ ×ÙÐÏÌÎÑÔØ ÐÏÄËÌÀÞÅÎÉÑ, ÎÏ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ ÔÅÒÍÉÎÁÌØÎÏÇÏ ÓÅÒ×ÅÒÁ ÍÏÖÅÔ ÜÔÏÇÏ É ÎÅ ÐÏÄÄÅÒÖÉ×ÁÔØ.) ë ÔÏÍÕ ÖÅ ÐÒÉ ÜÔÏÍ ÏÔÓÕÔÓÔ×ÕÅÔ ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÅ É ÐÏ×ÔÏÒ ËÏÎÓÏÌØÎÙÈ ÓÏÏÂÝÅÎÉÊ. ïÄÎÁËÏ ÐÒÉÌÏÖÉ× ÎÅËÏÔÏÒÙÅ ÕÓÉÌÉÑ É ÉÓÐÏÌØÚÕÑ ÏÐÒÅÄÅÌ£ÎÎÏÅ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ÔÁËÏÅ, ËÁË conserver (ÏÐÉÓÁÎÏ ÄÁÌÅÅ), ÜÔÕ ÓÉÓÔÅÍÕ ÍÏÖÎÏ ÚÁÓÔÁ×ÉÔØ ÈÏÒÏÛÏ ÒÁÂÏÔÁÔØ. åÝ£ ÏÄÉÎ ÐÏÄÈÏÄ, ÐÒÅÄÌÏÖÅÎÎÙÊ âÒÏÎÏÍ çÏÎÄ×ÁÎÏÊ (Bron Gondwana), ÐÏÈÏÖ ÎÁ ÏÐÉÓÁÎÎÏÅ ×ÙÛÅ ÒÅÛÅÎÉÅ. åÓÌÉ ×ÁÛÉ ÓÅÒ×ÅÒÙ ÉÍÅÀÔ ÎÅÓËÏÌØËÏ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ÐÏÒÔÏ×, ×Ù ÍÏÖÅÔÅ ÐÏÄËÌÀÞÉÔØ ËÁÖÄÙÊ Ó×ÏÂÏÄÎÙÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÏÒÔ Ë ËÏÎÓÏÌØÎÏÍÕ ÐÏÒÔÕ ÂÌÉÖÁÊÛÅÇÏ ÓÅÒ×ÅÒÁ, ÓÏÚÄÁ× ÔÅÍ ÓÁÍÙÍ ËÏÌØÃÏ ËÏÎÓÏÌØÎÙÈ ÓÏÅÄÉÎÅÎÉÊ (× ÎÅËÏÔÏÒÏÍ ÐÏÒÑÄËÅ). üÔÏ ÍÏÖÅÔ ÄÏÓÔÁÔÏÞÎÏ ÈÏÒÏÛÏ ÒÁÂÏÔÁÔØ ×ÍÅÓÔÅ Ó ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ conserver, ÏÄÎÁËÏ, Ó ÄÒÕÇÏÊ ÓÔÏÒÏÎÙ, ÍÏÖÅÔ ÎÅÓËÏÌØËÏ ÚÁÐÕÔÙ×ÁÔØ (× ÓÍÙÓÌÅ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÚÁÐÏÍÉÎÁÎÉÑ, ËÁËÏÊ ÐÏÒÔ Ë ËÁËÏÊ ËÏÎÓÏÌÉ ÐÏÄËÌÀÞÅÎ). é ÜÔÏÇÏ ÎÅ ÐÏÌÕÞÉÔÓÑ, ÅÓÌÉ ×ÁÍ ÎÕÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÐÏÒÔÙ × ÄÒÕÇÉÈ ÃÅÌÑÈ (ÔÁËÉÈ, ËÁË ÐÏÄËÌÀÞÅÎÉÅ ÍÏÄÅÍÏ×) ÌÉÂÏ ÎÁ ×ÁÛÉÈ ÍÁÛÉÎÁÈ ÎÅÔ Ó×ÏÂÏÄÎÙÈ ÐÏÒÔÏ×. ìÉÂÏ, ÅÓÌÉ ×ÁÛ ÂÀÄÖÅÔ ÐÒÅ×ÙÛÁÅÔ ÎÅÏÂÈÏÄÉÍÏÓÔØ × ÈÁËÅÒÓËÉÈ ÒÅÛÅÎÉÑÈ, ×Ù ÍÏÖÅÔÅ ÐÒÉÏÂÒÅÓÔÉ ÏÄÎÏ ÉÚ ÇÏÔÏ×ÙÈ ÒÅÛÅÎÉÊ. ïÎÉ ÒÁÚÌÉÞÁÀÔÓÑ ÐÏ ÓÔÏÉÍÏÓÔÉ É Ó×ÏÉÍ ×ÏÚÍÏÖÎÏÓÔÑÍ. ðÏÓÍÏÔÒÉÔÅ, Ë ÐÒÉÍÅÒÕ, Lightwave, Perle, Avocent ÉÌÉ Black Box. üÔÉ ÒÅÛÅÎÉÑ ÍÏÇÕÔ ÏËÁÚÁÔØÓÑ ÄÏÓÔÁÔÏÞÎÏ ÄÏÒÏÇÉÍÉ - ÏÂÙÞÎÏ ÏÔ 100 ÄÏ 400 ÄÏÌÌ. óûá ÚÁ ÐÏÒÔ. îÁÛÅ ÒÅÛÅÎÉÅ ÷ Ó×ÅÔÅ ÔÒÅÂÏ×ÁÎÉÊ ×ÙÛÅ ÍÙ ×ÙÂÒÁÌÉ ÒÅÛÅÎÉÅ ÎÁ ÏÓÎÏ×Å ×ÙÄÅÌÅÎÎÏÇÏ ðë ÐÏÄ ÕÐÒÁ×ÌÅÎÉÅÍ &unix; Ó ÍÎÏÇÏÐÏÒÔÏ×ÙÍ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÍ ÁÄÁÐÔÅÒÏÍ É ÏÐÒÅÄÅÌ£ÎÎÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ, ÐÒÅÄÎÁÚÎÁÞÅÎÎÙÍ ÄÌÑ ÒÁÂÏÔÙ Ó ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÍÉ ËÏÎÓÏÌÑÍÉ. ïÎÏ ÓÏÓÔÏÉÔ ÉÚ ÓÌÅÄÕÀÝÉÈ ÜÌÅÍÅÎÔÏ×: ðÏÄÅÒÖÁÎÎÙÊ ðë. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ &pentium; 166 Ó ÛÉÎÏÊ PCI, 2-ÇÉÇÁÂÁÊÔÎÙÍ Ö£ÓÔËÉÍ ÄÉÓËÏÍ É 64 ÍÅÇÁÂÁÊÔÁÍÉ ïúõ. üÔÏ ÐÒÅ×ÙÛÁÅÔ ÔÒÅÂÏ×ÁÎÉÑ ×ÙÐÏÌÎÑÅÍÏÊ ÚÁÄÁÞÉ, ÂÏÌÅÅ ÞÅÍ ÄÏÓÔÁÔÏÞÎÙÍ ÂÕÄÅÔ P-100, 500 íÂ, 32 íÂ. &unix;-ÓÉÓÔÅÍÁ ÄÌÑ ðë. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ &os; 4.3, ÔÁË ËÁË × ÎÁÛÅÍ ÏÆÉÓÅ ÏÎÁ ÉÓÐÏÌØÚÏ×ÁÌÁÓØ É ÄÌÑ ÄÒÕÇÉÈ ÚÁÄÁÞ. íÎÏÇÏÐÏÒÔÏ×ÙÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÁÄÁÐÔÅÒ. íÙ ×ÙÂÒÁÌÉ 8-ÐÏÒÔÏ×ÙÊ ÁÄÁÐÔÅÒ &easyio; PCI ËÏÍÐÁÎÉÉ Stallion Technologies. üÔÏ ÓÔÏÉÌÏ ÎÁÍ ÐÏÒÑÄËÁ $AUD740, ÍÅÎØÛÅ ÞÅÍ $100 ÚÁ ÐÏÒÔ, ÚÁÐÌÁÞÅÎÎÙÈ Harris Technologies (Õ ÎÉÈ ÅÓÔØ ÍÎÏÇÏ ×ÓÅÇÏ, ÎÏ ÜÔÏ ÎÅ ÏÂÑÚÁÔÅÌØÎÏ ÓÁÍÏÅ ÄÅÛ£×ÏÅ ÍÅÓÔÏ - ÐÏÉÝÉÔÅ ÐÏÂÌÉÚÏÓÔÉ, ×Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ÍÅÓÔÏ ÇÏÒÁÚÄÏ ÄÅÛÅ×ÌÅ). áÄÁÐÔÅÒ ÉÍÅÅÔ ÓÚÁÄÉ ÂÏÌØÛÏÊ ÒÁÚß£Í DB80 É ÐÏÄËÌÀÞÁÅÍÙÊ ËÁÂÅÌØ, ÉÍÅÀÝÉÊ ÂÌÏË ÉÚ 8 ÇΣÚÄ RJ-45. (íÙ ×ÙÂÒÁÌÉ ×ÁÒÉÁÎÔ Ó RJ-45, ÔÁË ËÁË ÎÁÛÁ ËÁÂÅÌØÎÁÑ ÓÉÓÔÅÍÁ ÐÏÌÎÏÓÔØÀ ÐÏÓÔÒÏÅÎÁ ÎÁ RJ-45. üÔÏ ÐÏÚ×ÏÌÑÅÔ ÎÁÍ ÐÅÒÅËÌÀÞÁÔØ ÓÏÅÄÉÎÅÎÉÑ ÏÔ ÎÕÖÎÏÇÏ ÂÌÏËÁ Ë ËÏÎÓÏÌØÎÏÍÕ ÓÅÒ×ÅÒÕ ÂÅÚ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ËÁÂÅÌÅÊ.) üÔÏ ÅÄÉÎÓÔ×ÅÎÎÁÑ ×ÅÝØ, ËÏÔÏÒÕÀ ÎÁÍ ÐÒÉÛÌÏÓØ ÐÒÉÏÂÒÅÓÔÉ, ÞÔÏÂÙ ×Ó£ ÚÁÒÁÂÏÔÁÌÏ. ÷ òÏÓÓÉÉ, ×ÏÚÍÏÖÎÏ, ÂÕÄÅÔ ÐÒÏÝÅ ÎÁÊÔÉ ËÁÒÔÙ Omega PCI ËÏÍÐÁÎÉÉ ëâ "ëÒÏÎÉËÓ" / Cronyx Engineering, ÍÅÎÅÅ $40 ÚÁ ÐÏÒÔ. [ÐÒÉÍ. ÐÅÒÅ×.]. íÙ ÐÏÓÔÒÏÉÌÉ Ä×Á ÓÅÒ×ÅÒÁ, ÐÏ ÏÄÎÏÍÕ ÄÌÑ ËÁÖÄÏÇÏ ÍÁÛÉÎÎÏÇÏ ÚÁÌÁ, Ó 8 ÐÏÒÔÁÍÉ × ÏÄÎÏÍ É 16 ÐÏÒÔÁÍÉ (Ä×ÕÍÑ ÁÄÁÐÔÅÒÁÍÉ &easyio; PCI) × ÄÒÕÇÏÍ. åÓÌÉ ÂÙ ÎÁÍ ÎÕÖÎÏ ÂÙÌÏ ÂÏÌÅÅ 16 ÐÏÒÔÏ×, ÔÏ ÐÏ ÓÔÏÉÍÏÓÔÉ ÂÏÌÅÅ ÜÆÆÅËÔÉ×ÎÙÍ ÂÙÌÏ ÂÙ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÄÒÕÇÉÈ ÁÄÁÐÔÅÒÏ× Stallion. ôÅÏÒÅÔÉÞÅÓËÉ ÍÙ ÍÏÖÅÍ ÐÏÄÄÅÒÖÉ×ÁÔØ 128 ÐÏÒÔÏ× ÎÁ ËÁÖÄÏÍ ÓÅÒ×ÅÒÅ (ÐÒÉ ÐÏÍÏÝÉ 2 ÈÏÓÔ-ÁÄÁÐÔÅÒÏ× EasyConnect 8/64 É 8 16-ÐÏÒÔÏ×ÙÈ ÍÏÄÕÌÅÊ RJ-45) ÏÂÝÅÊ ÓÔÏÉÍÏÓÔØÀ $AUD12,000. íÏÄÅÍ ÄÌÑ ÕÄÁÌ£ÎÎÏÇÏ ÄÏÓÔÕÐÁ Ë ÈÏÓÔÕ ËÏÎÓÏÌØÎÏÇÏ ÓÅÒ×ÅÒÅ ÐÒÉ ÏÔÓÕÔÓÔ×ÉÉ ÓÅÔÉ. íÙ ÅÝ£ ÜÔÏÇÏ ÎÅ ÄÅÌÁÌÉ, ÔÁË ËÁË ËÏÍÐØÀÔÅÒÎÙÊ ÚÁÌ ÎÁÈÏÄÉÔÓÑ ÒÑÄÏÍ, ÎÏ ËÏÇÄÁ ÍÙ ÐÅÒÅÎÅÓÅÍ ÓÅÒ×ÅÒ × óÉÄÎÅÊ, ÍÙ ÄÏÂÁ×ÉÍ ÍÏÄÅÍ. éÄÅÑ ÚÁËÌÀÞÁÅÔÓÑ × ÔÏÍ, ÞÔÏ ÐÒÉ ÏÔÓÕÔÓÔ×ÉÉ ÓÅÔÉ ×Ù ÍÏÖÅÔÅ ÐÏÚ×ÏÎÉÔØ, ÐÏÄËÌÀÞÉÔØÓÑ Ë ÓÅÒ×ÅÒÎÏÊ ÍÁÛÉÎÅ É ÚÁÐÕÓÔÉÔØ ËÏÎÓÏÌØÎÕÀ ÐÒÏÇÒÁÍÍÕ ÌÏËÁÌØÎÏ. ÷ ÃÅÌÑÈ ÂÅÚÏÐÁÓÎÏÓÔÉ ÍÙ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÏÓÔÁ×ÉÍ ÍÏÄÅÍ ×ÙËÌÀÞÅÎÎÙÍ, É ÐÏÐÒÏÓÉÍ ÔÁÍÏÛÎÉÈ ÖÉÔÅÌÅÊ óÉÄÎÅÑ ÎÁÖÁÔØ ÈÏÒÏÛÏ ×ÉÄÎÕÀ ËÎÏÐËÕ ÐÒÉ ÎÅÏÂÈÏÄÉÍÏÓÔÉ. ðÒÏÇÒÁÍÍÁ ÐÏÄ ÎÁÚ×ÁÎÉÅÍ conserver. ïÎÁ ×ÙÐÏÌÎÑÅÔ ×Ó£, ÞÔÏ ÔÒÅÂÕÅÔÓÑ ÄÌÑ ×ËÌÀÞÅÎÉÑ ÕÄÁÌ£ÎÎÏÇÏ ÄÏÓÔÕÐÁ Ë ËÏÎÓÏÌÑÍ, ÏÂÅÓÐÅÞÉ×ÁÅÔ ÐÏ×ÔÏÒ ××ÏÄÁ, ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÅ É ÔÁË ÄÁÌÅÅ. ïÎÁ ÐÏÓÔÁ×ÌÑÅÔÓÑ × ×ÉÄÅ Ä×ÕÈ ÂÌÏËÏ×: ÓÅÒ×ÅÒ ÐÏÄ ÉÍÅÎÅÍ conserver, ÒÁÂÏÔÁÀÝÉÊ ËÁË ÄÁÅÍÏÎ É ÐÏÄËÌÀÞÁÀÝÉÊÓÑ Ë ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÍ ÐÏÒÔÁÍ, ×ÙÐÏÌÎÑÀÝÉÊ ×ÅÄÅÎÉÅ ÖÕÒÎÁÌÏ× É ÐÒÏÞÉÅ ÄÅÊÓÔ×ÉÑ, É ËÌÉÅÎÔÓËÁÑ ÐÒÏÇÒÁÍÍÁ ÐÏÄ ÎÁÚ×ÁÎÉÅÍ console, ËÏÔÏÒÁÑ ÍÏÖÅÔ ÐÏÄËÌÀÞÁÔØÓÑ Ë ÓÅÒ×ÅÒÕ, ÐÏËÁÚÙ×ÁÔØ ËÏÎÓÏÌØÎÙÅ ÓÏÏÂÝÅÎÉÑ, ÐÏÓÙÌÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ ÎÁÖÁÔÉÊ ËÌÁ×ÉÛ (É BREAK) É ÔÏÍÕ ÐÏÄÏÂÎÏÅ. ôÁËÁÑ ÁÒÈÉÔÅËÔÕÒÁ ÏÂÅÓÐÅÞÉ×ÁÅÔ ×ÙÐÏÌÎÅÎÉÅ ×ÓÅÈ ÏÓÎÏ×ÎÙÈ ÔÒÅÂÏ×ÁÎÉÊ, ËÒÏÍÅ ÕÄÁÌ£ÎÎÏÇÏ ÕÐÒÁ×ÌÅÎÉÑ ÜÌÅËÔÒÏÐÉÔÁÎÉÅÍ: õÄÁÌ£ÎÎÙÊ ÄÏÓÔÕÐ ÏÂÅÓÐÅÞÉ×ÁÅÔÓÑ ÚÁ ÓÞ£Ô ÔÏÇÏ, ÞÔÏ ËÌÉÅÎÔÓËÁÑ ÐÒÏÇÒÁÍÍÁ console ÒÁÂÏÔÁÅÔ × ÓÅÔÉ. ðÒÏÔÏËÏÌÉÒÏ×ÁÎÉÅ ×ÅÄ£ÔÓÑ ÐÒÏÇÒÁÍÍÏÊ conserver. åÓÌÉ ÓÅÔØ ÎÅ ÒÁÂÏÔÁÅÔ, ÔÏ ÍÙ ÍÏÖÅÍ ÉÓÐÏÌØÚÏ×ÁÔØ ËÏÎÓÏÌØ ðë ÄÌÑ ÌÏËÁÌØÎÏÇÏ ÚÁÐÕÓËÁ ËÌÉÅÎÔÁ console. ÷ ÓÌÕÞÁÅ ÇÅÏÇÒÁÆÉÞÅÓËÉ ÕÄÁÌ£ÎÎÙÈ ÍÅÓÔ ÍÙ ÍÏÖÅÍ ÄÏÂÁ×ÉÔØ ÍÏÄÅÍ ÄÌÑ ËÏÍÍÕÔÉÒÕÅÍÏÇÏ ÄÏÓÔÕÐÁ Ë ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ ÓÅÒ×ÅÒÁ ÄÌÑ ÚÁÐÕÓËÁ ËÌÉÅÎÔÁ. õÓÔÁÎÏ×É× ÐÁÔÞÉ ÎÁ ÓÅÒ×ÅÒÙ &solaris; (ÏÂÒÁÔÉÔÅÓØ Ë ), ÍÙ ÍÏÖÅÍ ÉÚÂÅÖÁÔØ ÎÅÒÁÂÏÔÏÓÐÏÓÏÂÎÏÓÔÉ ×ÓÅÇÏ ËÏÍÐØÀÔÅÒÎÏÇÏ ÚÁÌÁ ÐÒÉ ÓÂÏÅ × ËÏÎÓÏÌØÎÏÍ ÓÅÒ×ÅÒÅ ÎÁ ÂÁÚÅ ðë (ÉÌÉ ÐÒÉ ÏÔËÌÀÞÅÎÉÑ ÜÌÅËÔÒÏÐÉÔÁÎÉÑ, ÉÌÉ ÐÏ ËÁËÏÊ-ÔÏ ÄÒÕÇÏÊ ÐÒÉÞÉÎÅ). õ ÎÁÓ ÕÖÅ ÅÓÔØ ÐÅÊÄÖÉÎÇÏ×ÏÅ ÏÐÏ×ÅÝÅÎÉÅ Ó ÄÒÕÇÏÊ ÕÓÔÁÎÏ×ÌÅÎÎÏÊ ÎÁÍÉ ÓÉÓÔÅÍÙ, ÏÄÎÁËÏ ÎÁ ËÏÎÓÏÌØÎÏÍ ÓÅÒ×ÅÒÅ ÅÓÔØ ×ÓÑ ÎÕÖÎÁÑ ÉÎÆÏÒÍÁÃÉÑ ÖÕÒÎÁÌÏ×, ÔÁË ÞÔÏ ÐÒÉ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÜÔÏ ÍÏÖÅÔ ÂÙÔØ ÌÅÇËÏ ÒÅÁÌÉÚÏ×ÁÎÏ. é ÄÁÖÅ ÅÓÔØ ÍÏÄÅÍ ÄÌÑ Ú×ÏÎËÁ × ÐÅÊÄÖÉÎÇÏ×ÕÀ ËÏÍÐÁÎÉÀ! îÁ ÄÁÎÎÙÊ ÍÏÍÅÎÔ ÍÙ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÍ ÕÄÁÌ£ÎÎÏÅ ÕÐÒÁ×ÌÅÎÉÅ ÜÌÅËÔÒÏÐÉÔÁÎÉÅÍ. îÅËÏÔÏÒÙÅ ×ÅÒÓÉÉ ÐÒÏÇÒÁÍÍÙ conserver ÜÔÏ ÐÏÄÄÅÒÖÉ×ÁÀÔ, ÎÏ ÜÔÏ ÔÒÅÂÕÅÔ ÎÁÌÉÞÉÑ ÓÐÅÃÉÁÌØÎÙÈ ÁÄÁÐÔÅÒÏ×, ÕÐÒÁ×ÌÑÅÍÙÈ ÞÅÒÅÚ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÓÏÅÄÉÎÅÎÉÑ. õ ÎÁÓ ÎÅÔ ÏÓÔÒÏÊ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÐÏ ÕÄÁÌ£ÎÎÏÍÕ ×ÙËÌÀÞÅÎÉÀ (Õ ÎÁÓ ÅÓÔØ ÏÂÓÌÕÖÉ×ÁÀÝÉÊ ÐÅÒÓÏÎÁÌ × ËÁÖÄÏÍ ÕÄÁÌ£ÎÎÏÍ ÏÆÉÓÅ, ËÏÔÏÒÙÊ ÍÏÖÅÔ ÜÔÏ ÓÄÅÌÁÔØ ÐÏÄ ÎÁÛÉÍ ÒÕËÏ×ÏÄÓÔ×ÏÍ), ÔÁË ÞÔÏ ÜÔÏ ÎÅ ÂÏÌØÛÁÑ ÐÒÏÂÌÅÍÁ, É ÍÙ ÍÏÖÅÍ ÌÅÇËÏ ÜÔÏ ÄÏÂÁ×ÉÔØ, ÅÓÌÉ Õ×ÉÄÉÍ × ÜÔÏÍ ÎÅÏÂÈÏÄÉÍÏÓÔØ É ÐÏÌÕÞÉÍ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÅ ÏÂÏÒÕÄÏ×ÁÎÉÅ. üÔÏ ÒÅÛÅÎÉÅ ÂÙÌÏ ÏÞÅÎØ ÄÅÛ£×ÙÍ. ïÂÝÁÑ ÓÔÏÉÍÏÓÔØ 9-ÐÏÒÔÏ×ÏÇÏ ÓÅÒ×ÅÒÁ ÓÏÓÔÁ×ÉÌÁ $AUD750 ÚÁ ÁÄÁÐÔÅÒÙ ××ÏÄÁ/×Ù×ÏÄÁ, ÔÁË ËÁË ÍÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ÕÓÔÁÒÅ×ÛÉÊ ðë É Õ ÎÁÓ ÉÍÅÌÏÓØ ÏÂÏÒÕÄÏ×ÁÎÉÅ × ×ÉÄÅ ÓÐÅÃÉÁÌØÎÙÈ ËÁÂÅÌÅÊ. åÓÌÉ ÂÙ ÍÙ ×Ó£ ÐÏËÕÐÁÌÉ, ÔÏ ÜÔÏ ÏÂÏÛÌÏÓØ ÂÙ ×ÓÅÇÏ ÌÉÛØ ÐÒÉÍÅÒÎÏ × $AUD1500 ÚÁ 8-ÐÏÒÔÏ×ÙÊ ÓÅÒ×ÅÒ. îÁÓÔÒÏÊËÁ ÓÅÒ×ÅÒÁ ðÒÏ×ÅÒËÁ ÄÒÁÊ×ÅÒÁ Stallion &os; ÁÄÅË×ÁÔÎÏ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÁÄÁÐÔÅÒÙ Stallion ÎÁÞÉÎÁÑ Ó ×ÅÒÓÉÉ 4.4. åÓÌÉ ×ÁÛÁ ×ÅÒÓÉÑ ÓÔÁÒÛÅ, ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÏÂÎÏ×ÉÔØ ÅÅ (ÜÔÏ ÎÕÖÎÏ ÓÄÅÌÁÔØ ÅÝÅ É ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ×ÁÛÁ ÓÉÓÔÅÍÁ ÎÅ ÂÙÌÁ ÐÏÄ×ÅÒÖÅÎÁ ÉÚ×ÅÓÔÎÙÍ ÐÒÏÂÌÅÍÁÍ ÚÁÝÉÔÙ). ïÂÒÁÔÉÔÅÓØ Ë ÏÐÉÓÁÎÉÀ × ÆÁÊÌÅ /usr/src/UPDATING É òÕËÏ×ÏÄÓÔ×Å &os; ÚÁ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÅÊ Ï ÏÂÎÏ×ÌÅÎÉÉ ÓÉÓÔÅÍÙ. ëÏÎÆÉÇÕÒÁÃÉÑ ÎÏ×ÏÇÏ ÑÄÒÁ äÒÁÊ×ÅÒ Stallion ÎÅ ×ËÌÀÞ£Î × ÉÓÐÏÌØÚÕÅÍÏÅ ÐÏ ÕÍÏÌÞÁÎÉÀ ÑÄÒÏ GENERIC, ÔÁË ÞÔÏ ×ÁÍ ÎÕÖÎÏ ÓÏÚÄÁÔØ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÑÄÒÁ Ó ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍÉ ÚÁÐÉÓÑÍÉ. ïÂÒÁÔÉÔÅÓØ Ë ÓÐÒÁ×ËÅ ÐÏ &man.stl.4; É ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÍÕ ÒÁÚÄÅÌÕ òÕËÏ×ÏÄÓÔ×Á &os;. óÏÚÄÁÎÉÅ ÕÓÔÒÏÊÓÔ× äÌÑ ÁÄÁÐÔÅÒÁ Stallion ×ÁÍ ÎÕÖÎÏ ÓÏÚÄÁÔØ ÆÁÊÌÙ ÕÓÔÒÏÊÓÔ× (ËÏÔÏÒÙÅ ÐÏ ÕÍÏÌÞÁÎÉÀ ÎÅ ÓÏÚÄÁÀÔÓÑ). ÷Ï ×ÒÅÍÑ ×ÙÐÏÌÎÅÎÉÑ ÏÐÉÓÁÎÎÏÊ ×ÙÛÅ ÐÒÏÃÅÄÕÒÙ ÎÏ×ÁÑ ×ÅÒÓÉÑ /dev/MAKEDEV Ó ÐÏÄÄÅÒÖËÏÊ Stallion ÂÕÄÅÔ ÓÏÚÄÁÎÁ ÕÔÉÌÉÔÏÊ mergemaster. åÓÌÉ Õ ×ÁÓ ÉÍÅÅÔÓÑ ÁÄÁÐÔÅÒ Stallion Ó ÂÏÌÅÅ ÞÅÍ 8 ÐÏÒÔÁÍÉ, ÔÏ ×ÁÍ ÎÕÖÎÏ ÏÔÒÅÄÁËÔÉÒÏ×ÁÔØ /dev/MAKEDEV É ÉÚÍÅÎÉÔØ ÏÐÒÅÄÅÌÅÎÉÅ maxport × ÒÁÊÏÎÅ ÓÔÒÏËÉ 250. ðÏ ÕÍÏÌÞÁÎÉÀ MAKEDEV ÓÏÚÄÁÅÔ ÆÁÊÌÙ ÕÓÔÒÏÊÓÔ× ÄÌÑ 8 ÐÏÒÔÏ×, ÞÔÏÂÙ ÕÍÅÎØÛÉÔØ ÒÁÚÍÅÒ ËÁÔÁÌÏÇÁ /dev. ÷ÙÐÏÌÎÉÔÅ ÐÒÉÍÅÒÎÏ ÔÁËÕÀ ËÏÍÁÎÄÕ: &prompt.root; cd /dev/ && sh MAKEDEV cuaE0 ÄÌÑ ÓÏÚÄÁÎÉÑ ÕÓÔÒÏÊÓÔ× ÄÌÑ ÉÓÈÏÄÑÝÉÈ Ú×ÏÎËÏ× ÄÌÑ ÐÅÒ×ÏÇÏ ÁÄÁÐÔÅÒÁ Stallion. äÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÌÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ÏÂÒÁÔÉÔÅÓØ Ë ÒÁÚßÑÓÎÅÎÉÑÍ × MAKEDEV É ÓÐÒÁ×ÏÞÎÏÊ ÓÔÒÁÎÉÃÅ &man.stl.4;. ëÏÍÐÉÌÑÃÉÑ conserver ðÏÓÍÏÔÒÉÔÅ ÒÁÚÄÅÌ Ï ×ÅÒÓÉÑÈ conserver; ÉÓÐÏÌØÚÕÅÍÁÑ ÍÎÏÊ ×ÅÒÓÉÑ ÎÁÈÏÄÉÔÓÑ × ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ× &os;, ÏÄÎÁËÏ, ÓÕÝÅÓÔ×ÕÀÔ É ÄÒÕÇÉÅ ×ÅÒÓÉÉ. éÍÅÅÔÓÑ Ä×Á ÓÐÏÓÏÂÁ ÕÓÔÁÎÏ×ËÉ conserver. ÷Ù ÍÏÖÅÔÅ ÌÉÂÏ ÓËÏÍÐÉÌÉÒÏ×ÁÔØ Å£ ÉÚ ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, ÌÉÂÏ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÍÅÈÁÎÉÚÍÏÍ ÐÏÒÔÏ× &os;. éÓÐÏÌØÚÏ×ÁÎÉÅ ÍÅÈÁÎÉÚÍÁ ÐÏÒÔÏ× éÓÐÏÌØÚÏ×ÁÎÉÅ ÐÏÒÔÏ× Ñ×ÌÑÅÔÓÑ ÂÏÌÅÅ ÑÓÎÙÍ ÐÏÄÈÏÄÏÍ, ÔÁË ËÁË ÓÉÓÔÅÍÁ ÐÁËÅÔÏ× ÍÏÖÅÔ ÏÔÓÌÅÖÉ×ÁÔØ ÕÓÔÁÎÏ×ÌÅÎÎÏÅ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ É ÐÏÌÎÏÓÔØÀ ÕÄÁÌÑÔØ ÅÇÏ, ÅÓÌÉ ÏÎÏ ÎÅ ÉÓÐÏÌØÚÕÅÔÓÑ. òÅËÏÍÅÎÄÕÅÍ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏÒÔ comms/conserver-com. ðÅÒÅÊÄÉÔÅ × ËÁÔÁÌÏÇ ÜÔÏÇÏ ÐÏÒÔÁ É (ÒÁÂÏÔÁÑ ËÁË ÐÏÌØÚÏ×ÁÔÅÌØ root) ÎÁÂÅÒÉÔÅ: &prompt.root; make DEFAULTHOST=consolehost install ÇÄÅ consolehost Ñ×ÌÑÅÔÓÑ ÉÍÅÎÅÍ ÍÁÛÉÎÙ, ÎÁ ËÏÔÏÒÏÊ ÒÁÂÏÔÁÅÔ ËÏÎÓÏÌØÎÙÊ ÓÅÒ×ÅÒ. úÁÄÁÎÉÅ ÜÔÏÇÏ ÐÒÉ ËÏÍÐÉÌÑÃÉÉ ÂÉÎÁÒÎÏÇÏ ÆÁÊÌÁ ÉÚÂÁ×ÌÑÅÔ ÏÔ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÕËÁÚÙ×ÁÔØ ÅÇÏ ËÁÖÄÙÊ ÒÁÚ ÐÒÉ ÚÁÐÕÓËÅ ÐÒÏÇÒÁÍÍÙ ÌÉÂÏ ÐÏÄÄÅÒÖÉ×ÁÔØ ÆÁÊÌÙ conserver.cf ÄÌÑ ËÁÖÄÏÇÏ ÈÏÓÔÁ. üÔÁ ËÏÍÁÎÄÁ ÚÁÇÒÕÚÉÔ, ÕÓÔÁÎÏ×ÉÔ ÐÁÔÞÉ, ÓËÏÎÆÉÇÕÒÉÒÕÅÔ, ÓËÏÍÐÉÌÉÒÕÅÔ É ÕÓÔÁÎÏ×ÉÔ ÐÒÏÇÒÁÍÍÕ conserver. ðÏÓÌÅ ÜÔÏÇÏ ×Ù ÍÏÖÅÔÅ ×ÙÐÏÌÎÉÔØ make package ÄÌÑ ÓÏÚÄÁÎÉÑ ÂÉÎÁÒÎÏÇÏ ÐÁËÅÔÁ, ËÏÔÏÒÙÊ ÍÏÖÎÏ ÕÓÔÁÎÏ×ÉÔØ ÎÁ ÏÓÔÁÌØÎÙÈ ÈÏÓÔÁÈ &os; ÐÏ ËÏÍÁÎÄÅ &man.pkg.add.1;. äÌÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÇÉÂËÏÓÔÉ ×Ù ÍÏÖÅÔÅ ÓÏÚÄÁÔØ Ä×Å ×ÅÒÓÉÉ ÐÁËÅÔÁ: ÏÄÎÕ ÄÌÑ ÍÁÛÉÎÙ Ó ËÏÎÓÏÌØÎÙÍ ÓÅÒ×ÅÒÏÍ ÂÅÚ ÐÁÒÁÍÅÔÒÁ DEFAULTHOST, Á ×ÔÏÒÕÀ ÄÌÑ ×ÓÅÈ ÏÓÔÁÌØÎÙÈ ÈÏÓÔÏ× Ó ÐÁÒÁÍÅÔÒÏÍ DEFAULTHOST. üÔÏ ÚÎÁÞÉÔ, ÞÔÏ ËÌÉÅÎÔÓËÁÑ ÐÒÏÇÒÁÍÍÁ ËÏÎÓÏÌÉ ÎÁ ÍÁÛÉÎÅ Ó ËÏÎÓÏÌØÎÙÍ ÓÅÒ×ÅÒÏÍ ÐÏ ÕÍÏÌÞÁÎÉÀ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ localhost, ÞÔÏ ÂÕÄÅÔ ÒÁÂÏÔÁÔØ ÐÒÉ ÏÔÓÕÔÓÔ×ÉÉ ÓÅÒ×ÅÒÁ ÉÍ£Î, ÐÒÉ ÓÂÏÑÈ × ÓÅÔÉ, Á ÔÁËÖÅ ÐÏÚ×ÏÌÉÔ ×ÙÐÏÌÎÑÔØ ÄÏ×ÅÒÑÅÍÙÅ (ÔÏ ÅÓÔØ ÂÅÓÐÁÒÏÌØÎÙÅ) ÐÏÄËÌÀÞÅÎÉÑ ÞÅÒÅÚ IP-ÁÄÒÅÓ localhost ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÐÏÄËÌÀÞÅÎÎÙÈ Ë ÍÁÛÉÎÅ Ó ËÏÎÓÏÌØÎÙÍ ÓÅÒ×ÅÒÏÍ (ÌÉÂÏ Ó ÜËÒÁÎÁ ËÏÎÓÏÌÉ, ÌÉÂÏ Ó ×ÓÐÏÍÏÇÁÔÅÌØÎÏÇÏ ÍÏÄÅÍÁ). ÷ÅÒÓÉÑ ÄÌÑ ÏÓÔÁÌØÎÙÈ ÍÁÛÉÎ Ó ÁÒÇÕÍÅÎÔÏÍ DEFAULTHOST ÏÚÎÁÞÁÅÔ, ÞÔÏ ÐÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ ÐÒÏÓÔÏ ÉÓÐÏÌØÚÏ×ÁÔØ ËÌÉÅÎÔÁ console ÂÅÚ ÕËÁÚÁÎÉÑ ËÁÖÄÙÊ ÒÁÚ ÉÍÅÎÉ ÈÏÓÔÁ, É ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÎÁÓÔÒÁÉ×ÁÔØ ÆÁÊÌ conserver.cf ÎÁ ËÁÖÄÏÊ ÍÁÛÉÎÅ. éÚ tar-ÁÒÈÉ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× åÓÌÉ ×Ù ÐÒÅÄÐÏÞÉÔÁÅÔÅ ÔÁËÏÊ ÓÐÏÓÏÂ, ÔÏ ÍÏÖÅÔÅ ÚÁÇÒÕÚÉÔØ conserver É ÓËÏÍÐÉÌÉÒÏ×ÁÔØ ÅÇÏ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ. ÷ÁÍ ÍÏÖÅÔ ÐÏÎÁÄÏÂÉÔØÓÑ ÓÄÅÌÁÔØ ÜÔÏ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ ÕÓÔÁÎÏ×ÉÔØ ËÌÉÅÎÔ ËÏÎÓÏÌÉ ÎÁ ÎÅ-&os; ÓÉÓÔÅÍÙ. íÙ ÉÓÐÏÌØÚÕÅÍ ËÌÉÅÎÔ ÎÁ ÎÁÛÉÈ ÍÁÛÉÎÁÈ Ó &solaris;, É ÏÎ ÂÅÚ ÐÒÏÂÌÅÍ ×ÚÁÉÍÏÄÅÊÓÔ×ÕÅÔ Ó ÓÅÒ×ÅÒÏÍ ÎÁ &os;. üÔÏ ÐÏÚ×ÏÌÑÅÔ ËÁÖÄÏÍÕ ×Ï ×ÓÅÊ ËÏÍÐÁÎÉÉ (ÍÎÏÇÉÅ ÉÚ ËÏÔÏÒÙÈ ÉÍÅÀÔ ðë ÂÅÚ ÄÏÓÔÕÐÁ Ë ÈÏÓÔÕ Ó &os; ÓÏ Ó×ÏÅÇÏ ÒÁÂÏÞÅÇÏ ÍÅÓÔÁ) ÏÂÒÁÝÁÔØÓÑ Ë ËÏÎÓÏÌØÎÏÍÕ ÓÅÒ×ÅÒÕ. úÁÇÒÕÚÉÔÅ ÆÁÊÌ Ó FTP-ÓÁÊÔÁ conserver.com. òÁÓÐÁËÕÊÔÅ ÅÇÏ × ÌÀÂÏÊ ËÁÔÁÌÏÇ, ÚÁÔÅÍ ÓËÏÎÆÉÇÕÒÉÒÕÊÔÅ, ×ÙÐÏÌÎÉ× &prompt.user; ./configure ðÁÒÁÍÅÔÒ ÐÏÍÏÇÁÅÔ ÉÚÂÅÖÁÔØ ÕËÁÚÁÎÉÑ ÇÌÁ×ÎÏÇÏ ÓÅÒ×ÅÒÁ ËÁÖÄÙÊ ÒÁÚ ÐÒÉ ÕÄÁÌ£ÎÎÏÍ ÚÁÐÕÓËÅ ËÌÉÅÎÔÁ (ÉÌÉ ÐÏÓÔÏÑÎÎÏÇÏ ÏÂÎÏ×ÌÅÎÉÑ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ× ÎÁ ×ÓÅÈ ÕÄÁÌ£ÎÎÙÈ ÈÏÓÔÁÈ). ðÁÒÁÍÅÔÒ ÐÏÍÏÇÁÅÔ ÉÚÂÅÖÁÔØ ÎÅÏÂÈÏÄÉÍÏÓÔÉ × ÏÂÎÏ×ÌÅÎÉÉ ÆÁÊÌÁ ÎÁ ×ÓÅÈ ÍÁÛÉÎÁÈ. ðÏÓÌÅ ÜÔÏÇÏ ÎÁÂÅÒÉÔÅ make É, ÒÁÂÏÔÁÑ ËÁË ÐÏÌØÚÏ×ÁÔÅÌØ root, make install. ëÏÎÆÉÇÕÒÁÃÉÑ conserver ðÒÏÇÒÁÍÍÁ conserver ÎÁÓÔÒÁÉ×ÁÅÔÓÑ ÞÅÒÅÚ ÆÁÊÌ Ó ÉÍÅÎÅÍ conserver.cf. üÔÏÔ ÆÁÊÌ ÏÂÙÞÎÏ ÎÁÈÏÄÉÔÓÑ × ËÁÔÁÌÏÇÅ /usr/local/etc É ÏÎ ÚÁÄÏËÕÍÅÎÔÉÒÏ×ÁÎ ÎÁ ÓÐÒÁ×ÏÞÎÏÊ ÓÔÒÁÎÉÃÅ &man.conserver.cf.5;. îÁÛ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ×ÙÇÌÑÄÉÔ ÐÒÉÍÅÒÎÏ ÔÁË: LOGDIR=/var/log/consoles gallows:/dev/cuaE0:9600p:&: roo:/dev/cuaE1:9600p:&: kanga:/dev/cuaE2:9600p:&: %% allow: itga.com.au trusted: 127.0.0.1 buzz ðÅÒ×ÁÑ ÓÔÒÏËÁ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÐÏ ÕÍÏÌÞÁÎÉÀ ×ÓÅ ÆÁÊÌÙ ÐÒÏÔÏËÏÌÏ× ÂÕÄÕÔ ÒÁÓÐÏÌÁÇÁÔØÓÑ × ËÁÔÁÌÏÇÅ /var/log/consoles. óÉÍ×ÏÌ & × ËÁÖÄÏÊ ÓÔÒÏËÅ ÕËÁÚÙ×ÁÅÔ ÎÁ ÔÏ, ÞÔÏ ÆÁÊÌ ÖÕÒÎÁÌÁ ÄÌÑ ÜÔÏÊ ÍÁÛÉÎÙ ÂÕÄÅÔ ÎÁÚÙ×ÁÔØÓÑ /var/log/consoles/machine. ÷ ÓÌÅÄÕÀÝÉÈ ÔÒ£È ÓÔÒÏËÁÈ ÐÏËÁÚÁÎÙ ÔÒÉ ÍÁÛÉÎÙ, Ë ËÏÔÏÒÙÍ ÎÁÍ ÎÕÖÎÏ ÐÏÄËÌÀÞÁÔØÓÑ. íÙ ÉÓÐÏÌØÚÕÅÍ ÕÓÔÒÏÊÓÔ×Á cuaEx ×ÍÅÓÔÏ ttyEx, ÐÏÔÏÍÕ ÞÔÏ ÎÁ ËÏÎÓÏÌØÎÙÈ ÐÏÒÔÁÈ ÏÂÙÞÎÏ ÏÔÓÕÔÓÔ×ÕÅÔ ÎÅÓÕÝÁÑ. üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÏÔËÒÙÔÉÅ ttyEx ÂÕÄÅÔ ÚÁ×ÉÓÁÔØ, É conserver ÎÉËÏÇÄÁ ÎÅ ÓÍÏÖÅÔ ÏÓÕÝÅÓÔ×ÉÔØ ÐÏÄËÌÀÞÅÎÉÅ. éÓÐÏÌØÚÏ×ÁÎÉÅ ÕÓÔÒÏÊÓÔ×Á cuaEx ÐÏÚ×ÏÌÑÅÔ ÕÊÔÉ ÏÔ ÜÔÏÊ ÐÒÏÂÌÅÍÙ. äÒÕÇÉÍ ÒÅÛÅÎÉÅÍ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÕÓÔÒÏÊÓÔ× ttyEx É ÒÁÚÒÅÛÅÎÉÅ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÎÁ ÜÔÉÍ ÐÏÒÔÁÈ ÐÒÏÇÒÁÍÍÎÏÊ ÎÅÓÕÝÅÊ, ×ÏÚÍÏÖÎÏ, ÐÕÔ£Í ÕÓÔÁÎÏ×ËÉ ÜÔÏÇÏ ÐÒÉ ÐÏÍÏÝÉ ÕÓÔÒÏÊÓÔ×Á ttyiEx × ÆÁÊÌÅ /etc/rc.serial. ðÏÓÍÏÔÒÉÔÅ ËÏÍÍÅÎÔÁÒÉÉ × ÜÔÏÍ ÆÁÊÌÅ ÄÌÑ ×ÙÑÓÎÅÎÉÑ ×ÓÅÈ ÄÅÔÁÌÅÊ. ôÁËÖÅ ÐÏÓÍÏÔÒÉÔÅ &man.sio.4; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÉÎÆÏÒÍÁÃÉÉ Ï ÕÓÔÒÏÊÓÔ×ÁÈ Ó ÎÁÞÁÌØÎÙÍ ÓÏÓÔÏÑÎÉÅÍ É Ó ÂÌÏËÉÒÏ×ÁÎÎÙÍ ÓÏÓÔÏÑÎÉÅÍ. (äÒÁÊ×ÅÒ Stallion ÔÁËÖÅ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÜÔÉ ÓÏÇÌÁÛÅÎÉÑ). é ÐÒÏÞÔÉÔÅ &man.stty.1; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÐÏÄÒÏÂÎÏÓÔÅÊ Ï ÕÓÔÁÎÏ×ËÅ ÒÅÖÉÍÏ× ÒÁÂÏÔÙ ÕÓÔÒÏÊÓÔ×. ÷ ÐÏÓÌÅÄÎÅÍ ÒÁÚÄÅÌÅ ÕËÁÚÁÎÏ, ÞÔÏ ÌÀÂÏÊ ÐÏÌØÚÏ×ÁÔÅÌØ, ÚÁÒÅÇÉÓÔÒÉÒÏ×Á×ÛÉÊÓÑ ÎÁ ÓÅÒ×ÅÒÎÏÊ ÍÁÛÉÎÅ, ÉÍÅÅÔ ÄÏÓÔÕÐ ÂÅÚ ÐÁÒÏÌÑ ËÏ ×ÓÅÍ ËÏÎÓÏÌÑÍ. íÙ ÄÅÌÁÅÍ ÔÁË, ÐÏÔÏÍÕ ÞÔÏ ÎÁ ÜÔÏÊ ÍÁÛÉÎÅ ÎÅÔ ÕÞ£ÔÎÙÈ ÚÁÐÉÓÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, É ÏÎÁ ÂÅÚÏÐÁÓÎÏ ÉÚÏÌÉÒÏ×ÁÎÁ ÏÔ ×ÎÅÛÎÅÇÏ ÍÉÒÁ ÍÅÖÓÅÔÅ×ÙÍ ÜËÒÁÎÏÍ. óÔÒÏËÁ ÒÁÚÒÅÛÅÎÉÑ ÐÏÚ×ÏÌÑÅÔ ×ÓÅÍ ÎÁ ÜÔÏÊ ÍÁÛÉÎÅ ×ÎÕÔÒÉ ÎÁÛÅÊ ÏÒÇÁÎÉÚÁÃÉÉ ÉÍÅÔØ ÄÏÓÔÕÐ Ë ËÏÎÓÏÌØÎÏÍÕ ÓÅÒ×ÅÒÕ, ÅÓÌÉ ÏÎ ÓÏÏÂÝÉÔ Ó×ÏÊ ÐÁÒÏÌØ, ËÏÔÏÒÙÊ ÚÁÐÉÓÁÎ × ÆÁÊÌÅ conserver.passwd (ÏÂÒÁÔÉÔÅÓØ Ë ÓÌÅÄÕÀÝÅÍÕ ÒÁÚÄÅÌÕ). úÁÄÁÎÉÅ ÐÁÒÏÌÅÊ ÄÌÑ conserver æÁÊÌ conserver.passwd ÓÏÄÅÒÖÉÔ ÚÁÛÉÆÒÏ×ÁÎÎÕÀ ×ÅÒÓÉÀ ÐÁÒÏÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. æÁÊÌ ÏÐÉÓÁÎ ÎÁ ÓÐÒÁ×ÏÞÎÏÊ ÓÔÒÁÎÉÃÅ conserver.cf(5). åÄÉÎÓÔ×ÅÎÎÏÊ ÈÉÔÒÏÓÔØÀ Ñ×ÌÑÅÔÓÑ ÚÁÐÏÌÎÅÎÉÅ ÆÁÊÌÁ ÚÁÛÉÆÒÏ×ÁÎÎÙÍÉ ÐÁÒÏÌÑÍÉ. ÷Ï &os; ÎÅÔ ÅÄÉÎÏÇÏ ÓÐÏÓÏÂÁ ÇÅÎÅÒÁÃÉÉ ÚÁÛÉÆÒÏ×ÁÎÎÙÈ ÐÁÒÏÌÅÊ ÄÌÑ ×ËÌÀÞÅÎÉÑ × ÄÒÕÇÏÊ ÆÁÊÌ (ÏÄÎÁËÏ ÓÍÏÔÒÉÔÅ ÎÉÖÅ). ôÁË ÞÔÏ Ñ ÎÁÓËÏÒÏ ÓÏÚÄÁÌ ÈÁËÅÒÓËÉÊ perl-ÓËÒÉÐÔ ÄÌÑ ÜÔÏÇÏ: @rands = (); foreach (0..4) { push(@rands, rand 64); } $salt = join '', ('.', '/', 0..9, 'A'..'Z', 'a'..'z')[@rands]; $salt = '$1$' . $salt . '$'; print 'Enter password: '; `stty -echo`; $cleartext = <>; `stty echo`; chop($cleartext); print crypt($cleartext, $salt), "\n"; ïÎ ÉÓÐÏÌØÚÕÅÔ ÐÁÒÏÌÉ &os; Ó MD5-ÛÉÆÒÏ×ÁÎÉÅÍ. úÁÐÕÓË ÓËÒÉÐÔÁ ÎÁ ÄÒÕÇÉÈ ×ÁÒÉÁÎÔÁÈ &unix; ÉÌÉ ×Ï &os; Ó ÛÉÆÒÏ×ÁÎÉÅÍ ÐÁÒÏÌÅÊ DES, ÓËÏÒÅÅ ×ÓÅÇÏ, ÐÏÔÒÅÂÕÅÔ ÄÒÕÇÏÊ ÂÁÚÙ ÛÉÆÒÏ×ÁÎÉÑ. îÅÄÁ×ÎÏ &a.kris.email; ÐÏËÁÚÁÌ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÄÏÓÔÉÞØ ÔÏÇÏ ÖÅ ÜÆÆÅËÔÁ ÐÒÉ ÐÏÍÏÝÉ ËÏÍÁÎÄÙ openssl passwd: &prompt.user; openssl passwd -1 Password: password $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/ úÁÐÕÓË <application>conserver</application> ×Ï ×ÒÅÍÑ ÚÁÇÒÕÚËÉ ÓÉÓÔÅÍÙ óÕÝÅÓÔ×ÕÀÔ Ä×Á ÓÐÏÓÏÂÁ ÜÔÏ ÓÄÅÌÁÔØ. ÷Ï-ÐÅÒ×ÙÈ, ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓËÁÔØ conserver ÐÒÉ ÐÏÍÏÝÉ init, ×ËÌÀÞÉ× ÓÔÒÏÞËÕ × /etc/ttys, ÐÏÄÏÂÎÕÀ ÓÌÅÄÕÀÝÅÊ: cuaE0 "/usr/local/sbin/conserver" unknown on insecure úÄÅÓØ ÅÓÔØ Ä×Á ÐÒÅÉÍÕÝÅÓÔ×Á: init ÐÅÒÅÚÁÐÕÓÔÉÔ ÇÌÁ×ÎÙÊ ËÏÎÓÏÌØÎÙÊ ÓÅÒ×ÅÒ, ÅÓÌÉ ÐÏ ËÁËÏÊ-ÔÏ ÐÒÉÞÉÎÅ ÏÎ Á×ÁÒÉÊÎÏ ÚÁ×ÅÒÛÉÔ Ó×ÏÀ ÒÁÂÏÔÕ (ÎÏ ÍÙ ÐÏËÁ ÐÏÄÏÂÎÙÈ ÓÌÕÞÁÅ× ÎÅ ÎÁÂÌÀÄÁÌÉ), É ÏÎ ÏÂÅÓÐÅÞÉ×ÁÅÔ ÔÏ, ÞÔÏ ÓÔÁÎÄÁÒÔÎÁÑ ×ÙÄÁÞÁ ÐÒÏÃÅÓÓÁ conserver ÂÕÄÅÔ ÎÁÐÒÁ×ÌÅÎÁ ÎÁ ÕËÁÚÁÎÎÙÊ tty (× ÜÔÏÍ ÓÌÕÞÁÅ cuaE0). üÔÏ ÐÏÌÅÚÎÏ, ÐÏÔÏÍÕ ÞÔÏ ×Ù ÍÏÖÅÔÅ ÐÏÄËÌÀÞÉÔØ ÔÅÒÍÉÎÁÌ Ë ÐÏÒÔÕ, Á ÐÒÏÇÒÁÍÍÁ conserver ×ÙÄÁÓÔ ×ÓÀ ËÏÎÓÏÌØÎÕÀ ×ÙÄÁÞÕ, ÎÅ ÐÏÐÁ×ÛÕÀ ÐÏÄËÌÀÞÅÎÎÏÍÕ ËÏÎÓÏÌØÎÏÍÕ ËÌÉÅÎÔÕ. ôÁËÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÐÏÌÅÚÎÏ × ËÁÞÅÓÔ×Å ÉÎÓÔÒÕÍÅÎÔÁ ÍÏÎÉÔÏÒÉÎÇÁ ÏÂÝÅÇÏ ÈÁÒÁËÔÅÒÁ, ÞÔÏÂÙ ÓÍÏÔÒÅÔØ, ÞÔÏ ÐÒÏÉÓÈÏÄÉÔ. íÙ ÓÄÅÌÁÌÉ ÔÁËÏÊ ÔÅÒÍÉÎÁÌ × ËÏÍÐØÀÔÅÒÎÏÍ ÚÁÌÅ ×ÉÄÉÍÙÍ ÉÚ ÏÓÎÏ×ÎÏÇÏ ÏÆÉÓÁ. üÔÏ ÏÞÅÎØ ÕÄÏÂÎÁÑ ×ÏÚÍÏÖÎÏÓÔØ. íÉÎÕÓÏÍ ÚÁÐÕÓËÁ conserver ÉÚ ÆÁÊÌÁ ttys Ñ×ÌÑÅÔÓÑ ÎÅ×ÏÚÍÏÖÎÏÓÔØ ÅÇÏ ÚÁÐÕÓËÁ × ÒÅÖÉÍÅ ÄÁÅÍÏÎÁ (ÌÉÂÏ &man.init.8; ÂÕÄÅÔ ÐÏÓÔÏÑÎÎÏ ÅÇÏ ÐÅÒÅÚÁÐÕÓËÁÔØ). üÔÏ ÚÎÁÞÉÔ, ÞÔÏ conserver ÎÅ ÂÕÄÅÔ ÚÁÐÉÓÙ×ÁÔØ PID-ÆÁÊÌ, ÞÔÏ ÕÓÌÏÖÎÑÅÔ ÓÍÅÎÕ ÖÕÒÎÁÌØÎÙÈ ÆÁÊÌÏ×. ôÁËÉÍ ÏÂÒÁÚÏÍ, ÍÙ ÚÁÐÕÓËÁÅÍ conserver ÉÚ rc.d-ÓËÒÉÐÔÁ. åÓÌÉ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÌÉ conserver ËÁË ÐÏÒÔ, ÔÏ × ËÁÔÁÌÏÇÅ /usr/local/etc/rc.d ÂÕÄÅÔ ÕÓÔÁÎÏ×ÌÅÎ ÆÁÊÌ conserver.sh.sample. óËÏÐÉÒÕÊÔÅ É/ÉÌÉ ÐÅÒÅÉÍÅÎÕÊÔÅ ÅÇÏ × conserver.sh ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÚÁÓÔÁ×ÉÔØ conserver ÚÁÐÕÓËÁÔØÓÑ × ÍÏÍÅÎÔ ÚÁÇÒÕÚËÉ ÓÉÓÔÅÍÙ. îÁ ÓÁÍÏÍ ÄÅÌÅ ÍÙ ÉÓÐÏÌØÚÕÅÍ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÕÀ ×ÅÒÓÉÀ ÜÔÏÇÏ ÓËÒÉÐÔÁ, ËÏÔÏÒÁÑ ÔÁËÖÅ ÐÏÄËÌÀÞÁÅÔ conserver Ë ÔÅÒÍÉÎÁÌÕ ÐÏÓÒÅÄÓÔ×ÏÍ tty-ÕÓÔÒÏÊÓÔ×Á, ÔÁË ÞÔÏ ÍÙ ÍÏÖÅÍ ÏÔÓÌÅÖÉ×ÁÔØ ÎÅÚÁÍÅÞÅÎÎÕÀ ËÏÎÓÏÌØÎÕÀ ×ÙÄÁÞÕ. îÁÛ ÓËÒÉÐÔ conserver.sh ×ÙÇÌÑÄÉÔ ÐÒÉÍÅÒÎÏ ÔÁË: #!/bin/sh # # Startup for conserver # PATH=/usr/bin:/usr/local/bin case "$1" in 'start') TTY=/dev/cuaE7 conserver -d > $TTY # get NL->CR+NL mapping so msgs look right stty < /dev/cuaE7 opost onlcr echo -n ' conserver' ;; 'stop') kill `cat /var/run/conserver.pid` && echo -n ' conserver' ;; *) echo "Usage: $0 { start | stop }" ;; esac exit 0 ïÔÍÅÔØÔÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÕÓÔÒÏÊÓÔ×Á cuaE0 É ÎÅÏÂÈÏÄÉÍÏÓÔØ ÚÁÄÁÎÉÑ tty-ÒÅÖÉÍÏ× ÄÌÑ ÐÒÁ×ÉÌØÎÏÊ ÏÂÒÁÂÏÔËÉ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÅÊ NL-<CR). ïÂÒÅÚÁÎÉÅ ÖÕÒÎÁÌØÎÙÈ ÆÁÊÌÏ× ÷Ï &os; ÉÍÅÅÔÓÑ ÐÒÏÇÒÁÍÍÁ ÐÏÄ ÎÁÚ×ÁÎÉÅÍ newsyslog, ËÏÔÏÒÁÑ ÂÕÄÅÔ ÏÂÓÌÕÖÉ×ÁÔØ ÕÓÅÞÅÎÉÅ ÖÕÒÎÁÌØÎÏÇÏ ÆÁÊÌÁ × Á×ÔÏÍÁÔÉÞÅÓËÏÍ ÒÅÖÉÍÅ. ðÒÏÓÔÏ ÄÏÂÁ×ØÔÅ ÎÅËÏÔÏÒÙÅ ÓÔÒÏËÉ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ /etc/newsyslog.conf ÄÌÑ ÖÕÒÎÁÌÏ× ËÏÎÓÏÌÅÊ: # # The log files from conserver /var/log/consoles/gallows 644 10 1000 * Z /var/run/conserver.pid /var/log/consoles/kanga 644 10 1000 * Z /var/run/conserver.pid /var/log/consoles/roo 644 10 1000 * Z /var/run/conserver.pid úÄÅÓØ ÐÒÏÇÒÁÍÍÅ newsyslog (ËÏÔÏÒÁÑ ×ÙÐÏÌÎÑÅÔÓÑ ÐÏ ÔÁÊÍÅÒÕ ÏÄÉÎ ÒÁÚ × ËÁÖÄÙÊ ÞÁÓ) ÕËÁÚÙ×ÁÅÔÓÑ, ÞÔÏ ÆÁÊÌÙ ÐÒÏÔÏËÏÌÏ× ÒÁÂÏÔÙ ËÏÎÓÏÌÅÊ ÄÏÌÖÎÙ ÁÒÈÉ×ÉÒÏ×ÁÔØÓÑ É ÓÖÉÍÁÔØÓÑ, ËÁË ÔÏÌØËÏ ÏÎÉ ÄÏÓÔÉÇÎÕÔ ÏÂߣÍÁ × 1 íÂÁÊÔ, ÞÔÏ ÍÙ ÄÏÌÖÎÙ ÈÒÁÎÉÔØ 10 ÔÁËÉÈ ÖÕÒÎÁÌÏ×, É ÞÔÏ ÄÌÑ ÐÏÄÁÞÉ ÓÉÇÎÁÌÁ SIGHUP ×Ù ÉÓÐÏÌØÚÕÅÔÅ PID, ÚÁÐÉÓÁÎÎÙÊ × ÆÁÊÌÅ conserver.pid. üÔÏ ÇÌÁ×ÎÙÊ ÓÅÒ×ÅÒ, É ÏÎ ÂÕÄÅÔ ÐÅÒÅÄÁ×ÁÔØ ÓÉÇÎÁÌ ×ÓÅÍ ÄÏÞÅÒÎÉÍ ÐÒÏÃÅÓÓÁÍ. äÁ, ÏÎ ÂÕÄÅÔ ÐÏÓÙÌÁÔØ ÓÉÇÎÁÌ HUP ×ÓÅÍ ËÌÉÅÎÔÁÍ, ËÁË ÔÏÌØËÏ ÐÏÎÁÄÏÂÉÔÓÑ ÏÂÎÏ×ÉÔØ ÅÄÉÎÓÔ×ÅÎÎÙÊ ÆÁÊÌ ÖÕÒÎÁÌÁ, ÎÏ ÜÔÏ ÄÏÓÔÁÔÏÞÎÏ Ä£ÛÅ×Ï. äÌÑ ×ÙÑÓÎÅÎÉÑ ×ÓÅÈ ÐÏÄÒÏÂÎÏÓÔÅÊ ÏÂÒÁÔÉÔÅÓØ Ë &man.newsyslog.8;. ðÏÄËÌÀÞÅÎÉÅ ËÁÂÅÌÅÊ üÔÏ ×ÓÅÇÄÁ Ñ×ÌÑÅÔÓÑ ÓÁÍÏÊ ÓÌÏÖÎÏÊ ÞÁÓÔØÀ ÔÁËÏÇÏ ÒÏÄÁ ÐÒÏÂÌÅÍ. äÌÑ ÐÏÓÔÒÏÅÎÉÑ Õ ÎÁÓ ÉÍÅÌÏÓØ ÔÏÌØËÏ ÏËÏÌÏ ÄÅÓÑÔËÁ ËÁÂÅÌÅÊ/ÏËÏÎÞÁÎÉÊ Ë ÎÉÍ, É ÅÝ£ ÎÁÂÏÒ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÉÎÓÔÒÕÍÅÎÔÏ× É ÏÂÏÒÕÄÏ×ÁÎÉÑ, ÔÁË ÞÔÏ ÍÙ ÓÄÅÌÁÌÉ ×Ó£ ÓÁÍÉ. ïÄÎÁËÏ ÅÓÌÉ ×Ù Ë ÜÔÏÍÕ ÎÅ ÇÏÔÏ×Ù, ÌÉÂÏ ×ÁÍ ÎÕÖÎÏ ÓÄÅÌÁÔØ ÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï ËÁÂÅÌÅÊ, ÔÏ ×ÁÍ ÍÏÖÎÏ ÐÒÉÏÂÒÅÓÔÉ ÉÈ ÎÁ ÚÁËÁÚ. ðÏÓÍÏÔÒÉÔÅ ÓÐÒÁ×ÏÞÎÉËÉ ÆÉÒÍ, ÔÁÍ ÎÁÊÄ£ÔÓÑ ÎÁ ÕÄÉ×ÌÅÎÉÅ ÍÎÏÇÏ ÍÅÓÔ, ÇÄÅ ÓÄÅÌÁÀÔ ×Ó£ ÎÕÖÎÏÅ! ðÒÉÏÂÒÅÔÅÎÉÅ ËÁÂÅÌÅÊ, ÓÄÅÌÁÎÎÙÈ ÎÁ ÚÁËÁÚ, ÜÔÏ ÈÏÒÏÛÏ, É ×Ù ÐÏÌÕÞÉÔÅ ÂÏÌÅÅ ÐÒÏÆÅÓÓÉÏÎÁÌØÎÙÊ ÒÅÚÕÌØÔÁÔ, ÏÄÎÁËÏ ÜÔÏ ÍÏÖÅÔ ÂÙÔØ ÄÏÒÏÇÏ×ÁÔÏ. ë ÐÒÉÍÅÒÕ, ÎÁÂÏÒÙ ÐÅÒÅÈÏÄÎÉËÏ× RJ-45 × DB-25, ÏÐÉÓÙ×ÁÅÍÙÅ ÎÉÖÅ, ÓÔÏÑÔ ÏËÏÌÏ $10 ËÁÖÄÙÊ; ËÁÂÅÌÉ ÎÁ ÚÁËÁÚ ÏÂÏÊÄÕÔÓÑ ÐÒÉÍÅÒÎÏ × Ä×Á ÒÁÚÁ ÄÏÒÏÖÅ (É ÂÕÄÕÔ ÄÏÓÔÁ×ÌÅÎÙ ÞÅÒÅÚ ÎÅÓËÏÌØËÏ ÎÅÄÅÌØ). ðÏÄÏÂÎÙÍ ÖÅ ÏÂÒÁÚÏÍ ÉÚÇÏÔÏ×ÌÅÎÉÅ ÐÅÒÅÈÏÄÎÉËÁ RJ-45 × RJ-45 ÏÂÏÊÄ£ÔÓÑ ÄÏÓÔÁÔÏÞÎÏ Ä£ÛÅ×Ï (ÓËÁÖÅÍ, ÐÏ $5 ËÁÖÄÙÊ), ÎÏ ÚÁÊÍ£Ô ÍÎÏÇÏ ×ÒÅÍÅÎÉ. úÁËÁÚÎÏÅ ÇÎÅÚÄÏ RJ-45 Ó ÐÅÒÅÈÏÄÎÉËÏÍ RJ-45 ÓÔÏÉÔ ÏËÏÌÏ $25 ËÁÖÄÏÅ. ÷Ï ×ÓÅÈ ÓÌÕÞÁÑÈ × ÏÆÉÓÅ É ËÏÍÐØÀÔÅÒÎÏÍ ÚÁÄÅ ÍÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ËÁÂÅÌØ ÔÉÐÁ RJ-45 Cat-V. óÀÄÁ ×ËÌÀÞÁÅÔÓÑ ÐÒÏÂÒÏÓ ÍÏÎÔÁÖÎÙÈ ËÁÂÅÌÅÊ ÍÅÖÄÕ ÓÔÏÊËÁÍÉ × ËÏÍÐØÀÔÅÒÎÏÍ ÚÁÌÅ. äÌÑ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ÓÏÅÄÉÎÅÎÉÊ ÍÙ ÉÓÐÏÌØÚÕÅÍ ÐÏÄËÌÀÞÁÅÍÙÅ ÓÏÅÄÉÎÉÔÅÌÉ, Õ ËÏÔÏÒÙÈ ÎÁ ÚÁÄÎÅÊ ÓÔÅÎËÅ ÅÓÔØ ÇΣÚÄÁ RJ-45. üÔÏ ÐÏÚ×ÏÌÑÅÔ ÎÁÍ ÐÒÉ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ÏÒÇÁÎÉÚÏ×Ù×ÁÔØ ÓÏÅÄÉÎÅÎÉÑ RJ-45–DB-25. ëÏÔÏÒÏÅ ÔÁËÖÅ ÕÄÏÂÎÏ, ÐÏÔÏÍÕ ÞÔÏ ÅÓÔØ ÍÎÏÖÅÓÔ×Ï ÎÅÐÒÁ×ÉÌØÎÙÈ ÓÐÏÓÏÂÏ× ÏÒÇÁÎÉÚÏ×ÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÅ ÓÏÅÄÉÎÅÎÉÑ ÎÁ ×ÉÌËÅ RJ-45. ôÁË ÞÔÏ ÐÒÉ ÐÒÏÂÒÏÓÅ ËÁÂÅÌÅÊ ÎÕÖÎÏ ÏÞÅÎØ ÏÓÔÏÒÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÁ×ÉÌØÎÏÅ ÓÏÏÔ×ÅÔÓÔ×ÉÅ. ã×ÅÔÏ×ÁÑ ÒÁÚÍÅÔËÁ RJ-45 ëÁÂÅÌÉ É ×ÉÌËÉ RJ-45 ÉÍÅÀÔ 8 ËÏÎÔÁËÔÏ×/ÐÒÏ×ÏÄÎÉËÏ×. ïÎÉ ÉÓÐÏÌØÚÕÀÔÓÑ ËÁË 4 ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÐÁÒÙ. éÍÅÅÔÓÑ ÎÅÓËÏÌØËÏ ÓÏÇÌÁÛÅÎÉÊ Ï ÔÏÍ, ËÁË ÐÁÒÙ ÓÏÏÔ×ÅÔÓÔ×ÕÀÔ ËÏÎÔÁËÔÁÍ, ÏÄÎÁËÏ × 100baseT ÉÓÐÏÌØÚÕÅÔÓÑ ÓÁÍÙÊ ÒÁÓÐÒÏÓÔÒÁΣÎÎÙÊ (ÉÚ×ÅÓÔÎÙÊ ËÁË EIA 586B). éÍÅÀÔÓÑ ÔÒÉ ÒÁÓÐÒÏÓÔÒÁΣÎÎÙÈ ÓÏÇÌÁÛÅÎÉÑ ÐÏ Ã×ÅÔÏ×ÏÍÕ ÏÂÏÚÎÁÞÅÎÉÀ ÄÌÑ ÏÔÄÅÌØÎÙÈ ÐÒÏ×ÏÄÎÉËÏ× × ËÁÂÅÌÑÈ RJ-45. ÷ÏÔ ÏÎÉ: <!-- XXX: äÏÂÁ×ÉÔØ ÚÁÇÏÌÏ×ÏË ÄÌÑ ÜÔÏÊ ÔÁÂÌÉÃÙ --> ëÏÎÔÁËÔ óÈÅÍÁ 1 óÈÅÍÁ 2 (EIA 568B) óÈÅÍÁ 3 (EIA 568A) ðÁÒÁ 1 óÉÎÉÊ âÅÌÙÊ+úÅÌ£ÎÙÊ âÅÌÙÊ+ïÒÁÎÖÅ×ÙÊ 2+ 2 ïÒÁÎÖÅ×ÙÊ úÅÌ£ÎÙÊ ïÒÁÎÖÅ×ÙÊ 2- 3 þ£ÒÎÙÊ âÅÌÙÊ+ïÒÁÎÖÅ×ÙÊ âÅÌÙÊ+úÅÌ£ÎÙÊ 3+ 4 ëÒÁÓÎÙÊ óÉÎÉÊ óÉÎÉÊ 1+ 5 úÅÌ£ÎÙÊ âÅÌÙÊ+óÉÎÉÊ âÅÌÙÊ+óÉÎÉÊ 1- 6 ö£ÌÔÙÊ ïÒÁÎÖÅ×ÙÊ úÅÌ£ÎÙÊ 3- 7 ëÏÒÉÞÎÅ×ÙÊ âÅÌÙÊ+ëÏÒÉÞÎÅ×ÙÊ âÅÌÙÊ+ëÏÒÉÞÎÅ×ÙÊ 4+ 8 âÅÌÙÊ ÉÌÉ óÅÒÙÊ ëÏÒÉÞÎÅ×ÙÊ ëÏÒÉÞÎÅ×ÙÊ 4-
úÁÍÅÔÉÍ, ÞÔÏ ÓÔÁÎÄÁÒÔÙ EIA 468A and EIA 568B ÏÔÌÉÞÁÀÔÓÑ ÔÏÌØËÏ Ã×ÅÔÏÍ 2 É 3 ÐÁÒÙ. ðÏÄÒÏÂÎÏÓÔÉ ÍÏÖÎÏ ÐÒÏÞÉÔÁÔØ ÎÁ ÓÁÊÔÅ ÔÅÈÎÉÞÅÓËÏÊ ÐÏÄÄÅÒÖËÉ Cabletron. ëÏÎÔÁËÔÙ ÒÁÚßÅÍÁ RJ-45 ÎÕÍÅÒÕÀÔÓÑ Ó 1 ÄÏ 8. ðÅÒ×ÙÊ ËÏÎÔÁËÔ ÒÁÓÐÏÌÏÖÅÎ ÓÌÅ×Á, ÅÓÌÉ ÄÅÒÖÁÔØ ÏÂÖÁÔÙÊ ËÁÂÅÌØ ÒÁÚßÅÍÏÍ ××ÅÒÈ É ÚÁÝÅÌËÏÊ ÏÔ ÓÅÂÑ. ÷ ÒÏÚÅÔËÅ RJ-45, ÒÁÓÐÏÌÏÖÅÎÎÏÊ ÚÁÝÅÌËÏÊ ××ÅÒÈ, ËÏÎÔÁËÔ 1 ÒÁÓÐÏÌÏÖÅÎ ÓÐÒÁ×Á. ÷ÏÔ ÉÌÌÀÓÔÒÁÃÉÑ (ÂÅÓÓÔÙÄÎÏ ÓÔÑÎÕÔÁÑ Ó ÓÁÊÔÁ Cabletron), ÐÏËÁÚÙ×ÁÀÝÁÑ ×ÓÅ ÜÔÏ: ÷ ÎÁÛÅÍ ÓÌÕÞÁÅ ÍÙ ÉÍÅÌÉ ÄÅÌÏ Ó ÞÅÔÙÒØÍÑ ×ÉÄÁÍÉ ÏÂÏÒÕÄÏ×ÁÎÉÑ: óÅÒ×ÅÒÁ Sun ëÏÎÓÏÌØ ÓÅÒ×ÅÒÁ Sun ÒÁÂÏÔÁÅÔ × ÒÅÖÉÍÅ DTE (Ô.Å. ÐÏÓÙÌÁÅÔ ÄÁÎÎÙÅ ÐÏ ÌÉÎÉÉ TxD, ÐÒÉÎÉÍÁÅÔ ÄÁÎÎÙÅ ÐÏ RxD É ÁËÔÉ×ÉÒÕÅÔ ÓÉÇÎÁÌ DTR) Ó ÒÁÚßÅÍÏÍ DB-25 "ÍÁÍÁ". äÌÑ ËÏÎÓÏÌØÎÏÇÏ ÓÅÒ×ÅÒÁ ÎÁ ÂÁÚÅ Stallion ÎÁÍ ÐÏÔÒÅÂÏ×ÁÌÉÓØ ÐÅÒÅÈÏÄÎÉËÉ, ÒÁÂÏÔÁÀÝÉÅ ËÁË DCE É ÏÂÌÁÄÁÀÝÉÅ ÒÁÚßÅÍÏÍ DB-25 "ÐÁÐÁ" (Ô.Å. ÒÁÂÏÔÁÀÝÉÅ ÏÄÎÏ×ÒÅÍÅÎÎÏ ËÁË ÎÕÌØ-ÍÏÄÅÍ É ËÁË ÐÅÒÅÈÏÄÎÉË RJ-45—DB-25. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ÒÁÚÂÏÒÎÙÅ ÐÅÒÅÈÏÄÎÉËÉ, ÓÏÄÅÒÖÁÝÉÅ ÒÏÚÅÔËÕ RJ-45, 8 ËÏÒÏÔËÉÈ ÐÒÏ×ÏÄÏ×, ÚÁËÁÎÞÉ×ÁÀÝÉÈÓÑ ËÏÎÔÁËÔÁÍÉ DB-25, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÐÒÏÉÚ×ÏÌØÎÏ ËÏÍÍÕÔÉÒÏ×ÁÔØÓÑ × ËÏÒÐÕÓ ÒÁÚßÅÍÁ DB-25. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ÎÅÓËÏÌØËÏ ÓÈÅÍ ÓÏÅÄÉÎÅÎÉÑ, × ÞÁÓÔÎÏÓÔÉ, MOD-TAP part no. 06-9888-999-00 É FA730 series ÏÔ ËÏÍÐÁÎÉÉ Black Box. ëÏÎÔÁËÔÙ ÐÅÒÅÈÏÄÎÉËÏ×, ËÏÔÏÒÙÅ ÐÏÐÁÌÉÓØ ÎÁÍ, ÂÙÌÉ ÍÁÒËÉÒÏ×ÁÎÙ ÔÁË (ËÏÎÔÁËÔÙ Ó 1 ÐÏ 8): óÉÎÉÊ, ïÒÁÎÖÅ×ÙÊ, þÅÒÎÙÊ, ëÒÁÓÎÙÊ, úÅÌÅÎÙÊ, öÅÌÔÙÊ, ëÏÒÉÞÎÅ×ÙÊ, âÅÌÙÊ (ÐÒÉ ×ÚÇÌÑÄÅ ÓÏ ÓÔÏÒÏÎÙ ÒÏÚÅÔËÉ RJ-45, ÚÁÝÅÌËÁ Ó×ÅÒÈÕ, ËÏÎÔÁËÔ 1 ÓÐÒÁ×Á). ïÎÉ ÂÙÌÉ ÓËÏÍÍÕÔÉÒÏ×ÁÎÙ Ó ÒÁÚßÅÍÏÍ DB-25 ×ÏÔ ÔÁË: <!-- XXX: Add a title here --> ëÏÎÔÁËÔ RJ-45 Stallion ã×ÅÔ óÉÇÎÁÌ ëÏÎÔÁËÔ ÒÁÚßÅÍÁ DB-25 "ÐÁÐÁ" Sun óÉÇÎÁÌ RS232 1 óÉÎÉÊ DCD 20 DTR 2 ïÒÁÎÖÅ×ÙÊ RTS 5 CTS 3 þÅÒÎÙÊ úÁÚÅÍÌÅÎÉÅ 1 úÁÚÅÍÌÅÎÉÅ 4 ëÒÁÓÎÙÊ TxD 3 RxD 5 úÅÌÅÎÙÊ RxD 2 TxD 6 öÅÌÔÙÊ óÉÇÎÁÌØÎÙÊ ÎÏÌØ 7 óÉÇÎÁÌØÎÙÊ ÎÏÌØ 7 ëÏÒÉÞÎÅ×ÙÊ CTS 4 RTS 8 âÅÌÙÊ RTS 8 DCD
äÌÑ ×ÁÛÉÈ ËÁÂÅÌÅÊ É ÐÅÒÅÈÏÄÎÉËÏ× Ã×ÅÔÁ ÍÏÇÕÔ ÏÔÌÉÞÁÔØÓÑ. îÁÐÒÉÍÅÒ, 8 ÐÒÏ×ÏÄ ÍÏÖÅÔ ÂÙÔØ ÓÅÒÏÇÏ, Á ÎÅ ÂÅÌÏÇÏ Ã×ÅÔÁ. îÅ ÚÁÂÕÄØÔÅ ÞÅÔËÏ ÐÏÍÅÔÉÔØ ÐÅÒÅÈÏÄÎÉË, ÔÁË ÞÔÏÂÙ ÐÏÍÅÔËÁ ÎÅ ÓÔÅÒÌÁÓØ É ÎÅ ÏÔ×ÁÌÉÌÁÓØ ÓÏ ×ÒÅÍÅÎÅÍ! íÁÒÛÒÕÔÉÚÁÔÏÒÙ Cisco 16xx/26xx/36xx ñ ÐÏÌÁÇÁÀ, ÞÔÏ ×ÓÅ ÐÒÏÄÕËÔÙ Cisco, ÉÓÐÏÌØÚÕÀÝÉÅ ÒÁÚßÅÍÙ RJ-45 ÄÌÑ ËÏÎÓÏÌÉ É ÒÁÂÏÔÁÀÝÉÅ ÐÏÄ ÕÐÒÁ×ÌÅÎÉÅÍ &ios;, ÔÒÅÂÕÀÔ ÏÄÉÎÁËÏ×ÙÈ ËÁÂÅÌÅÊ, ÎÏ ÌÕÞÛÅ ÂÕÄÅÔ ÄÏÐÏÌÎÉÔÅÌØÎÏ ÐÒÏ×ÅÒÉÔØ. íÙ ÒÁÂÏÔÁÌÉ ÔÏÌØËÏ Ó ÍÁÒÛÒÕÔÉÚÁÔÏÒÁÍÉ ÓÅÒÉÊ 1600, 2600 É 3600. é Stallion, É Cisco 2600 ÉÓÐÏÌØÚÕÀÔ ÒÁÚßÅÍÙ RJ-45, ÎÏ ÏÎÉ, ÒÁÚÕÍÅÅÔÓÑ, ÎÅ ÓÏ×ÍÅÓÔÉÍÙ, ÐÏÜÔÏÍÕ ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÓÐÅÃÉÁÌØÎÏ ÏÂÖÁÔÙÊ (É ÐÏÄËÌÀÞÅÎÎÙÊ × ÐÒÁ×ÉÌØÎÏÊ ÏÒÉÅÎÔÁÃÉÉ!) ËÁÂÅÌØ RJ-45-RJ-45. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ÓÔÁÎÄÁÒÔÎÙÅ ÐÒÏ×ÏÄÁ RJ45 ÏÔ ÍÁÒÛÒÕÔÉÚÁÔÏÒÏ× ÄÏ ÐÁÔÞ-ÐÁÎÅÌÅÊ É ÓÐÅÃÉÁÌØÎÏ ÐÏÄÇÏÔÏ×ÌÅÎÎÙÅ ÏÔ ÐÁÔÞ-ÐÁÎÅÌÉ ÄÏ ÒÁÚßÅÍÏ× ËÁÒÔÙ Stallion. ðÁÒÁ ÓÐÅÃÉÁÌØÎÙÈ ËÁÂÅÌÅÊ Stallion-Cisco ÂÙÌÁ ÓÄÅÌÁÎÁ ÐÕÔÅÍ ÒÁÚÒÅÚÁÎÉÑ ÐÏÐÏÌÁÍ ÓÔÁÎÄÁÒÔÎÏÇÏ Ä×ÕÈÍÅÔÒÏ×ÏÇÏ ÐÁÔÞ-ËÏÒÄÁ É ÎÁÂÉ×ÁÎÉÑ ÒÁÚßÅÍÏ× RJ-45 ÎÁ ÐÏÌÕÞÉ×ÛÉÅÓÑ Ó×ÏÂÏÄÎÙÅ ËÏÎÃÙ. éÚÎÁÞÁÌØÎÙÊ ÒÁÚßÅÍ ÐÒÅÄÎÁÚÎÁÞÁÅÔÓÑ ÄÌÑ ÓÔÏÒÏÎÙ ÍÁÒÛÒÕÔÉÚÁÔÏÒÁ Cisco, ÏÂÖÁÔÙÊ ÄÌÑ Stallion. ã×ÅÔÁ ÐÒÏ×ÏÄÏ× (ËÁË É ÐÒÅÖÄÅ, ÄÅÒÖÁ ËÁÂÅÌØ ÒÁÚßÅÍÏÍ ××ÅÒÈ É ÚÁÝÅÌËÏÊ ÏÔ ÓÅÂÑ, ÓÌÅ×Á ÎÁÐÒÁ×Ï) × ÎÁÛÅÍ ÓÌÕÞÁÅ ÂÙÌÉ ÔÁËÉÍÉ: ÂÅÌÏ-ÚÅÌÅÎÙÊ, ÚÅÌÅÎÙÊ, ÂÅÌÏ-ÏÒÁÎÖÅ×ÙÊ, ÓÉÎÉÊ, ÂÅÌÏ-ÓÉÎÉÊ, ÏÒÁÎÖÅ×ÙÊ, ÂÅÌÏ-ËÏÒÉÞÎÅ×ÙÊ, ËÏÒÉÞÎÅ×ÙÊ. äÌÑ ÓÔÏÒÏÎÙ Stallion ÓÌÅÄÏ×ÁÌÏ ÏÂÒÅÚÁÔØ ËÏÒÉÞÎÅ×ÕÀ É ÚÅÌÅÎÕÀ ÐÁÒÙ. úÁÔÅÍ, × ÕÖÅ ÏÐÉÓÁÎÎÏÊ ÒÁÓÓÔÁÎÏ×ËÅ, ÏÓÔÁ×ÛÉÅÓÑ ÐÒÏ×ÏÄÁ ËÏÍÍÕÔÉÒÏ×ÁÌÉÓØ ÔÁË: ÐÕÓÔÏ, ÐÕÓÔÏ, ÓÉÎÉÊ, ÏÒÁÎÖÅ×ÙÊ, ÂÅÌÏ-ÏÒÁÎÖÅ×ÙÊ, ÂÅÌÏ-ÓÉÎÉÊ, ÐÕÓÔÏ, ÐÕÓÔÏ, ËÁË ÐÏËÁÚÁÎÏ ÎÉÖÅ: <!-- XXX: add title for this table --> ëÏÎÔÁËÔ RJ-45 Cisco ã×ÅÔ óÉÇÎÁÌ Cisco ëÏÎÔÁËÔ RJ-45 Stallion óÉÇÎÁÌ Stallion 1 ÂÅÌÏ-ÚÅÌÅÎÙÊ RTS N/C   2 ÚÅÌÅÎÙÊ DTR N/C   3 ÂÅÌÏ-ÏÒÁÎÖÅ×ÙÊ TxD 5 RxD 4 ÓÉÎÉÊ Gnd 3 Gnd 5 ÓÉÎÉÊ Gnd 6 Gnd 6 ÏÒÁÎÖÅ×ÙÊ RxD 4 TxD 7 ÂÅÌÏ-ËÏÒÉÞÎÅ×ÙÊ DSR N/C   8 ËÏÒÉÞÎÅ×ÙÊ CTS N/C  
÷ÎÏ×Ø ÏÔÍÅÔÉÍ, ÞÔÏ Ã×ÅÔÁ ×ÁÛÉÈ ËÁÂÅÌÅÊ É ÐÅÒÅÈÏÄÎÉËÏ× ÍÏÇÕÔ ÏÔÌÉÞÁÔØÓÑ. áËËÕÒÁÔÎÏ ÐÏÍÅÔØÔÅ ËÁÖÄÙÊ ËÏÎÅà ËÁÂÅÌÑ É ÔÝÁÔÅÌØÎÏ ÐÒÏÔÅÓÔÉÒÕÊÔÅ ÅÇÏ. ôÅÓÔÉÒÏ×ÁÎÉÅ ÍÏÖÅÔ ÓÔÁÔØ ÐÏ-ÎÁÓÔÏÑÝÅÍÕ ÓÌÏÖÎÙÍ, ÐÏÓËÏÌØËÕ ÅÇÏ ÎÅÌØÚÑ ÐÒÏÉÚ×ÅÓÔÉ ÐÒÉ ÐÏÍÏÝÉ ÓÔÁÎÄÁÒÔÎÏÇÏ RJ-45 ÔÅÓÔÅÒÁ! úÁÍÅÔÉÍ ÅÝÅ ÒÁÚ: ÕÂÅÄÉÔÅÓØ, ÞÔÏ ×Ù ÐÏÍÅÔÉÌÉ ÎÏ×ÙÊ ËÁÂÅÌØ ÔÁË, ÞÔÏÂÙ ÅÇÏ ÂÙÌÏ ÌÅÇËÏ ÓÒÁÚÕ ÏÐÏÚÎÁÔØ ËÁË ÓÐÅÃÉÁÌØÎÙÊ É ÎÅÌØÚÑ ÂÙÌÏ ÂÙ ÐÅÒÅÐÕÔÁÔØ Ó ÏÂÙÞÎÙÍ ÐÁÔÞ-ËÏÒÄÏÍ. îÅÓËÏÌØËÏ ÓÏ×ÅÔÏ× ÏÔ èØÀ éÒ×ÉÎÁ (Hugh Irvine): äÅÌÁÊÔÅ ÉÈ ÉÚ ËÁÂÅÌÑ ÄÒÕÇÏÇÏ Ã×ÅÔÁ ìÕÞÛÉÊ ÓÐÏÓÏ ÍÁÒËÉÒÏ×ËÉ ËÁÂÅÌÑ, ËÏÔÏÒÙÊ ÍÎÅ ×ÓÔÒÅÞÁÌÓÑ: ÚÁÐÁÑÔØ ÎÁÐÅÞÁÔÁÎÎÕÀ ÜÔÉËÅÔËÕ ÐÏÄ ÐÒÏÚÒÁÞÎÙÊ ÔÅÒÍÏÕÓÁÄÏÞÎÙÊ ËÅÍÂÒÉË ÎÁ ËÏÎÅà ËÁÂÅÌÑ ÐÅÒÅÄ ÒÁÚÄÅÌËÏÊ ÒÁÚßÅÍÁ íÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÍÁÒËÅÒÙ ÔÉÐÁ Panduit, ÐÒÉËÒÅÐÌÑÅÍÙÅ Ë ËÁÂÅÌÀ ÓÔÑÖËÁÍÉ, ÎÏ ÎÁ ÎÉÈ ÓÏ ×ÒÅÍÅÎÅÍ ×ÙÃ×ÅÔÁÀÔ ÞÅÒÎÉÌÁ. ëÏÍÍÕÔÁÔÏÒÙ Cisco &catalyst; ëÁË ÎÉ ÓÔÒÁÎÎÏ, ÒÁÓÐÏÌÏÖÅÎÉÅ ÓÉÇÎÁÌÏ× ÎÁ ËÏÎÔÁËÔÁÈ ËÏÎÓÏÌØÎÏÇÏ ÐÏÒÔÁ ËÏÍÍÕÔÁÔÏÒÏ× &catalyst; ÉÎÏÇÄÁ ÏÔÌÉÞÁÅÔÓÑ ÏÔ ÉÓÐÏÌØÚÕÅÍÏÇÏ × ÍÁÒÛÒÕÔÉÚÁÔÏÒÁÈ Cisco. ñ ÐÏÌÁÇÁÀ, ÞÔÏ ËÁÒÔÁ ÓÉÇÎÁÌÏ× ÏÐÒÅÄÅÌÑÅÔÓÑ ÉÓÐÏÌØÚÕÅÍÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ. åÓÌÉ ËÏÍÍÕÔÁÔÏÒ ÒÁÂÏÔÁÅÔ ÐÏÄ ÕÐÒÁ×ÌÅÎÉÅÍ &ios;, ÐÒÉÍÅÎÑÅÔÓÑ ÒÁÓËÌÁÄËÁ, ÏÐÉÓÁÎÎÁÑ ×ÙÛÅ. ÷ ÐÒÏÔÉ×ÎÏÍ ÓÌÕÞÁÅ, ÓÌÅÄÕÅÔ ÐÒÉÍÅÎÉÔØ ÈÉÔÒÏÓÔØ. ë ÓÞÁÓÔØÀ, ×ÓÑ ÒÁÚÎÉÃÁ × ÒÁÓÐÏÌÏÖÅÎÉÉ ÓÉÇÎÁÌÏ× ÚÁËÌÀÞÁÅÔÓÑ × ÔÏÍ, ÞÔÏ ÏÄÎÁ ÉÚ ÒÁÓËÌÁÄÏË Ñ×ÌÑÅÔÓÑ ÚÅÒËÁÌØÎÙÍ ÏÔÒÁÖÅÎÉÅÍ ÄÒÕÇÏÊ. åÝÅ ÒÁÄÏÓÔÎÅÅ ÔÏ, ÞÔÏ × ËÏÍÐÌÅËÔÅ Ó ÏÂÏÒÕÄÏ×ÁÎÉÅÍ Cisco (ËÁË Ó ËÏÍÍÕÔÁÔÏÒÁÍÉ &catalyst;, ÔÁË É Ó 2600) ÐÏÓÔÁ×ÌÑÅÔÓÑ ÓÐÅÃÉÁÌØÎÙÊ ÐÅÒÅ×ÅÒÎÕÔÙÊ (rollover) ËÁÂÅÌØ; ÏÎ-ÔÏ ÎÁÍ É ÎÕÖÅÎ. íÙ ÉÓÐÏÌØÚÏ×ÁÌÉ ÐÅÒÅ×ÅÒÎÕÔÙÊ ËÁÂÅÌØ ÄÌÑ Ó×ÑÚÉ ËÏÎÓÏÌØÎÏÇÏ ÐÏÒÔÁ ËÏÍÍÕÔÁÔÏÒÏ× &catalyst; É ÐÁÔÞ-ÐÁÎÅÌÉ, Á ÚÁÔÅÍ ÏÐÉÓÁÎÎÙÊ ×ÙÛÅ ÄÌÑ Cisco 2600 ÓÐÅÃÉÁÌØÎÙÊ ËÁÂÅÌØ ÏÔ ÐÁÔÞ-ÐÁÎÅÌÉ ÄÏ ËÁÒÔÙ Stallion. ÷ÓÅ ÐÒÅËÒÁÓÎÏ ÒÁÂÏÔÁÌÏ. ðÅÒÅ×ÅÒÎÕÔÙÊ ËÁÂÅÌØ ÉÍÅÅÔ ÎÁ ÏÂÏÉÈ ËÏÎÃÁÈ ÒÁÚßÅÍÙ RJ-45 É ÐÒÅÄÎÁÚÎÁÞÅÎ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ×ÍÅÓÔÅ Ó ÐÅÒÅÈÏÄÎÉËÁÍÉ RJ-45 - DB-25 É RJ-45 - DB-9 (ÔÁËÖÅ ÐÏÓÔÁ×ÌÑÅÍÙÍÉ × ËÏÍÐÌÅËÔÅ; ÎÅÒÁÚÂÏÒÎÙÍÉ) ÄÌÑ ÐÒÉÓÏÅÄÉÎÅÎÉÑ Ë ËÏÎÓÏÌÉ. ÷ ÎÁÛÅÍ ÓÌÕÞÁÅ ËÁÂÅÌØ ÂÙÌ ÐÌÏÓËÉÍ, ÄÌÉÎÏÊ ÏËÏÌÏ 2 Í, ÇÏÌÕÂÏÇÏ ÉÌÉ ÞÅÒÎÏÇÏ Ã×ÅÔÁ. ðÏÐÙÔËÉ ÉÓÐÏÌØÚÏ×ÁÔØ ÅÇÏ ËÁË ÏÂÙÞÎÙÊ 100-íÂÉÔÎÙÊ ÓÅÔÅ×ÏÊ ËÁÂÅÌØ ÏËÏÎÞÁÔÓÑ ÎÅÕÄÁÞÅÊ! ïÐÒÅÄÅÌÉÔØ ÔÁËÏÊ ËÁÂÅÌØ ÌÅÇËÏ, ÅÓÌÉ ×ÚÑÔØ ÏÂÁ ÒÁÚßÅÍÁ (ËÁÂÅÌÅÍ ×ÎÉÚ, ÚÁÝÅÌËÏÊ ÏÔ ÓÅÂÑ) É ÓÒÁ×ÎÉÔØ Ã×ÅÔÁ ËÏÎÔÁËÔÏ×. òÁÚßÅÍÙ ÄÏÌÖÎÙ ×ÙÇÌÑÄÅÔØ ÚÅÒËÁÌØÎÏ; × ÎÁÛÅÍ ÓÌÕÞÁÅ ÜÔÏ ÂÙÌÉ ÓÅÒÙÊ-ÏÒÁÎÖÅ×ÙÊ-ÞÅÒÎÙÊ-ËÒÁÓÎÙÊ-ÚÅÌÅÎÙÊ-ÖÅÌÔÙÊ-ÓÉÎÉÊ-ËÏÒÉÞÎÅ×ÙÊ Ó ÏÄÎÏÊ ÓÔÏÒÏÎÙ, É ËÏÒÉÞÎÅ×ÙÊ-ÓÉÎÉÊ-ÖÅÌÔÙÊ-ÚÅÌÅÎÙÊ-ËÒÁÓÎÙÊ-ÞÅÒÎÙÊ-ÏÒÁÎÖÅ×ÙÊ-ÓÅÒÙÊ Ó ÄÒÕÇÏÊ. åÓÌÉ Õ ×ÁÓ ÎÅÔ ÐÏÄ ÒÕËÏÊ ÐÅÒÅ×ÅÒÎÕÔÏÇÏ ËÁÂÅÌÑ, ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ËÁÂÅÌØ ÄÌÑ ÍÁÒÛÒÕÔÉÚÁÔÏÒÁ 26xx, ÐÅÒÅ×ÅÒÎÕ× ÅÇÏ: ÉÓÈÏÄÎÙÊ ÒÁÚßÅÍ Ó 8 ËÏÎÔÁËÔÁÍÉ × Stallion, ÎÏ×ÙÊ Ó 4 ËÏÎÔÁËÔÁÍÉ × ËÏÍÍÕÔÁÔÏÒ &catalyst;. óÅÒ×ÅÒÁ &os; (ÉÌÉ ÌÀÂÙÅ ÄÒÕÇÉÅ ÓÉÓÔÅÍÙ ÎÁ ÂÁÚÅ ðë &i386;, ÉÓÐÏÌØÚÕÀÝÉÅ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÕÀ ËÏÎÓÏÌØ) íÙ ÉÓÐÏÌØÚÕÅÍ &os; 4 ÎÁ ÐÁÒÅ ðë ÁÒÈÉÔÅËÔÕÒÙ &i386; ÄÌÑ ÒÁÚÌÉÞÎÙÈ ÐÅÒÉÆÅÒÉÊÎÙÈ ÎÕÖÄ. &os; ÏÂÙÞÎÏ ÉÓÐÏÌØÚÕÅÔ ÜËÒÁÎ É ËÌÁ×ÉÁÔÕÒÕ × ËÁÞÅÓÔ×Å ËÏÎÓÏÌÉ, ÎÏ ÍÏÖÅÔ ÂÙÔØ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎÁ × ÒÅÖÉÍ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÊ ËÏÎÓÏÌÉ (ËÁË ÐÒÁ×ÉÌÏ, ÎÁ ÐÅÒ×ÙÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÏÒÔ, ÉÚ×ÅÓÔÎÙÊ ËÁË COM1 × DOS/&windows; ÉÌÉ ttyd0 × &unix;). ðÏÄËÌÀÞÅÎÉÅ ÔÁËÉÈ ËÏÎÓÏÌÅÊ ÚÁ×ÉÓÉÔ ÏÔ ÉÓÐÏÌØÚÕÅÍÏÇÏ ÏÂÏÒÕÄÏ×ÁÎÉÑ. óÔÁÒÙÅ ðë ÉÓÐÏÌØÚÏ×ÁÌÉ ÒÁÚßÅÍ DB-25 "ÍÁÍÁ", É ÄÌÑ ÎÉÈ ÐÏÄÈÏÄÉÔ ÏÐÉÓÁÎÎÙÊ ×ÙÛÅ ×ÁÒÉÁÎÔ ÄÌÑ ÓÅÒ×ÅÒÁ Sun. äÌÑ ÓÏ×ÒÅÍÅÎÎÙÈ ðë Ó ÒÁÚßÅÍÁÍÉ DB-9 "ÐÁÐÁ" ÓÕÝÅÓÔ×ÕÀÔ Ä×Á ×ÁÒÉÁÎÔÁ: ÉÓÐÏÌØÚÏ×ÁÔØ ÐÅÒÅÈÏÄÎÉË DB9 - DB-25 (ÎÅ ÒÅËÏÍÅÎÄÕÅÔÓÑ, ÐÏÓËÏÌØËÕ ÓÏ ×ÒÅÍÅÎÅÍ ÔÁËÉÅ ÓÏÅÄÉÎÅÎÉÑ ÒÁÚÂÁÌÔÙ×ÁÀÔÓÑ É ×ÅÄÕÔ Ë ÎÅÐÒÅÄÓËÁÚÕÅÍÙÍ ÐÏÔÅÒÑÍ Ó×ÑÚÉ) ÉÌÉ ÓÏÂÒÁÔØ ËÁÂÅÌØ RJ-45 - DB-9: <!-- XXX: add title for this table --> ëÏÎÔÁËÔ RJ-45 Stallion ã×ÅÔ óÉÇÎÁÌ ëÏÎÔÁËÔ DB-9 "ÍÁÍÁ" óÉÇÎÁÌ RS232 1 óÉÎÉÊ DCD 4 DTR 2 ïÒÁÎÖÅ×ÙÊ RTS 8 CTS 3 þÅÒÎÙÊ úÁÝÉÔÎÁÑ ÚÅÍÌÑ N/C   4 ëÒÁÓÎÙÊ TxD 2 RxD 5 úÅÌÅÎÙÊ RxD 3 TxD 6 öÅÌÔÙÊ óÉÇÎÁÌØÎÙÊ ÎÏÌØ 5 óÉÇÎÁÌØÎÙÊ ÎÏÌØ 7 ëÏÒÉÞÎÅ×ÙÊ CTS 7 RTS 8 âÅÌÙÊ RTS 1 DCD
óÍ. ÔÁËÖÅ ÒÁÚÄÅÌ . ÷ ÎÅÍ ×Ù ÎÁÊÄÅÔÅ ÓÏ×ÅÔÙ ÐÏ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÀ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÊ ËÏÎÓÏÌÉ × &os;. ðÒÏ ÓÉÓÔÅÍÙ Sun É ÓÉÇÎÁÌ Break ÷ÓÑËÉÊ, ËÔÏ ÈÏÔØ ÒÁÚ ×ÙËÌÀÞÁÌ ÔÅÒÍÉÎÁÌ, ÉÓÐÏÌØÚÕÅÍÙÊ × ËÁÞÅÓÔ×Å ËÏÎÓÏÌÉ ÄÌÑ ÓÅÒ×ÅÒÁ Sun, ÚÎÁÅÔ, ÞÔÏ ÐÒÏÉÓÈÏÄÉÔ × ÒÅÚÕÌØÔÁÔÅ É ÐÏÞÅÍÕ ÜÔÏ Ñ×ÌÑÅÔÓÑ ÐÒÏÂÌÅÍÏÊ. ïÂÏÒÕÄÏ×ÁÎÉÅ Sun ÓÞÉÔÁÅÔ ÓÉÇÎÁÌ BREAK ÎÁ ËÏÎÓÏÌÉ ËÏÍÁÎÄÏÊ ÏÓÔÁÎÏ×ÉÔØ ÓÉÓÔÅÍÕ É ×ÅÒÎÕÔØÓÑ × ÍÏÎÉÔÏÒ ÚÁÇÒÕÚÞÉËÁ. óÉÇÎÁÌ BREAK — ÓÐÅÃÉÁÌØÎÙÊ ÓÒÏÞÎÙÊ ÓÉÇÎÁÌ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÇÏ ÐÏÒÔÁ, ÚÁËÌÀÞÁÀÝÉÊÓÑ × ÁËÔÉ×ÉÚÁÃÉÉ (ÕÓÔÁÎÏ×ËÉ × ÕÒÏ×ÅÎØ ÎÉÖÅ -5 ÷) ÓÉÇÎÁÌÁ TxD ÎÁ ×ÒÅÍÑ ÂÏÌØÛÅÅ ÞÅÍ ÔÒÅÂÕÅÔÓÑ ÎÁ ÐÅÒÅÄÁÞÕ Ä×ÕÈ ÓÉÍ×ÏÌÏ× (ÏËÏÌÏ 2 ÍÓ ÄÌÑ ÓËÏÒÏÓÔÉ 9600 bps). ë ÓÏÖÁÌÅÎÉÀ, ÜÔÏÔ ÓÉÇÎÁÌ ÞÁÓÔÏ ×ÏÚÎÉËÁÅÔ ÐÒÉ ×ËÌÀÞÅÎÉÉ ÉÌÉ ×ÙËÌÀÞÅÎÉÉ ËÏÍÍÕÎÉËÁÃÉÏÎÎÏÇÏ ÏÂÏÒÕÄÏ×ÁÎÉÑ. ÷ ÞÁÓÔÎÏÓÔÉ, ËÁÒÔÙ Stallion ÔÁËÖÅ ÇÅÎÅÒÉÒÕÀÔ BREAK ÐÒÉ ÏÔËÌÀÞÅÎÉÉ ÐÉÔÁÎÉÑ ËÏÍÐØÀÔÅÒÁ. åÓÌÉ ÎÅ ÐÒÅÄÐÒÉÎÉÍÁÔØ ÓÐÅÃÉÁÌØÎÙÈ ÄÅÊÓÔ×ÉÊ, ÜÔÏ ÍÏÖÅÔ ÐÒÉ×ÅÓÔÉ Ë ÏÓÔÁÎÏ×ËÅ ×ÓÅÈ ÓÅÒ×ÅÒÏ× Sun, ÐÏÄËÌÀÞÅÎÎÙÈ Ë ËÏÎÓÏÌØÎÏÍÕ ÓÅÒ×ÅÒÕ, ÐÒÉ ÅÇÏ ÏÔËÌÀÞÅÎÉÉ (ÐÒÉ ÏÔËÁÚÅ ÂÌÏËÁ ÐÉÔÁÎÉÑ, ÉÌÉ × ÒÅÚÕÌØÔÁÔÅ ÎÅÏÓÔÏÒÏÖÎÙÈ ÄÅÊÓÔ×ÉÊ ÏÐÅÒÁÔÏÒÁ, ÉÌÉ ÐÏ ÅÝÅ ËÁËÉÍ-ÌÉÂÏ ÐÒÉÞÉÎÁÍ). ñÓÎÏ, ÞÔÏ ÔÁËÁÑ ÓÉÔÕÁÃÉÑ ÎÅÐÒÉÅÍÌÅÍÁ. ë ÓÞÁÓÔØÀ, Õ ËÏÍÐÁÎÉÉ Sun ÅÓÔØ ÎÁÂÏÒ ÉÓÐÒÁ×ÌÅÎÉÊ. äÌÑ ïó &solaris; ×ÅÒÓÉÉ 2.6 É ÂÏÌÅÅ ÐÏÚÄÎÉÈ, ÐÒÉ ÐÏÍÏÝÉ ËÏÍÁÎÄÙ kbd(1) ÍÏÖÎÏ ÚÁÐÒÅÔÉÔØ ÐÅÒÅÈÏÄ × ÍÏÎÉÔÏÒ ÚÁÇÒÕÚÞÉËÁ ÐÏ ÓÉÇÎÁÌÕ BREAK. üÔÏ ÕÖÅ ÎÅÐÌÏÈÏ ÄÌÑ ÎÁÞÁÌÁ, ÎÏ ÌÉÛÁÅÔ ×ÁÓ ÛÁÎÓÏ× ×ÏÓÓÔÁÎÏ×ÉÔØ ÐÏ×ÉÓÛÕÀ ÍÁÛÉÎÕ, ×ÅÒÎÕ× ÅÅ × ÚÁÇÒÕÚÞÉË. îÁÞÉÎÁÑ Ó &solaris; ×ÅÒÓÉÉ 8, ËÏÍÁÎÄÕ kbd ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ ÕÓÔÁÎÏ×ËÉ ÁÌØÔÅÒÎÁÔÉ×ÎÏÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ ÐÒÅÒÙ×ÁÎÉÑ: kbd -a alternate. ðÏÓÌÅ ÁËÔÉ×ÁÃÉÉ, ÄÌÑ ×ÏÚ×ÒÁÔÁ × ÍÏÎÉÔÏÒ ÚÁÇÒÕÚËÉ ÎÅÏÂÈÏÄÉÍÏ × ÔÅÞÅÎÉÅ 5 ÓÅËÕÎÄ ×ÙÄÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ: Return ~ CtrlB. üÔÁ ×ÏÚÍÏÖÎÏÓÔØ ÍÏÖÅÔ ÂÙÔØ ×ËÌÀÞÅÎÁ ÎÁ ÐÏÓÔÏÑÎÎÏÊ ÏÓÎÏ×Å ÐÕÔÅÍ ÒÅÄÁËÔÉÒÏ×ÁÎÉÑ ÆÁÊÌÁ /etc/default/kbd; ÐÏÄÒÏÂÎÅÅ ÓÍ. ÓÐÒÁ×ÏÞÎÕÀ ÓÔÒÁÎÉÃÕ kbd(1). ïÔÍÅÔÉÍ, ÞÔÏ ÁÌØÔÅÒÎÁÔÉ×ÎÁÑ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÁËÔÉ×ÉÒÕÅÔÓÑ ÐÏÓÌÅ ÐÅÒÅÈÏÄÁ ÑÄÒÁ × ÍÎÏÇÏÐÏÌØÚÏ×ÁÔÅÌØÓËÉÊ ÒÅÖÉÍ É ÏÂÒÁÂÏÔËÉ ÆÁÊÌÁ ÎÁÞÁÌØÎÙÈ ÕÓÔÁÎÏ×ÏË. ÷ ÐÅÒÉÏÄ ÎÁÞÁÌØÎÏÊ ÚÁÇÒÕÚËÉ (×ËÌÀÞÅÎÉÅ ÐÉÔÁÎÉÑ É × ÐÒÏÃÅÓÓÅ ÚÁÇÒÕÚËÉ ÑÄÒÁ) É × ÏÄÎÏÐÏÌØÚÏ×ÁÔÅÌØÓËÏÍ ÒÅÖÉÍÅ ÄÌÑ ×ÏÚ×ÒÁÔÁ × ÍÏÎÉÔÏÒ ÚÁÇÒÕÚËÉ ÎÕÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÉÇÎÁÌ BREAK. éÚ ËÏÎÓÏÌØÎÏÇÏ ËÌÉÅÎÔÁ ÅÇÏ ÍÏÖÎÏ ÁËÔÉ×ÉÒÏ×ÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØÀ Esc c l 1. åÓÌÉ Õ ×ÁÓ ÅÓÔØ ÓÅÒ×ÉÓÎÙÊ ËÏÎÔÒÁËÔ Ó ËÏÍÐÁÎÉÅÊ Sun, ×Ù ÍÏÖÅÔÅ ÓËÁÞÁÔØ ÐÁÔÞÉ, ÒÅÁÌÉÚÕÀÝÉÅ ÁÌØÔÅÒÎÁÔÉ×ÎÕÀ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÐÒÅÒÙ×ÁÎÉÑ, ÄÌÑ &solaris; ×ÅÒÓÉÊ 2.6 É 2.7. &solaris; 2.6 ÔÒÅÂÕÅÔ ÐÁÔÞÁ 105924-10 ÉÌÉ ×ÙÛÅ; &solaris; 2.7 — 107589-02 ÉÌÉ ×ÙÛÅ. íÙ ÐÒÉÍÅÎÉÌÉ ÜÔÏÔ ÐÁÔÞ ÎÁ ×ÓÅÈ ÎÁÛÉÈ ÓÅÒ×ÅÒÁÈ &solaris; 2.6 É ÄÏÂÁ×ÉÌÉ ÅÇÏ (×ÍÅÓÔÅ Ó ÕÓÔÁÎÏ×ËÏÊ ÄÌÑ ÆÁÊÌÁ /etc/default/kbd) × ÓÔÁÒÔÏ×ÕÀ ËÏÎÆÉÇÕÒÁÃÉÀ, ÔÁË ÞÔÏÂÙ ÌÀÂÏÊ ÎÏ×ÙÊ ÓÅÒ×ÅÒ Á×ÔÏÍÁÔÉÞÅÓËÉ ÂÙÌ ÐÒÁ×ÉÌØÎÏ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎ. îÁÛÉ ÔÅÓÔÙ ÐÏËÁÚÁÌÉ, ÞÔÏ ÎÉ ÍÁÒÛÒÕÔÉÚÁÔÏÒÙ Cisco 16xx, 26xx, ÎÉ ËÏÍÍÕÔÁÔÏÒÙ &catalyst; ÎÅ ÐÏÄ×ÅÒÖÅÎÙ ÐÒÏÂÌÅÍÅ ÓÉÇÎÁÌÁ BREAK, ×ÏÚÎÉËÁÀÝÅÇÏ ÐÒÉ ÐÏÔÅÒÅ ÐÉÔÁÎÉÑ ËÁÒÔÏÊ Stallion. ÷ ÎÁÓÔÏÑÝÅÅ ×ÒÅÍÑ ÍÁÒÛÒÕÔÉÚÁÔÏÒÙ É ËÏÍÍÕÔÁÔÏÒÙ Cisco ÒÅÁÇÉÒÕÀÔ ÎÁ ÓÉÇÎÁÌ BREAK ÔÏÌØËÏ × ÔÅÞÅÎÉÅ ÐÅÒ×ÙÈ 30 ÓÅËÕÎÄ ÐÏÓÌÅ ×ËÌÀÞÅÎÉÑ ÐÉÔÁÎÉÑ ÉÌÉ ÐÅÒÅÚÁÇÒÕÚËÉ. éÓÐÏÌØÚÏ×ÁÎÉÅ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÊ ËÏÎÓÏÌÉ × &os; ðÏÄÒÏÂÎÏ ÜÔÁ ÐÒÏÃÅÄÕÒÁ ÏÐÉÓÁÎÁ × ÏÔÄÅÌØÎÏÊ ÇÌÁ×Å òÕËÏ×ÏÄÓÔ×Á &os;. úÄÅÓØ ÍÙ ÐÒÉ×ÏÄÉÍ ËÒÁÔËÉÊ ÐÅÒÅÞÅÎØ. ðÒÏ×ÅÒØÔÅ ËÏÎÆÉÇÕÒÁÃÉÀ ÑÄÒÁ ðÒÏ×ÅÒØÔÅ, ÞÔÏ ÆÁÊÌ ËÏÎÆÉÇÕÒÁÃÉÉ ÑÄÒÁ ÓÏÄÅÒÖÉÔ flags 0x10 × ÓÔÒÏËÅ, ÏÐÉÓÙ×ÁÀÝÅÊ ÕÓÔÒÏÊÓÔ×Ï sio0. üÔÏÔ ÆÌÁÇ ÒÁÚÒÅÛÁÅÔ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÕÓÔÒÏÊÓÔ×Á (ÉÚ×ÅÓÔÎÏÇÏ ÔÁËÖÅ ËÁË COM1 × DOS/&windows; ÉÌÉ ËÁË /dev/ttyd0 × &os;) × ËÁÞÅÓÔ×Å ËÏÎÓÏÌÉ. æÌÁÇ ÕÓÔÁÎÏ×ÌÅÎ × ÏÂÏÉÈ ÐÒÉÍÅÒÁÈ ÓÔÁÎÄÁÒÔÎÏÊ ËÏÎÆÉÇÕÒÁÃÉÉ ÑÄÒÁ (GENERIC É LINT), ÔÁË ÞÔÏ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÏÎ ÕÓÔÁÎÏ×ÌÅÎ É × ×ÁÛÅÍ ÑÄÒÅ. óÏÚÄÁÊÔÅ ÆÁÊÌ <filename>/boot.conf</filename> file üÔÏÔ ÆÁÊÌ ÄÏÌÖÅÎ ÓÏÓÔÏÑÔØ ÉÚ ÏÄÎÏÊ ÓÔÒÏËÉ, ÓÏÄÅÒÖÁÝÅÊ ÔÏÌØËÏ -h (ÂÅÚ ËÁ×ÙÞÅË). üÔÏÔ ÆÌÁÇ ÕËÁÚÙ×ÁÅÔ ÚÁÇÒÕÚÏÞÎÙÍ ÂÌÏËÁÍ &os; ÐÅÒÅËÌÀÞÉÔØÓÑ ÎÁ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÕÀ ËÏÎÓÏÌØ. ïÔÒÅÄÁËÔÉÒÕÊÔÅ ÆÁÊÌ <filename>/etc/ttys</filename> îÅÏÂÈÏÄÉÍÙ ÓÌÅÄÕÀÝÉÅ ÉÚÍÅÎÅÎÉÑ: åÓÌÉ ×Ù ÎÅ ÓÏÂÉÒÁÅÔÅÓØ ÐÏÄËÌÀÞÁÔØ ËÌÁ×ÉÁÔÕÒÕ É ÍÏÎÉÔÏÒ Ë ÜÔÏÍÕ ÓÅÒ×ÅÒÕ, ÎÁÊÄÉÔÅ ×ÓÅ ÓÔÒÏËÉ ÄÌÑ ÕÓÔÒÏÊÓÔ× ttyv, ÔÁËÉÈ ËÁË ttyv1 "/usr/libexec/getty Pc" cons25 on secure úÁÍÅÎÉÔÅ on ÎÁ off. üÔÏ ÚÁÐÒÅÔÉÔ ÚÁÐÕÓË ÕÔÉÌÉÔ ÒÅÇÉÓÔÒÁÃÉÉ ÎÁ ÎÅÎÕÖÎÙÈ ÂÏÌÅÅ ×ÉÄÅÏ ËÏÎÓÏÌÑÈ. îÁÊÄÉÔÅ ÓÔÒÏËÕ, ÓÏÄÅÒÖÁÝÕÀ ttyd0. éÚÍÅÎÉÔÅ ÅÅ Ó ttyd0 "/usr/libexec/getty std.9600" dialup off secure ÎÁ ttyd0 "/usr/libexec/getty std.9600" vt100 on secure (ÚÁÍÅÎÉÔÅ vt100 ÎÁ ÔÉÐ ÔÅÒÍÉÎÁÌÁ ×ÁÛÅÊ ËÏÎÓÏÌÉ. èÏÒÏÛÉÍ ×ÙÂÏÒÏÍ ÍÏÖÅÔ ÂÙÔØ xterm). üÔÏ ÐÏÚ×ÏÌÉÔ ×ÁÍ ÚÁÒÅÇÉÓÔÒÉÒÏ×ÁÔØÓÑ ÎÁ ËÏÎÓÏÌÉ ÐÏÓÌÅ ÔÏÇÏ, ËÁË ÓÉÓÔÅÍÁ ÐÅÒÅÊÄÅÔ × ÍÎÏÇÏÐÏÌØÚÏ×ÁÔÅÌØÓËÉÊ ÒÅÖÉÍ. ðÅÒÅÚÁÇÒÕÚÉÔÅÓØ — É ×ÓÅ! óÏÏÂÒÁÖÅÎÉÑ ÂÅÚÏÐÁÓÎÏÓÔÉ ðÒÏÔÏËÏÌ "ËÌÉÅÎÔ-ÓÅÒ×ÅÒ" ÕÔÉÌÉÔÙ conserver ÔÒÅÂÕÅÔ ÏÔ ÐÏÌØÚÏ×ÁÔÅÌÑ ËÌÉÅÎÔÓËÏÊ ÕÔÉÌÉÔÙ console ××ÏÄÁ ÐÁÒÏÌÑ. üÔÏÔ ÐÁÒÏÌØ ÐÅÒÅÄÁÅÔÓÑ ÐÏ ÓÅÔÉ × ÏÔËÒÙÔÏÍ ×ÉÄÅ! ëÁË ÓÌÅÄÓÔ×ÉÅ, ÕÔÉÌÉÔÁ conserver ÎÅ ÏÓÏÂÅÎÎÏ ÐÒÉÇÏÄÎÁ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÎÅÂÅÚÏÐÁÓÎÙÈ ÓÅÔÑÈ (× ÔÏÍ ÞÉÓÌÅ × ÉÎÔÅÒÎÅÔ). éÓÐÏÌØÚÏ×ÁÎÉÅ ÕÎÉËÁÌØÎÙÈ ÐÁÒÏÌÅÊ ÄÌÑ conserver ÓÌÅÇËÁ ÓÍÑÇÞÁÅÔ ÐÒÏÂÌÅÍÕ, ÏÄÎÁËÏ ÌÀÂÏÊ, ËÔÏ ÓÐÏÓÏÂÅÎ ÐÒÏÓÌÕÛÁÔØ ÓÅÔÅ×ÏÊ ÔÒÁÆÉË ÍÅÖÄÕ ËÌÉÅÎÔÏÍ É ÓÅÒ×ÅÒÏÍ conserver, ÍÏÖÅÔ ÌÅÇËÏ ÐÏÌÕÞÉÔØ ËÏÎÓÏÌØÎÙÊ ÄÏÓÔÕÐ, Á Ó ËÏÎÓÏÌÉ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÐÒÅÒÙ×ÁÎÉÑ. äÌÑ ÕÄÁÌÅÎÎÏÊ ÒÁÂÏÔÙ ÉÓÐÏÌØÚÕÊÔÅ ËÁËÉÅ-ÌÉÂÏ ÚÁÝÉÝÅÎÎÙÅ ÐÒÏÔÏËÏÌÙ, ÔÁËÉÅ ËÁË SSH ÄÌÑ ÒÅÇÉÓÔÒÁÃÉÉ ÎÁ ËÏÎÓÏÌØÎÏÍ ÓÅÒ×ÅÒÅ É ÚÁÐÕÓËÁÊÔÅ ËÏÎÓÏÌØÎÙÊ ËÌÉÅÎÔ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÏÔÔÕÄÁ. òÁÚÌÉÞÎÙÅ ×ÅÒÓÉÉ Conserver ðÒÏÇÒÁÍÍÁ conserver ÒÁÓÓÌÏÉÌÁÓØ ÎÁ ÎÅÓËÏÌØËÏ ÎÅÚÁ×ÉÓÉÍÙÈ ×ÅÒÓÉÊ. óÁÊÔ, ÕÐÏÍÉÎÁÅÍÙÊ ÎÉÖÅ, ÓÕÄÑ ÐÏ ×ÓÅÍÕ, ÓÏÄÅÒÖÉÔ ÐÏÓÌÅÄÎÀÀ É ÎÁÉÂÏÌÅÅ ÐÏÌÎÕÀ ×ÅÒÓÉÀ ÉÚ ÄÏÓÔÕÐÎÙÈ. îÁ ÍÏÍÅÎÔ ÎÁÐÉÓÁÎÉÑ ÓÔÁÔØÉ (ÉÀÌØ 2004 Ç.) ÜÔÏ ×ÅÒÓÉÑ 8.1.9. óÁÊÔ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ âÒÁÊÁÎÏÍ óÔÜÎÓÅÌÌÏÍ (Bryan Stansell), bryan@conserver.com, ËÏÔÏÒÙÊ Ó×ÅÌ ×ÏÅÄÉÎÏ ÒÁÂÏÔÕ ÍÎÏÇÉÈ ÒÁÚÒÁÂÏÔÞÉËÏ× (ÐÅÒÅÞÉÓÌÅÎÙ ÎÁ ÅÇÏ ÓÁÊÔÅ). ëÏÌÌÅËÃÉÑ ÐÏÒÔÏ× &os; ÓÏÄÅÒÖÉÔ conserver ×ÅÒÓÉÉ 8.5 × ËÁÔÁÌÏÇÅ comms/conserver. óÕÄÑ ÐÏ ×ÓÅÍÕ, ÏÎ ÂÏÌÅÅ ÓÔÁÒÙÊ, É ÓÏÄÅÒÖÉÔ ÍÅÎØÛÅ ×ÏÚÍÏÖÎÏÓÔÅÊ, ÞÅÍ 8.1.9 (× ÞÁÓÔÎÏÓÔÉ, ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÔ ËÏÎÓÏÌÉ, ÓÏÅÄÉÎÅÎÎÙÅ Ó ÐÏÒÔÁÍÉ ÔÅÒÍÉÎÁÌØÎÙÈ ÓÅÒ×ÅÒÏ×, ÉÌÉ ÆÁÊÌ ÐÁÒÏÌÅÊ conserver.passwd), Á ÔÁËÖÅ ÎÁÐÉÓÁÎ ÄÏ×ÏÌØÎÏ Ó×ÏÅÏÂÒÁÚÎÏ (ÉÓÐÏÌØÚÕÑ ÐÒÅÐÒÏÃÅÓÓÏÒ ÄÌÑ ÇÅÎÅÒÁÃÉÉ ÉÓÈÏÄÎÏÇÏ ÔÅËÓÔÁ ÎÁ ÑÚÙËÅ C). ÷ÅÒÓÉÑ 8.5 ×ÅÄÅÔÓÑ ëÅ×ÉÎÏÍ âÒÁÕÎÓÄÏÒÆÏÍ (Kevin S. Braunsdorf) ksb+conserver@sa.fedex.com, × ÐÒÏÛÌÏÍ ÏÓÎÏ×ÎÙÍ Á×ÔÏÒÏÍ conserver; âÒÁÊÁÎ ÏÓÎÏ×Ù×ÁÌÓÑ ÎÁ ÅÇÏ ÒÁÚÒÁÂÏÔËÁÈ. ÷ÅÒÓÉÑ 8.5 ÐÏÄÄÅÒÖÉ×ÁÅÔ ÏÄÎÕ ×ÏÚÍÏÖÎÏÓÔØ, ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÍÕÀ 8.1.9: ÕÐÒÁ×ÌÅÎÉÅ ÐÉÔÁÎÉÅÍ ÕÄÁÌÅÎÎÙÈ ÍÁÛÉÎ ÞÅÒÅÚ ÓÐÅÃÉÁÌØÎÙÊ ËÏÎÔÒÏÌÌÅÒ, ÕÐÒÁ×ÌÑÅÍÙÊ ÐÏ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÍÕ ÐÏÒÔÕ. îÁÞÉÎÁÑ Ó ÄÅËÁÂÒÑ 2001 Ç., ×ÅÒÓÉÑ âÒÁÊÁÎÁ (× ÎÁÓÔÏÑÝÅÅ ×ÒÅÍÑ 8.1.9) ÐÒÉÓÕÔÓÔ×ÕÅÔ × ÄÅÒÅ×Å ÐÏÒÔÏ× × ËÁÔÁÌÏÇÅ comms/conserver-com. íÙ ÒÅËÏÍÅÎÄÕÅÍ ÉÓÐÏÌØÚÏ×ÁÔØ ÉÍÅÎÎÏ ÅÅ ËÁË ÂÏÌÅÅ ÐÏÄÈÏÄÑÝÕÀ ÄÌÑ ÐÏÓÔÒÏÅÎÉÑ ËÏÎÓÏÌØÎÏÇÏ ÓÅÒ×ÅÒÁ. óÓÙÌËÉ óÁÊÔ ÐÏÓÌÅÄÎÅÊ ×ÅÒÓÉÉ ÐÒÏÇÒÁÍÍÙ conserver. ftp://ftp.conserver.com/conserver/conserver-8.1.9.tar.gz áÒÈÉ× ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× ÄÌÑ ×ÅÒÓÉÉ 8.1.9 ÐÒÏÇÒÁÍÍÙ conserver. óÁÊÔ ËÏÍÐÁÎÉÉ Stallion Technologies. îÁÐÉÓÁÎÎÙÊ äÜ×ÉÄÏÍ èÁÒÒÉÓÏÍ (Davis Harris) íÁÌÙÊ ó×ÉÔÏË úÎÁÎÉÊ Ï ëÏÎÓÏÌÑÈ, ÓÏÄÅÒÖÁÝÉÊ ÍÁÓÓÕ ÐÏÌÅÚÎÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ËÏÎÓÏÌÑÈ É ×ÏÏÂÝÅ Ï ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÈ ÐÏÒÔÁÈ. âÏÌØÛÏÊ ó×ÉÔÏË úÎÁÎÉÊ Ï ëÏÎÓÏÌÑÈ ÓÏÄÅÒÖÉÔ ÅÝÅ ÂÏÌÅÅ ÐÏÄÒÏÂÎÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï ÓÏÅÄÉÎÅÎÉÉ ÏÄÎÉÈ ÕÓÔÒÏÊÓÔ× Ó ÄÒÕÇÉÍÉ. ï, ÜÔÉ óÔÁÎÄÁÒÔÙ! äÕÇ èØÀÄÖÅÓ (Doug Hughes) ÓÏÚÄÁÌ ÓÈÏÖÉÊ ËÏÎÓÏÌØÎÙÊ ÓÅÒ×ÅÒ ÎÁ ÏÓÎÏ×Å ÕÔÉÌÉÔÙ screen É ÓÔÁÒÏÊ ÍÁÛÉÎÙ ÐÏÄ ÕÐÒÁ×ÌÅÎÉÅÍ &sunos;. ëÏÍÐÁÎÉÑ Real Weasel ÐÒÏÉÚ×ÏÄÉÔ ×ÉÄÅÏËÁÒÔÙ ÄÌÑ ÛÉÎ ISA ÉÌÉ PCI, × ÒÅÁÌØÎÏÓÔÉ ÐÒÏÉÚ×ÏÄÑÝÉÅ ×Ù×ÏÄ × ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÏÒÔ. ïÎÉ ÍÏÇÕÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÄÌÑ ËÏÎÓÏÌÅÊ ðë × ÔÅÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍÁÈ, ËÏÔÏÒÙÅ ÎÅ ÍÏÇÕÔ ÂÙÔØ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎÙ × ÒÅÖÉÍ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÊ ËÏÎÓÏÌÉ ÄÏÓÔÁÔÏÞÎÏ ÒÁÎÏ × ÐÒÏÃÅÓÓÅ ÚÁÇÒÕÚËÉ. óÐÒÁ×ÏÞÎÙÅ ÓÔÒÁÎÉÃÙ console(8) conserver(8) conserver.cf(5) + +
diff --git a/ru_RU.KOI8-R/articles/contributing/article.xml b/ru_RU.KOI8-R/articles/contributing/article.xml index 4789111ac8..bbb07455ae 100644 --- a/ru_RU.KOI8-R/articles/contributing/article.xml +++ b/ru_RU.KOI8-R/articles/contributing/article.xml @@ -1,549 +1,551 @@
õÞÁÓÔÉÅ × ÐÒÏÅËÔÅ FreeBSD ÷ ÜÔÏÊ ÓÔÁÔØÅ ÏÐÉÓÁÎÙ ÒÁÚÌÉÞÎÙÅ ÓÐÏÓÏÂÙ, ËÏÔÏÒÙÍÉ ÏÔÄÅÌØÎÙÅ ÌÉÃÁ É ÏÒÇÁÎÉÚÁÃÉÊ ÍÏÇÕÔ ÐÒÉÎÑÔØ ÕÞÁÓÔÉÅ × ðÒÏÅËÔÅ FreeBSD. äÖÏÒÄÁÎ èÁÂÂÁÒÄ ôÅËÓÔ ÐÒÅÄÏÓÔÁ×ÉÌ &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ÕÞÁÓÔÉÅ éÔÁË, ×Ù ÈÏÔÉÔÅ ×ÎÅÓÔÉ Ó×ÏÊ ×ËÌÁÄ ×Ï FreeBSD? üÔÏ ×ÅÌÉËÏÌÅÐÎÏ! öÉÚÎÅÓÐÏÓÏÂÎÏÓÔØ FreeBSD ÏÓÎÏ×ÁÎÁ ÎÁ ÐÏÍÏÝÉ Å£ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. ÷ÁÛÁ ÐÏÍÏÝØ ÎÅ ÔÏÌØËÏ ÐÒÉÎÉÍÁÅÔÓÑ, ÏÎÁ ÖÉÚÎÅÎÎÏ ÎÅÏÂÈÏÄÉÍÁ ÄÌÑ ÐÒÏÄÏÌÖÅÎÉÑ ÒÏÓÔÁ FreeBSD. îÅÓÍÏÔÒÑ ÎÁ Õ×ÅÒÅÎÉÑ ÎÅËÏÔÏÒÙÈ ÌÀÄÅÊ, ×ÁÍ ÎÅ ÎÕÖÎÏ ÂÙÔØ ÇÅÎÉÁÌØÎÙÍ ÐÒÏÇÒÁÍÍÉÓÔÏÍ ÉÌÉ ÐÅÒÓÏÎÏÊ, ÌÉÞÎÏ Ó×ÑÚÁÎÎÏÊ Ó ÒÕËÏ×ÏÄÑÝÅÊ ÇÒÕÐÐÏÊ FreeBSD, ÞÔÏÂÙ ×ÁÛÁ ÐÏÍÏÝØ ÂÙÌÁ ÐÒÉÎÑÔÁ. FreeBSD ÒÁÚÒÁÂÁÔÙ×ÁÅÔ ÂÏÌØÛÏÅ É Õ×ÅÌÉÞÉ×ÁÀÝÅÅÓÑ ËÏÌÉÞÅÓÔ×Ï ÕÞÁÓÔÎÉËÏ× ÓÏ ×ÓÅÇÏ ÍÉÒÁ, ÓÁÍÏÇÏ ÒÁÚÎÏÇÏ ×ÏÚÒÁÓÔÁ É ÒÁÚÎÙÈ ÏÂÌÁÓÔÅÊ ÔÅÈÎÉÞÅÓËÏÊ ÜËÓÐÅÒÔÉÚÙ. òÁÂÏÔÙ, ËÏÔÏÒÕÀ ÎÅÏÂÈÏÄÉÍÏ ÓÄÅÌÁÔØ, ×ÓÅÇÄÁ ÂÏÌØÛÅ, ÞÅÍ ÒÁÚÒÁÂÏÔÞÉËÏ×, ÍÏÇÕÝÉÈ Å£ ×ÙÐÏÌÎÉÔØ, É ÄÏÐÏÌÎÉÔÅÌØÎÁÑ ÐÏÍÏÞØ ×ÓÅÇÄÁ ÐÒÉ×ÅÔÓÔ×ÕÅÔÓÑ. ðÒÏÅËÔ FreeBSD ÚÁÎÉÍÁÅÔÓÑ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÏÊ × ÃÅÌÏÍ, Á ÎÅ ÔÏÌØËÏ ÑÄÒÏÍ ÉÌÉ ÎÅÓËÏÌØËÉÍÉ ÏÔÄÅÌØÎÙÍÉ ÕÔÉÌÉÔÁÍÉ. ôÁËÉÍ ÏÂÒÁÚÏÍ, × ÎÁÛÅÍ TODO-ÓÐÉÓËÅ ÛÉÒÏËÉÊ ÓÐÅËÔÒ ÚÁÄÁÞ: ÏÔ ÄÏËÕÍÅÎÔÁÃÉÉ, ÂÅÔÁ-ÔÅÓÔÉÒÏ×ÁÎÉÑ É ÐÒÅÚÅÎÔÁÃÉÊ ÄÏ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ É ÓÐÅÃÉÆÉÞÅÓËÉÈ ÒÁÚÒÁÂÏÔÏË ÕÒÏ×ÎÑ ÑÄÒÁ. ìÀÄÉ ÌÀÂÏÇÏ ÕÒÏ×ÎÑ ÐÒÁËÔÉÞÅÓËÉ × ÌÀÂÏÊ ÏÂÌÁÓÔÉ ÏÐÒÅÄÅÌ£ÎÎÏ ÓÍÏÇÕÔ ÐÏÍÏÞØ ÐÒÏÅËÔÕ. ëÏÍÍÅÒÞÅÓËÉÅ ÓÔÒÕËÔÕÒÙ, Ó×ÑÚÁÎÎÙÅ Ó ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ FreeBSD, ÔÁËÖÅ ÐÒÉÇÌÁÛÁÀÔÓÑ Ë ÄÉÁÌÏÇÕ. îÕÖÎÙ ÌÉ ×ÁÍ ÏÓÏÂÙÅ ÒÁÓÛÉÒÅÎÉÑ, ÄÌÑ ÒÁÂÏÔÙ ×ÁÛÅÇÏ ÐÒÏÄÕËÔÁ? ÷Ù Õ×ÉÄÉÔÅ, ÞÔÏ ÍÙ ÏÔ×ÅÞÁÅÍ ÎÁ ×ÁÛÉ ÚÁÐÒÏÓÙ, ÅÓÌÉ ÏÎÉ ÎÅ ÓÌÉÛËÏÍ ÎÅÏÂÙÞÎÙ. ÷Ù ÒÁÂÏÔÁÅÔÅ ÎÁÄ ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ ÐÒÏÄÕËÔÁÍÉ? äÁÊÔÅ ÎÁÍ ÚÎÁÔØ! íÙ ÓÍÏÖÅÍ ÒÁÂÏÔÁÔØ ×ÍÅÓÔÅ ÎÁÄ ÎÅËÏÔÏÒÙÍÉ ÅÇÏ ÁÓÐÅËÔÁÍÉ. íÉÒ Ó×ÏÂÏÄÎÏÇÏ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ ÓÔÁ×ÉÔ ÐÏÄ ÓÏÍÎÅÎÉÅ ÍÎÏÇÉÅ ÓÕÝÅÓÔ×ÕÀÝÉÅ ÐÒÅÄÓÔÁ×ÌÅÎÉÑ Ï ÔÏÍ, ËÁË ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÅ ÒÁÚÒÁÂÁÔÙ×ÁÅÔÓÑ, ÐÒÏÄÁ£ÔÓÑ É ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ, É ÍÙ ÎÁÓÔÏÑÔÅÌØÎÏ ÐÒÏÓÉÍ ×ÁÓ ÐÏÓÍÏÔÒÅÔØ ÎÁ ÎÅÇÏ ÅÝ£ ÒÁÚ. þÔÏ ÎÕÖÎÏ ÷ ÓÌÅÄÕÀÝÅÍ ÐÅÒÅÞÎÅ ÐÒÅÄÓÔÁ×ÌÅÎÙ ÚÁÄÁÞÉ É ÐÏÄÐÒÏÅËÔÙ, Ñ×ÌÑÀÝÉÅÓÑ ÎÅËÏÔÏÒÙÍ ÏÔÒÁÖÅÎÉÅÍ ÒÁÚÌÉÞÎÙÈ ÓÐÉÓËÏ× TODO É ÚÁÐÒÏÓÏ× ÐÏÌØÚÏ×ÁÔÅÌÅÊ. ôÅËÕÝÉÅ ÚÁÄÁÞÉ ÎÅ ÄÌÑ ÐÒÏÇÒÁÍÍÉÓÔÏ× íÎÏÇÉÅ ÌÀÄÉ, Ó×ÑÚÁÎÎÙÅ Ó FreeBSD, ÎÅ Ñ×ÌÑÀÔÓÑ ÐÒÏÇÒÁÍÍÉÓÔÁÍÉ. ÷ ðÒÏÅËÔÅ ÕÞÁÓÔ×ÕÀÔ ÓÏÚÄÁÔÅÌÉ ÄÏËÕÍÅÎÔÁÃÉÉ, Web-ÄÉÚÁÊÎÅÒÙ É ÓÐÅÃÉÁÌÉÓÔÙ ÐÏ ÐÏÄÄÅÒÖËÅ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. ÷ÓÅ, ÞÔÏ ÉÍ ÎÕÖÎÏ ÄÌÑ ÕÞÁÓÔÉÑ, ÜÔÏ Ó×Ï£ ×ÒÅÍÑ É ÖÅÌÁÎÉÅ ÕÞÉÔØÓÑ. ðÅÒÉÏÄÉÞÅÓËÉ ÞÉÔÁÊÔÅ FAQ É òÕËÏ×ÏÄÓÔ×Ï. åÓÌÉ ÞÔÏ-ÔÏ ÏÐÉÓÁÎÏ ÐÌÏÈÏ, ÕÓÔÁÒÅÌÏ ÉÌÉ ÄÁÖÅ ÐÏÌÎÏÓÔØÀ ÎÅÐÒÁ×ÉÌØÎÏ, ÄÁÊÔÅ ÎÁÍ ÚÎÁÔØ. åÝ£ ÌÕÞÛÅ, ÅÓÌÉ ×Ù ÐÒÉÛÌ£ÔÅ ÎÁÍ ÉÓÐÒÁ×ÌÅÎÉÅ (×ÙÕÞÉÔØ Docbook ÎÅ ÔÁË ÓÌÏÖÎÏ, ÎÏ É ÐÒÏÔÉ× ÐÏÓÌÁÎÉÊ × ÆÏÒÍÁÔÅ ASCII ÎÉËÔÏ ×ÏÚÒÁÖÁÔØ ÎÅ ÂÕÄÅÔ). ðÏÍÏÇÉÔÅ ÐÅÒÅ×ÅÓÔÉ ÄÏËÕÍÅÎÔÁÃÉÀ FreeBSD ÎÁ ×ÁÛ ÒÏÄÎÏÊ ÑÚÙË. åÓÌÉ ÄÏËÕÍÅÎÔÁÃÉÑ ÎÁ ×ÁÛÅÍ ÑÚÙËÅ ÕÖÅ ÓÕÝÅÓÔ×ÕÅÔ, ×Ù ÍÏÖÅÔÅ ÐÏÍÏÞØ ÐÅÒÅ×ÅÓÔÉ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÄÏËÕÍÅÎÔÙ ÉÌÉ ÐÒÏ×ÅÒÉÔØ, ÎÅ ÕÓÔÁÒÅÌÉ ÌÉ ÐÅÒÅ×ÏÄÙ. ðÅÒ×ÙÍ ÄÅÌÏÍ ×ÚÇÌÑÎÉÔÅ ÎÁ FAQ ÐÏ ÐÅÒÅ×ÏÄÁÍ × õÞÅÂÎÉËÅ ÐÒÏÅËÔÁ ÄÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD. ÷ÁÓ ÎÅ ÐÒÉÚÙ×ÁÀÔ ÐÅÒÅ×ÅÓÔÉ ×ÓÅ ÄÏËÕÍÅÎÔÙ FreeBSD — ËÁË ÄÏÂÒÏ×ÏÌÅÃ, ×Ù ÍÏÖÅÔÅ ÄÅÌÁÔØ ÓÔÏÌØËÏ ÐÅÒÅ×ÏÄÏ×, ÓËÏÌØËÏ ÚÁÈÏÔÉÔÅ. åÓÌÉ ËÔÏ-ÔÏ ÎÁÞÁÌ ÐÅÒÅ×ÏÄ, ÄÒÕÇÉÅ ×ÓÅÇÄÁ ÐÒÉÓÏÅÄÉÎÑÔÓÑ. åÓÌÉ Õ ×ÁÓ ÅÓÔØ ×ÒÅÍÑ É ÖÅÌÁÎÉÅ ÐÅÒÅ×ÅÓÔÉ ÏÄÎÕ ÞÁÓÔØ ÄÏËÕÍÅÎÔÁÃÉÉ, ÐÏÖÁÌÕÊÓÔÁ, ÐÅÒÅ×ÅÄÉÔÅ ÉÎÓÔÒÕËÃÉÉ ÐÏ ÕÓÔÁÎÏ×ËÅ. ÷ÒÅÍÑ ÏÔ ×ÒÅÍÅÎÉ (ÉÌÉ ÄÁÖÅ ÒÅÇÕÌÑÒÎÏ) ÞÉÔÁÊÔÅ &a.questions; É &ng.misc;. ÷ÁÍ ÍÏÖÅÔ ÐÏÎÒÁ×ÉÔØÓÑ ÄÅÌÉÔØÓÑ Ó×ÏÉÍ ÏÐÙÔÏÍ É ÐÏÍÏÇÁÔØ ÌÀÄÑÍ ÒÅÛÁÔØ ÉÈ ÐÒÏÂÌÅÍÙ; ÉÎÏÇÄÁ ×Ù ÓÍÏÖÅÔÅ ÕÚÎÁÔØ ÄÌÑ ÓÅÂÑ ÞÔÏ-ÔÏ ÎÏ×ÏÅ! üÔÉ ÆÏÒÕÍÙ ÍÏÇÕÔ ÔÁËÖÅ ÓÔÁÔØ ÉÓÔÏÞÎÉËÏÍ ÉÄÅÊ, ÎÁÄ ËÏÔÏÒÙÍÉ ×ÁÍ ÓÔÏÉÔ ÐÏÒÁÂÏÔÁÔØ. ôÅËÕÝÉÅ ÚÁÄÁÞÉ ÄÌÑ ÐÒÏÇÒÁÍÍÉÓÔÏ× âÏÌØÛÉÎÓÔ×Ï ÚÁÄÁÞ, ÐÅÒÅÞÉÓÌÅÎÎÙÈ ÚÄÅÓØ, ÔÒÅÂÕÀÔ ÌÉÂÏ ÚÎÁÞÉÔÅÌØÎÙÈ ÚÁÔÒÁÔ ×ÒÅÍÅÎÉ, ÌÉÂÏ ÇÌÕÂÏËÉÈ ÚÎÁÎÉÊ ÑÄÒÁ FreeBSD, ÌÉÂÏ ÔÏÇÏ É ÄÒÕÇÏÇÏ. ïÄÎÁËÏ ÉÍÅÅÔÓÑ ÔÁËÖÅ ÍÎÏÇÏ ÐÏÌÅÚÎÙÈ ÚÁÄÁÞ, ËÏÔÏÒÙÅ ÐÏÄÏÊÄÕÔ ÄÌÑ ×ÏÓËÒÅÓÎÙÈ ÈÁËÅÒÏ×. åÓÌÉ ×Ù ÒÁÂÏÔÁÅÔÅ Ó FreeBSD-CURRENT É ÏÂÌÁÄÁÅÔÅ ÈÏÒÏÛÉÍ ÐÏÄËÌÀÞÅÎÉÅÍ Ë Internet, ÔÏ ÓÕÝÅÓÔ×ÕÅÔ ÍÁÛÉÎÁ current.FreeBSD.org, ËÏÔÏÒÁÑ ÓÔÒÏÉÔ ÐÏÌÎÙÊ ÒÅÌÉÚ ÅÖÅÄÎÅ×ÎÏ—ÓÅÊÞÁÓ É ×ÓÅÇÄÁ. ðÏÐÒÏÂÕÊÔÅ ÕÓÔÁÎÏ×ÉÔØ ÓÁÍÙÊ ÐÏÓÌÅÄÎÉÊ ÒÅÌÉÚ Ó ÜÔÏÊ ÍÁÛÉÎÙ É ÓÏÏÂÝÉÔÅ ÏÂÏ ×ÓÅÈ ÏÂÎÁÒÕÖÅÎÎÙÈ ÐÒÉ ÜÔÏÍ ÏÛÉÂËÁÈ. þÉÔÁÊÔÅ &a.bugs;. úÄÅÓØ ÍÏÖÅÔ ×ÓÔÒÅÔÉÔØÓÑ ÐÒÏÂÌÅÍÁ, ËÏÔÏÒÕÀ ×Ù ÓÍÏÖÅÔÅ ËÏÎÓÔÒÕËÔÉ×ÎÏ ÐÒÏËÏÍÍÅÎÔÉÒÏ×ÁÔØ ÉÌÉ ÐÁÔÞÉ, ËÏÔÏÒÙÅ ×Ù ÍÏÖÅÔÅ ÐÒÏÔÅÓÔÉÒÏ×ÁÔØ. ìÉÂÏ ×Ù ÍÏÖÅÔÅ ÄÁÖÅ ÐÏÐÙÔÁÔØÓÑ ÉÓÐÒÁ×ÉÔØ ËÁËÕÀ-ÔÏ ÐÒÏÂÌÅÍÕ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ. åÓÌÉ ×Ù ÚÎÁÅÔÅ Ï ÓÕÝÅÓÔ×Ï×ÁÎÉÉ ËÁËÉÈ-ÌÉÂÏ ÉÓÐÒÁ×ÌÅÎÉÊ ÏÛÉÂÏË, ÕÓÐÅÛÎÏ ÐÒÉÍÅΣÎÎÙÈ Ë -CURRENT, ÎÏ ÅÝ£ ÎÅ ÐÅÒÅÎÅÓ£ÎÎÙÈ × -STABLE ÐÏÓÌÅ ÄÏÓÔÁÔÏÞÎÏ ÂÏÌØÛÏÇÏ ÉÎÔÅÒ×ÁÌÁ ×ÒÅÍÅÎÉ (ÏÂÙÞÎÏ ÎÅÓËÏÌØËÏ ÎÅÄÅÌØ), ÎÁÐÒÁ×ØÔÅ ËÏÍÍÉÔÔÅÒÕ ×ÅÖÌÉ×ÏÅ ÎÁÐÏÍÉÎÁÎÉÅ. ðÅÒÅÎÏÓ ÓÔÏÒÏÎÎÅÇÏ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ × ËÁÔÁÌÏÇ src/contrib ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×. ðÒÏ×ÅÒËÁ ÁËÔÕÁÌØÎÏÓÔÉ ËÏÄÁ × ËÁÔÁÌÏÇÅ src/contrib. ðÏÓÔÒÏÅÎÉÅ ÉÚ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× (ÉÌÉ Å£ ÞÁÓÔÉ) Ó ×ËÌÀÞÅÎÉÅÍ ÒÅÖÉÍÁ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÐÒÅÄÕÐÒÅÖÄÅÎÉÊ, ÉÚÂÁ×ÌÅÎÉÅ ÏÔ ÎÉÈ. éÓÐÒÁ×ÌÅÎÉÅ ÐÒÅÄÕÐÒÅÖÄÅÎÉÊ ÏÔ ÐÏÒÔÏ×, ËÏÔÏÒÙÅ ÉÓÐÏÌØÚÕÀÔ ÎÅÄÏÐÕÓÔÉÍÙÅ ×ÙÚÏ×Ù ÔÉÐÁ gets() ÉÌÉ ×ËÌÀÞÁÀÔ ÆÁÊÌ ÏÂßÑ×ÌÅÎÉÊ malloc.h. åÓÌÉ ×Ù ÓÏÚÄÁ×ÁÌÉ ÐÏÒÔÙ É ×ÁÍ ÐÒÉÈÏÄÉÌÏÓØ ÄÅÌÁÔØ ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ &os; ÉÓÐÒÁ×ÌÅÎÉÑ, ÐÏÛÌÉÔÅ ×ÁÛÉ ÐÁÔÞÉ Á×ÔÏÒÁÍ ÏÒÉÇÉÎÁÌØÎÏÇÏ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ (ÜÔÏ ÕÐÒÏÓÔÉÔ ×ÁÍ ÖÉÚÎØ ÐÒÉ ×ÙÐÕÓËÅ ÓÌÅÄÕÀÝÅÊ ×ÅÒÓÉÉ). îÁÊÄÉÔÅ ËÏÐÉÉ ÏÆÉÃÉÁÌØÎÙÈ ÓÔÁÎÄÁÒÔÏ×, ÎÁÐÒÉÍÅÒ, &posix;. ÷Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ÎÅÓËÏÌØËÏ ÓÓÙÌÏË ÎÁ ÎÉÈ ÎÁ ÓÔÒÁÎÉÃÅ Web-ÓÁÊÔÁ ðÒÏÅËÔÁ ÓÏÏÔ×ÅÔÓÔ×ÉÑ FreeBSD ÓÔÁÎÄÁÒÔÁÍ C99 & POSIX. óÒÁ×ÎÉÔÅ ÐÏ×ÅÄÅÎÉÅ FreeBSD Ó ÔÅÍ, ÞÔÏ ÏÐÒÅÄÅÌÅÎÏ ÓÔÁÎÄÁÒÔÏÍ. åÓÌÉ ÒÅÁËÃÉÑ ÏÔÌÉÞÁÅÔÓÑ, ÏÓÏÂÅÎÎÏ × ÎÅÚÎÁÞÉÔÅÌØÎÙÈ ÉÌÉ ÎÅÐÏÎÑÔÎÙÈ ÒÁÚÄÅÌÁÈ ÓÐÅÃÉÆÉËÁÃÉÉ, ÎÁÐÒÁ×ØÔÅ Ï ÜÔÏÍ PR. åÓÌÉ ÍÏÖÅÔÅ, ÎÁÊÄÉÔÅ, ËÁË ÉÓÐÒÁ×ÉÔØ ÜÔÏ É ×ËÌÀÞÉÔÅ × PR ÐÁÔÞ. åÓÌÉ ×Ù ÐÏÌÁÇÁÅÔÅ, ÞÔÏ × ÓÔÁÎÄÁÒÔÅ ÅÓÔØ ÏÛÉÂËÁ, ÎÁÐÒÁ×ØÔÅ ÚÁÐÒÏÓ ÅÇÏ ÒÁÚÒÁÂÏÔÞÉËÁÍ. ðÒÅÄÌÏÖÉÔÅ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÚÁÄÁÞÉ ÄÌÑ ÜÔÏÇÏ ÓÐÉÓËÁ! òÁÂÏÔÁ Ó ÂÁÚÏÊ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ PR ÂÁÚÁ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ óÐÉÓÏË ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ FreeBSD ÓÏÄÅÒÖÉÔ ×ÓÅ ÁËÔÕÁÌØÎÙÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ É ÚÁÐÒÏÓÙ ÎÁ ÕÌÕÞÛÅÎÉÑ, ËÏÔÏÒÙÅ ÂÙÌÉ ÐÏÓÌÁÎÙ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ FreeBSD. âÁÚÁ ÄÁÎÎÙÈ PR ÓÏÄÅÒÖÉÔ ÚÁÄÁÞÉ ËÁË ÄÌÑ ÐÒÏÇÒÁÍÍÉÓÔÏ×, ÔÁË É ÎÅ ÄÌÑ ÎÉÈ. ðÒÏÓÍÏÔÒÉÔÅ ÏÔËÒÙÔÙÅ PR, ÎÁÊÄÉÔÅ ÔÅ, ÞÔÏ ÐÒÉ×ÌÅËÕÔ ×ÁÛÅ ×ÎÉÍÁÎÉÅ. îÅËÏÔÏÒÙÅ ÉÚ ÎÉÈ ÍÏÇÕÔ ÂÙÔØ ÏÞÅÎØ ÐÒÏÓÔÙÍÉ, ÔÒÅÂÕÀÝÉÍÉ ÌÉÛØ ÅÝ£ ÏÄÎÏÊ ÐÁÒÙ ÇÌÁÚ, ÞÔÏÂÙ ÐÏÓÍÏÔÒÅÔØ É ÐÏÄÔ×ÅÒÄÉÔØ, ÞÔÏ ÐÒÅÄÌÁÇÁÅÍÏÅ × PR ÉÓÐÒÁ×ÌÅÎÉÅ ÄÏÓÔÁÔÏÞÎÏ. äÒÕÇÉÅ ÍÏÇÕÔ ÂÙÔØ ÇÏÒÁÚÄÏ ÓÌÏÖÎÅÅ É ÄÁÖÅ ×Ï×ÓÅ ÎÅ ÓÏÄÅÒÖÁÔØ ÉÓÐÒÁ×ÌÅÎÉÑ. îÁÞÎÉÔÅ Ó ÔÅÈ PR, ËÏÔÏÒÙÅ ÎÉËÏÍÕ ÅÝ£ ÎÅ ÎÁÚÎÁÞÅÎÙ. åÓÌÉ PR ÕÖÅ ÚÁ ËÅÍ-ÔÏ ÚÁËÒÅÐÌÅÎÏ, ÎÏ ÓÏÄÅÒÖÉÔ ÐÒÏÂÌÅÍÕ, ËÏÔÏÒÕÀ ×Ù ÍÏÖÅÔÅ ÒÅÛÉÔØ, ÎÁÐÒÁ×ØÔÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ ÐÉÓØÍÏ ÞÅÌÏ×ÅËÕ, ËÏÔÏÒÏÍÕ ÎÁÚÎÁÞÅÎÏ ÜÔÏ PR, É ÓÐÒÏÓÉÔÅ, ÍÏÖÅÔÅ ÌÉ ×Ù ÐÏÒÁÂÏÔÁÔØ ÎÁÄ ÎÅÊ—Õ ÎÉÈ ÕÖÅ ÍÏÖÅÔ ÇÏÔÏ× ÐÁÔÞ ÄÌÑ ÔÅÓÔÉÒÏ×ÁÎÉÑ ÉÌÉ ËÁËÉÅ-ÔÏ ÉÄÅÉ, ËÏÔÏÒÙÅ ÍÏÖÎÏ ×ÍÅÓÔÅ ÏÂÓÕÄÉÔØ. ÷ÙÂÅÒÉÔÅ ÏÄÉÎ ÉÚ ÐÕÎËÔÏ× ÓÏ ÓÔÒÁÎÉÞËÉ <quote>ÉÄÅÊ</quote> óÐÉÓÏË ÐÒÏÅËÔÏ× É ÉÄÅÊ ÄÌÑ ÄÏÂÒÏ×ÏÌØÃÅ× ÔÁËÖÅ ÄÏÓÔÕÐÅÎ ÄÌÑ ÌÀÄÅÊ, ÖÅÌÁÀÝÉÈ ÐÏÍÏÞØ ÐÒÏÅËÔÕ &os;. óÐÉÓÏË ÐÏÓÔÏÑÎÎÏ ÏÂÎÏ×ÌÑÅÔÓÑ É ÓÏÄÅÒÖÉÔ ÐÕÎËÔÙ, ËÁË ÄÌÑ ÐÒÏÇÒÁÍÍÉÓÔÏ×, ÔÁË É ÄÌÑ ÎÅ ÐÒÏÇÒÁÍÍÉÓÔÏ×, Ó ÉÎÆÏÒÍÁÃÉÅÊ Ï ËÁÖÄÏÍ ÐÒÏÅËÔÅ. ëÁË ÐÒÉÎÑÔØ ÕÞÁÓÔÉÅ × ÒÁÂÏÔÅ èÁÒÁËÔÅÒ ÕÞÁÓÔÉÑ × ÒÁÂÏÔÅ ÎÁÄ ÓÉÓÔÅÍÏÊ ÏÂÙÞÎÏ ÐÏÄÐÁÄÁÅÔ ÐÏÄ ÏÄÎÕ ÉÌÉ ÎÅÓËÏÌØËÏ ÉÚ ÓÌÅÄÕÀÝÉÈ 5 ËÁÔÅÇÏÒÉÊ: óÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ É ÏÔÚÙ×Ù ÏÂÝÅÇÏ ÈÁÒÁËÔÅÒÁ éÄÅÉ ÉÌÉ ÐÏÖÅÌÁÎÉÑ ÏÂÝÅÇÏ ÔÅÈÎÉÞÅÓËÏÇÏ ÈÁÒÁËÔÅÒÁ ÄÏÌÖÎÙ ÎÁÐÒÁ×ÌÑÔØÓÑ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ × ÁÄÒÅÓ &a.hackers;. ðÏÄÏÂÎÙÍ ÖÅ ÏÂÒÁÚÏÍ ÔÏÔ, ËÔÏ ÉÎÔÅÒÅÓÕÅÔÓÑ ÔÁËÉÍÉ ×ÅÝÁÍÉ (É ÕÓÔÏÊÞÉ× Ë ÂÏÌØÛÏÍÕ ÐÏÔÏËÕ ÐÏÞÔÙ!) ÍÏÖÅÔ ÐÏÄÐÉÓÁÔØÓÑ ÎÁ ÓÐÉÓÏË ÒÁÓÓÙÌËÉ &a.hackers;. ïÂÒÁÔÉÔÅÓØ Ë òÕËÏ×ÏÄÓÔ×Õ FreeBSD ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÜÔÏÍ É ÄÒÕÇÉÈ ÓÐÉÓËÁÈ ÒÁÓÓÙÌËÉ. åÓÌÉ ×Ù ÎÁÛÌÉ ÏÛÉÂËÕ ÉÌÉ ÐÒÅÄÌÁÇÁÅÔÅ ×ÎÅÓÔÉ ËÁËÏÅ-ÔÏ ËÏÎËÒÅÔÎÏÅ ÉÓÐÒÁ×ÌÅÎÉÅ, ÐÏÖÁÌÕÊÓÔÁ, ÏÔÐÒÁ×ØÔÅ ÓÏÏÂÝÅÎÉÅ ÐÒÉ ÐÏÍÏÝÉ ÐÒÏÇÒÁÍÍÙ &man.send-pr.1; ÉÌÉ Å£ Web-ÜË×É×ÁÌÅÎÔÁ. ðÏÓÔÁÒÁÊÔÅÓØ ÚÁÐÏÌÎÉÔØ ×ÓÅ ÐÏÌÑ × ÓÏÏÂÝÅÎÉÉ Ï ÏÛÉÂËÅ. åÓÌÉ ÅÇÏ ÒÁÚÍÅÒ ÏÎÏ ÎÅ ÐÒÅ×ÙÛÁÅÔ 65 ëÂÁÊÔ, ×ËÌÀÞÉÔÅ ×ÓÅ ÐÁÔÞÉ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ × ÓÏÏÂÝÅÎÉÅ. åÓÌÉ ÐÁÔÞ ÐÒÅÄÎÁÚÎÁÞÅÎ ÄÌÑ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, ÐÏÍÅÓÔÉÔÅ [PATCH] × ÔÅÍÅ ÓÏÏÂÝÅÎÉÑ. ðÒÉ ×ËÌÀÞÅÎÉÉ ÐÁÔÞÅÊ ÎÅ ÉÓÐÏÌØÚÕÊÔÅ ÔÅÈÎÉËÕ cut-and-paste, ÐÏÔÏÍÕ ÞÔÏ ÐÒÉ ÜÔÏÍ ÓÉÍ×ÏÌÙ ÔÁÂÕÌÑÃÉÉ ÐÒÅÏÂÒÁÚÕÀÔÓÑ × ÐÒÏÂÅÌÙ É ÐÁÔÞ ÓÔÁÎÏ×ÉÔÓÑ ÎÅÐÒÉÇÏÄÎÙÍ Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ. åÓÌÉ ÏÂß£Í ÐÁÔÞÅÊ ÐÒÅ×ÙÛÁÅÔ 20 ëÂÁÊÔ, ÌÕÞÛÅ ×ËÌÀÞÁÔØ ÉÈ × ÓÏÏÂÝÅÎÉÅ × ÓÖÁÔÏÍ ×ÉÄÅ, ÄÌÑ ÞÅÇÏ ÕÐÁËÕÊÔÅ ÉÈ (ÎÁÐÒÉÍÅÒ, ÐÒÉ ÐÏÍÏÝÉ &man.gzip.1; ÉÌÉ &man.bzip2.1;) É ÏÂÒÁÂÏÔÁÊÔÅ ÁÒÈÉ× ÕÔÉÌÉÔÏÊ &man.uuencode.1;. ðÏÓÌÅ ÏÔÐÒÁ×ËÉ ÓÏÏÂÝÅÎÉÑ ×Ù ÄÏÌÖÎÙ ÐÏÌÕÞÉÔØ ÐÏÄÔ×ÅÒÖÄÅÎÉÅ É ÎÏÍÅÒ ÄÌÑ ÏÔÓÌÅÖÉ×ÁÎÉÑ. óÏÈÒÁÎÉÔÅ ÜÔÏÔ ÎÏÍÅÒ, ÞÔÏÂÙ ÉÓÐÏÌØÚÏ×ÁÔØ ÅÇÏ × ÄÁÌØÎÅÊÛÅÍ ÐÒÉ ÎÁÐÒÁ×ÌÅÎÉÉ ÐÏÄÒÏÂÎÏÓÔÅÊ Ï ÐÒÏÂÌÅÍÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ ÎÁ ÁÄÒÅÓ &a.bugfollowup;. éÓÐÏÌØÚÕÊÔÅ ÎÏÍÅÒ × ËÁÞÅÓÔ×Å ÔÅÍÙ ÐÉÓØÍÁ, ÎÁÐÒÉÍÅÒ, "Re: kern/3377". äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÌÀÂÏÍ ÓÏÏÂÝÅÎÉÉ Ï ÏÛÉÂËÅ ÄÏÌÖÎÁ ÎÁÐÒÁ×ÌÑÔØÓÑ ÜÔÉÍ ÓÐÏÓÏÂÏÍ. åÓÌÉ ×Ù ÎÅ ÐÏÌÕÞÉÌÉ ÐÏÄÔ×ÅÒÖÄÅÎÉÑ × ÔÅÞÅÎÉÅ ÒÁÚÕÍÎÏÇÏ ÐÅÒÉÏÄÁ ×ÒÅÍÅÎÉ (ÏÔ 3 ÄÎÅÊ ÄÏ ÎÅÄÅÌÉ, × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ×ÁÛÅÇÏ ÐÏÄËÌÀÞÅÎÉÑ Ë ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ) ÉÌÉ ÐÏ ËÁËÏÊ-ÔÏ ÐÒÉÞÉÎÅ ÎÅ ÍÏÖÅÔÅ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ËÏÍÁÎÄÏÊ &man.send-pr.1;, ÔÏ ÍÏÖÅÔÅ ÐÏÐÒÏÓÉÔØ ËÏÇÏ-ÎÉÂÕÄØ ÎÁÐÒÁ×ÉÔØ ÓÏÏÂÝÅÎÉÅ ÚÁ ×ÁÓ ÎÁ ÁÄÒÅÓ &a.bugs;. ðÒÏÞÔÉÔÅ ÔÁËÖÅ ÜÔÕ ÓÔÁÔØÀ, ÞÔÏÂÙ ÕÚÎÁÔØ, ËÁË ÐÉÓÁÔØ ÈÏÒÏÛÉÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ. éÚÍÅÎÅÎÉÑ × ÄÏËÕÍÅÎÔÁÃÉÉ ÐÏÓÙÌËÁ ÄÏËÕÍÅÎÔÁÃÉÉ éÚÍÅÎÅÎÉÑ × ÄÏËÕÍÅÎÔÁÃÉÉ ÏÂÓÕÖÄÁÀÔÓÑ × &a.doc;. ðÏÖÁÌÕÊÓÔÁ, ÐÏÓÍÏÔÒÉÔÅ õÞÅÂÎÉË ðÒÏÅËÔÁ ÄÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÐÏÌÎÙÈ ÉÎÓÔÒÕËÃÉÊ. ðÏÓÙÌÁÊÔÅ Ó×ÏÉ ÐÏÖÅÌÁÎÉÑ É ÉÚÍÅÎÅÎÉÑ (ÐÒÉÎÉÍÁÀÔÓÑ ÄÁÖÅ ÓÁÍÙÅ ÎÅÂÏÌØÛÉÅ!) ÐÒÉ ÐÏÍÏÝÉ &man.send-pr.1;, ËÁË ÜÔÏ ÏÐÉÓÁÎÏ × ÒÁÚÄÅÌÅ Ï ÓÏÏÂÝÅÎÉÑÈ Ï ÏÛÉÂËÁÈ É ÏÂÝÉÈ ÐÏÖÅÌÁÎÉÑÈ. éÚÍÅÎÅÎÉÑ Ë ÉÍÅÀÝÅÍÕÓÑ ÉÓÈÏÄÎÏÍÕ ËÏÄÕ FreeBSD-CURRENT äÏÂÁ×ÌÅÎÉÅ ÎÏ×ÏÇÏ ÉÓÈÏÄÎÏÇÏ ËÏÄÁ ÉÌÉ ×ÎÅÓÅÎÉÅ ÉÚÍÅÎÅÎÉÊ × ÓÕÝÅÓÔ×ÕÀÝÉÊ Ñ×ÌÑÅÔÓÑ ÎÅ ÔÁËÏÊ ÐÒÏÓÔÏÊ ÚÁÄÁÞÅÊ, É ÚÁ×ÉÓÉÔ ×Ï ÍÎÏÇÏÍ ÏÔ ÔÏÇÏ, ÎÁÓËÏÌØËÏ ×Ù ÄÁÌÅËÉ ÏÔ ÔÅËÕÝÅÇÏ ÓÏÓÔÏÑÎÉÑ ÒÁÚÒÁÂÏÔÏË ×Ï FreeBSD. óÕÝÅÓÔ×ÕÀÔ ÓÐÅÃÉÁÌØÎÙÅ ÐÒÏÍÅÖÕÔÏÞÎÙÅ ÒÅÌÉÚÙ FreeBSD, ÉÚ×ÅÓÔÎÙÅ ËÁË FreeBSD-CURRENT, ËÏÔÏÒÙÅ ÄÏÓÔÕÐÎÙ ÎÅÓËÏÌØËÉÍÉ ÒÁÚÎÙÍÉ ÓÐÏÓÏÂÁÍÉ, ÕÄÏÂÎÙÍÉ ÒÁÚÒÁÂÏÔÞÉËÁÍ, ÁËÔÉ×ÎÏ ÒÁÂÏÔÁÀÝÉÍ ÎÁÄ ÓÉÓÔÅÍÏÊ. ïÂÒÁÔÉÔÅÓØ Ë òÕËÏ×ÏÄÓÔ×Õ FreeBSD ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÐÏÌÕÞÅÎÉÉ É ÉÓÐÏÌØÚÏ×ÁÎÉÉ FreeBSD-CURRENT. åÓÌÉ ×Ù ÒÁÂÏÔÁÅÔÅ Ó ÎÅÓËÏÌØËÏ ÕÓÔÁÒÅ×ÛÉÍÉ ÉÓÈÏÄÎÙÍÉ ÔÅËÓÔÁÍÉ, ÔÏ ×ÁÛÉ ÉÚÍÅÎÅÎÉÑ ÉÎÏÇÄÁ ÍÏÇÕÔ ÏËÁÚÁÔØÓÑ ÕÖÅ ÎÅÎÕÖÎÙÍÉ ÉÌÉ ÓÌÉÛËÏÍ ÂÏÌØÛÉÍÉ, ÞÔÏÂÙ ÐÏ×ÔÏÒÎÏ ÉÎÔÅÇÒÉÒÏ×ÁÔØ ÉÈ ×Ï FreeBSD. õÍÅÎØÛÉÔØ ÔÁËÏÊ ÒÉÓË ÍÏÖÎÏ, ÐÏÄÐÉÓÁ×ÛÉÓØ ÎÁ ÓÐÉÓËÉ ÒÁÓÓÙÌËÉ &a.announce; É &a.current;, × ËÏÔÏÒÙÈ ÏÂÓÕÖÄÁÅÔÓÑ ÔÅËÕÝÅÅ ÓÏÓÔÏÑÎÉÅ ÓÉÓÔÅÍÙ. ðÒÅÄÐÏÌÏÖÉÍ, ÞÔÏ ×Ù ÓÍÏÇÌÉ ÐÏÌÕÞÉÔØ ÁËÔÕÁÌØÎÙÅ ÉÓÈÏÄÎÙÅ ÔÅËÓÔÙ, ÎÁ ÂÁÚÅ ËÏÔÏÒÙÈ ÄÅÌÁÌÉ Ó×ÏÉ ÉÚÍÅÎÅÎÉÑ. ôÏÇÄÁ ÓÌÅÄÕÀÝÉÍ ÛÁÇÏÍ Ñ×ÌÑÅÔÓÑ ÓÏÚÄÁÎÉÅ ÎÁÂÏÒÁ ÆÁÊÌÏ×, ÏÔÒÁÖÁÀÝÉÈ ×ÁÛÉ ÉÚÍÅÎÅÎÉÑ ÄÌÑ ÉÈ ÐÏÓÙÌËÉ ÔÅÍ, ËÔÏ ÏÔ×ÅÞÁÅÔ ÚÁ ÐÏÄÄÅÒÖËÕ FreeBSD. üÔÏ ÄÅÌÁÅÔÓÑ ÐÒÉ ÐÏÍÏÝÉ ËÏÍÁÎÄÙ &man.diff.1;. ðÒÅÄÐÏÞÔÉÔÅÌØÎÙÍ ÆÏÒÍÁÔÏÍ &man.diff.1; ÄÌÑ ÐÏÓÙÌËÉ ÐÁÔÞÅÊ Ñ×ÌÑÅÔÓÑ ÕÎÉÆÉÃÉÒÏ×ÁÎÎÁÑ ×ÙÄÁÞÁ, ÓÏÚÄÁ×ÁÅÍÁÑ ËÏÍÁÎÄÏÊ diff -u. diff ë ÐÒÉÍÅÒÕ: &prompt.user; diff -u oldfile newfile ÉÌÉ &prompt.user; diff -u -r -N olddir newdir ÓÏÚÄÁÓÔ ÎÁÂÏÒ ÐÁÔÞÅÊ × ÕÎÉÆÉÃÉÒÏ×ÁÎÎÏÍ ÆÏÒÍÁÔÅ ÄÌÑ ËÏÎËÒÅÔÎÏÇÏ ÆÁÊÌÁ Ó ÉÓÈÏÄÎÙÍ ÔÅËÓÔÏÍ ÉÌÉ ÄÌÑ ÉÅÒÁÒÈÉÉ ËÁÔÁÌÏÇÏ×. äÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÍÏÖÎÏ ÎÁÊÔÉ × &man.diff.1;. ðÏÓÌÅ ÔÏÇÏ, ËÁË ×Ù ÐÏÌÕÞÉÌÉ ÎÁÂÏÒ diff-ÆÁÊÌÏ× (ËÏÔÏÒÙÅ ×Ù ÍÏÖÅÔÅ ÐÒÏÔÅÓÔÉÒÏ×ÁÔØ ËÏÍÁÎÄÏÊ &man.patch.1;), ×Ù ÄÏÌÖÎÙ ÐÒÉÓÌÁÔØ ÉÈ ÄÌÑ ×ËÌÀÞÅÎÉÑ ×Ï FreeBSD. ÷ÏÓÐÏÌØÚÕÊÔÅÓØ ÐÒÏÇÒÁÍÍÏÊ &man.send-pr.1;, ËÁË ÜÔÏ ÏÐÉÓÁÎÏ × ÒÁÚÄÅÌÅ Ï ÓÏÏÂÝÅÎÉÑÈ Ï ÏÛÉÂËÁÈ É ÏÂÝÉÈ ÚÁÍÅÞÁÎÉÑÈ. îÅ ÐÏÓÙÌÁÊÔÅ diff-ÆÁÊÌÙ × ÓÐÉÓÏË ÒÁÓÓÙÌËÉ &a.hackers;, ÏÎÉ ÂÕÄÕÔ ÐÏÔÅÒÑÎÙ! îÁÍ ÏÞÅÎØ ÎÕÖÎÁ ×ÁÛÁ ÐÏÍÏÝØ (ÜÔÏ ÄÏÂÒÏ×ÏÌØÎÙÊ ÐÒÏÅËÔ!); ÉÚ-ÚÁ ÎÁÛÅÊ ÚÁÎÑÔÏÓÔÉ ÍÙ ÎÅ ÓÍÏÖÅÍ ÒÁÓÓÍÏÔÒÅÔØ ÅÇÏ ÓÒÁÚÕ, É ÏÎ ÂÕÄÅÔ ÎÁÈÏÄÉÔØÓÑ × ÂÁÚÅ ÄÁÎÎÙÈ PR, ÐÏËÁ ÍÙ ÎÅ ÓÄÅÌÁÅÍ ÜÔÏ. õËÁÖÉÔÅ ÎÁ ×ÁÛÕ ÐÏÓÙÌËÕ, ×ËÌÀÞÉ× ÓÔÒÏËÕ [PATCH] × ÔÅÍÕ ÓÏÏÂÝÅÎÉÑ. uuencode åÓÌÉ ×Ù ÓÞÉÔÁÅÔÅ, ÞÔÏ ÜÔÏ ÎÕÖÎÏ (Ë ÐÒÉÍÅÒÕ, ×Ù ÄÏÂÁ×ÌÑÌÉ, ÕÄÁÌÑÌÉ ÉÌÉ ÐÅÒÅÉÍÅÎÏ×Ù×ÁÌÉ ÆÁÊÌÙ), ÔÏ ÏÂßÅÄÉÎÉÔÅ ×ÁÛÉ ÉÚÍÅÎÅÎÉÑ × tar-ÆÁÊÌ É ÏÂÒÁÂÏÔÁÊÔÅ ÅÇÏ ÐÒÏÇÒÁÍÍÏÊ &man.uuencode.1;. ðÒÉÎÉÍÁÀÔÓÑ ÔÁËÖÅ É ÁÒÈÉ×Ù, ÓÏÚÄÁÎÎÙÅ ÐÒÏÇÒÁÍÍÏÊ &man.shar.1;. åÓÌÉ ×ÁÛÅ ÉÚÍÅÎÅÎÉÅ ÐÏÔÅÎÃÉÁÌØÎÏ ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÓÏÍÎÉÔÅÌØÎÙÍ, ÎÁÐÒÉÍÅÒ, ×Ù ÎÅ Õ×ÅÒÅÎÙ × ÏÔÓÕÔÓÔ×ÉÉ ÌÉÃÅÎÚÉÏÎÎÙÈ ÏÇÒÁÎÉÞÅÎÉÊ ÏÔÎÏÓÉÔÅÌØÎÏ ÅÇÏ ÒÁÓÐÒÏÓÔÒÁÎÅÎÉÑ, ÔÏ ×Ù ÄÏÌÖÎÙ ÐÏÓÌÁÔØ ÅÇÏ ÎÁÐÒÑÍÕÀ × ÓÐÉÓÏË ÒÁÓÓÙÌËÉ &a.core;, Á ÎÅ ÞÅÒÅÚ &man.send-pr.1;. ÷ ÓÐÉÓËÅ ÒÁÓÓÙÌËÉ &a.core; ÕÞÁÓÔ×ÕÅÔ ÇÏÒÁÚÄÏ ÍÅÎØÛÅÅ ËÏÌÉÞÅÓÔ×Ï ÌÀÄÅÊ, ËÏÔÏÒÙÅ ×ÙÐÏÌÎÑÀÔ ÏÓÎÏ×ÎÕÀ ÅÖÅÄÎÅ×ÎÕÀ ÒÁÂÏÔÕ ÎÁÄ FreeBSD. úÁÍÅÔØÔÅ, ÞÔÏ ÜÔÁ ÇÒÕÐÐÁ ÔÁËÖÅ ÏÞÅÎØ ÚÁÎÑÔÁ, ÔÁË ÞÔÏ ÓÀÄÁ ÐÉÓØÍÁ ÎÕÖÎÏ ÐÏÓÙÌÁÔØ ÔÏÌØËÏ × ÓÌÕÞÁÅ ÄÅÊÓÔ×ÉÔÅÌØÎÏÊ ÎÅÏÂÈÏÄÉÍÏÓÔÉ. ðÏÖÁÌÕÊÓÔÁ, ÏÂÒÁÔÉÔÅÓØ Ë ÓÐÒÁ×ËÅ ÐÏ &man.intro.9; É &man.style.9; ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÎÅËÏÔÏÒÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÓÔÉÌÅ ËÏÄÉÒÏ×ÁÎÉÑ. íÙ ÎÁÄÅÅÍÓÑ, ÞÔÏ ×Ù ÈÏÔÑ ÂÙ ÐÒÉÍÅÔÅ ÜÔÕ ÉÎÆÏÒÍÁÃÉÀ Ë Ó×ÅÄÅÎÉÀ ÐÅÒÅÄ ÔÅÍ, ËÁË ÐÒÉÓÌÁÔØ ÎÁÍ Ó×ÏÊ ËÏÄ. îÏ×ÙÊ ËÏÄ ÉÌÉ ÂÏÌØÛÉÅ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ ÷ ÓÌÕÞÁÅ ÚÎÁÞÉÔÅÌØÎÏÇÏ ÏÂߣÍÁ ÐÒÉÓÌÁÎÎÏÇÏ ×ÁÍÉ ËÏÄÁ É ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÊ ÒÁÂÏÔÙ, ÌÉÂÏ ÄÏÂÁ×ÌÅÎÉÑ Ë FreeBSD ×ÁÖÎÏÊ ÎÏ×ÏÊ ÆÕÎËÃÉÉ, ÓÔÁÎÏ×ÉÔÓÑ ÐÒÁËÔÉÞÅÓËÉ ×ÓÅÇÄÁ ÎÅÏÂÈÏÄÉÍÏ ÐÏÓÙÌÁÔØ ÉÚÍÅÎÅÎÉÑ × ×ÉÄÅ tar-ÆÁÊÌÏ×, ÏÂÒÁÂÏÔÁÎÎÙÈ uuencode, ÉÌÉ ÐÅÒÅÄÁ×ÁÔØ ÉÈ ÎÁ Web-ÓÁÊÔ ÉÌÉ FTP-ÓÅÒ×ÅÒ ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÄÒÕÇÉÍÉ ÌÀÄØÍÉ. åÓÌÉ Õ ×ÁÓ ÎÅÔ ÄÏÓÔÕÐÁ Ë Web- ÉÌÉ FTP-ÓÅÒ×ÅÒÁÍ, ÐÏÐÒÏÓÉÔÅ × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÍ ÓÐÉÓËÅ ÒÁÓÓÙÌËÅ FreeBSD ËÏÇÏ-ÎÉÂÕÄØ ÒÁÚÍÅÓÔÉÔØ ÉÚÍÅÎÅÎÉÑ ÚÁ ×ÁÓ. ðÒÉ ÒÁÂÏÔÅ Ó ÂÏÌØÛÉÍ ÏÂߣÍÏÍ ËÏÄÁ ÎÅÉÚÂÅÖÎÏ ×ÏÚÎÉËÁÅÔ ×ÏÐÒÏÓ Ï ÓÏÂÌÀÄÅÎÉÉ Á×ÔÏÒÓËÉÈ ÐÒÁ×. äÏÐÕÓÔÉÍÙÍÉ ÌÉÃÅÎÚÉÏÎÎÙÍÉ ÓÏÇÌÁÛÅÎÉÑÍÉ ÄÌÑ ËÏÄÁ, ×ËÌÀÞÁÅÍÏÇÏ ×Ï FreeBSD, Ñ×ÌÑÀÔÓÑ ÓÌÅÄÕÀÝÉÅ: ÌÉÃÅÎÚÉÏÎÎÏÅ ÓÏÇÌÁÛÅÎÉÅ BSD ìÉÃÅÎÚÉÏÎÎÏÅ ÓÏÇÌÁÛÅÎÉÅ BSD. ïÎÏ Ñ×ÌÑÅÔÓÑ ÓÁÍÙÍ ÐÒÅÄÐÏÞÔÉÔÅÌØÎÙÍ ÉÚ-ÚÁ ÏÔÓÕÔÓÔ×ÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÕÓÌÏ×ÉÊ É ÏÂÝÅÊ ÐÒÉ×ÌÅËÁÔÅÌØÎÏÓÔÉ ÄÌÑ ËÏÍÍÅÒÞÅÓËÉÈ ËÏÍÐÁÎÉÊ. ðÒÏÅËÔ FreeBSD ÄÁÌ£Ë ÏÔ ÔÏÇÏ, ÞÔÏÂÙ ×ÙÓÔÕÐÁÔØ ÐÒÏÔÉ× ËÏÍÍÅÒÞÅÓËÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ, ÎÏ ÁËÔÉ×ÎÏ ÐÏÐÕÌÑÒÉÚÉÒÕÅÔ ÔÁËÏÅ ÐÅÒÅÓÅÞÅÎÉÅ ËÏÍÍÅÒÞÅÓËÉÈ ÉÎÔÅÒÅÓÏ×, ËÏÔÏÒÏÅ ÐÏÚ×ÏÌÉÔ ÐÏÓÔÅÐÅÎÎÏ ÚÁÐÕÓÔÉÔØ ÍÅÈÁÎÉÚÍ ÉÎ×ÅÓÔÉÃÉÊ ×Ï FreeBSD. GPL GNU General Public License GNU General Public License GNU General Public License, ÉÌÉ GPL. üÔÏ ÌÉÃÅÎÚÉÏÎÎÏÅ ÓÏÇÌÁÛÅÎÉÅ ÎÅ ÏÞÅÎØ ÐÏÐÕÌÑÒÎÏ Õ ÎÁÓ ÉÚ-ÚÁ ÏÂߣÍÁ ÔÒÅÂÏ×ÁÎÉÊ, ËÏÔÏÒÙÅ ÎÕÖÎÏ ×ÙÐÏÌÎÑÔØ ×ÓÅÍ, ËÔÏ ÓÏÂÉÒÁÅÔÓÑ ÉÓÐÏÌØÚÏ×ÁÔØ ËÏÄ × ËÏÍÍÅÒÞÅÓËÉÈ ÃÅÌÑÈ. ïÄÎÁËÏ, ÕÞÉÔÙ×ÁÑ ÁÂÓÏÌÀÔÎÏÅ ÐÒÅ×ÏÓÈÏÄÓÔ×Ï ÏÂߣÍÁ ÜÔÏÇÏ ËÏÄÁ (ËÏÍÐÉÌÑÔÏÒ, ÁÓÓÅÍÂÌÅÒ, ÉÎÓÔÒÕÍÅÎÔÙ ÆÏÒÍÁÔÉÒÏ×ÁÎÉÑ ÔÅËÓÔÁ É ÔÁË ÄÁÌÅÅ) ÂÙÌÏ ÂÙ ÇÌÕÐÏ ÏÔËÁÚÙ×ÁÔØÓÑ ÏÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÒÁÚÒÁÂÏÔÏË, ÐÏÄÐÁÄÁÀÝÉÈ ÐÏÄ ÄÅÊÓÔ×ÉÅ ÜÔÏÊ ÌÉÃÅÎÚÉÉ. ëÏÄ, ÒÁÓÐÒÏÓÔÒÁÎÑÅÍÙÊ ÐÏ ÕÓÌÏ×ÉÑÍ ÌÉÃÅÎÚÉÏÎÎÏÇÏ ÓÏÇÌÁÛÅÎÉÑ GPL ÔÁËÖÅ ÒÁÚÍÅÝÁÅÔÓÑ × ÏÔÄÅÌØÎÏÊ ÞÁÓÔÉ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, × /sys/gnu ÉÌÉ /usr/src/gnu, É ÐÏÜÔÏÍÕ ÌÅÇËÏ ÉÄÅÎÔÉÆÉÃÉÒÕÅÔÓÑ ×ÓÑËÉÍ, ÄÌÑ ËÏÇÏ GPL ÐÒÅÄÓÔÁ×ÌÑÅÔ ÐÒÏÂÌÅÍÕ. òÁÚÒÁÂÏÔËÉ, ÐÏÄÐÁÄÁÀÝÉÅ ÐÏÄ ÄÅÊÓÔ×ÉÅ ÄÒÕÇÉÈ ÔÉÐÏ× ÌÉÃÅÎÚÉÏÎÎÙÈ ÓÏÇÌÁÛÅÎÉÊ, ÄÏÌÖÎÙ ÂÙÔØ ÔÝÁÔÅÌØÎÏ ÐÒÏÓÍÏÔÒÅÎÙ ÐÅÒÅÄ ÐÒÉÎÑÔÉÅÍ ÒÅÛÅÎÉÑ Ï ÉÈ ×ËÌÀÞÅÎÉÉ ×Ï FreeBSD. òÁÚÒÁÂÏÔËÉ, ÎÁ ËÏÔÏÒÙÅ ÒÁÓÐÒÏÓÔÒÁÎÑÀÔÓÑ Ö£ÓÔËÉÅ ÏÇÒÁÎÉÞÅÎÉÑ ËÏÍÍÅÒÞÅÓËÉÈ ÌÉÃÅÎÚÉÏÎÎÙÈ ÓÏÇÌÁÛÅÎÉÊ, ÏÂÙÞÎÏ ÏÔ×ÅÒÇÁÀÔÓÑ, Á Á×ÔÏÒÁÍ ×ÓÅÇÄÁ ÐÒÅÄÌÁÇÁÅÔÓÑ ÒÁÓÐÒÏÓÔÒÁÎÑÔØ ÐÏÄÏÂÎÙÅ ÉÚÍÅÎÅÎÉÑ ÐÏ ÓÏÂÓÔ×ÅÎÎÙÍ ËÁÎÁÌÁÍ. äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÎÁ ×ÁÛÕ ÒÁÂÏÔÕ ÒÁÓÐÒÏÓÔÒÁÎÑÌÉÓØ ÕÓÌÏ×ÉÑ ÌÉÃÅÎÚÉÏÎÎÏÇÏ ÏÇÒÁÎÉÞÅÎÉÑ × ÓÔÉÌÅ BSD, ÒÁÚÍÅÓÔÉÔÅ ÓÌÅÄÕÀÝÉÊ ÔÅËÓÔ × ÓÁÍÏÍ ÎÁÞÁÌÅ ËÁÖÄÏÇÏ ÆÁÊÌÁ Ó ÉÓÈÏÄÎÙÍÉ ÔÅËÓÔÁÍÉ, ËÏÔÏÒÙÅ ×Ù ÈÏÔÉÔÅ ÚÁÝÉÔÉÔØ, ÚÁÍÅÎÉ× ÔÅËÓÔ ÍÅÖÄÕ %% ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÊ ÉÎÆÏÒÍÁÃÉÅÊ: Copyright (c) %%ÐÏÌÎÙÅ_ÎÏÍÅÒÁ_ÇÏÄÏ×%% %%×ÁÛÅ_ÉÍÑ%%, %%×ÁÛ_ÛÔÁÔ%% %%×ÁÛ_ÐÏÞÔÏ×ÙÊ_ÉÎÄÅËÓ%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $&os;$ äÌÑ ×ÁÛÅÇÏ ÕÄÏÂÓÔ×Á ËÏÐÉÑ ÜÔÏÇÏ ÔÅËÓÔÁ ÒÁÚÍÅÝÅÎÁ × ÆÁÊÌÅ /usr/share/examples/etc/bsd-style-copyright. äÅÎØÇÉ, ÏÂÏÒÕÄÏ×ÁÎÉÅ ÉÌÉ Internet-ÄÏÓÔÕÐ íÙ ×ÓÅÇÄÁ Ó ÕÄÏ×ÏÌØÓÔ×ÉÅÍ ÐÒÉÍÅÍ ÍÁÔÅÒÉÁÌØÎÕÀ ÐÏÍÏÝØ, ÎÕÖÎÕÀ ÄÌÑ ÄÁÌØÎÅÊÛÅÇÏ ÓÕÝÅÓÔ×Ï×ÁÎÉÑ ðÒÏÅËÔÁ FreeBSD, Á × ÄÏÂÒÏ×ÏÌØÎÏÍ ÐÒÏÅËÔÅ, ÔÉÐÁ ÎÁÛÅÇÏ ÍÁÌÅÎØËÁÑ ÐÏÍÏÝØ ÍÏÖÅÔ ÐÏÓÌÕÖÉÔØ ÄÏÌÇÏ! âÅÚ×ÏÚÍÅÚÄÎÁÑ ÐÅÒÅÄÁÞÁ ×ÙÞÉÓÌÉÔÅÌØÎÏÊ ÔÅÈÎÉËÉ ÔÁËÖÅ ÏÞÅÎØ ×ÁÖÎÁ ÄÌÑ ÒÁÓÛÉÒÅÎÉÑ ÓÐÉÓËÁ ÐÏÄÄÅÒÖÉ×ÁÅÍÏÇÏ ÐÅÒÉÆÅÒÉÊÎÏÇÏ ÏÂÏÒÕÄÏ×ÁÎÉÑ, ÔÁË ËÁË ÏÂÙÞÎÏ Õ ÎÁÓ ÎÅÔ ÓÒÅÄÓÔ× ÄÌÑ ÓÁÍÏÓÔÏÑÔÅÌØÎÏÇÏ ÅÇÏ ÐÒÉÏÂÒÅÔÅÎÉÑ. <anchor id="donations"/>æÉÎÁÎÓÏ×ÁÑ ÐÏÍÏÝØ The FreeBSD Foundation Ñ×ÌÑÅÔÓÑ ÎÅËÏÍÍÅÒÞÅÓËÏÊ ÏÒÇÁÎÉÚÁÃÉÅÊ, ÏÓ×ÏÂÏÖÄ£ÎÎÏÊ ÏÔ ÕÐÌÁÔÙ ÎÁÌÏÇÏ×, ÓÏÚÄÁÎÎÏÊ Ó ÃÅÌØÀ ÒÅÁÌÉÚÁÃÉÉ ÃÅÌÅÊ ðÒÏÅËÔÁ FreeBSD. ëÁË ÏÒÇÁÎÉÚÁÃÉÑ ÔÉÐÁ 501(c)3, æÏÎÄ ÏÂÙÞÎÏ ÏÓ×ÏÂÏÖÄÁÅÔÓÑ ÏÔ ÆÅÄÅÒÁÌØÎÏÇÏ ÎÁÌÏÇÁ óûá ÎÁ ÐÒÉÂÙÌØ. óÕÍÍÙ ÂÅÚ×ÏÚÍÅÚÄÎÙÈ ÐÏÖÅÒÔ×Ï×ÁÎÉÊ ÔÁËÉÍ ÏÒÇÁÎÉÚÁÃÉÑÍ ÞÁÓÔÏ ×ÙÞÉÔÁÀÔÓÑ ÉÚ ÏÂÝÅÊ ÓÕÍÍÙ ÎÁÌÏÇÏÏÂÌÁÇÁÅÍÏÊ ÐÒÉÂÙÌÉ. æÉÎÁÎÓÏ×ÁÑ ÐÏÍÏÝØ ÍÏÖÅÔ ÂÙÔØ ÎÁÐÒÁ×ÌÅÎÁ × ×ÉÄÅ ÞÅËÏ× ÎÁ ÁÄÒÅÓ:
The FreeBSD Foundation P.O. Box 20247 Boulder, CO 80308 USA
The FreeBSD Foundation ÔÅÐÅÒØ ÍÏÖÅÔ ÐÒÉÎÉÍÁÔØ ÐÏÍÏÝØ ÞÅÒÅÚ Web ÐÏ ÓÉÓÔÅÍÅ PayPal. äÌÑ ÎÁÐÒÁ×ÌÅÎÉÑ ÐÏÍÏÝÉ, ÐÏÖÁÌÕÊÓÔÁ, ÐÏÓÅÔÉÔÅ Web-ÓÁÊÔ æÏÎÄÁ. äÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï æÏÎÄÅ FreeBSD ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ ÓÔÒÁÎÉÃÅ, ÓÏÄÅÒÖÁÝÅÊ ××ÏÄÎÕÀ ÉÎÆÏÒÍÁÃÉÉ Ï æÏÎÄÅ FreeBSD. äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÏÂÒÁÔÉÔØÓÑ × æÏÎÄ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ, ÎÁÐÉÛÉÔÅ ÐÉÓØÍÏ ÎÁ ÁÄÒÅÓ bod@FreeBSDFoundation.org. ðÏÍÏÝØ × ×ÉÄÅ ÏÂÏÒÕÄÏ×ÁÎÉÑ ÂÅÚ×ÏÚÍÅÚÄÎÁÑ ÐÏÍÏÝØ ðÒÏÅËÔ FreeBSD Ó ÕÄÏ×ÏÌØÓÔ×ÉÅ ÐÒÉÍÅÔ ÐÏÍÏÝØ × ×ÉÄÅ ÏÂÏÒÕÄÏ×ÁÎÉÑ, ËÏÔÏÒÏÍÕ ÏÎ ÎÁÊÄ£Ô ÈÏÒÏÛÅÅ ÐÒÉÍÅÎÅÎÉÅ. åÓÌÉ ×Ù ÚÁÉÎÔÅÒÅÓÏ×ÁÎÙ × ÐÅÒÅÄÁÞÅ ÏÂÏÒÕÄÏ×ÁÎÉÑ, ÐÏÖÁÌÕÊÓÔÁ, ÏÂÒÁÔÉÔÅÓØ Ë òÕËÏ×ÏÄÓÔ×Õ ãÅÎÔÒÁ ÐÏÖÅÒÔ×Ï×ÁÎÉÊ. + +
diff --git a/ru_RU.KOI8-R/articles/cups/article.xml b/ru_RU.KOI8-R/articles/cups/article.xml index 280c872dd0..3226ebca9f 100644 --- a/ru_RU.KOI8-R/articles/cups/article.xml +++ b/ru_RU.KOI8-R/articles/cups/article.xml @@ -1,399 +1,401 @@
õÎÉ×ÅÒÓÁÌØÎÁÑ óÉÓÔÅÍÁ ðÅÞÁÔÉ Unix ÎÁ FreeBSD Chess Griffin
chess@chessgriffin.com
 &tm-attrib.freebsd; &tm-attrib.general; $FreeBSD$ $FreeBSD$ üÔÁ ÓÔÁÔØÑ ÐÏÓ×ÑÝÅÎÁ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÀ õÎÉ×ÅÒÓÁÌØÎÏÊ óÉÓÔÅÍÙ ðÅÞÁÔÉ UNIX (CUPS) ÎÁ &os;. úÎÁËÏÍÉÍÓÑ Ó õÎÉ×ÅÒÓÁÌØÎÏÊ óÉÓÔÅÍÏÊ ðÅÞÁÔÉ UNIX (CUPS) printing CUPS õÎÉ×ÅÒÓÁÌØÎÁÑ óÉÓÔÅÍÁ ðÅÞÁÔÉ UNIX (Common Unix Printing System, ÉÌÉ ÓÏËÒÁÝÅÎÎÏ CUPS), ÐÒÅÄÏÓÔÁ×ÌÑÅÔ ÐÅÒÅÎÏÓÉÍÕÀ ÓÒÅÄÕ ÐÅÞÁÔÉ ÄÌÑ &unix; É &unix;-ÐÏÄÏÂÎÙÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ. ïÎÁ ÂÙÌÁ ÒÁÚÒÁÂÏÔÁÎÁ ËÏÍÐÁÎÉÅÊ Easy Software Products, ÞÔÏÂÙ ÐÒÅÄÏÓÔÁ×ÉÔØ ÓÔÁÎÄÁÒÔÎÏÅ ÒÅÛÅÎÉÅ × ÐÅÞÁÔÉ ÄÌÑ ×ÓÅÈ ÒÁÚÒÁÂÏÔÞÉËÏ× É ÐÏÌØÚÏ×ÁÔÅÌÅÊ &unix;. õÎÉ×ÅÒÓÁÌØÎÁÑ óÉÓÔÅÍÁ ðÅÞÁÔÉ UNIX ÉÓÐÏÌØÚÕÅÔ ÐÒÏÔÏËÏÌ ÍÅÖÓÅÔÅ×ÏÊ ÐÅÞÁÔÉ (Internet Printing Protocol, IPP) ËÁË ÏÓÎÏ×Õ ÄÌÑ ÕÐÒÁ×ÌÅÎÉÑ ÚÁÄÁÎÉÑÍÉ ÎÁ ÐÅÞÁÔØ É ÏÞÅÒÅÄÑÍÉ. ôÁËÖÅ ÞÁÓÔÉÞÎÏ ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ ÓÌÅÄÕÀÝÉÅ ÐÒÏÔÏËÏÌÙ: LPD, SMB É AppSocket (ÔÁËÖÅ ÉÚ×ÅÓÔÎÙÊ ËÁË JetDirect). CUPS ÄÁÅÔ ×ÏÚÍÏÖÎÏÓÔØ ÏÂÚÏÒÁ ÓÅÔÅ×ÙÈ ÐÒÉÎÔÅÒÏ× É ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÏÐÃÉÊ, ÂÁÚÉÒÕÀÝÉÈÓÑ ÎÁ ðÏÓÔóËÒÉÐÔ ïÐÉÓÁÎÉÉ ðÒÉÎÔÅÒÏ× (PostScript Printer Definition, PPD), ÞÔÏÂÙ ÐÏÄÄÅÒÖÉ×ÁÔØ × &unix; ÏÂÝÅÐÒÉÎÑÔÙÅ ÔÒÁÄÉÃÉÉ ÐÅÞÁÔÉ. ÷ ÒÅÚÕÌØÔÁÔÅ CUPS ÉÄÅÁÌØÎÏ ÐÏÄÈÏÄÉÔ ÄÌÑ ÓÏ×ÍÅÓÔÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÐÒÉÎÔÅÒÏ× × ÓÍÅÛÁÎÎÏÊ ÓÒÅÄÅ ÉÚ &os;, &linux;, &macos; X ÉÌÉ &windows;. ïÆÉÃÉÁÌØÎÙÊ ÓÁÊÔ õÎÉ×ÅÒÓÁÌØÎÏÊ óÉÓÔÅÍÙ ðÅÞÁÔÉ UNIX — . õÓÔÁÎÏ×ËÁ ÓÅÒ×ÅÒÁ ÐÅÞÁÔÉ CUPS CUPS ÍÏÖÅÔ ÂÙÔØ ÕÓÔÁÎÏ×ÌÅÎÁ ÉÚ ÐÏÒÔÏ× ÉÌÉ ÕÖÅ ÓÏÂÒÁÎÎÙÈ ÐÁËÅÔÏ×. þÔÏÂÙ ÕÓÔÁÎÏ×ÉÔØ CUPS ÉÚ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ×, ×ÙÐÏÌÎÉÔÅ Ó ÐÒÉ×ÉÌÅÇÉÑÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑ root ÓÌÅÄÕÀÝÕÀ ËÏÍÁÎÄÕ: &prompt.root; cd /usr/ports/print/cups && make install clean äÌÑ ÕÓÔÁÎÏ×ËÉ CUPS ÉÓÐÏÌØÚÕÑ ÐÁËÅÔ, ÚÁÐÕÓÔÉÔÅ ÎÁ ×ÙÐÏÌÎÅÎÉÅ ÔÁËÕÀ ËÏÍÁÎÄÕ: &prompt.root; pkg_add -r cups äÒÕÇÉÅ ÎÅÏÂÑÚÁÔÅÌØÎÙÅ, ÎÏ ÒÅËÏÍÅÎÄÕÅÍÙÅ Ë ÕÓÔÁÎÏ×ËÅ ÐÏÒÔÙ ÉÌÉ ÐÁËÅÔÙ ÜÔÏ print/gutenprint-cups É print/hplip, ËÁÖÄÙÊ ÉÚ ËÏÔÏÒÙÈ ÄÏÂÁ×ÌÑÅÔ ÄÒÁÊ×ÅÒÁ É ÕÔÉÌÉÔÙ ÄÌÑ ÒÁÚÎÏÏÂÒÁÚÎÙÈ ÐÒÉÎÔÅÒÏ×. ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÆÁÊÌÙ ËÏÎÆÉÇÕÒÁÃÉÉ CUPS ÍÏÇÕÔ ÂÙÔØ ÎÁÊÄÅÎÙ × ÄÉÒÅËÔÏÒÉÉ /usr/local/etc/cups. îÁÓÔÒÏÊËÁ ÓÅÒ×ÅÒÁ ÐÅÞÁÔÉ CUPS þÔÏÂÙ ÎÁÓÔÒÏÉÔØ ÓÅÒ×ÅÒ CUPS ÎÅÏÂÈÏÄÉÍÏ ÏÔÒÅÄÁËÔÉÒÏ×ÁÔØ ÎÅÓËÏÌØËÏ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×. äÌÑ ÎÁÞÁÌÁ ÓÏÚÄÁÊÔÅ ÉÌÉ ÉÓÐÒÁ×ØÔÅ ÆÁÊÌ /etc/devfs.rules É ÄÏÂÁ×ØÔÅ ÓÌÅÄÕÀÝÕÀ ÉÎÆÏÒÍÁÃÉÀ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÕÓÔÁÎÏ×ÉÔØ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ ÐÒÁ×Á ÎÁ ×ÓÅ ÐÏÔÅÎÃÉÁÌØÎÙÅ ÆÁÊÌÙ ÕÓÔÒÏÊÓÔ× ÐÒÉÎÔÅÒÏ× É Ó×ÑÚÁÔØ ÐÒÉÎÔÅÒÙ Ó ÇÒÕÐÐÏÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ cups: [system=10] add path 'unlpt*' mode 0660 group cups add path 'ulpt*' mode 0660 group cups add path 'lpt*' mode 0660 group cups add path 'usb/X.Y.Z' mode 0660 group cups úÁÍÅÎÉÔÅ X, Y É Z ÎÏÍÅÒÁÍÉ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÇÏ ÐÒÉÎÔÅÒÕ ÃÅÌÅ×ÏÇÏ ÕÓÔÒÏÊÓÔ×Á USB, ÏÔÏÂÒÁÖÁÅÍÏÇÏ × ËÁÔÁÌÏÇÅ /dev/usb. þÔÏÂÙ ÎÁÊÔÉ ÔÒÅÂÕÅÍÙÅ ÚÎÁÞÅÎÉÑ, ÐÒÏÓÍÏÔÒÉÔÅ ×Ù×ÏÄ &man.dmesg.8; É ÎÁÊÄÉÔÅ Ó×ÑÚÁÎÎÏÅ Ó ×ÁÛÉÍ ÐÒÉÎÔÅÒÏÍ ÉÍÑ ÓÐÅÃÉÁÌØÎÏÇÏ ÕÓÔÒÏÊÓÔ×Á ugenX.Y, ÐÏÓÌÅÄÎÅÅ ÂÕÄÅÔ ÓÉÍ×ÏÌÉÞÅÓËÏÊ ÓÓÙÌËÏÊ ÎÁ ÉÓËÏÍÏÅ ÕÓÔÒÏÊÓÔ×Ï × ËÁÔÁÌÏÇÅ /dev/usb. úÁÔÅÍ, ÄÏÂÁ×ØÔÅ ÓÌÅÄÕÀÝÉÅ Ä×Å ÚÁÐÉÓÉ × /etc/rc.conf: cupsd_enable="YES" devfs_system_ruleset="system" üÔÉ Ä×Å ÚÁÐÉÓÉ ÂÕÄÕÔ ÚÁÐÕÓËÁÔØ ÓÅÒ×ÅÒ ÐÅÞÁÔÉ CUPS ×Ï ×ÒÅÍÑ ÚÁÇÒÕÚËÉ ÓÉÓÔÅÍÙ É ÐÒÉÍÅÎÑÔØ ÌÏËÁÌØÎÏÅ ÐÒÁ×ÉÌÏ devfs, ÓÏÚÄÁÎÎÏÅ ×ÙÛÅ. äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÅÞÁÔØ CUPS ÓÔÁÌÁ ÄÏÓÔÕÐÎÁ ÄÌÑ ÎÅËÏÔÏÒÙÈ µsoft.windows; ËÌÉÅÎÔÏ×, ÎÅÏÂÈÏÄÉÍÏ ÒÁÓËÏÍÍÅÎÔÉÒÏ×ÁÔØ ÓÌÅÄÕÀÝÕÀ ÚÁÐÉÓØ × /usr/local/etc/cups/mime.types É /usr/local/etc/cups/mime.convs: application/octet-stream ðÏ ÏËÏÎÞÁÎÉÀ ×ÎÅÓÅÎÉÑ ÉÚÍÅÎÅÎÉÊ ÓÌÕÖÂÙ &man.devfs.8; É CUPS ÎÅÏÂÈÏÄÉÍÏ ÐÅÒÅÚÁÐÕÓÔÉÔØ, ÄÌÑ ÞÅÇÏ ÐÅÒÅÚÁÇÒÕÚÉÔÅ ÏÐÅÒÁÃÉÏÎÎÕÀ ÓÉÓÔÅÍÕ ÉÌÉ ×ÙÐÏÌÎÉÔÅ ÏÔ ÐÏÌØÚÏ×ÁÔÅÌÑ root ÓÌÅÄÕÀÝÉÅ Ä×Å ËÏÍÁÎÄÙ: &prompt.root; /etc/rc.d/devfs restart &prompt.root; /usr/local/etc/rc.d/cupsd restart îÁÓÔÒÏÊËÁ ÐÒÉÎÔÅÒÏ× ÎÁ ÓÅÒ×ÅÒÅ ÐÅÞÁÔÉ CUPS ðÏÓÌÅ ÔÏÇÏ, ËÁË ÓÉÓÔÅÍÁ CUPS ÂÙÌÁ ÕÓÔÁÎÏ×ÌÅÎÁ É ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎÁ, ÓÉÓÔÅÍÎÙÊ ÁÄÍÉÎÉÓÔÒÁÔÏÒ ÍÏÖÅÔ ÎÁÞÁÔØ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÅ ÌÏËÁÌØÎÙÈ ÐÒÉÎÔÅÒÏ×, ÐÏÄËÌÀÞÅÎÎÙÈ Ë ÓÅÒ×ÅÒÕ ÐÅÞÁÔÉ CUPS. üÔÁ ÞÁÓÔØ ÐÒÏÃÅÓÓÁ ÏÞÅÎØ ÐÏÈÏÖÁ, ÅÓÌÉ ÎÅ ÉÄÅÎÔÉÞÎÁ ÎÁÓÔÒÏÊËÅ ÐÒÉÎÔÅÒÏ× CUPS × ÄÒÕÇÉÈ &unix;-ÐÏÄÏÂÎÙÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍÁÈ, ÔÁËÉÈ ËÁË ÄÉÓÔÒÉÂÕÔÉ×Ù &linux;. ïÓÎÏ×ÎÙÍ ÓÐÏÓÏÂÏÍ ÕÐÒÁ×ÌÅÎÉÑ É ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ÓÅÒ×ÅÒÁ CUPS Ñ×ÌÑÅÔÓÑ ×ÅÂ-ÉÎÔÅÒÆÅÊÓ, ÎÁ ËÏÔÏÒÙÊ ÍÏÖÎÏ ÐÏÐÁÓÔØ ÚÁÐÕÓÔÉ× ×ÅÂ-ÂÒÁÕÚÅÒ É ÎÁÂÒÁ× × ÅÇÏ ÁÄÒÅÓÎÏÊ ÓÔÒÏËÅ. åÓÌÉ ÓÅÒ×ÅÒ CUPS ÎÁÈÏÄÉÔÓÑ ÎÁ ÄÒÕÇÏÊ ÍÁÛÉÎÅ × ÓÅÔÉ, ÚÁÍÅÎÉÔÅ localhost ÎÁ IP ÁÄÒÅÓ ÓÅÒ×ÅÒÁ. ÷ÅÂ-ÉÎÔÅÒÆÅÊÓ CUPS ÄÏÓÔÁÔÏÞÎÏ ÏÞÅ×ÉÄÅÎ, ÔÁÍ ÅÓÔØ ÒÁÚÄÅÌÙ ÄÌÑ ÕÐÒÁ×ÌÅÎÉÑ ÐÒÉÎÔÅÒÁÍÉ É ÚÁÄÁÎÉÑÍÉ ÎÁ ÐÅÞÁÔØ, Á×ÔÏÒÉÚÁÃÉÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ É Ô.Ð. ëÒÏÍÅ ÔÏÇÏ, × ÐÒÁ×ÏÊ ÞÁÓÔÉ ÓÔÒÁÎÉÃÙ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ÅÓÔØ ÎÅÓËÏÌØËÏ ÆÌÁÖËÏ× (check-box), ÄÁÀÝÉÈ ÕÄÏÂÎÙÊ ÄÏÓÔÕÐ Ë ÞÁÓÔÏ ÍÅÎÑÅÍÙÍ ÕÓÔÁÎÏ×ËÁÍ, ÔÁËÉÍ ËÁË ÒÁÚÒÅÛÅÎÉÅ ÐÕÂÌÉÞÎÏÇÏ ÄÏÓÔÕÐÁ Ë ÐÏÄËÌÀÞÅÎÎÙÍ Ë ÓÉÓÔÅÍÅ ÐÒÉÎÔÅÒÁÍ, ÐÒÅÄÏÓÔÁ×ÌÅÎÉÅ ÕÄÁÌÅÎÎÏÇÏ ÕÐÒÁ×ÌÅÎÉÑ ÓÅÒ×ÅÒÏÍ CUPS, ÉÚÍÅÎÅÎÉÅ ÕÒÏ×ÎÑ ÄÏÓÔÕÐÁ ÐÏÌØÚÏ×ÁÔÅÌÅÊ Ë ÐÒÉÎÔÅÒÁÍ É ÉÈ ÚÁÄÁÎÉÑÍ ÎÁ ÐÅÞÁÔØ. äÏÂÁ×ÌÅÎÉÅ ÐÒÉÎÔÅÒÁ × ÏÂÝÅÍ ÔÁËÏÅ ÖÅ ÐÒÏÓÔÏÅ, ËÁË ÎÁÖÁÔÉÅ Add Printer ÎÁ ÓÔÒÁÎÉÃÅ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ×ÅÂ-ÉÎÔÅÒÆÅÊÓÁ ÓÅÒ×ÅÒÁ CUPS ÉÌÉ ËÁË ÎÁÖÁÔÉÅ ÏÄÎÏÊ ÉÚ ËÎÏÐÏË New Printers Found ÎÁ ÔÏÊ ÖÅ ÓÔÒÁÎÉÃÅ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ. ëÏÇÄÁ ÐÅÒÅÄ ×ÁÍÉ ÐÒÅÄÓÔÁÎÅÔ ×ÙÐÁÄÁÀÝÉÊ ÓÐÉÓÏË Device, ÐÒÏÓÔÏ ×ÙÂÅÒÉÔÅ ÔÒÅÂÕÅÍÙÊ ÌÏËÁÌØÎÏ ÐÏÄËÌÀÞÅÎÎÙÊ ÐÒÉÎÔÅÒ, Á ÄÁÌØÛÅ ÓÌÅÄÕÊÔÅ ÐÏÄÓËÁÚËÁÍ ÉÎÔÅÒÆÅÊÓÁ. ÷ ÓÌÕÞÁÅ ÅÓÌÉ ÂÙÌÉ ÕÓÔÁÎÏ×ÌÅÎÙ ÐÏÒÔÙ ÉÌÉ ÐÁËÅÔÙ print/gutenprint-cups ÉÌÉ print/hplip, ËÁË ÕËÁÚÙ×ÁÌÏÓØ ×ÙÛÅ, ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÄÒÁÊ×ÅÒÁ ÐÅÞÁÔÉ ÂÕÄÕÔ ÄÏÓÔÕÐÎÙ ÎÁ ÐÏÓÌÅÄÕÀÝÉÈ ÓÔÒÁÎÉÃÁÈ, ÞÔÏ ÍÏÖÅÔ ÏÂÅÓÐÅÞÉÔØ ÂÏÌØÛÕÀ ÎÁÄÅÖÎÏÓÔØ É ÒÁÓÛÉÒÅÎÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ. ëÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÅ ËÌÉÅÎÔÏ× CUPS ðÏÓÌÅ ÔÏÇÏ, ËÁË ÓÅÒ×ÅÒ CUPS ÂÙÌ ÎÁÓÔÒÏÅÎ, ÐÒÉÎÔÅÒÙ ÄÏÂÁ×ÌÅÎÙ É ÓÄÅÌÁÎÙ ÄÏÓÔÕÐÎÙÍÉ × ÓÅÔÉ, ÓÌÅÄÕÀÝÉÊ ÛÁÇ — ÜÔÏ ÎÁÓÔÒÏÊËÁ ËÌÉÅÎÔÏ× ÉÌÉ ÍÁÛÉÎ, ËÏÔÏÒÙÅ ÂÕÄÕÔ ÉÍÅÔØ ÄÏÓÔÕÐ Ë ÓÅÒ×ÅÒÕ CUPS. åÓÌÉ Õ ×ÁÓ ÅÄÉÎÓÔ×ÅÎÎÙÊ ÎÁÓÔÏÌØÎÙÊ ËÏÍÐØÀÔÅÒ, ËÏÔÏÒÙÊ ÒÁÂÏÔÁÅÔ ÏÄÎÏ×ÒÅÍÅÎÎÏ É ÓÅÒ×ÅÒÏÍ É ËÌÉÅÎÔÏÍ, ÔÏ × ÂÏÌØÛÉÎÓÔ×Å ÜÔÏÊ ÉÎÆÏÒÍÁÃÉÉ ×Ù ÎÅ ÎÕÖÄÁÅÔÅÓØ. &unix; ËÌÉÅÎÔÙ îÁ &unix; ËÌÉÅÎÔÁÈ ÔÁËÖÅ ÐÏÔÒÅÂÕÅÔÓÑ ÕÓÔÁÎÏ×ÉÔØ CUPS. ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ ÐÅÞÁÔÉ ÎÁ ËÌÉÅÎÔÅ, CUPS-ÐÒÉÎÔÅÒÙ, ÐÒÉÓÕÔÓÔ×ÕÀÝÉÅ × ÓÅÔÉ, ÞÁÝÅ ×ÓÅÇÏ Á×ÔÏÍÁÔÉÞÅÓËÉ ÎÁÈÏÄÑÔÓÑ ÍÅÎÅÄÖÅÒÁÍÉ ÐÒÉÎÔÅÒÏ× ÒÁÚÎÙÈ ÇÒÁÆÉÞÅÓËÉÈ ÏÂÏÌÏÞÅË, ÔÁËÉÈ ËÁË GNOME ÉÌÉ KDE. ÷ ËÁÞÅÓÔ×Å ÁÌØÔÅÒÎÁÔÉ×Ù, ×Ù ÍÏÖÅÔÅ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ×ÅÂ-ÉÎÔÅÒÆÅÊÓÏÍ CUPS ÎÁ ËÌÉÅÎÔÓËÏÊ ÍÁÛÉÎÅ ÐÏ ÁÄÒÅÓÕ É ÎÁ ÓÔÒÁÎÉÃÅ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ×ÙÂÒÁÔØ Add Printer. ëÏÇÄÁ ÐÅÒÅÄ ×ÁÍÉ ÐÒÅÄÓÔÁÎÅÔ ×ÙÐÁÄÁÀÝÉÊ ÓÐÉÓÏË Device, ÐÒÏÓÔÏ ×ÙÂÅÒÉÔÅ ÓÅÔÅ×ÏÊ CUPS ÐÒÉÎÔÅÒ, ÅÓÌÉ ÏÎ ÂÙÌ ÏÂÎÁÒÕÖÅÎ Á×ÔÏÍÁÔÉÞÅÓËÉ, ÉÌÉ ×ÙÂÅÒÉÔÅ ipp ÉÌÉ http É ××ÅÄÉÔÅ IPP ÉÌÉ HTTP ÁÄÒÅÓ (URI) ÓÅÔÅ×ÏÇÏ CUPS ÐÒÉÎÔÅÒÁ: ipp://server-name-or-ip/printers/printername http://server-name-or-ip:631/printers/printername åÓÌÉ CUPS ËÌÉÅÎÔ ÎÅ ÎÁÈÏÄÉÔ × ÓÅÔÉ ÐÒÉÎÔÅÒÙ, ÄÏÓÔÕÐÎÙÅ ÞÅÒÅÚ ÓÅÒ×ÅÒ CUPS, ÔÏ ÉÎÏÇÄÁ ÐÏÍÏÇÁÅÔ ÓÏÚÄÁÎÉÅ ÉÌÉ ÉÚÍÅÎÅÎÉÅ ÆÁÊÌÁ /usr/local/etc/cups/client.conf Ó ÄÏÂÁ×ÌÅÎÉÅÍ ÅÄÉÎÓÔ×ÅÎÎÏÊ ÚÁÐÉÓÉ, ÐÏÄÏÂÎÏÊ ÓÌÅÄÕÀÝÅÊ: ServerName server-ip ÷ ÜÔÏÍ ÓÌÕÞÁÅ server-ip ÎÅÏÂÈÏÄÉÍÏ ÚÁÍÅÎÉÔØ ÎÁ IP ÁÄÒÅÓ ÓÅÒ×ÅÒÁ CUPS × ÓÅÔÉ. &windows;-ËÌÉÅÎÔÙ ÷ÅÒÓÉÉ &windows;, ÐÒÅÄÛÅÓÔ×ÕÀÝÉÅ XP, ÎÅ ÉÍÅÌÉ ×ÓÔÒÏÅÎÎÏÊ ÐÏÄÄÅÒÖËÉ ÐÒÏÔÏËÏÌÁ IPP. ïÄÎÁËÏ &windowsxp; É ÂÏÌÅÅ ÐÏÚÄÎÉÅ ×ÅÒÓÉÉ ÕÖÅ ÏÂÌÁÄÁÀÔ ÔÁËÏÊ ×ÏÚÍÏÖÎÏÓÔØÀ. óÌÅÄÏ×ÁÔÅÌØÎÏ, ÄÏÂÁ×ÉÔØ CUPS ÐÒÉÎÔÅÒ × ÜÔÉÈ ×ÅÒÓÉÑÈ &windows; ÄÏ×ÏÌØÎÏ ÐÒÏÓÔÏ. ÷ ÂÏÌØÛÉÎÓÔ×Å ÓÌÕÞÁÅ×, ÁÄÍÉÎÉÓÔÒÁÔÏÒÕ &windows; ÐÏÔÒÅÂÕÅÔÓÑ ÚÁÐÕÓÔÉÔØ ÍÁÓÔÅÒÁ ÕÓÔÁÎÏ×ËÉ ÐÒÉÎÔÅÒÁ (Add Printer) ×ÙÂÒÁÔØ ÓÅÔÅ×ÏÊ ÐÒÉÎÔÅÒ (Network Printer), Á ÚÁÔÅÍ ××ÅÓÔÉ URI ÓÌÅÄÕÀÝÅÇÏ ÆÏÒÍÁÔÁ: http://server-name-or-ip:631/printers/printername åÓÌÉ ÉÓÐÏÌØÚÕÅÔÓÑ ×ÅÒÓÉÑ &windows; ÂÅÚ ÐÏÄÄÅÒÖËÉ ÐÒÏÔÏËÏÌÁ IPP, ÔÏ ÏÂÝÉÍ ÓÌÕÞÁÅÍ ÐÏÄËÌÀÞÅÎÉÑ Ë CUPS-ÐÒÉÎÔÅÒÕ ÂÕÄÅÔ ÓÏ×ÍÅÓÔÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ CUPS É net/samba3. ïÐÉÓÁÎÉÅ ÜÔÏÊ ×ÏÚÍÏÖÎÏÓÔÉ ×ÙÈÏÄÉÔ ÚÁ ÒÁÍËÉ ÄÁÎÎÏÊ ÓÔÁÔØÉ. õÓÔÒÁÎÅÎÉÅ ÎÅÐÏÌÁÄÏË Ó CUPS ðÒÏÂÌÅÍÙ c CUPS ÞÁÓÔÏ ×ÏÚÎÉËÁÀÔ ÉÚ-ÚÁ ÎÅ×ÅÒÎÙÈ ÐÒÁ× ÄÏÓÔÕÐÁ. óÎÁÞÁÌÁ Ä×ÁÖÄÙ ÐÒÏ×ÅÒØÔÅ ÐÒÁ×Á ÄÏÓÔÕÐÁ × &man.devfs.8; (Ó×ÅÒØÔÅÓØ Ó ÕÖÅ ÏÐÉÓÁÎÎÙÍÉ ×ÙÛÅ). úÁÔÅÍ, ÐÒÏ×ÅÒØÔÅ ÒÅÁÌØÎÙÅ ÐÒÁ×Á ÕÓÔÒÏÊÓÔ×, ÓÏÚÄÁÎÎÙÈ × ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÅ. ôÁËÖÅ ÂÙ×ÁÅÔ ÐÏÌÅÚÎÙÍ ÕÄÏÓÔÏ×ÅÒÉÔØÓÑ, ÞÔÏ ×ÁÛ ÐÏÌØÚÏ×ÁÔÅÌØ ×ÈÏÄÉÔ × ÇÒÕÐÐÕ cups. åÓÌÉ Õ ×ÁÓ ÓËÌÁÄÙ×ÁÅÔÓÑ ×ÐÅÞÁÔÌÅÎÉÅ, ÞÔÏ ÆÌÁÖËÉ ÐÒÁ× ÄÏÓÔÕÐÁ ÎÁ ÓÔÒÁÎÉÃÅ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ×ÅÂ-ÉÎÔÅÒÆÅÊÓÁ CUPS ÎÅ ÒÁÂÏÔÁÀÔ, ÔÏ ÉÎÙÍ ÒÅÛÅÎÉÅÍ ÍÏÖÅÔ ÂÙÔØ ÒÅÚÅÒ×ÎÏÅ ËÏÐÉÒÏ×ÁÎÉÅ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÇÏ ÆÁÊÌÁ /usr/local/etc/cups/cupsd.conf É ÒÅÄÁËÔÉÒÏ×ÁÎÉÅ ÒÁÚÎÙÈ ÏÐÃÉÊ ËÏÎÆÉÇÕÒÁÃÉÉ Ó ÐÏÄÂÏÒÏÍ ÉÈ ËÏÍÂÉÎÁÃÉÊ. îÉÖÅ ÐÒÉ×ÅÄÅÎÏ ÓÏÄÅÒÖÉÍÏÅ ÔÅÓÔÏ×ÏÇÏ ÆÁÊÌÁ ËÏÎÆÉÇÕÒÁÃÉÉ /usr/local/etc/cups/cupsd.conf. ðÏÖÁÌÕÊÓÔÁ, ÏÂÒÁÔÉÔÅ ×ÎÉÍÁÎÉÅ ÎÁ ÔÏ, ÞÔÏ ÂÅÚÏÐÁÓÎÏÓÔØ × ÜÔÏÍ ÐÒÉÍÅÒÅ cupsd.conf ÂÙÌÁ ÐÏÖÅÒÔ×Ï×ÁÎÁ × ÕÇÏÄÕ ÐÒÏÓÔÏÔÅ ÎÁÓÔÒÏÊËÉ; ËÁË ÔÏÌØËÏ ÁÄÍÉÎÉÓÔÒÁÔÏÒ ÕÓÐÅÛÎÏ ÐÏÄÓÏÅÄÉÎÉÔÓÑ Ë ÓÅÒ×ÅÒÕ CUPS É ÓËÏÎÆÉÇÕÒÉÒÕÅÔ ËÌÉÅÎÔÏ×, ÒÅËÏÍÅÎÄÕÅÔÓÑ ÐÅÒÅÓÍÏÔÒÅÔØ ÄÁÎÎÕÀ ËÏÎÆÉÇÕÒÁÃÉÀ É ÄÏÂÁ×ÉÔØ ÒÁÚÇÒÁÎÉÞÅÎÉÅ ÄÏÓÔÕÐÁ. # Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel info # Administrator user group... SystemGroup wheel # Listen for connections on Port 631. Port 631 #Listen localhost:631 Listen /var/run/cups.sock # Show shared printers on the local network. Browsing On BrowseOrder allow,deny #BrowseAllow @LOCAL BrowseAllow 192.168.1.* # change to local LAN settings BrowseAddress 192.168.1.* # change to local LAN settings # Default authentication type, when authentication is required... DefaultAuthType Basic DefaultEncryption Never # comment this line to allow encryption # Allow access to the server from any machine on the LAN <Location /> Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Allow access to the admin pages from any machine on the LAN <Location /admin> #Encryption Required Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Allow access to configuration files from any machine on the LAN <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny #Allow localhost Allow 192.168.1.* # change to local LAN settings </Location> # Set the default printer/job policies... <Policy default> # Job-related operations must be done by the owner or an adminstrator... <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs \ Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription \ Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job \ CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> # All administration operations require an adminstrator to authenticate... <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer \ Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs \ Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer \ Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class \ CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default> AuthType Basic Require user @SYSTEM Order deny,allow </Limit> # Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> <Limit All> Order deny,allow </Limit> </Policy> îÁÓÔÒÏÊËÁ ÐÏÒÔÏ× ÉÓÐÏÌØÚÕÀÝÉÈ CUPS åÓÌÉ CUPS ÂÕÄÅÔ ÓÌÕÖÉÔØ × ËÁÞÅÓÔ×Å ÏÓÎÏ×ÎÏÊ ÓÉÓÔÅÍÙ ÐÅÞÁÔÉ, ÔÏ ÍÏÖÎÏ ÐÏ ÖÅÌÁÎÉÀ ÄÏÂÁ×ÉÔØ ÎÅÓËÏÌØËÏ ÚÁÐÉÓÅÊ × /etc/make.conf, ËÏÔÏÒÙÅ ×ÙÄÅÌÑÔ CUPS ÓÒÅÄÉ ÄÒÕÇÉÈ ÓÉÓÔÅÍ. ÷ÏÔ ÎÅËÏÔÏÒÙÅ ÉÚ ÎÉÈ: WITH_CUPS=YES CUPS_OVERWRITE_BASE=YES WITHOUT_LPR=YES ðÅÒ×ÁÑ ÐÅÒÅÍÅÎÎÁÑ, WITH_CUPS, ÄÏÂÁ×ÌÑÅÔ ÐÏÄÄÅÒÖËÕ CUPS Ë ÐÏÒÔÁÍ, × ËÏÔÏÒÙÈ ÐÒÅÄÕÓÍÏÔÒÅÎÁ ÔÁËÁÑ ×ÏÚÍÏÖÎÏÓÔØ. ÷ÔÏÒÁÑ ÚÁÐÉÓØ, CUPS_OVERWRITE_BASE, ÉÓÐÒÁ×ÉÔ ÎÅËÏÔÏÒÙÅ ÓÉÍ×ÏÌÉÞÅÓËÉÅ ÓÓÙÌËÉ É ÐÕÔÉ, ËÏÔÏÒÙÅ ÉÎÁÞÅ ÐÒÉ×ÏÄÉÌÉ-ÂÙ Ë ÓÉÓÔÅÍÅ ÐÅÞÁÔÉ &os; ÐÏ ÕÍÏÌÞÁÎÉÀ — LPR. ôÁËÖÅ ÏÎÁ ÐÒÅÄÏÔ×ÒÁÔÉÔ ÏÔËÁÔ ÜÔÉÈ ÉÚÍÅÎÅÎÉÊ ×Ï ×ÒÅÍÑ ÓÌÅÄÕÀÝÅÇÏ ÏÂÎÏ×ÌÅÎÉÑ ÓÉÓÔÅÍÙ ÐÏÓÒÅÄÓÔ×ÏÍ buildworld. ôÒÅÔØÑ ÐÅÒÅÍÅÎÎÁÑ, WITHOUT_LPR, ÐÒÅÄÏÔ×ÒÁÔÉÔ ×ËÌÀÞÅÎÉÅ ÐÏÄÄÅÒÖËÉ LPR × ÐÏÒÔÁÈ, ÐÏÔÅÎÃÉÁÌØÎÏ ÅÅ ÉÓÐÏÌØÚÕÀÝÉÈ. + +
diff --git a/ru_RU.KOI8-R/articles/problem-reports/article.xml b/ru_RU.KOI8-R/articles/problem-reports/article.xml index df0c165964..96184e7bff 100644 --- a/ru_RU.KOI8-R/articles/problem-reports/article.xml +++ b/ru_RU.KOI8-R/articles/problem-reports/article.xml @@ -1,1268 +1,1270 @@
óÏÓÔÁ×ÌÅÎÉÅ ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÅ ×Ï &os; $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; $FreeBSD$ üÔÁ ÓÔÁÔØÑ ÏÐÉÓÙ×ÁÅÔ, ËÁË ÎÁÉÌÕÞÛÉÍ ÏÂÒÁÚÏÍ ÓÆÏÒÍÕÌÉÒÏ×ÁÔØ É ÏÔÐÒÁ×ÉÔØ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ × ðÒÏÅËÔ &os;. Dag-Erling Smørgrav ôÅËÓÔ ÐÒÅÄÏÓÔÁ×ÉÌ Mark Linimon ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ
÷×ÅÄÅÎÉÅ ïÄÎÏÊ ÉÚ ÓÁÍÙÈ ÒÁÚÏÞÁÒÏ×Ù×ÁÀÝÉÈ ÐÒÁËÔÉË, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ × ËÁÞÅÓÔ×Å ÐÏÌØÚÏ×ÁÔÅÌÑ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, Ñ×ÌÑÅÔÓÑ ÏÔÐÒÁ×ËÁ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ, ËÏÔÏÒÏÅ ×ÓËÏÒÅ ÚÁËÒÙ×ÁÅÔÓÑ Ó ËÒÁÔËÉÍ É ÎÉÞÅÍÕ ÎÅ ÐÏÍÏÇÁÀÝÉÍ ÏÂßÑÓÎÅÎÉÅÍ ÔÉÐÁ ÜÔÏ ÎÅ ÐÒÏÂÌÅÍÁ ÉÌÉ ÎÅÐÒÁ×ÉÌØÎÏÅ PR. ðÏÄÏÂÎÙÍ ÖÅ ÏÂÒÁÚÏÍ ÏÄÎÏÊ ÉÚ ÓÁÍÙÈ ÒÁÚÏÞÁÒÏ×Ù×ÁÀÝÉÈ ÐÒÁËÔÉË, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ × ËÁÞÅÓÔ×Å ÒÁÚÒÁÂÏÔÞÉËÁ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, Ñ×ÌÑÅÔÓÑ ÐÏÌÕÞÅÎÉÅ ÍÁÓÓÙ ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÁÈ, ËÏÔÏÒÙÅ ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÎÅ Ñ×ÌÑÀÔÓÑ ÓÏÏÂÝÅÎÉÑÍÉ Ï ÐÒÏÂÌÅÍÁÈ, Á ÚÁÐÒÏÓÁÍÉ ÎÁ ÐÏÌÕÞÅÎÉÅ ÐÏÄÄÅÒÖËÉ, ÉÌÉ ËÏÔÏÒÙÅ ÓÏÄÅÒÖÁÔ ÍÁÌÏ ÉÌÉ ×ÏÏÂÝÅ ÎÅ ÓÏÄÅÒÖÁÔ ÎÉËÁËÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÓÕÔÉ ÐÒÏÂÌÅÍÙ ÉÌÉ ÓÐÏÓÏÂÅ ÅÅ ×ÏÓÐÒÏÉÚ×ÅÄÅÎÉÑ. ÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÄÅÌÁÅÔÓÑ ÐÏÐÙÔËÁ ÏÐÉÓÁÔØ ÔÏ, ËÁË ÓÏÓÔÁ×ÌÑÔØ ÈÏÒÏÛÉÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ. þÔÏ ÖÅ, ÓÐÒÏÓÉÔÅ ×Ù, Ñ×ÌÑÅÔÓÑ ÈÏÒÏÛÉÍ ÓÏÏÂÝÅÎÉÅÍ Ï ÐÒÏÂÌÅÍÅ? îÕ, ÅÓÌÉ ÐÅÒÅÊÔÉ ÐÒÑÍÏ Ë ÓÕÔÉ, ÔÏ ÈÏÒÏÛÉÍ ÓÏÏÂÝÅÎÉÅÍ Ï ÐÒÏÂÌÅÍÅ Ñ×ÌÑÅÔÓÑ ÔÏ, ËÏÔÏÒÏÅ ÍÏÖÅÔ ÂÙÔØ ÂÙÓÔÒÏ ÐÒÏÁÎÁÌÉÚÉÒÏ×ÁÎÏ É ÏÔÒÁÂÏÔÁÎÏ, Ë ÏÂÏÀÄÎÏÍÕ ÕÄÏ×ÌÅÔ×ÏÒÅÎÉÀ ËÁË ÐÏÌØÚÏ×ÁÔÅÌÑ, ÔÁË É ÒÁÚÒÁÂÏÔÞÉËÁ. èÏÔÑ × ÏÓÎÏ×ÎÏÍ ÓÔÁÔØÑ ÆÏËÕÓÉÒÕÅÔÓÑ ÎÁ ÓÏÏÂÝÅÎÉÑÈ Ï ÐÒÏÂÌÅÍÁÈ ×Ï &os;, ÂÏÌØÛÅÊ ÞÁÓÔØÀ ÏÎÁ ÄÏÌÖÎÁ ÈÏÒÏÛÏ ÐÏÄÈÏÄÉÔØ É ÄÒÕÇÉÍ ÐÒÏÇÒÁÍÍÎÙÍ ÐÒÏÅËÔÁÍ. úÁÍÅÔØÔÅ, ÞÔÏ ÜÔÁ ÓÔÁÔØÑ ÏÒÇÁÎÉÚÏ×ÁÎÁ ÐÏ ÔÅÍÁÔÉÞÅÓËÏÍÕ ÐÒÉÎÃÉÐÕ, Á ÎÅ ÈÒÏÎÏÌÏÇÉÞÅÓËÉ, ÔÁË ÞÔÏ ×Ù ÄÏÌÖÎÙ ÐÒÏÞÅÓÔØ ÄÏËÕÍÅÎÔ ÃÅÌÉËÏÍ ÐÒÅÖÄÅ, ÞÅÍ ÐÏÓÙÌÁÔØ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ, É ÎÅ ×ÏÓÐÒÉÎÉÍÁÔØ ÓÔÁÔØÀ ËÁË ÐÏÛÁÇÏ×ÏÅ ÒÕËÏ×ÏÄÓÔ×Ï.
ëÏÇÄÁ ÎÕÖÎÏ ÏÔÐÒÁ×ÌÑÔØ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ éÍÅÅÔÓÑ ÍÎÏÇÏ ËÌÁÓÓÏ× ÏÛÉÂÏË, É ÎÅ ×ÓÅ ÏÎÉ ÄÏÌÖÎÙ ÐÒÉ×ÏÄÉÔØ Ë ÐÏÑ×ÌÅÎÉÀ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ. ëÏÎÅÞÎÏ ÖÅ, ÎÅÔ ÉÄÅÁÌØÎÙÈ ÌÀÄÅÊ, É ÂÕÄÕÔ ÍÏÍÅÎÔÙ, ËÏÇÄÁ ×Ù ÒÅÛÉÔÅ, ÞÔÏ ÎÁÛÌÉ ÏÛÉÂËÕ × ÐÒÏÇÒÁÍÍÅ, Á ÎÁ ÓÁÍÏÍ ÄÅÌÅ ×Ù ÎÅÐÒÁ×ÉÌØÎÏ ÐÏÎÑÌÉ ÓÉÎÔÁËÓÉÓ ËÏÍÁÎÄÙ ÉÌÉ ÓÄÅÌÁÌÉ ÏÐÅÞÁÔËÕ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ (ÈÏÔÑ ÓÁÍÏ ÐÏ ÓÅÂÅ ÜÔÏ ÉÎÏÇÄÁ ÇÏ×ÏÒÉÔ Ï ÐÌÏÈÏÊ ÄÏËÕÍÅÎÔÁÃÉÉ ÉÌÉ ÎÅÐÒÁ×ÉÌØÎÏÊ ÏÂÒÁÂÏÔËÅ ÏÛÉÂÏË × ÐÒÉËÌÁÄÎÏÊ ÐÒÏÇÒÁÍÍÅ). åÓÔØ ÅÝÅ ÍÎÏÇÏ ÓÌÕÞÁÅ×, ËÏÇÄÁ ÐÏÓÙÌËÁ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ Ñ×ÎÏ ÎÅ Ñ×ÌÑÅÔÓÑ ÐÒÁ×ÉÌØÎÙÍ ÄÅÊÓÔ×ÉÅÍ, Á ÔÏÌØËÏ ÐÒÉ×ÏÄÉÔ Ë ÒÁÚÏÞÁÒÏ×ÁÎÉÀ ×ÁÓ É ÒÁÚÒÁÂÏÔÞÉËÏ×. é ÎÁÏÂÏÒÏÔ, ÅÓÔØ ÓÌÕÞÁÉ, ËÏÇÄÁ ÍÏÖÅÔ ÂÙÔØ ÎÕÖÎÏ ÐÏÓÌÁÔØ ÓÏÏÂÝÅÎÉÅ Ï ÞÅÍ-ÔÏ, ÎÅ Ñ×ÌÑÀÝÅÍÓÑ ÏÛÉÂËÏÊ — Ë ÐÒÉÍÅÒÕ, ÚÁÐÒÏÓ ÎÁ ÄÏÒÁÂÏÔËÕ ÉÌÉ ÒÁÓÛÉÒÅÎÉÅ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔÉ. îÏ ËÁË ÖÅ ÏÐÒÅÄÅÌÉÔØ, ÞÔÏ Ñ×ÌÑÅÔÓÑ ÏÛÉÂËÏÊ, Á ÞÔÏ ÎÅÔ? ðÒÏÓÔÙÍ ÐÒÁ×ÉÌÏÍ, ËÏÔÏÒÏÍÕ ÎÕÖÎÏ ÓÌÅÄÏ×ÁÔØ, Ñ×ÌÑÅÔÓÑ ÓÌÅÄÕÀÝÅÅ – ×ÁÛÁ ÐÒÏÂÌÅÍÁ ÎÅ Ñ×ÌÑÅÔÓÑ ÏÛÉÂËÏÊ, ÅÓÌÉ ÏÎÁ ÆÏÒÍÕÌÉÒÕÅÔÓÑ ËÁË ×ÏÐÒÏÓ (ÏÂÙÞÎÏ × ÆÏÒÍÅ ëÁË ÓÄÅÌÁÔØ X? ÉÌÉ çÄÅ ÍÏÖÎÏ ÎÁÊÔÉ Y?). îÅ ×ÓÅÇÄÁ ÜÔÏ ÔÁË ÏÄÎÏÚÎÁÞÎÏ, ÎÏ ÐÒÁ×ÉÌÏ ×ÏÐÒÏÓÁ ÐÏËÒÙ×ÁÅÔ ÂÏÌØÛÉÎÓÔ×Ï ÓÌÕÞÁÅ×. åÓÌÉ ÷ÁÍ ÎÕÖÅÎ ÏÔ×ÅÔ, ÌÕÞÛÅ ×ÓÅÇÏ ÚÁÄÁÔØ Ó×ÏÊ ×ÏÐÒÏÓ × &a.questions;. ÷ÏÔ ÎÅËÏÔÏÒÙÅ ÓÌÕÞÁÉ, × ËÏÔÏÒÙÈ ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÐÏÌÅÚÎÙÍ ÏÔÐÒÁ×ÉÔØ ÓÏÏÂÝÅÎÉÅ Ï ÞÅÍ-ÔÏ, ÞÔÏ ÎÅ Ñ×ÌÑÅÔÓÑ ÏÛÉÂËÏÊ: õ×ÅÄÏÍÌÅÎÉÅ Ï ÏÂÎÏ×ÌÅÎÉÉ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, ËÏÔÏÒÏÅ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ ÓÔÏÒÏÎÎÉÍÉ ÒÁÚÒÁÂÏÔÞÉËÁÍÉ (× ÏÓÎÏ×ÎÏÍ ÐÏÒÔÙ, ÎÏ ÔÁËÖÅ É ËÏÍÐÏÎÅÎÔÙ ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÙ, ÒÁÚÒÁÂÁÔÙ×ÁÅÍÙÅ ÓÔÏÒÏÎÎÉÍÉ ÏÒÇÁÎÉÚÁÃÉÑÍÉ, ÔÁËÉÅ, ËÁË BIND ÉÌÉ ÒÁÚÌÉÞÎÙÅ ÕÔÉÌÉÔÙ GNU). äÌÑ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ ÎÉËÅÍ ÐÏÒÔÏ× (ÐÅÒÅÍÅÎÎÁÑ MAINTAINER ÓÏÄÅÒÖÉÔ ports@FreeBSD.org), ÔÁËÉÅ Õ×ÅÄÏÍÌÅÎÉÑ Ï ÏÂÎÏ×ÌÅÎÉÉ ÂÕÄÕÔ ÚÁÍÅÞÅÎÙ ÚÁÉÎÔÅÒÅÓÏ×Á×ÛÉÍÓÑ ËÏÍÍÉÔÔÅÒÏÍ É ×ÁÓ ÍÏÇÕÔ ÐÏÐÒÏÓÉÔØ ÐÒÅÄÏÓÔÁ×ÉÔØ ÐÁÔÞ ÄÌÑ ÏÂÎÏ×ÌÅÎÉÑ ÐÏÒÔÁ; ÐÒÅÄÏÓÔÁ×ÌÅÎÉÅ ÐÁÔÞÁ ÄÏ ÔÏÇÏ, ËÁË ×ÁÓ ÐÏÐÒÏÓÑÔ Ï ÜÔÏÍ ÓÉÌØÎÏ Õ×ÅÌÉÞÉÔ ÛÁÎÓÙ ÔÏÇÏ, ÞÔÏ ÐÏÒÔ ÂÕÄÅÔ ÏÂÎÏ×̣Π×Ï×ÒÅÍÑ. åÓÌÉ ÐÏÒÔ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ, PR-Ù, ÕËÁÚÙ×ÁÀÝÉÅ Ï ÐÏÑ×ÌÅÎÉÉ ÎÏ×ÙÈ ÕÌÕÞÛÅÎÎÙÈ (upstream) ÒÅÌÉÚÏ× ÏÂÙÞÎÏ ÎÅ ÏÞÅÎØ ÐÏÌÅÚÎÙ, ÔÁË ËÁË ÏÎÉ ÐÒÉÂÁ×ÌÑÀÔ ÍÎÏÇÏ ×ÓÐÏÍÏÇÁÔÅÌØÎÏÊ ÒÁÂÏÔÙ ÄÌÑ ËÏÍÍÉÔÔÅÒÏ×, Á ÍÜÊÎÔÅÊÎÅÒ ÎÁ×ÅÒÎÑËÁ ÕÖÅ ÚÎÁÅÔ Ï ÎÏ×ÏÊ ×ÅÒÓÉÉ. ïÎÉ ÕÖÅ ÎÁ×ÅÒÎÑËÁ ÒÁÂÏÔÁÌÉ Ó ÒÁÚÒÁÂÏÔÞÉËÁÍÉ ÎÁÄ ÎÅÊ ÉÌÉ ÏÎÉ ×ÏÚÍÏÖÎÏ ÔÅÓÔÉÒÕÀÔ Å£, ÞÔÏÂÙ ÕÂÅÄÉÔØÓÑ × ÏÔÓÕÔÓÔ×ÉÉ ÒÅÇÒÅÓÓÉÉ É Ô.Ð. ÷ ÌÀÂÏÍ ÓÌÕÞÁÅ, ÓÌÅÄÏ×ÁÎÉÅ ÐÒÏÃÅÓÓÕ, ÏÐÉÓÁÎÎÏÍÕ × òÕËÏ×ÏÄÓÔ×Å ÐÏ ÓÏÚÄÁÎÉÀ ÐÏÒÔÏ× ÄÁÓÔ ÎÁÉÌÕÞÛÉÅ ÒÅÚÕÌØÔÁÔÙ. (ôÁËÖÅ ÍÏÖÎÏ ÏÚÎÁËÏÍÉÔØÓÑ Ó ÓÔÁÔØÅÊ ëÏÎÔÒÉÂÕÃÉÑ × ËÏÌÌÅËÃÉÀ ÐÏÒÔÏ× FreeBSD.) ïÛÉÂËÁ, ËÏÔÏÒÕÀ ÎÅÌØÚÑ ×ÏÓÐÒÏÉÚ×ÅÓÔÉ, ×ÒÑÄ ÌÉ ÂÕÄÅÔ ÉÓÐÒÁ×ÌÅÎÁ. åÓÌÉ ÏÛÉÂËÁ ×ÏÚÎÉËÌÁ ÔÏÌØËÏ ÅÄÉÎÏÖÄÙ, É ×Ù ÎÅ ÍÏÖÅÔÅ ÅÅ ×ÏÓÐÒÏÉÚ×ÅÓÔÉ, Ë ÔÏÍÕ ÖÅ ÎÉËÔÏ Ó ÎÅÊ ÂÏÌØÛÅ ÎÅ ÓÔÁÌËÉ×ÁÌÓÑ, ÎÅÔ ÎÉËÁËÉÈ ÛÁÎÓÏ×, ÞÔÏ ÒÁÚÒÁÂÏÔÞÉËÉ ÓÍÏÇÕÔ ÅÅ ×ÏÓÐÒÏÉÚ×ÅÓÔÉ ÉÌÉ ÐÏÎÑÔØ, ÞÔÏ ÄÅÌÁÅÔÓÑ ÎÅÐÒÁ×ÉÌØÎÏ. üÔÏ ÎÅ ÚÎÁÞÉÔ, ÞÔÏ ÔÁËÏÇÏ ÎÅ ÓÌÕÞÁÅÔÓÑ, ÎÏ ÜÔÏ ÚÎÁÞÉÔ, ÞÔÏ ÛÁÎÓÏ× Õ ×ÁÛÅÇÏ ÓÏÏÂÝÅÎÉÑ ÄÏÊÔÉ ËÏÇÄÁ-ÌÉÂÏ ÄÏ ÓÔÁÄÉÉ ÉÓÐÒÁ×ÌÅÎÉÑ ÏÛÉÂËÉ ÏÞÅÎØ ÍÁÌÙ. þÁÓÔÏ ÜÔÉ ×ÉÄÙ ÏÛÉÂÏË ×ÏÚÎÉËÁÀÔ ÉÚ-ÚÁ ÎÅÕÄÏ×ÌÅÔ×ÏÒÉÔÅÌØÎÏÊ ÒÁÂÏÔÙ Ö£ÓÔËÉÈ ÄÉÓËÏ×, ÐÅÒÅÇÒÅ×ÛÉÈÓÑ ÐÒÏÃÅÓÓÏÒÏ×. ÷ÓÅÇÄÁ, ËÏÇÄÁ ÜÔÏ ×ÏÚÍÏÖÎÏ ×Ù ÄÏÌÖÎÙ ÏÔÓÌÅÖÉ×ÁÔØ ÔÁËÉÅ ÓÌÕÞÁÉ ÐÅÒÅÄ ÐÏÓÙÌËÏÊ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÅ. ôÅÐÅÒØ, ÞÔÏÂÙ ÏÐÒÅÄÅÌÉÔØ ËÏÍÕ ×Ù ÄÏÌÖÎÙ ÏÔÐÒÁ×ÉÔØ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ, ×Ù ÄÏÌÖÎÙ ÐÏÎÉÍÁÔØ, ÞÔÏ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ËÏÔÏÒÏÅ ×ÈÏÄÉÔ ×Ï &os;, ÓÏÓÔÁ×ÌÑÅÔÓÑ ÉÚ ÎÅÓËÏÌØËÉÈ ÒÁÚÌÉÞÎÙÈ ÞÁÓÔÅÊ: ëÏÄ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ, ËÏÔÏÒÙÊ ÐÉÛÅÔÓÑ É ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ ËÏÎÔÒÉÂØÀÔÏÒÁÍÉ &os;. ôÁËÏÊ, ËÁË ÑÄÒÏ, ÂÉÂÌÉÏÔÅËÁ C, ÄÒÁÊ×ÅÒÁ ÕÓÔÒÏÊÓÔ× (×ÈÏÄÑÔ × ËÁÔÅÇÏÒÉÀ kern); ÕÔÉÌÉÔÙ (bin); ÓÔÒÁÎÉÃÙ ÓÐÒÁ×ÏÞÎÉËÁ É ÄÏËÕÍÅÎÔÁÃÉÑ (docs); ×ÅÂ-ÓÔÒÁÎÉÃÙ (www). ÷ÓÅ ÏÛÉÂËÉ × ÜÔÉÈ ÏÂÌÁÓÔÑÈ ÄÏÌÖÎÙ ÂÙÔØ ÓÏÏÂÝÅÎÙ ÒÁÚÒÁÂÏÔÞÉËÁÍ &os;. ëÏÄ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ, ËÏÔÏÒÙÊ ÐÉÛÅÔÓÑ É ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ ÄÒÕÇÉÍ, ÉÍÐÏÒÔÉÒÕÅÔÓÑ ×Ï &os; É ÁÄÁÐÔÉÒÕÅÔÓÑ. ðÒÉÍÅÒÙ ×ËÌÀÞÁÀÔ × ÓÅÂÑ: bind, &man.gcc.1; É &man.sendmail.8;. âÏÌØÛÉÎÓÔ×Ï ÏÛÉÂÏË, ÐÏÐÁÄÁÀÝÉÅ × ÄÁÎÎÙÅ ÏÂÌÁÓÔÉ ÄÏÌÖÎÙ ÂÙÔØ ÓÏÏÂÝÅÎÙ ÒÁÚÒÁÂÏÔÞÉËÁÍ &os;, ÎÏ × ÎÅËÏÔÏÒÙÈ ÓÌÕÞÁÑÈ ÏÎÉ ÄÏÌÖÎÙ ÂÙÔØ ÏÔÐÒÁ×ÌÅÎÙ ÉÚÎÁÞÁÌØÎÙÍ ÒÁÚÒÁÂÏÔÞÉËÁÍ, ÅÓÌÉ ÐÒÏÂÌÅÍÙ ÎÅ Ñ×ÌÑÀÔÓÑ ÓÐÅÃÉÆÉÞÎÙÍÉ ÄÌÑ &os;. ïÂÙÞÎÏ ÏÛÉÂËÉ ÔÁËÏÇÏ ÒÏÄÁ ÐÏÐÁÄÁÀÔ ÐÏÄ ËÁÔÅÇÏÒÉÉ bin ÉÌÉ gnu. ïÔÄÅÌØÎÙÅ ÐÒÉÌÏÖÅÎÉÑ, ÎÅ ×ÈÏÄÑÝÉÅ × ÂÁÚÏ×ÕÀ ÓÉÓÔÅÍÕ, ÎÏ Ñ×ÌÑÀÝÉÅÓÑ ÞÁÓÔØÀ ëÏÌÌÅËÃÉÉ ðÏÒÔÏ× &os; (ËÁÔÅÇÏÒÉÑ ports). âÏÌØÛÉÎÓÔ×Ï ÜÔÉÈ ÐÒÉÌÏÖÅÎÉÊ ÎÅ ÐÉÛÅÔÓÑ ÒÁÚÒÁÂÏÔÞÉËÁÍÉ &os;; ÞÔÏ ÐÒÅÄÏÓÔÁ×ÌÑÅÔ &os;, ÔÁË ÜÔÏ ÔÏÌØËÏ ÌÉÛØ ÉÎÆÒÁÓÔÒÕËÔÕÒÕ ÄÌÑ ÕÓÔÁÎÏ×ËÉ ÐÒÉÌÏÖÅÎÉÑ. óÌÅÄÏ×ÁÔÅÌØÎÏ, ×Ù ÄÏÌÖÎÙ ÏÔÐÒÁ×ÌÑÔØ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ ÒÁÚÒÁÂÏÔÞÉËÁÍ &os; ÔÏÌØËÏ ÔÏÇÄÁ, ËÏÇÄÁ ×Ù Õ×ÅÒÅÎÙ × ÔÏÍ, ÞÔÏ ÐÒÏÂÌÅÍÁ ÓÐÅÃÉÆÉÞÎÁ ÄÌÑ &os; - ÉÎÁÞÅ ÏÔÐÒÁ×ÌÑÊÔŠţ Á×ÔÏÒÁÍ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ. úÁÔÅÍ ×Ù ÄÏÌÖÎÙ ÕÂÅÄÉÔØÓÑ, ÄÅÊÓÔ×ÉÔÅÌØÎÏ ÌÉ ÐÒÏÂÌÅÍÁ ÓÕÝÅÓÔ×ÕÅÔ. óÕÝÅÓÔ×ÕÅÔ ×ÓÅÇÏ ÎÅÓËÏÌØËÏ ×ÅÝÅÊ, ËÏÔÏÒÙÅ ÒÁÚÄÒÁÖÁÀÔ ÒÁÚÒÁÂÏÔÞÉËÁ ÂÏÌØÛÅ, ÞÅÍ ÐÏÌÕÞÅÎÉÅ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÅ, ËÏÔÏÒÕÀ ÏÎ ÕÖÅ ÉÓÐÒÁ×ÉÌ. åÓÌÉ ÐÒÏÂÌÅÍÁ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ, ÔÏ ×ÁÍ ÎÕÖÎÏ ÓÎÁÞÁÌÁ ÐÒÏÞÅÓÔØ ÒÁÚÄÅÌ ×ÅÒÓÉÉ &os; ÉÚ FAQ, ÅÓÌÉ ×Ù ÅÝ£ ÎÅ ÚÎÁËÏÍÙ Ó ÄÁÎÎÏÊ ÔÅÍÏÊ. äÌÑ &os; ×ÏÚÍÏÖÎÏ ÉÓÐÒÁ×ÌÑÔØ ÐÒÏÂÌÅÍÙ ÔÏÌØËÏ ÄÌÑ ÎÅËÏÔÏÒÙÈ ÎÅÄÁ×ÎÉÈ ×ÅÔÏË ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÙ, ÐÏÜÔÏÍÕ ÏÔÐÒÁ×ËÁ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÅ ÄÌÑ ÂÏÌÅÅ ÓÔÁÒÏÊ ×ÅÒÓÉÉ ÐÒÉ×ÅÄ£Ô Ë ÔÏÍÕ, ÞÔÏ ÒÁÚÒÁÂÏÔÞÉË ÐÏÓÏ×ÅÔÕÅÔ ×ÁÍ ÏÂÎÏ×ÉÔØÓÑ ÄÏ ÐÏÄÄÅÒÖÉ×ÁÅÍÏÊ ×ÅÒÓÉÉ, ÞÔÏÂÙ ÐÏÓÍÏÔÒÅÔØ ÐÒÉÓÕÔÓÔ×ÕÅÔ ÌÉ × ÎÅÊ ÐÒÏÂÌÅÍÁ. ëÏÍÁÎÄÁ ÏÆÉÃÅÒÏ× ÂÅÚÏÐÁÓÎÏÓÔÉ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÓÐÉÓÏË ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ ×ÅÒÓÉÊ.. åÓÌÉ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ÐÏÒÔÁÍÉ, ÐÏÍÎÉÔÅ, ÞÔÏ ×Ù ÓÎÁÞÁÌÁ ÄÏÌÖÎÙ ÏÂÎÏ×ÉÔØÓÑ ÄÏ ÓÁÍÏÊ ÐÏÓÌÅÄÎÅÊ ×ÅÒÓÉÉ ëÏÌÌÅËÃÉÉ ðÏÒÔÏ× É ÐÒÏ×ÅÒÉÔØ, ÓÕÝÅÓÔ×ÕÅÔ ÌÉ × ÎÅÊ ÐÒÏÂÌÅÍÁ. éÚ-ÚÁ ÂÙÓÔÒÙÈ ×ÎÅÓÅÎÉÊ ÉÚÍÅÎÅÎÉÊ × ÜÔÉ ÐÒÉÌÏÖÅÎÉÑ, ÎÅÏÓÕÝÅÓÔ×ÉÍÙÍ ÄÌÑ &os; Ñ×ÌÑÅÔÓÑ ÐÏÄÄÅÒÖËÁ ÞÅÇÏ-ÌÉÂÏ, ËÒÏÍÅ ÓÁÍÙÈ ÐÏÓÌÅÄÎÉÈ ×ÅÒÓÉÊ, É ÐÒÏÂÌÅÍÙ ÓÏ ÕÓÔÁÒÅ×ÛÉÍÉ ×ÅÒÓÉÑÍÉ ÐÒÉÌÏÖÅÎÉÊ ÐÒÏÓÔÏ ÎÅ ÍÏÇÕÔ ÂÙÔØ ÉÓÐÒÁ×ÌÅÎÙ.
ðÏÄÇÏÔÏ×ËÁ îÕÖÎÏ ÓÌÅÄÏ×ÁÔØ ÈÏÒÏÛÅÍÕ ÐÒÁ×ÉÌÕ ×ÓÅÇÄÁ ÓÎÁÞÁÌÁ ×ÙÐÏÌÎÑÔØ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÉÓÓÌÅÄÏ×ÁÎÉÑ ÐÅÒÅÄ ÔÅÍ, ËÁË ÐÏÓÌÁÔØ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ. íÏÖÅÔ ÂÙÔØ, Ï ×ÁÛÅÊ ÐÒÏÂÌÅÍÅ ÕÖÅ ÓÏÏÂÝÅÎÏ; ÍÏÖÅÔ ÂÙÔØ, ÏÎÁ ÎÅÄÁ×ÎÏ ÏÂÓÕÖÄÁÌÁÓØ ÉÌÉ ÏÂÓÕÖÄÁÅÔÓÑ × ÓÐÉÓËÁÈ ÒÁÓÓÙÌËÉ; ÏÎÁ ÍÏÖÅÔ ÂÙÔØ ÕÖÅ ÉÓÐÒÁ×ÌÅÎÁ × ÂÏÌÅÅ ÎÏ×ÏÊ ×ÅÒÓÉÉ, ÞÅÍ ÔÁ, ÞÔÏ ×Ù ÉÓÐÏÌØÚÕÅÔÅ. ðÏÜÔÏÍÕ ×Ù ÄÏÌÖÎÙ ÐÒÏ×ÅÒÉÔØ ×ÓÅ ÏÂÙÞÎÙÅ ÍÅÓÔÁ ÄÏ ÔÏÇÏ, ËÁË ÐÏÓÌÁÔØ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ. äÌÑ &os; ÜÔÏ ÚÎÁÞÉÔ: &os; FAQ (ïÔ×ÅÔÙ ÎÁ ÞÁÓÔÏ ÚÁÄÁ×ÁÅÍÙÅ ×ÏÐÒÏÓÙ). FAQ ÓÏÄÅÒÖÉÔ ÏÔ×ÅÔÙ ÎÁ ×ÏÐÒÏÓÙ ÉÚ ÓÁÍÙÈ ÒÁÚÎÙÈ ËÁÔÅÇÏÒÉÊ, × ÞÁÓÔÎÏÓÔÉ, ÁÐÐÁÒÁÔÎÏÊ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ, ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÈ ÐÒÏÇÒÁÍÍ É ËÏÎÆÉÇÕÒÁÃÉÉ ÑÄÒÁ. óÐÉÓËÉ ÒÁÓÓÙÌËÉ—ÅÓÌÉ ÷Ù ÎÅ ÐÏÄÐÉÓÁÎÙ ÎÁ ÎÉÈ, ×ÏÓÐÏÌØÚÕÊÔÅÓØ ÐÏÉÓËÏÍ × ÁÒÈÉ×ÁÈ ÎÁ ÓÁÊÔÅ &os;. åÓÌÉ ×ÁÛÁ ÐÒÏÂÌÅÍÁ ÎÅ ÏÂÓÕÖÄÁÌÁÓØ × ÓÐÉÓËÁÈ ÒÁÓÓÙÌËÉ, ×Ù ÍÏÖÅÔÅ ÐÏÐÙÔÁÔØÓÑ ÏÐÕÂÌÉËÏ×ÁÔØ ÓÏÏÂÝÅÎÉÅ Ï ÎÅÊ É ÐÏÄÏÖÄÁÔØ ÎÅÓËÏÌØËÏ ÄÎÅÊ, ÐÏËÁ ËÔÏ-ÎÉÂÕÄØ ÎÅ ÓÍÏÖÅÔ Õ×ÉÄÅÔØ ÔÏ, ÞÔÏ ×Ù ÎÅ ÚÁÍÅÔÉÌÉ. ëÁË ×ÁÒÉÁÎÔ, ×ÅÓØ ×Å—ÉÓÐÏÌØÚÕÊÔÅ ×ÁÛÕ ÌÀÂÉÍÕÀ ÐÏÉÓËÏ×ÕÀ ÓÉÓÔÅÍÕ ÄÌÑ ÐÏÉÓËÁ ËÁËÉÈ-ÌÉÂÏ ÓÓÙÌÏË ÐÏ ×ÁÛÅÊ ÐÒÏÂÌÅÍÅ. ÷Ù ÍÏÖÅÔÅ ÄÁÖÅ Õ×ÉÄÅÔØ ÓÓÙÌËÉ ÎÁ ÁÒÈÉ×Ù ÓÐÉÓËÏ× ÒÁÓÓÙÌËÉ ÉÌÉ ÔÅÌÅËÏÎÆÅÒÅÎÃÉÊ, Ï ËÏÔÏÒÙÈ ×Ù ÎÅ ÚÎÁÌÉ ÉÌÉ ÎÅ ÄÕÍÁÌÉ ÔÁÍ ÉÓËÁÔØ. óÌÅÄÕÀÝÉÍ ÐÕÎËÔÏÍ ÄÏÌÖÎÁ ÂÙÔØ ÂÁÚÁ ÄÁÎÎÙÈ PR &os; (GNATS). åÓÌÉ ÔÏÌØËÏ ×ÁÛÁ ÐÒÏÂÌÅÍÁ ÎÅ ÎÏ×Á ÉÌÉ ÒÅÄËÁ, ÅÓÔØ ÎÅËÏÔÏÒÙÊ ÛÁÎÓ, ÞÔÏ Ï ÎÅÊ ÕÖÅ ÓÏÏÂÝÅÎÏ. é ÓÁÍÏÅ ×ÁÖÎÏÅ, ×Ù ÄÏÌÖÎÙ ÐÏÓÍÏÔÒÅÔØ ÎÅ ÚÁÔÒÁÇÉ×ÁÅÔ ÌÉ ÄÏËÕÍÅÎÔÁÃÉÑ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ ×ÁÛÕ ÐÒÏÂÌÅÍÕ. äÌÑ ÏÓÎÏ×ÎÏÇÏ ËÏÄÁ &os; ×Ù ÄÏÌÖÎÙ ÔÝÁÔÅÌØÎÏ ÉÚÕÞÉÔØ ÓÏÄÅÒÖÉÍÏÅ ÆÁÊÌÁ /usr/src/UPDATING ÉÌÉ ÅÇÏ ÔÅËÕÝÕÀ ×ÅÒÓÉÀ ÐÏ ÁÄÒÅÓÕ . (åÓÌÉ ×Ù ÐÅÒÅÈÏÄÉÔÅ Ó ÏÄÎÏÊ ×ÅÒÓÉÉ ÎÁ ÄÒÕÇÕÀ, ÏÓÏÂÅÎÎÏ ÅÓÌÉ ×Ù ÏÂÎÏ×ÌÑÅÔÅÓØ ÄÏ &os.current;, ÔÏ × ÜÔÏÍ ÆÁÊÌÅ ×Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ÍÎÏÇÏ ×ÁÖÎÏÊ ÉÎÆÏÒÍÁÃÉÉ). åÓÌÉ ÖÅ ×ÁÛÁ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ËÏÌÌÅËÃÉÅÊ ÐÏÒÔÏ× &os;, ×Ù ÄÏÌÖÎÙ ÏÂÒÁÔÉÔØÓÑ Ë ÆÁÊÌÕ /usr/ports/UPDATING (ÉÚÍÅÎÅÎÉÑ, ËÁÓÁÀÝÉÅÓÑ ÉÎÄÉ×ÉÄÕÁÌØÎÙÈ ÐÏÒÔÏ×) ÉÌÉ Ë /usr/ports/CHANGES (ÉÚÍÅÎÅÎÉÑ, ËÁÓÁÀÝÉÅÓÑ ×ÓÅÊ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ×). ïÎÉ ÔÁËÖÅ ÄÏÓÔÕÐÎÙ ÞÅÒÅÚ ÉÎÔÅÒÆÅÊÓ svnweb: É .
îÁÐÉÓÁÎÉÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ ôÅÐÅÒØ, ÐÏÓÌÅ ÔÏÇÏ, ËÁË ×Ù ÒÅÛÉÌÉ, ÞÔÏ ×ÁÛ ×ÏÐÒÏÓ ÐÏÄÐÁÄÁÅÔ ÐÏÄ ËÁÔÅÇÏÒÉÀ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ, É ÜÔÏ ÐÒÏÂÌÅÍÁ &os;, ÓÁÍÏÅ ×ÒÅÍÑ ÎÁÐÉÓÁÔØ ÓÏÂÓÔ×ÅÎÎÏ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ (PR). ðÒÅÖÄÅ ÞÅÍ ÍÙ ÕÇÌÕÂÉÍÓÑ × ÞÁÓÔÎÏÓÔÉ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÓÏÚÄÁÎÉÑ É ÏÔÐÒÁ×ËÉ PR, ×ÏÔ ÎÅÓËÏÌØËÏ ÓÏ×ÅÔÏ×, ËÏÔÏÒÙÅ ÐÏÍÏÇÕÔ ×ÁÍ ÓÄÅÌÁÔØ PR ÂÏÌÅÅ ÜÆÆÅËÔÉ×ÎÙÍ.
ëÁË ÐÉÓÁÔØ ÈÏÒÏÛÉÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ ïÓÎÏ×ÎÙÍ ÑÚÙËÏÍ ÏÂÝÅÎÉÑ ÒÁÚÒÁÂÏÔÞÉËÏ× FreeBSD Ñ×ÌÑÅÔÓÑ ÁÎÇÌÉÊÓËÉÊ. âÁÚÁ ÄÁÎÎÙÈ ÐÏ ÐÒÏÂÌÅÍÁÍ ÔÁËÖÅ ×ÅÄÅÔÓÑ ÎÁ ÁÎÇÌÉÊÓËÏÍ. åÓÌÉ ×Ù ÉÓÐÙÔÙ×ÁÅÔÅ ÐÒÏÂÌÅÍÙ Ó ÆÏÒÍÕÌÉÒÏ×ËÏÊ ÏÐÉÓÁÎÉÑ ÐÒÏÂÌÅÍÙ ÐÏ-ÁÎÇÌÉÊÓËÉ, Ó×ÑÖÉÔÅÓØ ÓÏ Ó×ÏÉÍÉ ÓÏÏÔÅÞÅÓÔ×ÅÎÎÉËÁÍÉ, ËÏÔÏÒÙÅ ÐÏÍÏÇÕÔ ×ÁÍ ÓÏÓÔÁ×ÉÔØ PR. îÅ ÏÓÔÁ×ÌÑÊÔÅ ÐÏÌÅ Synopsis (ËÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ) ÐÕÓÔÙÍ. óÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ ÐÏÐÁÄÁÀÔ ËÁË × ÓÐÉÓËÉ ÒÁÓÓÙÌËÉ, ËÏÔÏÒÙÅ ÚÁÔÅÍ ÒÁÓÈÏÄÑÔÓÑ ÐÏ ×ÓÅÍÕ ÍÉÒÕ (× ÎÉÈ ÐÏÌÅ Synopsis ÏÐÒÅÄÅÌÑÅÔ ÔÅÍÕ ÐÉÓØÍÁ), ÔÁË É × ÂÁÚÕ ÄÁÎÎÙÈ. ðÒÏÓÍÁÔÒÉ×ÁÀÝÉÊ ÜÔÕ ÂÁÚÕ, ËÁË ÐÒÁ×ÉÌÏ, ÐÒÏÊÄÅÔ ÍÉÍÏ PR Ó ÐÕÓÔÙÍ ËÒÁÔËÉÍ ÏÐÉÓÁÎÉÅÍ. îÅ ÚÁÂÕÄØÔÅ, ÞÔÏ PR ÏÓÔÁÅÔÓÑ × ÂÁÚÅ ÄÏ ÔÅÈ ÐÏÒ, ÐÏËÁ ËÔÏ-ÌÉÂÏ ÎÅ ÚÁËÒÏÅÔ ÅÇÏ; ÓÏÏÂÝÅÎÉÅ-ÁÎÏÎÉÍ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÐÒÏÓÔÏ ÐÏÔÅÒÑÅÔÓÑ ÎÁ ÏÂÝÅÍ ÆÏÎÅ. éÚÂÅÇÁÊÔÅ ÔÕÍÁÎÎÙÈ ÏÐÉÓÁÎÉÊ × ÐÏÌÅ Synopsis. îÅ ÓÔÏÉÔ ÐÒÅÄÐÏÌÁÇÁÔØ, ÞÔÏ ÞÉÔÁÀÝÉÊ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ×ÌÁÄÅÅÔ ËÏÎÔÅËÓÔÏÍ; ÐÏÜÔÏÍÕ, ÞÅÍ ÐÏÄÒÏÂÎÅÅ ×Ù ÏÐÉÛÅÔÅ ÓÉÔÕÁÃÉÀ, ÔÅÍ ÌÕÞÛÅ. ÷ ÞÁÓÔÎÏÓÔÉ, Ë ËÁËÏÊ ÞÁÓÔÉ ÓÉÓÔÅÍÙ ÏÔÎÏÓÉÔÓÑ ×ÁÛÁ ÐÒÏÂÌÅÍÁ? ðÒÏÑ×ÌÑÅÔÓÑ ÌÉ ÏÎÁ ÎÁ ÜÔÁÐÅ ÕÓÔÁÎÏ×ËÉ ÉÌÉ ×Ï ×ÒÅÍÑ ÎÏÒÍÁÌØÎÏÊ ÒÁÂÏÔÙ? îÁÐÒÉÍÅÒ, ×ÍÅÓÔÏ ÓÔÒÏËÉ Synopsis: portupgrade is broken ÓÌÅÄÏ×ÁÌÏ ÂÙ ÎÁÐÉÓÁÔØ ÞÔÏ-ÔÏ ×ÒÏÄÅ Synopsis: port ports-mgmt/portupgrade coredumps on -current. ÷ ÓÌÕÞÁÅ ÐÏÒÔÉÒÏ×ÁÎÎÙÈ ÐÒÉÌÏÖÅÎÉÊ × ÐÏÌÅ Synopsis ÐÏÌÅÚÎÏ ÕËÁÚÙ×ÁÔØ ÎÅ ÔÏÌØËÏ ÉÍÑ ÐÏÒÔÁ, ÎÏ É ËÁÔÅÇÏÒÉÀ. åÓÌÉ Õ ×ÁÓ ÅÓÔØ ÇÏÔÏ×ÙÊ ÐÁÔÞ, ÓËÁÖÉÔÅ Ï ÜÔÏÍ. PR, ÓÏÄÅÒÖÁÝÉÊ ÐÁÔÞ, ÉÍÅÅÔ ËÕÄÁ ÂÏÌØÛÅ ÛÁÎÓÏ× ÂÙÔØ ÒÁÓÓÍÏÔÒÅÎÎÙÍ. ÷ ÜÔÏÍ ÓÌÕÞÁÅ ÄÏÂÁ×ØÔÅ ÓÔÒÏËÕ [patch] (×ËÌÀÞÁÑ Ë×ÁÄÒÁÔÎÙÅ ÓËÏÂËÉ) × ÎÁÞÁÌÏ ÐÏÌÑ Synopsis (ÈÏÔÑ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÉÍÅÎÎÏ ÜÔÏÊ ÆÏÒÍÙ ÎÅÏÂÑÚÁÔÅÌØÎÏ, ÏÎÁ Ñ×ÌÑÅÔÓÑ ÓÔÁÎÄÁÒÔÏÍ ÄÅ-ÆÁËÔÏ). åÓÌÉ ×Ù ÏÔ×ÅÞÁÅÔÅ ÚÁ ÉÓÈÏÄÎÙÅ ÔÅËÓÔÙ, ÓÏÏÂÝÉÔÅ Ï ÜÔÏÍ. åÓÌÉ ×Ù ÏÔ×ÅÞÁÅÔÅ ÚÁ ÞÁÓÔØ ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× (ÎÁÐÒÉÍÅÒ, ÐÏÒÔ), ×Ù ÍÏÖÅÔÅ ÄÏÂÁ×ÉÔØ × ÎÁÞÁÌÏ ÐÏÌÑ Synopsis ÓÔÒÏËÕ [maintainer update] (×ËÌÀÞÁÑ Ë×ÁÄÒÁÔÎÙÅ ÓËÏÂËÉ), Á ÔÁËÖÅ ÕÓÔÁÎÏ×ÉÔØ ËÌÁÓÓ ×ÁÛÅÇÏ PR (ÐÏÌÅ Class) × maintainer-update. ÷ ÜÔÏÍ ÓÌÕÞÁÅ ËÏÍÍÉÔÔÅÒÕ, ÏÂÒÁÂÁÔÙ×ÁÀÝÅÍÕ ×ÁÛ PR, ÎÅ ÐÒÉÄ£ÔÓÑ ÌÉÛÎÉÊ ÒÁÚ ÐÒÏ×ÅÒÑÔØ. âÕÄØÔÅ ÔÏÞÎÙ × ÆÏÒÍÕÌÉÒÏ×ËÁÈ. þÅÍ ÂÏÌØÛÅ ÉÎÆÏÒÍÁÃÉÉ ×Ù ÍÏÖÅÔÅ ÐÒÅÄÏÓÔÁ×ÉÔØ Ï ÐÒÏÂÌÅÍÅ, ÔÅÍ ÂÏÌØÛÅ Õ ×ÁÓ ÛÁÎÓÏ× ÐÏÌÕÞÉÔØ ÏÔ×ÅÔ. ÷ËÌÀÞÉÔÅ ÉÎÆÏÒÍÁÃÉÀ Ï ×ÅÒÓÉÉ &os;, ËÏÔÏÒÕÀ ×Ù ÉÓÐÏÌØÚÕÊÔÅ (ÓÕÝÅÓÔ×ÕÅÔ ÓÐÅÃÉÁÌØÎÏÅ ÐÏÌÅ ÄÌÑ ÅÇÏ ×ËÌÀÞÅÎÉÑ, ÓÍÏÔÒÉÔÅ ÎÉÖÅ) É ÎÁ ËÁËÏÊ ÁÒÈÉÔÅËÔÕÒÅ. óÏÏÂÝÉÔÅ, ÉÓÐÏÌØÚÕÅÔÅ ÌÉ ×Ù release ×ÅÒÓÉÀ (ÕÓÔÁÎÏ×ÉÌÉ Ó ËÏÍÐÁËÔ-ÄÉÓËÁ ÌÉÂÏ ÚÁÇÒÕÚÉÌÉ) ÉÌÉ ÓËÁÞÁÌÉ Å£ Ó ÐÏÍÏÝØÀ Subversion (É ÅÓÌÉ ÔÁË, ÔÏ ÓÏÏÂÝÉÔÅ ÎÏÍÅÒ ÒÅ×ÉÚÉÉ). åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ &os.current;, ÔÏ ÐÅÒ×ÙÊ ×ÏÐÒÏÓ, ËÏÔÏÒÙÊ ×ÁÍ ÍÏÇÕÔ ÚÁÄÁÔØ, ÂÕÄÅÔ ÐÒÏ ÎÏÍÅÒ ÒÅ×ÉÚÉÉ, ÔÁË ËÁË ÉÓÐÒÁ×ÌÅÎÉÑ ÄÌÑ ÜÔÏÊ ×ÅÔËÉ (ÏÓÏÂÅÎÎÏ × ÓÌÕÞÁÅ ÓÅÒØ£ÚÎÙÈ ÐÒÏÂÌÅÍ) ÉÍÅÀÔ ÔÅÎÄÅÎÃÉÀ ÐÏÑ×ÌÑÔØÓÑ ÓÌÉÛËÏÍ ÂÙÓÔÒÏ. ÷ËÌÀÞÉÔÅ ÉÎÆÏÒÍÁÃÉÀ Ï ÔÏÍ, ËÁËÉÅ ÇÌÏÂÁÌØÎÙÅ ÏÐÃÉÉ ×Ù ÕËÁÚÁÌÉ × make.conf. îÁ ÚÁÍÅÔËÕ: ïÂßÑ×ÌÅÎÉÅ ÏÐÃÉÊ ÎÁÐÏÄÏÂÉÅ -02 É ÄÒÕÇÉÈ, ÏÐÉÓÁÎÎÙÈ × &man.gcc.1; ×Ï ÍÎÏÇÉÈ ÓÌÕÞÁÑÈ ÍÏÖÅÔ ÂÙÔØ ÐÒÉÞÉÎÏÊ ÏÛÉÂÏË. èÏÔÑ É ÒÁÚÒÁÂÏÔÞÉËÉ &os; ÂÕÄÕÔ ÐÒÉÎÉÍÁÔØ ÐÁÔÞÉ, Õ ÎÉÈ ÎÅ ÂÕÄÅÔ ÖÅÌÁÎÉÑ ÉÓÓÌÅÄÏ×ÁÔØ ÔÁËÉÅ ÓÌÕÞÁÉ ÉÚ-ÚÁ ÏÔÓÕÔÓÔ×ÉÑ ×ÒÅÍÅÎÉ É ÄÏÂÒÏ×ÏÌØÃÅ×, É ×ÍÅÓÔÏ ÜÔÏÇÏ ÏÎÉ ÍÏÇÕÔ ÏÔ×ÅÔÉÔØ, ÞÔÏ ÜÔÏ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ. åÓÌÉ ÐÒÏÂÌÅÍÕ ÍÏÖÎÏ ÌÅÇËÏ ÐÏ×ÔÏÒÉÔØ, ×ËÌÀÞÉÔÅ ÎÅÏÂÈÏÄÉÍÕÀ ÉÎÆÏÒÍÁÃÉÀ, ÞÔÏÂÙ ÒÁÚÒÁÂÏÔÞÉË ÓÍÏÇ ×ÏÓÐÒÏÉÚ×ÅÓÔÉ ÅÅ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ. åÓÌÉ ÐÒÏÂÌÅÍÁ ÐÒÏÑ×ÌÑÅÔÓÑ ÐÒÉ ÎÅËÏÔÏÒÙÈ ××ÏÄÉÍÙÈ ÄÁÎÎÙÈ, ÔÏ, ÐÏ ×ÏÚÍÏÖÎÏÓÔÉ, ÐÒÉ×ÅÄÉÔÅ ÉÈ ×ÍÅÓÔÅ Ó ÐÏÌÕÞÁÅÍÙÍ É ÏÖÉÄÁÅÍÙÍ ×Ù×ÏÄÏÍ. åÓÌÉ ÖÅ ××ÏÄÉÍÙÈ ÄÁÎÎÙÈ ÍÎÏÇÏ ÉÌÉ ÖÅ ÉÈ ÎÅÌØÚÑ ÒÁÚÇÌÁÛÁÔØ, ÔÏ ÐÏÐÒÏÂÕÊÔÅ ×ÙÄÅÌÉÔØ ÉÚ ÎÉÈ ÌÉÛØ ÎÅÂÏÌØÛÏÊ ÆÒÁÇÍÅÎÔ, ÐÒÉ×ÏÄÑÝÉÊ Ë ×ÏÚÎÉËÎÏ×ÅÎÉÀ ÐÒÏÂÌÅÍÙ, É ×ËÌÀÞÉÔÅ ÅÇÏ × PR. åÓÌÉ ×ÁÛÁ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ÑÄÒÏÍ, ÂÕÄØÔÅ ÇÏÔÏ×Ù ÐÒÅÄÏÓÔÁ×ÉÔØ ÓÌÅÄÕÀÝÕÀ ÉÎÆÏÒÍÁÃÉÀ (×ÁÍ ÎÅ ÏÂÑÚÁÔÅÌØÎÏ ×ËÌÀÞÁÔØ Å£ ×ÓÀ, ÏÎÁ ÐÏÊÄ£Ô ÌÉÛØ ÎÁ ÚÁÐÏÌÎÅÎÉÅ ÂÁÚÙ ÄÁÎÎÙÈ, ÎÏ ×Ù ÄÏÌÖÎÙ ×ËÌÀÞÉÔØ ÉÎÆÏÒÍÁÃÉÀ, ËÏÔÏÒÁÑ ÐÏ ×ÁÛÅÍÕ ÍÎÅÎÉÀ ÁËÔÕÁÌØÎÁ): ÷ÁÛÕ ËÏÎÆÉÇÕÒÁÃÉÀ ÑÄÒÁ, ×ËÌÀÞÁÑ ÔÏ, ËÁËÉÅ ÕÓÔÒÏÊÓÔ×Á Õ ×ÁÓ ÕÓÔÁÎÏ×ÌÅÎÙ ÷ËÌÀÞÅÎÙ ÌÉ Õ ×ÁÓ ÏÐÃÉÉ ÏÔÌÁÄËÉ (ÎÁÐÒÉÍÅÒ, WITNESS), É ÅÓÌÉ ÔÁË, ÔÏ ÓÕÝÅÓÔ×ÕÅÔ ÌÉ ÐÒÏÂÌÅÍÁ ÐÏÓÌÅ ÉÚÍÅÎÅÎÉÑ ÚÎÁÞÅÎÉÑ ÜÔÏÊ ÏÐÃÉÉ ðÏÌÎÙÊ ×Ù×ÏÄ ÏÂÒÁÔÎÏÊ ÔÒÁÓÓÉÒÏ×ËÉ (backtrace), ÐÁÎÉËÉ ÉÌÉ ÉÎÏÇÏ ËÏÎÓÏÌØÎÏÇÏ ×Ù×ÏÄÁ, ÉÌÉ ÖÅ ÚÁÐÉÓÉ ÉÚ /var/log/messages, ÅÓÌÉ ÏÎÉ ÂÙÌÉ ÓÇÅÎÅÒÉÒÏ×ÁÎÙ ÷Ù×ÏÄ ËÏÍÁÎÄÙ pciconf -l, Á ÔÁËÖÅ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ ÞÁÓÔÉ ×Ù×ÏÄÁ dmesg, × ÓÌÕÞÁÅ, ÅÓÌÉ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ËÏÎËÒÅÔÎÙÍ ÏÂÏÒÕÄÏ×ÁÎÉÅÍ ðÒÏÞÌÉ ÌÉ ×Ù src/UPDATING, ÏÐÉÓÁÎÁ ÌÉ ÔÁÍ ×ÁÛÁ ÐÒÏÂÌÅÍÁ (ËÔÏ-ÎÉÂÕÄØ ÓÐÒÏÓÉÔ ÏÂÑÚÁÔÅÌØÎÏ) úÁÐÕÓËÁÅÔÓÑ ÌÉ ÄÒÕÇÏÅ ÑÄÒÏ (ÜÔÏ ÄÌÑ ÔÅÈ ÓÌÕÞÁÅ×, ËÏÇÄÁ ÐÒÉÞÉÎÏÊ ÓÂÏÑ ÓÔÁÌÏ ÏÂÏÒÕÄÏ×ÁÎÉÅ, ÎÁÐÒÉÍÅÒ ÏÔËÁÚÙ×ÁÀÝÉÅ ×ÉÎÞÅÓÔÅÒÙ ÉÌÉ ÐÅÒÅÇÒÅ×ÛÉÅÓÑ ÐÒÏÃÅÓÓÏÒÙ, ÞÔÏ ÍÏÖÅÔ ÍÁÓËÉÒÏ×ÁÔØ ÐÒÏÂÌÅÍÙ ÑÄÒÁ) åÓÌÉ ÖÅ ×ÁÛÁ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ÐÏÒÔÁÍÉ, ÔÏ ÐÒÅÄÏÓÔÁ×ØÔÅ ÓÌÅÄÕÀÝÕÀ ÉÎÆÏÒÍÁÃÉÀ (×ÁÍ ÎÅ ÏÂÑÚÁÔÅÌØÎÏ ×ËÌÀÞÁÔØ Å£ ×ÓÀ, ÏÎÁ ÐÏÊÄÅÔ ÌÉÛØ ÎÁ ÚÁÐÏÌÎÅÎÉÅ ÂÁÚÙ ÄÁÎÎÙÈ, ÎÏ ×Ù ÄÏÌÖÎÙ ×ËÌÀÞÉÔØ ÉÎÆÏÒÍÁÃÉÀ, ËÏÔÏÒÁÑ ÐÏ ×ÁÛÅÍÕ ÍÎÅÎÉÀ ÁËÔÕÁÌØÎÁ): ëÁËÉÅ ÐÏÒÔÙ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÌÉ éÍÅÀÔÓÑ ÌÉ ËÁËÉÅ-ÌÉÂÏ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ËÏÔÏÒÙÅ ÐÅÒÅÐÉÓÙ×ÁÀÔ ÐÅÒ×ÏÎÁÞÁÌØÎÏ-ÕÓÔÁÎÏ×ÌÅÎÎÙÅ × bsd.port.mk, ÔÁËÉÅ ËÁË, PORTSDIR) ðÒÏÞÌÉ ÌÉ ×Ù ports/UPDATING, É ÏÐÉÓÁÎÁ ÌÉ ÔÁÍ ×ÁÛÁ ÐÒÏÂÌÅÍÁ (ËÔÏ-ÎÉÂÕÄØ ÓÐÒÏÓÉÔ ÏÂÑÚÁÔÅÌØÎÏ) éÚÂÅÇÁÊÔÅ ÎÅÞÅÔËÉÈ ÚÁÐÒÏÓÏ× Ï ÎÏ×ÙÈ ×ÏÚÍÏÖÎÏÓÔÑÈ. óÏÏÂÝÅÎÉÅ ÔÉÐÁ ËÔÏ-ÔÏ ÏÂÑÚÁÔÅÌØÎÏ ÄÏÌÖÅÎ ÓÄÅÌÁÔØ ÔÁË, ÞÔÏÂÙ ÔÁËÁÑ-ÔÏ ÕÔÉÌÉÔÁ ×ÅÌÁ ÓÅÂÑ ÔÁË-ÔÏ ÉÍÅÅÔ ËÕÄÁ ÍÅÎØÛÅ ÛÁÎÓÏ× ×ÓÔÒÅÔÉÔØ ÐÏÚÉÔÉ×ÎÙÊ ÏÔËÌÉË, ÞÅÍ ÂÏÌÅÅ ÞÅÔËÏ ÓÆÏÒÍÕÌÉÒÏ×ÁÎÎÙÊ ÚÁÐÒÏÓ. ðÏÍÎÉÔÅ, ÞÔÏ ÉÓÈÏÄÎÙÅ ÔÅËÓÔÙ ÄÏÓÔÕÐÎÙ ×ÓÅÍ, ÔÁË ÞÔÏ ÅÓÌÉ ×ÁÍ ÎÕÖÎÁ ÒÅÁÌÉÚÁÃÉÑ ËÁËÏÇÏ-ÔÏ ÎÏ×ÏÇÏ Ó×ÏÊÓÔ×Á, ÌÕÞÛÉÊ ÓÐÏÓÏ— ×ÚÑÔØÓÑ ÚÁ ÒÁÂÏÔÕ ÓÁÍÏÍÕ! îÅ ÚÁÂÕÄØÔÅ ÔÁËÖÅ, ÞÔÏ ÔÁËÉÅ ÍÏÍÅÎÔÙ ÌÕÞÛÅ ÏÂÓÕÖÄÁÔØ × ÓÐÉÓËÁÈ ÒÁÓÓÙÌËÉ, ÔÁËÉÈ ËÁË freebsd-questions, ÞÅÍ ÄÅÌÁÔØ ÜÔÏ ÐÏÓÒÅÄÓÔ×ÏÍ ÂÁÚÙ ÄÁÎÎÙÈ PR. õÂÅÄÉÔÅÓØ, ÞÔÏ ×ÁÛÁ ÐÒÏÂÌÅÍÁ ÅÝÅ ÎÉËÅÍ ÎÅ ÏÐÉÓÁÎÁ. íÙ ÕÖÅ ÇÏ×ÏÒÉÌÉ Ï ÜÔÏÍ, ÎÏ ÓÔÏÉÔ ÐÏ×ÔÏÒÉÔØÓÑ. ðÏÔÒÁÔØÔÅ ÐÁÒÕ ÍÉÎÕÔ ÎÁ ÓÏÓÔÁ×ÌÅÎÉÅ ÚÁÐÒÏÓÏ× Ë ÂÁÚÅ PR: . (îÅÓÍÏÔÒÑ ÎÁ ÐÏ×ÔÏÒÙ, Ï ÜÔÏÍ ÐÏÓÔÏÑÎÎÏ ÚÁÂÙ×ÁÀÔ) óÏÏÂÝÁÊÔÅ Ï ÏÄÎÏÊ ÐÒÏÂÌÅÍÅ × ÏÄÎÏÍ PR. éÚÂÅÇÁÊÔÅ ÏÐÉÓÁÎÉÑ Ä×ÕÈ É ÂÏÌÅÅ ÐÒÏÂÌÅÍ × ÏÄÎÏÍ ÓÏÏÂÝÅÎÉÉ (ÉÓËÌÀÞÅÎÉÅÍ Ñ×ÌÑÀÔÓÑ ×ÚÁÉÍÏÓ×ÑÚÁÎÎÙÅ ÐÒÏÂÌÅÍÙ). ïÆÏÒÍÌÑÑ ÐÁÔÞÉ, ÎÅ ÐÙÔÁÊÔÅÓØ × ÎÉÈ ÄÏÂÁ×ÌÑÔØ ÍÎÏÖÅÓÔ×Ï ÆÕÎËÃÉÏÎÁÌØÎÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ ÉÌÉ ÉÓÐÒÁ×ÌÑÔØ ÉÍÉ ÎÅÓËÏÌØËÏ ÏÛÉÂÏË × ÏÄÎÏÍ É ÔÏÍ ÖÅ ÓÏÏÂÝÅÎÉÉ Ï ÐÒÏÂÌÅÍÅ (ÏÐÑÔØ ÖÅ, ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ×ÚÁÉÍÏÓ×ÑÚÁÎÎÙÈ ÐÒÏÂÌÅÍ) — ÄÌÑ ÔÁËÉÈ PR-Ï× ÐÏÔÒÅÂÕÅÔÓÑ ÚÎÁÞÉÔÅÌØÎÏ ÂÏÌØÛÅ ×ÒÅÍÅÎÉ ÎÁ ÏÂÒÁÂÏÔËÕ. éÚÂÅÇÁÊÔÅ ÐÏÌÅÍÉËÉ. åÓÌÉ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ËÁÓÁÅÔÓÑ ÏÂÌÁÓÔÉ ÉÌÉ ÓÐÏÓÏÂÏ× ÒÅÁÌÉÚÁÃÉÉ, ËÏÔÏÒÙÅ ÒÁÎÅÅ ×ÙÚ×ÁÌÉ ÒÁÚÎÏÇÌÁÓÉÑ, ×ÁÍ ÓÔÏÉÔ ÂÙÔØ ÇÏÔÏ×ÙÍ ÐÒÅÄÏÓÔÁ×ÉÔØ ÎÅ ÔÏÌØËÏ ÐÁÔÞÉ, ÎÏ É ×ÎÑÔÎÙÅ ÁÒÇÕÍÅÎÔÙ, ÐÏÞÅÍÕ ÓÌÅÄÕÅÔ ÐÏÓÔÕÐÁÔØ ÉÍÅÎÎÏ ÔÁË (ÔÏ ÅÓÔØ, ÜÔÏ ðÒÁ×ÉÌØÎÙÊ ðÕÔØ). ëÁË ÏÔÍÅÞÁÌÏÓØ ×ÙÛÅ, ÁËËÕÒÁÔÎÙÊ ÐÏÉÓË ÐÏ ÁÒÈÉ×Õ ÓÐÉÓËÏ× ÒÁÓÓÙÌËÉ ÎÉËÏÇÄÁ ÎÅ ÐÏÍÅÛÁÅÔ. âÕÄØÔÅ ×ÅÖÌÉ×Ù. ðÏÞÔÉ ËÁÖÄÙÊ ÉÚ ÔÅÈ, ËÔÏ ÍÏÖÅÔ ÚÁÎÉÍÁÔØÓÑ ×ÁÛÉÍ ÓÏÏÂÝÅÎÉÅÍ, Ñ×ÌÑÅÔÓÑ ÄÏÂÒÏ×ÏÌØÃÅÍ. îÉËÏÍÕ ÎÅ ÐÏÎÒÁ×ÑÔÓÑ ÕËÁÚÁÎÉÑ, ËÁË É ÞÔÏ ÄÅÌÁÔØ, ËÏÇÄÁ ÏÎ É ÔÁË ÚÁÎÉÍÁÅÔÓÑ ÜÔÉÍ, ÄÁ ÅÝÅ É ÐÏ ËÁËÉÍ-ÌÉÂÏ ÐÒÉÞÉÎÁÍ, ÏÔÌÉÞÎÙÍ ÏÔ ÆÉÎÁÎÓÏ×ÙÈ. ÷ÏÏÂÝÅ ÇÏ×ÏÒÑ, ÜÔÏÇÏ ÐÏÄÈÏÄÁ ÓÌÅÄÕÅÔ ÐÒÉÄÅÒÖÉ×ÁÔØÓÑ, ÉÍÅÑ ÄÅÌÏ Ó ÌÀÂÙÍ ÐÒÏÅËÔÏÍ Ó ïÔËÒÙÔÙÍÉ éÓÈÏÄÎÙÍÉ ÔÅËÓÔÁÍÉ (Open Source).
ðÒÅÖÄÅ ×ÓÅÇÏ åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÊÔÅ ÕÔÉÌÉÔÕ &man.send-pr.1; ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ÐÅÒÅÍÅÎÎÁÑ ×ÁÛÅÇÏ ÏËÒÕÖÅÎÉÑ VISUAL (ÉÌÉ EDITOR, ÅÓÌÉ VISUAL ÎÅ ÚÁÄÁÎÁ) ÚÁÄÁÎÁ ÐÏÄÈÏÄÑÝÉÍ ÏÂÒÁÚÏÍ. óÌÅÄÕÅÔ ÔÁËÖÅ ÐÒÏ×ÅÒÉÔØ ÒÁÂÏÔÏÓÐÏÓÏÂÎÏÓÔØ ÓÉÓÔÅÍÙ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. õÔÉÌÉÔÁ &man.send-pr.1; ÉÓÐÏÌØÚÕÅÔ ÐÏÞÔÏ×ÕÀ ÓÉÓÔÅÍÕ ÄÌÑ ÏÔÐÒÁ×ËÉ É ÏÔÓÌÅÖÉ×ÁÎÉÑ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ. åÓÌÉ Ó ÍÁÛÉÎÙ, ÎÁ ËÏÔÏÒÏÊ ×Ù ÚÁÐÕÓËÁÅÔÅ &man.send-pr.1;, ÎÅÌØÚÑ ÏÔÐÒÁ×ÉÔØ ÐÏÞÔÕ, ÓÏÏÂÝÅÎÉÅ ÎÅ ÐÏÐÁÄ£Ô × ÂÁÚÕ ÄÁÎÎÙÈ GNATS. ï ÎÁÓÔÒÏÊËÅ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ ×Ï &os; ÍÏÖÎÏ ÐÒÏÞÉÔÁÔØ × ÇÌÁ×Å üÌÅËÔÒÏÎÎÁÑ ÐÏÞÔÁ òÕËÏ×ÏÄÓÔ×Á ÐÏ &os; ÐÏ ÁÄÒÅÓÕ . õÂÅÄÉÔÅÓØ, ÞÔÏ ×ÁÛ ÐÏÞÔÏ×ÙÊ ËÌÉÅÎÔ ÎÅ ÉÓËÁÚÉÔ ÓÏÏÂÝÅÎÉÅ ÐÏ ÐÕÔÉ × GNATS. ÷ ÞÁÓÔÎÏÓÔÉ, ÅÓÌÉ ×ÁÛ ÐÏÞÔÏ×ÙÊ ËÌÉÅÎÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÅÒÅÎÏÓÉÔ ÓÔÒÏËÉ, ÉÚÍÅÎÑÅÔ ÓÉÍ×ÏÌÙ ÔÁÂÕÌÑÃÉÉ ÎÁ ÐÒÏÂÅÌÙ ÉÌÉ ÐÒÅÄÏÔ×ÒÁÝÁÅÔ ÉÎÔÅÒÐÒÅÔÁÃÉÀ ÓÉÍ×ÏÌÏ× ÎÏ×ÏÊ ÓÔÒÏËÉ, ÌÀÂÏÊ ÐÁÔÞ, ËÏÔÏÒÙÊ ×Ù ÐÒÉÛÌ£ÔÅ ÏËÁÖÅÔÓÑ ÎÅÐÒÉÇÏÄÎÙÍ. äÌÑ ÔÅËÓÔÁ ÍÙ ÈÏÔÅÌÉ ÂÙ, ÞÔÏÂÙ ×Ù ÄÅÌÁÌÉ ÓÔÒÏÞËÉ ÒÁÚÍÅÒÏÍ ÐÒÉÍÅÒÎÏ × 70 ÓÉÍ×ÏÌÏ× ÄÌÑ ÞÉÔÁÂÅÌØÎÏÓÔÉ PR ÎÁ ×Å ÓÔÒÁÎÉÃÅ. ðÒÉÍÅÒÎÙÅ ÓÏÏÂÒÁÖÅÎÉÑ ÄÏÌÖÎÙ ÕÞÉÔÙ×ÁÔØÓÑ ÐÒÉ ÏÔÐÒÁ×ËÅ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÅ ÞÅÒÅÚ ×ÅÂ-ÆÏÒÍÕ ×ÍÅÓÔÏ &man.send-pr.1;. ðÏÍÎÉÔÅ, ÞÔÏ ÏÐÅÒÁÃÉÉ ËÏÐÉÒÏ×ÁÎÉÑ-×ÓÔÁ×ËÉ ÍÏÇÕÔ ÉÍÅÔØ ÓÔÏÒÏÎÎÉÅ ÜÆÆÅËÔÙ × ÆÏÒÍÁÔÉÒÏ×ÁÎÉÉ ÔÅËÓÔÁ. ÷ ÏÐÒÅÄÅÌ£ÎÎÙÈ ÓÌÕÞÁÑÈ ÍÏÖÅÔ ÂÙÔØ ÎÅÏÂÈÏÄÉÍÏ ÉÓÐÏÌØÚÏ×ÁÔØ &man.uuencode.1; ÄÌÑ ÇÁÒÁÎÔÉÉ ÔÏÇÏ, ÞÔÏ ÐÁÔÞÉ ÐÒÉÄÕÔ ÎÅ ÉÚÍÅΣÎÎÙÍÉ. é ÎÁËÏÎÅÃ, ÅÓÌÉ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ÂÕÄÅÔ ÏÂߣÍÎÙÍ, ×Ù ÄÏÌÖÎÙ ÐÒÉÇÏÔÏ×ÉÔØ ÅÇÏ × offline, ÞÔÏÂÙ ÎÉÞÅÇÏ ÎÅ ÐÏÔÅÒÑÌÏÓØ × ÓÌÕÞÁÅ, ÅÓÌÉ ÂÕÄÅÔ ÐÒÏÂÌÅÍÁ ÐÒÉ ÅÇÏ ÏÔÐÒÁ×ËÅ. üÔÏ ÏÓÏÂÅÎÎÏ ËÁÓÁÅÔÓÑ ×ÅÂ-ÆÏÒÍÙ.
÷ÌÏÖÅÎÉÅ ÐÁÔÞÅÊ ÉÌÉ ÆÁÊÌÏ× îÉÖÅÓÌÅÄÕÀÝÅÅ ÐÒÉÍÅÎÉÍÏ Ë ÐÅÒÅÄÁÞÅ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ ÐÏÓÒÅÄÓÔ×ÏÍ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ: ðÒÏÇÒÁÍÍÁ &man.send-pr.1; ÐÒÅÄÕÓÍÁÔÒÉ×ÁÅÔ ÐÒÉÓÏÅÄÉÎÅÎÉÅ ÆÁÊÌÏ× Ë ÓÏÏÂÝÅÎÉÀ Ï ÐÒÏÂÌÅÍÅ. ÷Ù ÍÏÖÅÔÅ ×ÌÏÖÉÔØ ÓËÏÌØËÏ ÕÇÏÄÎÏ ÆÁÊÌÏ×, ÎÏ ËÁÖÄÙÊ Ó ÕÎÉËÁÌØÎÙÍ ÉÍÅÎÅÍ (ÉÍÅÅÔÓÑ × ×ÉÄÕ ÉÍÑ ÆÁÊÌÁ ÂÅÚ ÍÁÒÛÒÕÔÁ). ðÒÏÓÔÏ ÉÓÐÏÌØÚÕÊÔÅ ÐÁÒÁÍÅÔÒ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ ÄÌÑ ÚÁÄÁÎÉÑ ÉÍÅÎ ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ×Ù ÈÏÔÉÔÅ ÐÒÉÓÏÅÄÉÎÉÔØ: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors îÅ ÂÅÓÐÏËÏÊÔÅÓØ Ï ÂÉÎÁÒÎÙÈ ÆÁÊÌÁÈ, ÏÎÉ ÂÕÄÕÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÅÒÅËÏÄÉÒÏ×ÁÎÙ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÎÅ ÐÏ×ÒÅÄÉÔØ ÒÁÂÏÔÅ ×ÁÛÅÊ ÐÏÞÔÏ×ÏÊ ÐÒÏÇÒÁÍÍÙ. åÓÌÉ ×Ù ×ËÌÁÄÙ×ÁÅÔÅ ÐÁÔÞ, ÏÂÑÚÁÔÅÌØÎÏ ÉÓÐÏÌØÚÕÊÔÅ ÐÁÒÁÍÅÔÒ ÉÌÉ ×ÍÅÓÔÅ Ó ËÏÍÁÎÄÏÊ &man.diff.1; ÄÌÑ ÓÏÚÄÁÎÉÑ ËÏÎÔÅËÓÔÎÏÇÏ ÉÌÉ ÕÎÉÆÉÃÉÒÏ×ÁÎÎÏÇÏ diff-ÆÁÊÌÁ (ÕÎÉÆÉÃÉÒÏ×ÁÎÎÙÊ ÆÏÒÍÁÔ ÐÒÅÄÐÏÞÔÉÔÅÌÅÎ), É ÏÂÑÚÁÔÅÌØÎÏ ÕËÁÖÉÔÅ ÔÏÞÎÙÅ ÎÏÍÅÒÁ SVN ÒÅ×ÉÚÉÊ ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ×Ù ÉÚÍÅÎÑÌÉ, ÞÔÏÂÙ ÒÁÚÒÁÂÏÔÞÉËÉ, ËÏÔÏÒÙÅ ÂÕÄÕÔ ÞÉÔÁÔØ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ, ÓÍÏÇÌÉ ÌÅÇËÏ ÅÇÏ ÐÒÉÍÅÎÉÔØ. äÌÑ ÐÒÏÂÌÅÍ, Ó×ÑÚÁÎÎÙÈ Ó ÑÄÒÏÍ ÉÌÉ Ó ÂÁÚÏ×ÙÍÉ ÕÔÉÌÉÔÁÍÉ, ÐÒÅÄÐÏÞÔÉÔÅÌØÎÅÅ ÂÕÄÅÔ ÐÁÔÞ ÏÔÎÏÓÉÔÅÌØÎÏ ×ÅÔËÉ &os.current; (ÉÌÉ Subversion-×ÅÔËÉ HEAD), ÔÁË ËÁË ×ÅÓØ ÎÏ×ÙÊ ËÏÄ ÄÏÌÖÅÎ ÂÙÔØ ÓÎÁÞÁÌÁ ÐÒÏÔÅÓÔÉÒÏ×ÁÎ × ÎÅÊ. ðÏÓÌÅ ÚÁ×ÅÒÛÅÎÉÑ ÔÅÓÔÉÒÏ×ÁÎÉÑ ËÏÄ ÂÕÄÅÔ ÉÎÔÅÇÒÉÒÏ×ÁÎ × ×ÅÔ×Ø &os.stable;. åÓÌÉ ×Ù ×ÓÔÁ×ÌÑÅÔÅ ÐÁÔÞ × ÔÅÌÏ ÓÏÏÂÝÅÎÉÑ, ÕÞÔÉÔÅ, ÞÔÏ ÎÅËÏÔÏÒÙÅ ÐÏÞÔÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ ÉÍÅÀÔ ÔÅÎÄÅÎÃÉÀ ÚÁÍÅÎÑÔØ ÔÁÂÕÌÑÃÉÉ ÓÅÒÉÅÊ ÐÒÏÂÅÌÏ×, ÞÔÏ ÐÏÌÎÏÓÔØÀ ÒÁÚÒÕÛÉÔ, ÎÁÐÒÉÍÅÒ, ÞÁÓÔØ ÆÁÊÌÁ ÓÂÏÒËÉ (Makefile). îÅ ÏÔÓÙÌÁÊÔÅ ÐÁÔÞÉ × ×ÉÄÅ ×ÌÏÖÅÎÉÊ, ÉÓÐÏÌØÚÕÑ Content-Transfer-Encoding: quoted-printable. üÔÏ ×ÙÐÏÌÎÉÔ ÜËÒÁÎÉÒÏ×ÁÎÉÅ (escaping) ÓÉÍ×ÏÌÏ× É ×ÅÓØ ÐÁÔÞ ÂÕÄÅÔ ÂÅÓÐÏÌÅÚÎÙÍ. óÌÅÄÕÅÔ ÔÁËÖÅ ÚÁÍÅÔÉÔØ, ÞÔÏ ×ËÌÀÞÅÎÉÅ ÎÅÂÏÌØÛÉÈ ÐÁÔÞÅÊ × ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ Ñ×ÌÑÅÔÓÑ ÐÒÉÅÍÌÅÍÏÊ ÐÒÁËÔÉËÏÊ, × ÏÓÏÂÅÎÎÏÓÔÉ ÅÓÌÉ ÏÎÉ ÒÅÛÁÀÔ ÐÒÏÂÌÅÍÕ, ÏÐÉÓÁÎÎÕÀ × ÓÏÏÂÝÅÎÉÉ, ÂÏÌØÛÉÅ ÖÅ ÐÁÔÞÉ, Á × ÏÓÏÂÅÎÎÏÓÔÉ ÎÏ×ÙÊ ËÏÄ, ËÏÔÏÒÙÊ ÍÏÖÅÔ ÔÒÅÂÏ×ÁÔØ ÚÎÁÞÉÔÅÌØÎÏÇÏ ÐÒÏÓÍÏÔÒÁ ÐÅÒÅÄ ÔÅÍ, ËÁË ÏÎ ÂÕÄÅÔ ×ÎÅÓÅÎ × ÄÅÒÅ×Ï ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, ÄÏÌÖÎÙ ÂÙÔØ ÒÁÚÍÅÝÅÎÙ ÎÁ web- ÉÌÉ ftp-ÓÅÒ×ÅÒÅ, Á × ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ ÄÏÌÖÅÎ ÂÙÔØ ×ËÌÀޣΠÔÏÌØËÏ URL ÕËÁÚÙ×ÁÀÝÉÊ ÎÁ ÜÔÏÔ ÐÁÔÞ. ïÞÅÎØ ÞÁÓÔÏ ÐÁÔÞÉ, ÐÅÒÅÓÙÌÁÅÍÙÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ, Á × ÏÓÏÂÅÎÎÏÓÔÉ ÅÓÌÉ ÚÁÄÅÊÓÔ×Ï×ÁÎÁ GNATS, ÂÙ×ÁÀÔ ÉÓËÁÖÅÎÙ, É, ËÁË ÓÌÅÄÓÔ×ÉÅ, ÞÅÍ ÂÏÌØÛÅ ÐÁÔÞ, ÔÅÍ ÔÒÕÄÎÅÅ ÂÕÄÅÔ ÄÌÑ ÚÁÉÎÔÅÒÅÓÏ×ÁÎÎÙÈ ÌÀÄÅÊ ÐÒÉ×ÅÓÔÉ ÅÇÏ Ë ÎÏÒÍÁÌØÎÏÍÕ ×ÉÄÕ. ôÁËÖÅ ÔÏ, ÞÔÏ ÐÁÔÞ ÂÕÄÅÔ ÒÁÚÍÅݣΠÏÔÄÅÌØÎÏ ÏÔ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ, ÄÁ£Ô ×ÏÚÍÏÖÎÏÓÔØ ÉÚÍÅÎÑÔØ ÅÇÏ ÎÅ ÏÔÓÙÌÁÑ ÐÏÌÎÙÊ ÐÁÔÞ × ÄÏÐÏÌÎÅÎÉÅ Ë ÉÚÎÁÞÁÌØÎÏÍÕ ÓÏÏÂÝÅÎÉÀ Ï ÐÒÏÂÌÅÍÅ. é ÎÁËÏÎÅÃ, ÂÏÌØÛÉÅ ÐÁÔÞÉ ÐÒÏÓÔÏ Õ×ÅÌÉÞÉ×ÁÀÔ ÒÁÚÍÅÒ ÂÁÚÙ ÄÁÎÎÙÈ, ÔÁË ËÁË ÚÁËÒÙÔÙÅ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÎÅ ÕÄÁÌÑÀÔÓÑ, Á ÓÏÈÒÁÎÑÀÔÓÑ É ÐÏÍÅÞÁÀÔÓÑ, ËÁË closed. ÷Ù ÄÏÌÖÎÙ ÔÁËÖÅ ÐÏÍÎÉÔØ, ÞÔÏ ÐÏËÁ ×Ù Ñ×ÎÏ ÎÅ ÕËÁÖÅÔÅ ÏÂÒÁÔÎÏÇÏ × ×ÁÛÅÍ ÓÏÏÂÝÅÎÉÉ Ï ÐÒÏÂÌÅÍÅ ÉÌÉ × ÓÁÍÉÈ ÐÁÔÞÁÈ, ÂÕÄÅÔ ÐÒÅÄÐÏÌÁÇÁÔØÓÑ, ÞÔÏ ÏÎÉ ÐÏÄÐÁÄÁÀÔ ÐÏÄ ÔÅ ÖÅ ÕÓÌÏ×ÉÑ ÌÉÃÅÎÚÉÒÏ×ÁÎÉÑ, ÞÔÏ É ÏÒÉÇÉÎÁÌØÎÙÊ ÆÁÊÌ, ÉÚÍÅÎÅÎÎÙÊ ×ÁÍÉ.
úÁÐÏÌÎÅÎÉÅ ÛÁÂÌÏÎÁ óÌÅÄÕÀÝÉÅ ÎÅÓËÏÌØËÏ ÁÂÚÁÃÅ× ÐÒÉÍÅÎÉÍÙ ÔÏÌØËÏ Ë ÓÐÏÓÏÂÕ ÐÏÄÁÞÉ PR ÞÅÒÅÚ ÜÌÅËÔÒÏÎÎÕÀ ÐÏÞÔÕ: ðÏÓÌÅ ÚÁÐÕÓËÁ ÕÔÉÌÉÔÙ &man.send-pr.1; ×ÁÍ ÂÕÄÅÔ ÐÒÅÄÓÔÁ×ÌÅÎ ÛÁÂÌÏÎ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ. ûÁÂÌÏÎ ÓÏÓÔÏÉÔ ÉÚ ÓÐÉÓËÁ ÐÏÌÅÊ, ÎÅËÏÔÏÒÙÅ ÉÚ ËÏÔÏÒÙÈ ÕÖÅ ÚÁÐÏÌÎÅÎÙ, Á ÎÅËÏÔÏÒÙÅ ÓÏÄÅÒÖÁÔ ËÏÍÍÅÎÔÁÒÉÉ, ÏÂßÑÓÎÑÀÝÉÅ ÎÁÚÎÁÞÅÎÉÅ ÐÏÌÑ ÉÌÉ ÐÅÒÅÞÉÓÌÑÀÝÉÅ ÐÏÄÈÏÄÑÝÉÅ ÚÎÁÞÅÎÉÑ. îÅ ÂÅÓÐÏËÏÊÔÅÓØ Ï ËÏÍÍÅÎÔÁÒÉÑÈ; ÏÎÉ ÂÕÄÕÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÕÄÁÌÅÎÙ, ÅÓÌÉ ×Ù ÉÈ ÎÅ ÉÚÍÅÎÑÌÉ (ÉÌÉ ÕÄÁÌÉÔÅ ÉÈ ÓÁÍÉ). ÷×ÅÒÈÕ ÛÁÂÌÏÎÁ, ÎÉÖÅ ÓÔÒÏË SEND-PR: ÎÁÈÏÄÑÔÓÑ ÚÁÇÏÌÏ×ËÉ ÐÏÞÔÏ×ÏÇÏ ÓÏÏÂÝÅÎÉÑ. ÷ÁÍ ÏÂÙÞÎÏ ÎÅ ÎÕÖÎÏ ÉÈ ÉÚÍÅÎÑÔØ, ÅÓÌÉ ÔÏÌØËÏ ×Ù ÎÅ ÐÏÓÙÌÁÅÔÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ Ó ÍÁÛÉÎÙ ÉÌÉ ÏÔ ÕÞÅÔÎÏÊ ÚÁÐÉÓÉ, ËÏÔÏÒÁÑ ÍÏÖÅÔ ÐÏÓÙÌÁÔØ, ÎÏ ÎÅ ÍÏÖÅÔ ÐÏÌÕÞÁÔØ ÜÌÅËÔÒÏÎÎÕÀ ÐÏÞÔÕ, × ÓÌÕÞÁÅ ÞÅÇÏ ×Ù ÍÏÖÅÔÅ ÚÁÄÁÔØ × ÐÏÌÑÈ From: É Reply-To: ×ÁÛÉ ÒÅÁÌØÎÙÅ ÁÄÒÅÓÁ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. ÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÐÏÓÌÁÔØ ÓÁÍÏÍÕ ÓÅÂÅ (ÉÌÉ ËÏÍÕ-ÔÏ ÅÝÅ) ËÏÐÉÀ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ, ÄÏÂÁ×É× ÏÄÉÎ ÉÌÉ ÂÏÌØÛÅÅ ËÏÌÉÞÅÓÔ×Ï ÁÄÒÅÓÏ× Ë ÚÁÇÏÌÏ×ËÕ Cc:. ÷ ÛÁÂÌÏÎÅ ×Ù ÎÁÊÄÅÔÅ Ä×Á ÏÄÎÏÓÔÒÏÞÎÙÈ ÐÏÌÑ: Submitter-Id: îÅ ÍÅÎÑÊÔÅ ÅÇÏ. úÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ current-users ÐÒÁ×ÉÌØÎÏ, ÄÁÖÅ ÅÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ &os.stable;. Confidential: ðÒÅÄ×ÁÒÉÔÅÌØÎÏ ÚÁÐÏÌÎÅÎÏ ËÁË no, ÅÇÏ ÉÚÍÅÎÅÎÉÅ ÎÅ ÉÍÅÅÔ ÚÎÁÞÅÎÉÑ, ÔÁË ËÁË ÎÅÔ ÔÁËÏÇÏ ÐÏÎÑÔÉÑ, ËÁË ËÏÎÆÉÄÅÎÃÉÁÌØÎÏÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ — ÂÁÚÁ ÄÁÎÎÙÈ PR ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ ÐÏ ×ÓÅÍÕ ÍÉÒÕ. äÁÌÅÅ ÏÐÉÓÁÎÙ ÏÂÝÉÅ ÐÏÌÑ ÄÌÑ ÐÏÞÔÏ×ÏÇÏ É ×Å ÉÎÔÅÒÆÅÊÓÁ: Originator: ðÏÖÁÌÕÊÓÔÁ, ÕËÁÖÉÔÅ ×ÁÛÅ ÒÅÁÌØÎÏÅ ÉÍÑ, ÚÁ ËÏÔÏÒÙÍ ÏÐÃÉÏÎÁÌØÎÏ ÓÌÅÄÕÅÔ ÁÄÒÅÓ ×ÁÛÅÊ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ × ÕÇÌÏ×ÙÈ ÓËÏÂËÁÈ. ïÂÙÞÎÏ, &man.send-pr.1; ÚÁÐÏÌÎÑÅÔ ÐÏÌÅ Originator ÓÏÄÅÒÖÉÍÙÍ ÐÏÌÑ gecos ÉÚ ÕÞÅÔÎÏÊ ÚÁÐÉÓÉ ÔÅËÕÝÅÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. ðÒÅÄÏÓÔÁ×ÌÅÎÎÙÊ ×ÁÍÉ ÁÄÒÅÓ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ ÓÔÁÎÅÔ ÐÕÂÌÉÞÎÏÊ ÉÎÆÏÒÍÁÃÉÅÊ É ÍÏÖÅÔ ÓÔÁÔØ ÄÏÓÔÕÐÎÙÍ ÓÐÁÍÅÒÁÍ. ðÏÜÔÏÍÕ ÓÏ×ÓÅÍ ÎÅ ÌÉÛÎÉÍÉ ÂÕÄÕÔ ÍÅÒÙ ÐÏ ÂÏÒØÂÅ ÓÏ ÓÐÁÍÏÍ ÎÁ ×ÁÛÅÊ ÓÔÏÒÏÎÅ, ÉÌÉ ÖÅ ÍÏÖÎÏ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ×ÒÅÍÅÎÎÙÍ ÁÄÒÅÓÏÍ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ. ïÄÎÁËÏ, ÅÓÌÉ ×Ù ÕËÁÖÅÔÅ ÎÅÓÕÝÅÓÔ×ÕÀÝÉÊ ÐÏÞÔÏ×ÙÊ ÁÄÒÅÓ, ÔÏ Õ ÎÁÓ ÎÅ ÂÕÄÅÔ ×ÏÚÍÏÖÎÏÓÔÉ ÕÔÏÞÎÑÔØ ÄÅÔÁÌÉ ÐÏ ×ÁÛÅÍÕ PR. Organization: ÷ÓÅ, ÞÔÏ ×Ù ÚÁÈÏÔÉÔÅ ÚÄÅÓØ ÕËÁÚÁÔØ. üÔÏ ÐÏÌÅ ÎÅ ÓÏÄÅÒÖÉÔ ÚÎÁÞÉÔÅÌØÎÏÊ ÉÎÆÏÒÍÁÃÉÉ. Synopsis: úÁÐÏÌÎÑÅÔÓÑ ËÒÁÔËÉÍ É ÔÏÞÎÙÍ ÏÐÉÓÁÎÉÅÍ ÐÒÏÂÌÅÍÙ. ëÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ ÉÓÐÏÌØÚÕÅÔÓÑ × ËÁÞÅÓÔ×Å ÔÅÍÙ ÓÏÏÂÝÅÎÉÑ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÙ Ï ÐÒÏÂÌÅÍÅ, É ÉÓÐÏÌØÚÕÅÔÓÑ ÐÒÉ ×ÙÄÁÞÅ ÓÐÉÓËÏ× É ×ÙÂÏÒËÁÈ ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÁÈ; ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÁÈ Ó ÎÅÐÏÎÑÔÎÙÍÉ ËÒÁÔËÉÍÉ ÏÐÉÓÁÎÉÑÍÉ ÞÁÝÅ ×ÓÅÇÏ ÉÇÎÏÒÉÒÕÀÔÓÑ. ðÏ×ÔÏÒÉÍ: ÅÓÌÉ Ë ×ÁÛÅÍÕ ÓÏÏÂÝÅÎÉÀ Ï ÐÒÏÂÌÅÍÅ ÐÒÉÌÏÖÅÎ ÐÁÔÞ, ÔÏ, ÐÏÖÁÌÕÊÓÔÁ, ÎÁÞÎÉÔÅ ËÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ Ó [patch] (×ËÌÀÞÁÑ Ë×ÁÄÒÁÔÎÙÅ ÓËÏÂËÉ); ÅÓÌÉ PR ÐÒÉÎÁÄÌÅÖÉÔ Ë ËÁÔÅÇÏÒÉÉ ports É ×Ù Ñ×ÌÑÅÔÅÓØ ÅÇÏ ÍÅÊÎÔÅÊÎÅÒÏÍ, ÔÏ ÎÁÞÎÉÔÅ ÏÐÉÓÁÎÉÅ Ó [maintainer update] (×ËÌÀÞÁÑ Ë×ÁÄÒÁÔÎÙÅ ÓËÏÂËÉ) É ÕÓÔÁÎÏ×ÉÔÅ ËÌÁÓÓ ÐÒÏÂÌÅÍÙ (ÐÏÌÅ Class) × maintainer-update. Severity: ïÄÎÏ ÉÚ non-critical, serious ÉÌÉ critical. îÅ ÐÅÒÅÕÓÅÒÄÓÔ×ÕÊÔÅ; ÉÚÂÅÇÁÊÔÅ ÐÏÍÅÔËÉ ×ÁÛÅÊ ÐÒÏÂÌÅÍÙ ËÁË critical, ÅÓÌÉ ÔÏÌØËÏ ÜÔÏ ÎÅ ÄÅÊÓÔ×ÉÔÅÌØÎÏ ËÒÉÔÉÞÎÁÑ ÐÒÏÂÌÅÍÁ (ÐÏ×ÒÅÖÄÅÎÉÅ ÄÁÎÎÙÈ, ÓÕÝÅÓÔ×ÅÎÎÁÑ ÐÏÔÅÒÑ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔÉ × -CURRENT), ÉÌÉ serious, ÅÓÌÉ ÔÏÌØËÏ ÜÔÏ ÎÅ ËÁÓÁÅÔÓÑ ÍÎÏÇÉÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ (ÐÁÎÉËÉ ÑÄÒÁ, ÂÌÏËÉÒÏ×ËÉ (freezes), ÐÒÏÂÌÅÍÙ Ó ËÏÎËÒÅÔÎÙÍÉ ÄÒÁÊ×ÅÒÁÍÉ ÕÓÔÒÏÊÓÔ× ÉÌÉ Ó ÓÉÓÔÅÍÎÙÍÉ ÕÔÉÌÉÔÁÍÉ). òÁÚÒÁÂÏÔÞÉËÉ &os; ÎÅ ÏÂÑÚÁÔÅÌØÎÏ ÂÕÄÕÔ ÒÁÂÏÔÁÔØ ÎÁÄ ×ÁÛÅÊ ÐÒÏÂÌÅÍÏÊ ÂÙÓÔÒÅÅ, ÅÓÌÉ ×Ù ÕÓÔÁÎÏ×ÉÔÅ ÓÌÉÛËÏÍ ×ÙÓÏËÉÊ ÕÒÏ×ÅÎØ ×ÁÖÎÏÓÔÉ, Ô.Ë. ÓÕÝÅÓÔ×ÕÅÔ ÍÎÏÇÏ ÄÒÕÇÉÈ ÌÀÄÅÊ, ËÏÔÏÒÙÅ ÓÄÅÌÁÌÉ ÔÏÖÅ ÓÁÍÏÅ — ÎÅËÏÔÏÒÙÅ ÒÁÚÒÁÂÏÔÞÉËÉ ×Ó£ ÖÅ ÕÄÅÌÑÔ ÜÔÏÍÕ ÐÏÌÀ ÎÅÍÎÏÇÏ ×ÎÉÍÁÎÉÑ É ÐÅÒÅÊÄÕÔ Ë ÓÌÅÄÕÀÝÅÍÕ ÓÏÏÂÝÅÎÉÀ ÉÍÅÎÎÏ ÉÚ-ÚÁ ÜÔÏÇÏ ÐÏÌÑ. âÏÌØÛÉÎÓÔ×Ï ÐÒÏÂÌÅÍ Ó ÂÅÚÏÐÁÓÎÏÓÔØÀ ÎÅ ÓÌÅÄÕÅÔ ÏÔÐÒÁ×ÌÑÔØ × GNATS, ÐÏÔÏÍÕ ÞÔÏ ×ÓÑ ÜÔÁ ÉÎÆÏÒÍÁÃÉÑ ÓÔÁÎÏ×ÉÔÓÑ ÐÕÂÌÉÞÎÏÊ. ðÏÖÁÌÕÊÓÔÁ, ÎÁÐÒÁ×ÌÑÊÔÅ ÐÏÄÏÂÎÙÅ ÏÔÞÅÔÙ ÎÁ ÜÌÅËÔÒÏÎÎÙÊ ÁÄÒÅÓ &a.security-officer;. Priority: ïÄÎÏ ÉÚ low, medium ÉÌÉ high. high ÄÏÌÖÅÎ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÄÌÑ ÐÒÏÂÌÅÍ, ËÏÔÏÒÙÅ ÚÁÔÒÏÎÕÔ ËÏÎËÒÅÔÎÏ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ &os;, Á medium ÄÌÑ ÞÅÇÏ-ÔÏ, ÞÔÏ ÚÁÔÒÏÎÅÔ ÍÎÏÇÉÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. ÷×ÉÄÕ ÍÁÓÓÏ×ÙÈ ÚÌÏÕÐÏÔÒÅÂÌÅÎÉÊ ÜÔÏ ÐÏÌÅ ÐÏÔÅÒÑÌÏ Ó×ÏÅ ÚÎÁÞÅÎÉÅ. Category: ÷ÙÂÅÒÉÔÅ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ ËÁÔÅÇÏÒÉÀ. ðÅÒ×ÙÍ ÄÅÌÏÍ ÎÅÏÂÈÏÄÉÍÏ ÒÅÛÉÔØ, Ë ËÁËÏÊ ÞÁÓÔÉ ÓÉÓÔÅÍÙ ÏÔÎÏÓÉÔÓÑ ×ÁÛÁ ÐÒÏÂÌÅÍÁ. ðÏÍÎÉÔÅ: &os; — ÚÁ×ÅÒÛÅÎÎÁÑ ÏÐÅÒÁÃÉÏÎÎÁÑ ÓÉÓÔÅÍÁ, ËÏÔÏÒÁÑ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÑÄÒÏ, ÓÔÁÎÄÁÒÔÎÙÅ ÂÉÂÌÉÏÔÅËÉ, ÍÎÏÖÅÓÔ×Ï ÄÒÁÊ×ÅÒÏ× ÐÅÒÉÆÅÒÉÊÎÏÇÏ ÏÂÏÒÕÄÏ×ÁÎÉÑ, Á ÔÁËÖÅ — ÂÏÌØÛÏÊ ÎÁÂÏÒ ÓÉÓÔÅÍÎÙÈ ÕÔÉÌÉÔ (ÂÁÚÏ×ÁÑ ÓÉÓÔÅÍÁ). ÷ ÄÏÐÏÌÎÅÎÉÅ Ë ÜÔÏÍÕ, × ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ× ÉÍÅÀÔÓÑ ÔÙÓÑÞÉ ÐÒÉÌÏÖÅÎÉÊ. óÌÅÄÏ×ÁÔÅÌØÎÏ, ÏÐÒÅÄÅÌÉÔÅÓØ: ÏÂÎÁÒÕÖÅÎÎÁÑ ×ÁÍÉ ÐÒÏÂÌÅÍÁ ÎÁÈÏÄÉÔÓÑ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ ÉÌÉ × ÞÅÍ-ÔÏ, ÕÓÔÁÎÏ×ÌÅÎÎÙÍ ÞÅÒÅÚ ËÏÌÌÅËÃÉÀ ÐÏÒÔÏ×. ÷ÏÔ ÏÐÉÓÁÎÉÅ ÏÓÎÏ×ÎÙÈ ËÁÔÅÇÏÒÉÊ: åÓÌÉ ÐÒÏÂÌÅÍÁ × ÑÄÒÅ, × ÂÉÂÌÉÏÔÅËÁÈ (ÔÁËÉÈ ËÁË ÓÔÁÎÄÁÒÔÎÁÑ ÂÉÂÌÉÏÔÅËÁ ó libc) ÉÌÉ × ÄÒÁÊ×ÅÒÅ ÉÚ ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÙ, ÔÏ ÉÓÐÏÌØÚÕÊÔÅ ËÁÔÅÇÏÒÉÀ kern. (åÓÔØ ÎÅÓËÏÌØËÏ ÉÓËÌÀÞÅÎÉÊ, ÏÐÉÓÁÎÎÙÈ ÎÉÖÅ). ÷ ÏÂÝÅÍ, ÜÔÏ ×Ó£, ÞÔÏ ÏÐÉÓÁÎÏ × ÒÁÚÄÅÌÁÈ 2, 3 ÉÌÉ 4 ÓÐÒÁ×ÏÞÎÉËÁ. åÓÌÉ ÐÒÏÂÌÅÍÁ Ó ÂÉÎÁÒÎÏÊ ÐÒÏÇÒÁÍÍÏÊ, ÎÁÐÒÉÍÅÒ Ó &man.sh.1; ÉÌÉ &man.mount.8;, ÔÏ ×ÁÍ ÐÒÅÖÄÅ ×ÓÅÇÏ ÎÅÏÂÈÏÄÉÍÏ ÏÐÒÅÄÅÌÉÔØ ÐÒÉÎÁÄÌÅÖÎÏÓÔØ ÐÒÏÇÒÁÍÍÙ Ë ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ ÉÌÉ Ë ÕÓÔÁÎÏ×ËÅ ÉÚ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ×. åÓÌÉ ×Ù ÎÅ Õ×ÅÒÅÎÙ, ×ÙÐÏÌÎÉÔÅ ËÏÍÁÎÄÕ whereis ÉÍÑ ÐÒÏÇÒÁÍÍÙ. ÷ &os; ÄÌÑ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ× ÓÕÝÅÓÔ×ÕÅÔ ÄÏÇÏ×ÏÒÅÎÎÏÓÔØ: ÕÓÔÁÎÏ×ËÁ ×ÅÄÅÔÓÑ × /usr/local, ÏÄÎÁËÏ ÜÔÏ ÍÏÖÅÔ ÂÙÔØ ÐÅÒÅÏÐÒÅÄÅÌÅÎÏ ÓÉÓÔÅÍÎÙÍ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ. äÌÑ ÔÁËÉÈ ÐÒÏÇÒÁÍÍ ÓÌÅÄÕÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ËÁÔÅÇÏÒÉÀ ports (ÄÁÖÅ ÅÓÌÉ ËÁÔÅÇÏÒÉÑ ÐÏÒÔÁ www; ÓÍ. ÎÉÖÅ). åÓÌÉ ÐÒÏÇÒÁÍÍÁ ÒÁÓÐÏÌÁÇÁÅÔÓÑ × /bin, /usr/bin, /sbin ÉÌÉ × /usr/sbin, ÔÏ ÜÔÏ ÞÁÓÔØ ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÙ, É ×ÁÍ ÓÌÅÄÕÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ËÁÔÅÇÏÒÉÀ bin. (îÅÓËÏÌØËÏ ÐÒÏÇÒÁÍÍ, ÎÁÐÒÉÍÅÒ &man.gcc.1;, ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÉÓÐÏÌØÚÕÀÔ ËÁÔÅÇÏÒÉÀ gnu, ÎÏ ÎÅ ÂÅÓÐÏËÏÊÔÅÓØ Ï ÜÔÏÍ ÓÅÊÞÁÓ.) ðÒÏÇÒÁÍÍÙ ÜÔÏÊ ËÁÔÅÇÏÒÉÉ ÏÐÉÓÁÎÙ × ÒÁÚÄÅÌÁÈ 1 É 8 ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ. åÓÌÉ ×Ù Õ×ÅÒÅÎÙ, ÞÔÏ × ÓÔÁÒÔÏ×ÙÈ ÓËÒÉÐÔÁÈ (rc) ÉÌÉ × ËÁËÏÍ-ÔÏ ÉÎÏÍ ÎÅÉÓÐÏÌÎÑÅÍÏÍ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ ÐÒÉÓÕÔÓÔ×ÕÅÔ ÏÛÉÂËÁ, ÔÏÇÄÁ ×ÅÒÎÏÊ ËÁÔÅÇÏÒÉÅÊ ÂÕÄÅÔ conf (configuration). üÔÉ ÓÕÝÎÏÓÔÉ ÏÐÉÓÙ×ÁÀÔÓÑ × ÒÁÚÄÅÌÅ 5 ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ. åÓÌÉ ×Ù ÎÁÛÌÉ ÐÒÏÂÌÅÍÕ × ÎÁÂÏÒÅ ÄÏËÕÍÅÎÔÁÃÉÉ (ÓÔÁÔØÉ, ËÎÉÇÉ, ÓÔÒÁÎÉÃÙ ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ), ÐÒÁ×ÉÌØÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ docs. åÓÌÉ ×Ù ÎÁÂÌÀÄÁÅÔÅ ÐÒÏÂÌÅÍÕ ÎÁ ÓÔÒÁÎÉÃÁÈ ÓÁÊÔÁ FreeBSD, ÔÏ ÐÒÁ×ÉÌØÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ www. åÓÌÉ ÐÒÏÂÌÅÍÁ Ó ÞÅÍ-ÔÏ ÉÚ ÐÏÒÔÁ, ÎÁÚÙ×ÁÅÍÏÇÏ www/someportname , ÔÏ ÏÎÁ ×ÓÅ ÖÅ ÐÒÉÎÁÄÌÅÖÉÔ Ë ËÁÔÅÇÏÒÉÉ ports. äÁÌÅÅ ÐÒÅÄÓÔÁ×ÌÅÎÙ ÂÏÌÅÅ ÓÐÅÃÉÁÌÉÚÉÒÏ×ÁÎÎÙÅ ËÁÔÅÇÏÒÉÉ. åÓÌÉ ÐÒÏÂÌÅÍÁ ÐÒÉÎÁÄÌÅÖÉÔ Ë kern, ÎÏ × ÔÏ ÖÅ ×ÒÅÍÑ ÉÍÅÅÔ ÄÅÌÏ Ó ÐÏÄÓÉÓÔÅÍÏÊ USB, ÔÏ ÐÒÁ×ÉÌØÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ usb. åÓÌÉ ÐÒÏÂÌÅÍÁ ÐÒÉÎÁÄÌÅÖÉÔ Ë kern É ÎÁÊÄÅÎÁ × ÐÏÔÏËÏ×ÙÈ ÂÉÂÌÉÏÔÅËÁÈ, ÐÒÁ×ÉÌØÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ threads. åÓÌÉ ÐÒÏÂÌÅÍÁ ÐÒÉÎÁÄÌÅÖÉÔ Ë ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ É ËÁÓÁÅÔÓÑ ÓÏÂÌÀÄÅÎÉÑ ÓÔÁÎÄÁÒÔÏ×, ÔÁËÉÈ ËÁË &posix;, ÐÒÁ×ÉÌØÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ standards. åÓÌÉ ÐÒÏÂÌÅÍÁ Ó×ÑÚÁÎÁ Ó ÏÛÉÂËÁÍÉ ×ÎÕÔÒÉ &java.virtual.machine; (&jvm;), ÄÁÖÅ ÅÓÌÉ &java; ÂÙÌÁ ÕÓÔÁÎÏ×ÌÅÎÁ ÉÚ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ×, ×ÁÍ ÓÌÅÄÕÅÔ ×ÙÂÒÁÔØ ËÁÔÅÇÏÒÉÀ java. âÏÌÅÅ ÏÂÝÉÅ ÐÒÏÂÌÅÍÙ Ó ÐÏÒÔÁÍÉ &java; ÐÏÐÁÄÁÀÔ ÐÏÄ ËÁÔÅÇÏÒÉÀ ports. äÁÌÅÅ ÐÅÒÅÞÉÓÌÅÎÙ ÏÓÔÁÌØÎÙÅ ËÁÔÅÇÏÒÉÉ. åÓÌÉ ×Ù Õ×ÅÒÅÎÙ, ÞÔÏ ÐÒÏÂÌÅÍÁ ÐÒÏÑ×ÌÑÅÔÓÑ ÔÏÌØËÏ ÎÁ ÉÓÐÏÌØÚÕÅÍÏÊ ×ÁÍÉ ÐÒÏÃÅÓÓÏÒÎÏÊ ÁÒÈÉÔÅËÔÕÒÅ, ×ÙÂÅÒÉÔÅ ÏÄÎÕ ÉÚ ÁÒÈÉÔÅËÔÕÒÎÏ-ÓÐÅÃÉÆÉÞÎÙÈ ËÁÔÅÇÏÒÉÊ: ÜÔÏ i386 ÄÌÑ Intel-ÓÏ×ÍÅÓÔÉÍÙÈ ÍÁÛÉÎ × 32-ÂÉÔÎÏÍ ÒÅÖÉÍÅ; amd64 ÄÌÑ AMD ÍÁÛÉÎ × 64-ÂÉÔÎÏÍ ÒÅÖÉÍÅ (ÓÀÄÁ ÔÁËÖÅ ×ÈÏÄÑÔ Intel-ÓÏ×ÍÅÓÔÉÍÙÅ ÍÁÛÉÎÙ ÒÁÂÏÔÁÀÝÉÅ × ÒÅÖÉÍÅ EMT64); É ÍÅÎÅÅ ÒÁÓÐÒÏÓÔÒÁÎÅÎÎÙÅ arm, ia64, powerpc É sparc64. ìÀÄÉ ÞÁÓÔÏ ÏÛÉÂÁÀÔÓÑ × ×ÙÂÏÒÅ ËÁÔÅÇÏÒÉÉ. åÓÌÉ ×Ù ÎÅ Õ×ÅÒÅÎÙ × ÐÒÁ×ÉÌØÎÏÓÔÉ ×ÙÂÏÒÁ, ÔÏ ÌÕÞÛÅ ÎÅ ÇÁÄÁÔØ, Á ×ÙÂÒÁÔØ misc. ðÒÁ×ÉÌØÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ËÁÔÅÇÏÒÉÉ õ ×ÁÓ ÐÒÏÓÔÏÊ ðë, É ×Ù ÐÏÄÏÚÒÅ×ÁÅÔÅ, ÞÔÏ ÓÔÏÌËÎÕÌÉÓØ Ó ÐÒÏÂÌÅÍÏÊ, ÓÐÅÃÉÆÉÞÎÏÊ ÄÌÑ ËÏÎËÒÅÔÎÏÇÏ ÞÉÐÓÅÔÁ ÉÌÉ ÍÁÔÅÒÉÎÓËÏÊ ÐÌÁÔÙ: ×ÅÒÎÁÑ ËÁÔÅÇÏÒÉÑ — i386. îÅÐÒÁ×ÉÌØÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ËÁÔÅÇÏÒÉÉ åÓÌÉ ×Ù ÎÁÂÌÀÄÁÅÔÅ ÐÒÏÂÌÅÍÕ Ó ÐÅÒÉÆÅÒÉÊÎÏÊ ËÁÒÔÏÊ ÒÁÓÛÉÒÅÎÉÑ ÎÁ ÒÁÓÐÒÏÓÔÒÁÎÅÎÎÏÊ ÛÉÎÅ ÉÌÉ ÎÅÐÏÌÁÄËÉ Ó ËÏÎËÒÅÔÎÏÇÏ ÔÉÐÁ ÖÅÓÔËÉÍ ÄÉÓËÏÍ: × ÜÔÏÍ ÓÌÕÞÁÅ ×ÏÚÍÏÖÎÏ, ÞÔÏ ÎÅÉÓÐÒÁ×ÎÏÓÔØ ÎÁÂÌÀÄÁÅÔÓÑ ÎÁ ÂÏÌÅÅ ÞÅÍ ÏÄÎÏÊ ÁÒÈÉÔÅËÔÕÒÅ, É ×ÅÒÎÙÍ ×ÙÂÏÒÏÍ ÂÕÄÅÔ kern. åÓÌÉ ×Ù ÎÅ ÚÎÁÅÔÅ × ÞÅÍ ÐÒÏÂÌÅÍÁ (ÉÌÉ ×ÁÍ ËÁÖÅÔÓÑ, ÞÔÏ ÏÐÉÓÁÎÉÅ ÎÅ ÐÏÐÁÄÁÅÔ ÎÉ ÐÏÄ ËÁËÕÀ ÉÚ ×ÙÛÅÏÂÏÚÎÁÞÅÎÎÙÈ), ÉÓÐÏÌØÚÕÊÔÅ ËÁÔÅÇÏÒÉÀ misc. ðÅÒÅÄ ÔÅÍ, ËÁË ÎÁÐÉÓÁÔØ PR, ÍÏÖÎÏ ÄÌÑ ÎÁÞÁÌÁ ÓÐÒÏÓÉÔØ ÐÏÍÏÝÉ × &a.questions;. ÷ÏÚÍÏÖÎÏ, ÔÁÍ ×ÁÍ ÐÏÄÓËÁÖÕÔ, ËÁËÕÀ ÉÚ ÓÕÝÅÓÔ×ÕÀÝÉÈ ËÁÔÅÇÏÒÉÊ ÓÌÅÄÕÅÔ ×ÙÂÒÁÔØ. ÷ÏÔ ÔÅËÕÝÉÊ ÐÅÒÅÞÅÎØ ËÁÔÅÇÏÒÉÊ (×ÚÑÔ ÉÚ ): advocacy: ÐÒÏÂÌÅÍÙ, Ó×ÑÚÁÎÎÙÅ Ó ÏÂÝÅÓÔ×ÅÎÎÙÍ ÍÎÅÎÉÅÍ Ï &os;. ÷ÙÛÌÏ ÉÚ ÕÐÏÔÒÅÂÌÅÎÉÑ. amd64: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ AMD64. arm: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ ARM. bin: ÐÒÏÂÌÅÍÙ Ó ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ ÉÚ ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÙ. conf: ÐÒÏÂÌÅÍÙ Ó ÆÁÊÌÁÍÉ ÎÁÓÔÒÏÊËÉ, ÉÓÐÏÌØÚÕÅÍÙÍÉ ÐÏ ÕÍÏÌÞÁÎÉÀ ÚÎÁÞÅÎÉÑÍÉ É ÐÒÏÞÅÅ. docs: ÐÒÏÂÌÅÍÙ ÓÏ ÓÔÒÁÎÉÃÁÍÉ ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ ÉÌÉ ÏÎÌÁÊÎÏ×ÏÊ ÄÏËÕÍÅÎÔÁÃÉÅÊ. gnu: ÐÒÏÂÌÅÍÙ Ó ÐÏÒÔÉÒÏ×ÁÎÎÙÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ GNU, ÔÁËÉÍ ËÁË &man.gcc.1; ÉÌÉ &man.grep.1;. i386: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ &i386;. ia64: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ ia64. java: ÐÒÏÂÌÅÍÙ, Ó×ÑÚÁÎÎÙÅ Ó ×ÉÒÔÕÁÌØÎÏÊ ÍÁÛÉÎÏÊ &java;. kern: ÐÒÏÂÌÅÍÙ Ó ÑÄÒÏÍ ÉÌÉ Ó ÂÉÂÌÉÏÔÅËÁÍÉ × ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÅ, ÉÌÉ Ó ÄÒÁÊ×ÅÒÁÍÉ ÕÓÔÒÏÊÓÔ×, ÎÅ Ó×ÑÚÁÎÎÙÍÉ Ó ËÁËÏÊ-ÌÉÂÏ ËÏÎËÒÅÔÎÏÊ ÐÌÁÔÆÏÒÍÏÊ. misc: ×ÓÅ, ÞÔÏ ÎÅ ÐÏÄÐÁÄÁÅÔ ÎÉ ÐÏÄ ËÁËÕÀ ÄÒÕÇÕÀ ËÁÔÅÇÏÒÉÀ. (îÁÄÏ ÏÔÍÅÔÉÔØ, ÞÔÏ ÎÅÔ ÐÏÞÔÉ ÎÉÞÅÇÏ, ÞÔÏÂÙ ÄÅÊÓÔ×ÉÔÅÌØÎÏ ÓÏÏÔ×ÅÔÓÔ×Ï×ÁÌÏ ÜÔÏÊ ËÁÔÅÇÏÒÉÉ, ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÐÒÏÂÌÅÍ Ó ÒÅÌÉÚÁÍÉ É Ó ÉÎÆÒÁÓÔÒÕËÔÕÒÏÊ ÓÂÏÒËÉ. ÷ÒÅÍÅÎÎÙÅ ÏÔËÁÚÙ ÐÒÉ ÐÏÓÔÒÏÅÎÉÉ ×ÅÔËÉ HEAD ÎÅ ÐÒÉÎÁÄÌÅÖÁÔ Ë ÄÁÎÎÏÊ ËÁÔÅÇÏÒÉÉ. ôÁËÖÅ ÎÁÄÏ ÏÔÍÅÔÉÔØ, ÞÔÏ ÐÒÏÂÌÅÍÙ ÜÔÏÊ ËÁÔÅÇÏÒÉÉ ÉÍÅÀÔ ÔÅÎÄÅÎÃÉÀ ÔÅÒÑÔØÓÑ ÌÅÇÞÅ ×ÓÅÇÏ). ports: ÐÒÏÂÌÅÍÙ, Ó×ÑÚÁÎÎÙÅ Ó ËÏÌÌÅËÃÉÅÊ ÐÏÒÔÏ×. powerpc: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ &powerpc;. sparc64: ÐÒÏÂÌÅÍÙ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ &sparc64;. standards: ÐÒÏÂÌÅÍÙ, Ó×ÑÚÁÎÎÙÅ Ó ÓÏÏÔ×ÅÔÓÔ×ÉÅÍ ÓÔÁÎÄÁÒÔÁÍ. threads: ÐÒÏÂÌÅÍÙ, ËÁÓÁÀÝÉÅÓÑ ÒÅÁÌÉÚÁÃÉÉ ÔÒÅÄÏ× ×Ï &os; (ÏÓÏÂÅÎÎÏ ×Ï &os.current;). usb: ÐÒÏÂÌÅÍÙ, ÏÔÎÏÓÑÝÉÅÓÑ Ë ÒÅÁÌÉÚÁÃÉÉ USB ×Ï &os;. www: ÉÚÍÅÎÅÎÉÑ ÉÌÉ ÕÌÕÞÛÅÎÉÑ ÓÁÊÔÁ &os; Class: ÷ÙÂÅÒÉÔÅ ÏÄÎÏ ÉÚ ÓÌÅÄÕÀÝÅÇÏ: sw-bug: ÏÛÉÂËÉ × ÐÒÏÇÒÁÍÍÎÏÍ ÏÂÅÓÐÅÞÅÎÉÉ. doc-bug: ÏÛÉÂËÉ × ÄÏËÕÍÅÎÔÁÃÉÉ. change-request: ÚÁÐÒÏÓÙ ÎÁ ÒÁÓÛÉÒÅÎÉÅ ÆÕÎËÃÉÊ ÉÌÉ ÉÚÍÅÎÅÎÉÅ × ÓÕÝÅÓÔ×ÕÀÝÉÈ. update: ÏÂÎÏ×ÌÅÎÉÑ ÐÏÒÔÏ× ÉÌÉ ÄÒÕÇÏÇÏ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ ÓÔÏÒÏÎÎÉÈ ÒÁÚÒÁÂÏÔÞÉËÏ×. maintainer-update: ÏÂÎÏ×ÌÅÎÉÑ × ÐÏÒÔÁÈ, ÄÌÑ ËÏÔÏÒÙÈ ×Ù Ñ×ÌÑÅÔÅÓØ ÏÔ×ÅÔÓÔ×ÅÎÎÏÊ ÐÅÒÓÏÎÏÊ. Release: éÓÐÏÌØÚÕÅÍÁÑ ×ÁÍÉ ×ÅÒÓÉÑ &os;. ïÎÏ ÚÁÐÏÌÎÑÅÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÒÏÇÒÁÍÍÏÊ &man.send-pr.1; É ÔÒÅÂÕÅÔ ÉÚÍÅÎÅÎÉÑ, ÅÓÌÉ ÔÏÌØËÏ ×Ù ÏÔÓÙÌÁÅÔÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ Ó ÓÉÓÔÅÍÙ, ÏÔÌÉÞÁÀÝÅÊÓÑ ÏÔ ÔÏÊ, ÇÄÅ ×Ù ÓÔÏÌËÎÕÌÉÓØ Ó ÐÒÏÂÌÅÍÏÊ. é ÎÁËÏÎÅÃ, ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÍÎÏÇÏÓÔÒÏÞÎÙÈ ÐÏÌÅÊ: Environment: ïÎÏ ÄÏÌÖÎÏ ÍÁËÓÉÍÁÌØÎÏ ÔÏÞÎÏ ÏÐÉÓÙ×ÁÔØ ÏËÒÕÖÅÎÉÅ, × ËÏÔÏÒÏÍ ×ÓÔÒÅÞÁÅÔÓÑ ÐÒÏÂÌÅÍÁ. óÀÄÁ ×ËÌÀÞÁÅÔÓÑ ×ÅÒÓÉÑ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÙ, ×ÅÒÓÉÑ ËÏÎËÒÅÔÎÏÊ ÐÒÏÇÒÁÍÍÙ ÉÌÉ ÆÁÊÌÁ, ÓÏÄÅÒÖÁÝÅÇÏ ÐÒÏÂÌÅÍÕ, É ÌÀÂÁÑ ÄÒÕÇÁÑ ÉÎÆÏÒÍÁÃÉÑ, ÔÁËÁÑ, ËÁË ËÏÎÆÉÇÕÒÁÃÉÑ ÓÉÓÔÅÍÙ, ÄÒÕÇÏÅ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ËÏÔÏÒÏÅ ×ÌÉÑÅÔ ÎÁ ÐÒÏÂÌÅÍÕ, É ÔÁË ÄÁÌÅÅ—ÐÒÏÓÔÏ ×ÓÅ, ÞÔÏ ÒÁÚÒÁÂÏÔÞÉË ÄÏÌÖÅÎ ÚÎÁÔØ ÄÌÑ ÓÏÚÄÁÎÉÑ ÕÓÌÏ×ÉÊ ÐÏÑ×ÌÅÎÉÑ ÐÒÏÂÌÅÍÙ. Description: ðÏÌÎÏÅ É ÔÏÞÎÏÅ ÏÐÉÓÁÎÉÅ ÐÒÏÂÌÅÍÙ, Ó ËÏÔÏÒÏÊ ×Ù ÓÔÏÌËÎÕÌÉÓØ. ðÏÐÙÔÁÊÔÅÓØ ÉÚÂÅÖÁÔØ Ó×ÏÉÈ ÐÒÅÄÐÏÌÏÖÅÎÉÊ Ï ÐÒÉÞÉÎÁÈ ÐÒÏÂÌÅÍÙ, ÅÓÌÉ ÔÏÌØËÏ ×Ù ÎÅ Õ×ÅÒÅÎÙ, ÞÔÏ ÐÒÁ×Ù, ÔÁË ËÁË ×Ù ÍÏÖÅÔÅ ÐÒÉ×ÅÓÔÉ ÒÁÚÒÁÂÏÔÞÉËÁ Ë ÎÅÐÒÁ×ÉÌØÎÙÍ ÐÒÅÄÐÏÌÏÖÅÎÉÑÍ Ï ÐÒÏÂÌÅÍÅ. How-To-Repeat: ðÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÄÅÊÓÔ×ÉÊ, ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÂÙÔØ ×ÙÐÏÌÎÅÎÙ ÄÌÑ ÐÏ×ÔÏÒÅÎÉÑ ÐÒÏÂÌÅÍÙ. Fix: ðÒÅÄÐÏÞÔÉÔÅÌÅÎ ÐÁÔÞ, ÉÌÉ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ ÏÂÈÏÄÎÏÊ ÐÕÔØ (ËÏÔÏÒÙÊ ÎÅ ÔÏÌØËÏ ÐÏÍÏÖÅÔ ÄÒÕÇÉÍ ÌÀÄÑÍ ÏÂÏÊÔÉ ÔÕ ÖÅ ÓÁÍÕÀ ÐÒÏÂÌÅÍÕ, ÎÏ ÔÁËÖÅ ÐÏÍÏÖÅÔ ÒÁÚÒÁÂÏÔÞÉËÕ ÐÏÎÑÔØ ÅÅ ÐÒÉÞÉÎÙ), ÏÄÎÁËÏ ÅÓÌÉ Õ ×ÁÓ ÎÅÔ ÎÉËÁËÉÈ ÚÄÒÁ×ÙÈ ÉÄÅÊ, ÔÏ ÌÕÞÛÅ ÏÓÔÁ×ÉÔØ ÜÔÏ ÐÏÌÅ ÐÕÓÔÙÍ, ÞÅÍ ÓÔÒÏÉÔ ÄÏÇÁÄËÉ.
ïÔÐÒÁ×ËÁ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ &man.send-pr.1;: ëÁË ÔÏÌØËÏ ×Ù ÚÁÐÏÌÎÉÔÅ ÛÁÂÌÏÎ, ÓÏÈÒÁÎÉÔÅ ÅÇÏ É ×ÙÊÄÅÔÅ ÉÚ ÒÅÄÁËÔÏÒÁ, &man.send-pr.1; ÚÁÐÒÏÓÉÔ ×ÁÓ s)end, e)dit or a)bort?. ÷Ù ÍÏÖÅÔÅ ÎÁÖÁÔØ s ÄÌÑ ÐÒÏÄÏÌÖÅÎÉÑ É ÏÔÐÒÁ×ËÉ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ, e ÄÌÑ ÐÏ×ÔÏÒÎÏÇÏ ÚÁÐÕÓËÁ ÒÅÄÁËÔÏÒÁ É ×ÙÐÏÌÎÅÎÉÑ ÄÁÌØÎÅÊÛÉÈ ÉÚÍÅÎÅÎÉÊ, ÉÌÉ a ÄÌÑ ÏÔËÁÚÁ ÏÔ ×ÁÛÅÇÏ ÓÏÏÂÝÅÎÉÑ. åÓÌÉ ×Ù ×ÙÂÅÒÅÔÅ ÐÏÓÌÅÄÎÅÅ, ÔÏ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ ÏÓÔÁÎÅÔÓÑ ÎÁ ÄÉÓËÅ (&man.send-pr.1; ÕËÁÖÅÔ ×ÁÍ ÉÍÑ ÆÁÊÌÁ ÐÅÒÅÄ ÚÁ×ÅÒÛÅÎÉÅÍ ÒÁÂÏÔÙ), ÔÁË ÞÔÏ ×Ù ÓÍÏÖÅÔÅ ÏÔÒÅÄÁËÔÉÒÏ×ÁÔØ ÅÇÏ ÎÁ Ó×ÏÊ ×ËÕÓ ÉÌÉ ÐÅÒÅÄÁÔØ × ÓÉÓÔÅÍÕ Ó ÌÕÞÛÉÍ ÐÏÄËÌÀÞÅÎÉÅÍ Ë ÓÅÔÉ, ÐÅÒÅÄ ÔÅÍ, ËÁË ÐÏÓÌÁÔØ ÅÇÏ ÐÒÉ ÐÏÍÏÝÉ ÐÁÒÁÍÅÔÒÁ ÐÒÏÇÒÁÍÍÙ &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report ðÒÉ ÜÔÏÍ ÂÕÄÅÔ ÐÒÏÞÉÔÁÎ ÕËÁÚÁÎÎÙÊ ÆÁÊÌ, ÂÕÄÅÔ ÐÒÏ×ÅÒÅÎÏ ÓÏÄÅÒÖÉÍÏÅ, ÕÂÒÁÎÙ ËÏÍÍÅÎÔÁÒÉÉ É ÓÏÏÂÝÅÎÉÅ ÂÕÄÅÔ ÏÔÏÓÌÁÎÏ. åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ×Å ÆÏÒÍÕ: ðÅÒÅÄ ÎÁÖÁÔÉÅÍ submit ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÚÁÐÏÌÎÉÔØ ÐÒÏ×ÅÒÏÞÎÏÅ ÐÏÌÅ ÔÅËÓÔÏÍ, ÐÒÅÄÓÔÁ×ÌÅÎÎÙÍ ÎÁ ËÁÒÔÉÎËÅ ÒÑÄÏÍ. üÔÁ ÎÅÐÏÐÕÌÑÒÎÁÑ ÍÅÒÁ ÂÙÌÁ ÐÒÉÎÑÔÁ × Ó×ÑÚÉ ÓÏ ÚÌÏÕÐÏÔÒÅÂÌÅÎÉÑÍÉ ÓÏ ÓÔÏÒÏÎÙ ÒÏÂÏÔÏ× É ÎÅËÏÔÏÒÙÈ ÎÅ×ÅÒÎÏ ÓÏÒÉÅÎÔÉÒÏ×ÁÎÎÙÈ ÉÎÄÉ×ÉÄÕÕÍÏ×. üÔÏ ÎÅÏÂÈÏÄÉÍÁÑ ÍÅÒÁ, ËÏÔÏÒÁÑ ÎÉËÏÍÕ ÎÅ ÎÒÁ×ÉÔÓÑ, É, ÐÏÖÁÌÕÊÓÔÁ, ÎÅ ÐÒÏÓÉÔÅ ÎÁÓ ÕÂÒÁÔØ Å£. ïÔÍÅÔÉÍ, ÞÔÏ ×ÁÍ ÎÁÓÔÏÑÔÅÌØÎÏ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÓÏÈÒÁÎÉÔØ ×ÁÛÕ ÒÁÂÏÔÕ (PR) ËÕÄÁ-ÎÉÂÕÄØ ÐÅÒÅÄ ÎÁÖÁÔÉÅÍ ËÎÏÐËÉ submit. òÁÓÐÒÏÓÔÒÁÎÅÎÎÁÑ ÐÏÌØÚÏ×ÁÔÅÌØÓËÁÑ ÏÛÉÂËÁ: ÏÔÏÂÒÁÖÅÎÉÅ ÂÒÁÕÚÅÒÏÍ ÕÓÔÁÒÅ×ÛÅÊ ÐÒÏ×ÅÒÏÞÎÏÊ ËÁÒÔÉÎËÉ ÉÚ ÅÇÏ ËÜÛÁ. åÓÌÉ ÜÔÏ ÐÒÏÉÚÏÊÄÅÔ × ×ÁÛÅÍ ÓÌÕÞÁÅ, ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ÂÕÄÅÔ ÏÔ×ÅÒÇÎÕÔÏ É ×ÁÛÉ ÔÒÕÄÙ ÐÒÏÐÁÄÕÔ. åÓÌÉ ÐÏ ËÁËÏÊ-ÌÉÂÏ ÐÒÉÞÉÎÅ ×Ù ÎÅ ÉÍÅÅÔÅ ×ÏÚÍÏÖÎÏÓÔÉ ×ÉÄÅÔØ ÐÒÏ×ÅÒÏÞÎÕÀ ËÁÒÔÉÎËÕ, Á ÔÁËÖÅ ÎÅ ÍÏÖÅÔÅ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ &man.send-pr.1;, ÐÏÖÁÌÕÊÓÔÁ ÐÒÉÍÉÔÅ ÎÁÛÉ ÉÚ×ÉÎÅÎÉÑ ÚÁ ÎÅÕÄÏÂÓÔ×Á É ÐÒÉÛÌÉÔÅ ×ÁÛ PR ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÏÊ ËÏÍÁÎÄÅ freebsd-bugbusters@FreeBSD.org.
ïÔÓÌÅÖÉ×ÁÎÉÅ ðÏÓÌÅ ÔÏÇÏ, ËÁË ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ÂÕÄÅÔ ÐÒÉÎÑÔÏ, ×Ù ÐÏÌÕÞÉÔÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ Õ×ÅÄÏÍÌÅÎÉÅ, × ËÏÔÏÒÏÍ ÂÕÄÅÔ ÕËÁÚÁÎ ÎÏÍÅÒ ÄÌÑ ÏÔÓÌÅÖÉ×ÁÎÉÑ, ËÏÔÏÒÙÊ ÂÙÌ ÎÁÚÎÁÞÅÎ ×ÁÛÅÍÕ ÓÏÏÂÝÅÎÉÀ Ï ÐÒÏÂÌÅÍÅ É URL, ËÏÔÏÒÙÊ ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ ÐÒÏ×ÅÒËÉ ÅÇÏ ÓÏÓÔÏÑÎÉÑ. ÷ ÓÌÕÞÁÅ ÕÄÁÞÉ ËÔÏ-ÎÉÂÕÄØ ÐÒÏÑ×ÉÔ ÉÎÔÅÒÅÓ Ë ×ÁÛÅÊ ÐÒÏÂÌÅÍÅ É ÐÏÐÙÔÁÅÔÓÑ ÅÅ ÒÅÛÉÔØ, ÉÌÉ, ËÁË ÜÔÏ ÂÙ×ÁÅÔ, ÏÐÉÓÁÔØ, ÐÏÞÅÍÕ ÜÔÏ ÎÅ Ñ×ÌÑÅÔÓÑ ÐÒÏÂÌÅÍÏÊ. ÷Ù ÂÕÄÅÔÅ Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÐÏ×ÅÝÁÔØÓÑ Ï ÌÀÂÏÍ ÉÚÍÅÎÅÎÉÉ ÓÏÓÔÏÑÎÉÑ É ÐÏÌÕÞÁÔØ ËÏÐÉÉ ×ÓÅÈ ËÏÍÍÅÎÔÁÒÉÅ× ÉÌÉ ÐÁÔÞÅÊ, ËÏÔÏÒÙÅ ÂÕÄÕÔ ÐÒÉÓÏÅÄÉÎÑÔØÓÑ × ÐÒÏÃÅÓÓÅ ÏÔÒÁÂÏÔËÉ ×ÁÛÅÇÏ ÓÏÏÂÝÅÎÉÑ Ï ÐÒÏÂÌÅÍÅ. åÓÌÉ ËÔÏ-ÔÏ ÚÁÐÒÏÓÉÔ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÏÔ ×ÁÓ, ÉÌÉ ×Ù ×ÓÐÏÍÎÉÔÅ ÉÌÉ ÏÂÎÁÒÕÖÉÔÅ ÎÅÞÔÏ, ÞÔÏ ÎÅ ÕËÁÚÁÌÉ × ÎÁÞÁÌØÎÏÍ ÓÏÏÂÝÅÎÉÉ, ÐÏÖÁÌÕÊÓÔÁ ÐÏÛÌÉÔÅ ×ÁÛÅ ÄÏÐÏÌÎÅÎÉÅ (ÏÔËÌÉË) Ó ÐÏÍÏÝØÀ ÏÄÎÏÇÏ ÉÚ ÜÔÉÈ ÓÐÏÓÏÂÏ×: óÁÍÙÊ ÐÒÏÓÔÏÊ ÐÕÔØ ÜÔÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ ÓÓÙÌËÕ (followup) ÎÁ ÉÎÄÉ×ÉÄÕÁÌØÎÏÊ ×Å ÓÔÒÁÎÉÞËÅ ÓÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÉ, Ë ËÏÔÏÒÏÊ ÍÏÖÎÏ ÐÅÒÅÊÔÉ, ÉÓÐÏÌØÚÕÑ ÓÔÒÁÎÉÞËÕ ÐÏÉÓËÁ PR. ëÌÉËÎÕ× ÎÁ ÜÔÏÊ ÓÓÙÌËÅ ÏÔËÒÏÅÔÓÑ ÏËÎÏ ÄÌÑ ÏÔÐÒÁ×ËÉ email Ó ÕÖÅ ËÏÒÒÅËÔÎÏ ÚÁÐÏÌÎÅÎÎÙÍÉ ÐÏÌÑÍÉ To: É Subject: (ÅÓÌÉ ×ÁÛ ÂÒÁÕÚÅÒ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎ ÄÌÑ ÜÔÏÇÏ). éÌÉ ÐÒÏÓÔÏ ÐÏÛÌÉÔÅ ÐÉÓØÍÏ ÎÁ ÁÄÒÅÓ &a.bugfollowup;, ×ËÌÀÞÉ× ÏÔÓÌÅÖÉ×ÁÅÍÙÊ ÎÏÍÅÒ × ÔÅÍÅ ÐÉÓØÍÁ, ÞÔÏÂÙ ÓÉÓÔÅÍÁ ÏÔÓÌÅÖÉ×ÁÎÉÑ ÓÏÏÂÝÅÎÉÊ ÍÏÇÌÁ ÚÎÁÔØ, Ë ËÁËÏÍÕ ÓÏÏÂÝÅÎÉÀ Ï ÐÒÏÂÌÅÍÅ ÅÇÏ ÐÒÉÓÏÅÄÉÎÉÔØ. åÓÌÉ ×Ù ÎÅ ×ËÌÀÞÉÔÅ ÏÔÓÌÅÖÉ×ÁÅÍÙÊ ÎÏÍÅÒ, GNATS ÒÁÓÔÅÒÑÅÔÓÑ É ÓÏÚÄÁÓÔ ÓÏ×ÅÒÛÅÎÎÏ ÎÏ×ÏÅ PR, ËÏÔÏÒÏÅ ÂÕÄÅÔ ÚÁËÒÅÐÌÅÎÏ ÚÁ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ GNATS. ÷ ÒÅÚÕÌØÔÁÔÅ ×ÁÛ ÏÔËÌÉË ÚÁÔÅÒÑÅÔÓÑ ÄÏ ÔÅÈ ÐÏÒ ÐÏËÁ ËÔÏ-ÎÉÂÕÄØ ÎÅ ÎÁÞÎ£Ô ÒÁÚÇÒÅÂÁÔØ ÓËÏÐÉ×ÛÉÊÓÑ ÍÕÓÏÒ, ÞÔÏ ÍÏÖÅÔ ÐÒÏÉÚÏÊÔÉ ÓÐÕÓÔÑ ÄÎÉ ÉÌÉ ÄÁÖÅ ÎÅÄÅÌÉ. îÅÐÒÁ×ÉÌØÎÏ: Subject: that PR I sent ðÒÁ×ÉÌØÎÏ: Subject: Re: ports/12345: compilation problem with foo/bar åÓÌÉ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ ÏÓÔÁÅÔÓÑ ÏÔËÒÙÔÙÍ ÐÏÓÌÅ ÔÏÇÏ, ËÁË ÐÒÏÂÌÅÍÁ ÂÙÌÁ ÒÅÛÅÎÁ, ÐÒÏÓÔÏ ÏÔÐÒÁ×ØÔÅ ÓÏÏÂÝÅÎÉÅ (ÔÁË, ËÁË ÜÔÏ ÏÐÉÓÁÎÏ ×ÙÛÅ), Ó ÕËÁÚÁÎÉÅÍ, ÞÔÏ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ ÍÏÖÅÔ ÂÙÔØ ÚÁËÒÙÔÏ, É ÅÓÌÉ ÜÔÏ ×ÏÚÍÏÖÎÏ, ÏÂßÑÓÎÉÔÅ, ËÁË É ËÏÇÄÁ ÐÒÏÂÌÅÍÁ ÂÙÌÁ ÕÓÔÒÁÎÅÎÁ.
ðÒÏÂÌÅÍÙ ×ÚÁÉÍÏÄÅÊÓÔ×ÉÑ Ó GNATS âÏÌØÛÉÎÓÔ×Ï PR ÐÒÏÈÏÄÑÔ ÓË×ÏÚØ ÓÉÓÔÅÍÕ É ÐÒÉÎÉÍÁÀÔÓÑ ÂÙÓÔÒÏ; ÏÄÎÁËÏ, ×Ï ×ÒÅÍÑ ÚÁÇÒÕÖÅÎÎÏÓÔÉ GNATS, ÐÏÄÔ×ÅÒÖÄÅÎÉÅ ÎÁ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ Ï ÐÒÏÂÌÅÍÅ ÍÏÖÅÔ ÚÁÄÅÒÖÁÔØÓÑ ÎÁ 10 É ÂÏÌÅÅ ÍÉÎÕÔ. ðÏÖÁÌÕÊÓÔÁ, ÓÏÈÒÁÎÑÊÔÅ ÓÐÏËÏÊÓÔ×ÉÅ. ðÏÍÉÍÏ ×ÓÅÇÏ ÐÒÏÞÅÇÏ, ÔÁË ËÁË GNATS ÐÏÌÕÞÁÅÔ ×ÓÅ ÄÁÎÎÙÅ ÞÅÒÅÚ ÜÌÅËÔÒÏÎÎÕÀ ÐÏÞÔÕ, ÓÔÁÎÏ×ÉÔÓÑ ÐÏÎÑÔÎÙÍ, ÐÏÞÅÍÕ &os; ÐÒÏÐÕÓËÁÅÔ ×ÓÅ ÓÏÏÂÝÅÎÉÑ ÞÅÒÅÚ ÓÐÁÍÆÉÌØÔÒÙ. åÓÌÉ ÐÏÄÔ×ÅÒÖÄÅÎÉÅ ÎÅ ÐÒÉÈÏÄÉÔ ÎÁ ÐÒÏÔÑÖÅÎÉÉ ÞÁÓÁ-Ä×ÕÈ, ÔÏ, ×ÏÚÍÏÖÎÏ, ÞÔÏ ×ÁÛÅ ÓÏÏÂÝÅÎÉÅ ÐÏÐÁÌÏ ÐÏÄ ÎÉÈ; ÅÓÌÉ ÔÁË, ÔÏ, ÐÏÖÁÌÕÊÓÔÁ, Ó×ÑÖÉÔÅÓØ Ó ÁÄÍÉÎÉÓÔÒÁÔÏÒÁÍÉ GNATS ÐÏ ÁÄÒÅÓÕ bugmeister@FreeBSD.org É ÐÏÐÒÏÓÉÔÅ ÐÏÍÏÝÉ. óÒÅÄÉ ÁÎÔÉÓÐÁÍ ÍÅÒ ÅÓÔØ ÏÄÎÁ, ËÏÔÏÒÁÑ ÓÏÐÏÓÔÁ×ÌÑÅÔ ÓÏÏÂÝÅÎÉÑ Ó ÍÎÏÖÅÓÔ×ÏÍ ÚÌÏÕÐÏÔÒÅÂÌÅÎÉÊ, ÎÁÂÌÀÄÁÅÍÙÈ × ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ Ó HTML-ÆÏÒÍÁÔÉÒÏ×ÁÎÉÅÍ ÔÅËÓÔÁ (ÏÄÎÁËÏ, ÓÀÄÁ ÎÅ ÏÔÎÏÓÉÔÓÑ ÐÒÏÓÔÏÅ ×ËÌÀÞÅÎÉÅ HTML × PR). íÙ ÎÁÓÔÏÑÔÅÌØÎÏ ÒÅËÏÍÅÎÄÕÅÍ ÎÅ ÉÓÐÏÌØÚÏ×ÁÔØ HTML-ÆÏÒÍÁÔÉÒÏ×ÁÎÎÙÊ ÔÅËÓÔ ÐÒÉ ÐÏÓÙÌËÅ PR: ÎÅ ÔÏÌØËÏ ÉÚ-ÚÁ ×ÅÒÏÑÔÎÏÓÔÉ ÐÏÐÁÄÁÎÉÑ × ÓÐÁÍÆÉÌØÔÒÙ, ÎÏ É ÉÚ-ÚÁ ÚÁÇÒÏÍÏÖÄÅÎÉÑ ÂÁÚÙ ÄÁÎÎÙÈ. ïÔÄÁÊÔÅ ÐÒÅÄÐÏÞÔÅÎÉÅ ÐÒÏÓÔÏÍÕ ÓÔÁÒÏÍÕ ÔÅËÓÔÏ×ÏÍÕ ÆÏÒÍÁÔÕ. ÷ ÒÅÄËÉÈ ÓÌÕÞÁÑÈ ×Ù ÍÏÖÅÔÅ ÓÔÏÌËÎÕÔØÓÑ Ó ÏÛÉÂËÏÊ GNATS, ËÏÇÄÁ PR ÐÒÉÎÑÔ É ÅÍÕ ÐÒÉÓ×ÏÅÎ ÎÏÍÅÒ, ÎÏ ÏÎ ÎÅ ÏÔÏÂÒÁÖÁÅÔÓÑ × ÓÐÉÓËÁÈ PR ÎÉ ÎÁ ÏÄÎÏÊ ÉÚ ÓÔÒÁÎÉà ×Å ÐÏÉÓËÁ PR. ÷ÅÒÏÑÔÎÏ, ÞÔÏ ÒÁÓÓÉÎÈÒÏÎÉÚÉÒÏ×ÁÌÓÑ ÉÎÄÅËÓ ÂÁÚÙ Ó ÓÁÍÏÊ ÂÁÚÏÊ. üÔÏÔ ÓÌÕÞÁÊ ÍÏÖÎÏ ÐÒÏ×ÅÒÉÔØ, ÏÂÒÁÔÉ×ÛÉÓØ Ë ÓÔÒÁÎÉÞËÅ Query PR Database É ÐÒÏËÏÎÔÒÏÌÉÒÏ×Á× ÎÁÌÉÞÉÅ ×ÁÛÅÇÏ PR. åÓÌÉ ÏÎ ÅÓÔØ, ÐÏÖÁÌÕÊÓÔÁ, ÉÚ×ÅÓÔÉÔÅ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏ× GNATS (bugmeister@FreeBSD.org). óÌÅÄÕÅÔ ÏÔÍÅÔÉÔØ, ÞÔÏ ÐÅÒÅÓÔÒÏÊËÁ ÂÁÚÙ ×ÙÐÏÌÎÑÅÔÓÑ ÐÅÒÉÏÄÉÞÅÓËÉ ÐÏ cron, É ÅÓÌÉ ×ÁÍ ÎÅ Ë ÓÐÅÈÕ, ÔÏ ÎÅ ÐÒÅÄÐÒÉÎÉÍÁÊÔÅ ÎÉËÁËÉÈ ÛÁÇÏ×.
äÏÐÏÌÎÉÔÅÌØÎÁÑ ÌÉÔÅÒÁÔÕÒÁ üÔÏ ÓÐÉÓÏË ÉÎÆÏÒÍÁÃÉÏÎÎÙÈ ÒÅÓÕÒÓÏ×, ÏÔÎÏÓÑÝÉÈÓÑ Ë ÐÒÁ×ÉÌØÎÏÍÕ ÎÁÐÉÓÁÎÉÀ É ÏÂÒÁÂÏÔËÅ ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÁÈ. ïÎ, ÂÅÚ ÓÏÍÎÅÎÉÑ, ÎÅ ÐÏÌÏÎ. How to Report Bugs Effectively—ÐÒÅËÒÁÓÎÏÅ ÜÓÓÅ, ËÏÔÏÒÏÅ ÎÁÐÉÓÁÌ Simon G. Tatham Ï ÓÏÓÔÁ×ÌÅÎÉÉ ÐÏÌÅÚÎÙÈ (ÎÅ ÓÐÅÃÉÆÉÞÎÙÈ ÄÌÑ &os;) ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÁÈ. Problem Report Handling Guidelines—ÉÎÔÅÒÅÓÎÙÊ ×ÚÇÌÑÄ ÎÁ ÏÂÒÁÂÏÔËÕ ÓÏÏÂÝÅÎÉÊ Ï ÐÒÏÂÌÅÍÁÈ ÓÁÍÉÍÉ ÒÁÚÒÁÂÏÔÞÉËÁÍÉ &os;.
+ +
diff --git a/ru_RU.KOI8-R/books/developers-handbook/Makefile b/ru_RU.KOI8-R/books/developers-handbook/Makefile index 1fa6b0331c..f0a1cca26b 100644 --- a/ru_RU.KOI8-R/books/developers-handbook/Makefile +++ b/ru_RU.KOI8-R/books/developers-handbook/Makefile @@ -1,51 +1,49 @@ # # The FreeBSD Russian Documentation Project # # $FreeBSD$ # $FreeBSDru: frdp/doc/ru_RU.KOI8-R/books/developers-handbook/Makefile,v 1.8 2005/05/05 09:07:25 andy Exp $ # # Original revision: r21373 # # Build the FreeBSD Developers' Handbook. # MAINTAINER=andy@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # Images IMAGES_EN = sockets/layers.eps sockets/sain.eps sockets/sainfill.eps sockets/sainlsb.eps sockets/sainmsb.eps sockets/sainserv.eps sockets/serv.eps sockets/serv2.eps sockets/slayers.eps # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= dma/chapter.xml SRCS+= introduction/chapter.xml SRCS+= ipv6/chapter.xml SRCS+= kerneldebug/chapter.xml SRCS+= kernelopts/chapter.xml SRCS+= l10n/chapter.xml SRCS+= policies/chapter.xml SRCS+= secure/chapter.xml SRCS+= sockets/chapter.xml SRCS+= testing/chapter.xml SRCS+= tools/chapter.xml SRCS+= x86/chapter.xml # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/ru_RU.KOI8-R/books/developers-handbook/book.xml b/ru_RU.KOI8-R/books/developers-handbook/book.xml index b5834f906a..17c08ceede 100644 --- a/ru_RU.KOI8-R/books/developers-handbook/book.xml +++ b/ru_RU.KOI8-R/books/developers-handbook/book.xml @@ -1,501 +1,503 @@ %chapters; ]> òÕËÏ×ÏÄÓÔ×Ï FreeBSD ÄÌÑ ÒÁÚÒÁÂÏÔÞÉËÏ× The FreeBSD Documentation Project
doc@FreeBSD.org
á×ÇÕÓÔ 2000 2000 The FreeBSD Documentation Project &legalnotice; $FreeBSD$ äÏÂÒÏ ÐÏÖÁÌÏ×ÁÔØ × ÒÕËÏ×ÏÄÓÔ×Ï FreeBSD ÄÌÑ ÒÁÚÒÁÂÏÔÞÉËÏ×. ÷×ÅÄÅÎÉÅ òÁÚÒÁÂÏÔËÁ ×Ï FreeBSD úÄÅÓØ ÎÅÏÂÈÏÄÉÍÏ ÂÕÄÅÔ ÏÂÓÕÄÉÔØ FreeBSD × ËÁÞÅÓÔ×Å ÐÌÁÔÆÏÒÍÙ ÄÌÑ ÒÁÚÒÁÂÏÔËÉ, ÐÏÄÈÏÄ Ë ÜÔÏÍÕ BSD, ÏÂÚÏÒ ÁÒÈÉÔÅËÔÕÒÙ, ÓÔÒÕËÔÕÒÁ /usr/src, ÉÓÔÏÒÉÑ É ÔÁË ÄÁÌÅÅ. óÐÁÓÉÂÏ ×ÁÍ ÚÁ ×ÙÂÏÒ FreeBSD × ËÁÞÅÓÔ×Å ÐÌÁÔÆÏÒÍÙ ÒÁÚÒÁÂÏÔËÉ! îÁÄÅÅÍÓÑ, ÞÔÏ ÏÎÁ ×ÁÓ ÎÅ ÐÏÄ×ÅÄÅÔ. ðÁÒÁÄÉÇÍÁ BSD ïÂÚÏÒ ÁÒÈÉÔÅËÔÕÒÙ óÔÒÕËÔÕÒÁ /usr/src ðÏÌÎÙÊ ÉÓÈÏÄÎÙÊ ËÏÄ FreeBSD ÉÍÅÅÔÓÑ ÎÁ ÎÁÛÅÍ ÏÂÝÅÄÏÓÔÕÐÎÏÍ ÈÒÁÎÉÌÉÝÅ CVS. ëÁË ÐÒÁ×ÉÌÏ, ÉÓÈÏÄÎÙÊ ËÏÄ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ × ËÁÔÁÌÏÇ /usr/src, ÓÏÄÅÒÖÁÝÉÊ ÓÌÅÄÕÀÝÉÅ ÐÏÄËÁÔÁÌÏÇÉ. ëÁÔÁÌÏÇ ïÐÉÓÁÎÉÅ bin/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /bin contrib/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, ËÏÔÏÒÏÅ ÐÒÅÄÏÓÔÁ×ÌÅÎÏ ÔÒÅÔØÉÍÉ ÌÉÃÁÍÉ. crypto/ éÓÈÏÄÎÙÊ ËÏÄ DES etc/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /etc games/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/games gnu/ õÔÉÌÉÔÙ, ÐÏÄÐÁÄÁÀÝÉÅ ÐÏÄ ÕÓÌÏ×ÉÑ GNU Public License include/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/include kerberosIV/ éÓÈÏÄÎÙÊ ËÏÄ Kerbereros ×ÅÒÓÉÉ IV kerberos5/ éÓÈÏÄÎÙÊ ËÏÄ Kerbereros ×ÅÒÓÉÉ 5 lib/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/lib libexec/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/libexec release/ æÁÊÌÙ, ÎÅÏÂÈÏÄÉÍÙÅ ÄÌÑ ×ÙÐÕÓËÁ ÒÅÌÉÚÁ FreeBSD sbin/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /sbin secure/ éÓÈÏÄÎÙÊ ËÏÄ FreeSec share/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /sbin sys/ éÓÈÏÄÎÙÅ ÔÅËÓÔÙ ÑÄÒÁ tools/ éÎÓÔÒÕÍÅÎÔÁÌØÎÙÅ ÓÒÅÄÓÔ×Á, ÉÓÐÏÌØÚÅÍÙÅ ÄÌÑ ÏÂÓÌÕÖÉ×ÁÎÉÑ É ÔÅÓÔÉÒÏ×ÁÎÉÑ FreeBSD usr.bin/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/bin usr.sbin/ éÓÈÏÄÎÙÊ ËÏÄ ÆÁÊÌÏ× ÉÚ /usr/sbin ïÓÎÏ×Ù &chap.secure; ñÄÒÏ éÓÔÏÒÉÑ ÑÄÒÁ Unix îÅÍÎÏÇÏ ÉÓÔÏÒÉÉ Ï ÑÄÒÅ Unix/BSD, ÓÉÓÔÅÍÎÙÈ ×ÙÚÏ×ÁÈ, ËÁË ÒÁÂÏÔÁÀÔ ÐÒÏÃÅÓÓÙ, ÂÌÏËÉÒÏ×ËÅ, ÐÌÁÎÉÒÏ×ËÅ ÚÁÄÁÞ, ÎÉÔÉ (ÑÄÒÁ), ÐÅÒÅËÌÀÞÅÎÉÅ ËÏÎÔÅËÓÔÁ, ÓÉÇÎÁÌÙ, ÐÒÅÒÙ×ÁÎÉÑ, ÍÏÄÕÌÉ É ÔÁË ÄÁÌÅÅ. &chap.locking; ðÁÍÑÔØ É ×ÉÒÔÕÁÌØÎÁÑ ÐÁÍÑÔØ ÷ÉÒÔÕÁÌØÎÁÑ ÐÁÍÑÔØ VM, ÐÏÓÔÒÁÎÉÞÎÁÑ ÐÏÄËÁÞËÁ É Ó×ÏÐÉÒÏ×ÁÎÉÅ, ×ÙÄÅÌÅÎÉÅ ÐÁÍÑÔÉ, ÔÅÓÔÉÒÏ×ÁÎÉÅ ÏÛÉÂÏË ÕÔÅÞËÉ ÐÁÍÑÔÉ, mmap, vnode É ÔÁË ÄÁÌÅÅ. óÉÓÔÅÍÁ ××ÏÄÁ/×Ù×ÏÄÁ UFS UFS, FFS, Ext2FS, JFS, inodes, buffer cache, labeling, locking, metadata, soft-updates, LFS, portalfs, procfs, vnodes, memory sharing, memory objects, TLBs, caching íÅÖÐÒÏÃÅÓÓÎÏÅ ×ÚÁÉÍÏÄÅÊÓÔ×ÉÅ óÉÇÎÁÌÙ óÉÇÎÁÌÙ, ËÏÎ×ÅÊÅÒÙ, ÓÅÍÁÆÏÒÙ, ÏÞÅÒÅÄÉ ÓÏÏÂÝÅÎÉÊ, ÓÏ×ÍÅÓÔÎÏ ÉÓÐÏÌØÚÕÅÍÁÑ ÐÁÍÑÔØ, ÓÏËÅÔÙ, Ä×ÅÒÉ òÁÂÏÔÁ × ÓÅÔÉ óÏËÅÔÙ óÏËÅÔÙ, bpf, IP, TCP, UDP, ICMP, OSI, bridging, firewalling, NAT, ËÏÍÍÕÔÁÃÉÑ É ÔÁË ÄÁÌÅÅ óÅÔÅ×ÙÅ ÆÁÊÌÏ×ÙÅ ÓÉÓÔÅÍÙ AFS AFS, NFS, SANs etc] òÁÂÏÔÁ Ó ÔÅÒÍÉÎÁÌÁÍÉ óÉÓÔÅÍÎÙÅ ËÏÎÓÏÌÉ Syscons, tty, PCVT, ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÁÑ ËÏÎÓÏÌØ, ÈÒÁÎÉÔÅÌÉ ÜËÒÁÎÁ É ÔÁË ÄÁÌÅÅ ú×ÕË OSS OSS, waveforms, etc äÒÁÊ×ÅÒÙ ÕÓÔÒÏÊÓÔ× &chap.driverbasics; &chap.pci; õÓÔÒÏÊÓÔ×Á USB üÔÁ ÇÌÁ×Á ÒÁÓÓËÁÖÅÔ Ï ÍÅÈÁÎÉÚÍÁÈ, ÉÓÐÏÌØÚÕÅÍÙÈ ×Ï FreeBSD ÄÌÑ ÎÁÐÉÓÁÎÉÑ ÄÒÁÊ×ÅÒÏ× ÄÌÑ ÕÓÔÒÏÊÓÔ× ÎÁ ÛÉÎÅ USB. NewBus üÔÁ ÇÌÁ×Á ÒÁÓÓËÁÖÅÔ Ï ÁÒÈÉÔÅËÔÕÒÅ NewBus ×Ï FreeBSD. áÐÐÁÒÁÔÎÙÅ ÐÌÁÔÆÏÒÍÙ IA-32 òÁÓÓËÁÚ Ï ÁÒÈÉÔÅËÔÕÒÎÙÈ ÏÓÏÂÅÎÎÏÓÔÑÈ FreeBSD/x86. Alpha òÁÓÓËÁÚ Ï ÁÒÈÉÔÅËÔÕÒÎÙÈ ÏÓÏÂÅÎÎÏÓÔÑÈ FreeBSD/alpha. ïÐÉÓÁÎÉÅ ÏÛÉÂÏË ×ÙÒÁ×ÎÉ×ÁÎÉÑ, ËÁË ÉÈ ÉÓÐÒÁ×ÌÑÔØ É ËÁË ÉÇÎÏÒÉÒÏ×ÁÔØ. ðÒÉÍÅÒ ÁÓÓÅÍÂÌÅÒÎÏÇÏ ËÏÄÁ ÄÌÑ FreeBSD/alpha. IA-64 òÁÓÓËÁÚ Ï ÁÒÈÉÔÅËÔÕÒÎÙÈ ÏÓÏÂÅÎÎÏÓÔÑÈ FreeBSD/ia64. ïÔÌÁÄËÁ Truss òÁÚÌÉÞÎÙÅ ÏÐÉÓÁÎÉÑ ÔÏÇÏ, ËÁË ÏÔÌÁÖÉ×ÁÔØ ÏÔÄÅÌØÎÙÅ ËÏÍÐÏÎÅÎÔÙ ÓÉÓÔÅÍÙ ÐÒÉ ÐÏÍÏÝÉ ÕÔÉÌÉÔ truss, ktrace, gdb, kgdb, etc ïÂÅÓÐÅÞÅÎÉÅ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ Linux Linux, SVR4 É ÔÁË ÄÁÌÅÅ ðÒÉÌÏÖÅÎÉÑ Dave A Patterson John L Hennessy 1998Morgan Kaufmann Publishers, Inc. 1-55860-428-6 Morgan Kaufmann Publishers, Inc. Computer Organization and Design The Hardware / Software Interface 1-2 W. Richard Stevens 1993Addison Wesley Longman, Inc. 0-201-56317-7 Addison Wesley Longman, Inc. Advanced Programming in the Unix Environment 1-2 Marshall Kirk McKusick Keith Bostic Michael J Karels John S Quarterman 1996Addison-Wesley Publishing Company, Inc. 0-201-54979-4 Addison-Wesley Publishing Company, Inc. The Design and Implementation of the 4.4 BSD Operating System 1-2 Aleph One Phrack 49; "Smashing the Stack for Fun and Profit" Chrispin Cowan Calton Pu Dave Maier StackGuard; Automatic Adaptive Detection and Prevention of Buffer-Overflow Attacks Todd Miller Theo de Raadt strlcpy and strlcat -- consistent, safe string copy and concatenation. + + diff --git a/ru_RU.KOI8-R/books/developers-handbook/chapters.ent b/ru_RU.KOI8-R/books/developers-handbook/chapters.ent index 5419653a3d..cad461601b 100644 --- a/ru_RU.KOI8-R/books/developers-handbook/chapters.ent +++ b/ru_RU.KOI8-R/books/developers-handbook/chapters.ent @@ -1,40 +1,40 @@ - +"> diff --git a/ru_RU.KOI8-R/books/fdp-primer/book.xml b/ru_RU.KOI8-R/books/fdp-primer/book.xml index ec7c536532..24f949ef65 100644 --- a/ru_RU.KOI8-R/books/fdp-primer/book.xml +++ b/ru_RU.KOI8-R/books/fdp-primer/book.xml @@ -1,265 +1,263 @@ %chapters; ]> õÞÅÂÎÉË ÐÏ ðÒÏÅËÔÕ äÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD ÄÌÑ ÎÏ×ÙÈ ÕÞÁÓÔÎÉËÏ× The FreeBSD Documentation Project 1998 1999 2000 2001 2002 2003 2004 2005 DocEng $FreeBSD$ $FreeBSD$ &bookinfo.legalnotice; âÌÁÇÏÄÁÒÉÍ ×ÁÓ ÚÁ ÔÏ, ÞÔÏ ×Ù ÓÔÁÌÉ ÞÁÓÔØÀ ðÒÏÅËÔÁ äÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD. ÷ÁÛÅ ÕÞÁÓÔÉÅ ÞÒÅÚ×ÙÞÁÊÎÏ ÎÕÖÎÏ. üÔÏÔ ÕÞÅÂÎÉË ÏÐÉÓÙ×ÁÅÔ ×ÓÅ, ÞÔÏ ×ÁÍ ÎÕÖÎÏ ÚÎÁÔØ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÒÉÎÑÔØ ÕÞÁÓÔÉÅ × ðÒÏÅËÔÅ äÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD, ÏÔ ÉÎÓÔÒÕÍÅÎÔÏ× É ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, ËÏÔÏÒÏÅ ×Ù ÂÕÄÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ (ËÁË ÏÂÑÚÁÔÅÌØÎÏÅ, ÔÁË É ÒÅËÏÍÅÎÄÕÅÍÏÅ), ÄÏ ÆÉÌÏÓÏÆÉÉ ðÒÏÅËÔÁ äÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ. üÔÏÔ ÄÏËÕÍÅÎÔ ×ÓÅ ×ÒÅÍÑ ÐÏÄ×ÅÒÇÁÅÔÓÑ ÉÚÍÅÎÅÎÉÑÍ, É ÎÅ ÐÏÌÏÎ. åÝÅ ÎÅ ÚÁËÏÎÞÅÎÎÙÅ ÒÁÚÄÅÌÙ ÐÏÍÅÞÅÎÙ ÚÎÁËÏÍ * × ÎÁÚ×ÁÎÉÉ. éÓÐÏÌØÚÕÅÍÙÅ ÓÏËÒÁÝÅÎÉÑ ðÒÉÇÌÁÛÅÎÉÑ ËÏÍÁÎÄÎÙÈ ÐÒÏÃÅÓÓÏÒÏ× ÷ ÓÌÅÄÕÀÝÅÊ ÔÁÂÌÉÃÅ ÐÏËÁÚÁÎÏ ÓÉÓÔÅÍÎÏÅ ÐÒÉÇÌÁÛÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ É ÐÒÉÇÌÁÛÅÎÉÅ ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ. ÷ ÐÒÉÍÅÒÁÈ ÔÁËÏÅ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÄÌÑ ÏÂÏÚÎÁÞÅÎÉÑ ÔÏÇÏ, ËÁËÉÍ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÄÏÌÖÅÎ ×ÙÐÏÌÎÑÔØÓÑ ÐÒÉÍÅÒ. ðÏÌØÚÏ×ÁÔÅÌØ ðÒÉÇÌÁÛÅÎÉÅ ïÂÙÞÎÙÊ ÐÏÌØÚÏ×ÁÔÅÌØ &prompt.user; root &prompt.root; ôÉÐÏÇÒÁÆÓËÉÅ ÓÏÇÌÁÛÅÎÉÑ ÷ ÓÌÅÄÕÀÝÅÊ ÔÁÂÌÉÃÅ ÏÐÉÓÁÎÙ ÔÉÐÏÇÒÁÆÓËÉÅ ÓÏÇÌÁÛÅÎÉÑ, ÉÓÐÏÌØÚÕÅÍÙÅ × ÜÔÏÊ ËÎÉÇÅ. úÎÁÞÅÎÉÅ ðÒÉÍÅÒÙ îÁÚ×ÁÎÉÑ ËÏÍÁÎÄ, ÉÍÅÎÁ ÆÁÊÌÏ× É ËÁÔÁÌÏÇÏ×. ÷ÙÄÁÞÁ ÎÁ ÜËÒÁÎ. ïÔÒÅÄÁËÔÉÒÕÊÔÅ ×ÁÛ ÆÁÊÌ .login.éÓÐÏÌØÚÕÊÔÅ ËÏÍÁÎÄÕ ls -a ÄÌÑ ×ÙÄÁÞÉ ÓÐÉÓËÁ ×ÓÅÈ ÆÁÊÌÏ×. You have mail. ôÏ, ÞÔÏ ÎÁÂÉÒÁÅÔÅ ×Ù, ËÏÇÄÁ ÜÔÏ ÏÔÌÉÞÁÅÔÓÑ ÏÔ ÜËÒÁÎÎÏÊ ×ÙÄÁÞÉ ËÏÍÐØÀÔÅÒÏÍ. &prompt.user; su Password: óÓÙÌËÉ ÎÁ ÓÔÒÁÎÉÃÙ ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ. ÷ÏÓÐÏÌØÚÕÊÔÅÓØ ËÏÍÁÎÄÏÊ su 1 ÄÌÑ ÓÍÅÎÙ ÉÍÅÎÉ ÐÏÌØÚÏ×ÁÔÅÌÑ. éÍÅÎÁ ÐÏÌØÚÏ×ÁÔÅÌÅÊ É ÇÒÕÐÐ ôÏÌØËÏ root ÍÏÖÅÔ ÜÔÏ ÄÅÌÁÔØ. ÷ÙÄÅÌÅÎÉÅ ÷Ù ÄÏÌÖÎÙ ÜÔÏ ÓÄÅÌÁÔØ. ðÅÒÅÍÅÎÎÙÅ ÐÁÒÁÍÅÔÒÙ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ; ÚÁÍÅÎÑÊÔÅ ÉÈ ÒÅÁÌØÎÙÍÉ ÎÁÚ×ÁÎÉÑÍÉ ÉÌÉ ÚÎÁÞÅÎÉÑÍÉ. äÌÑ ÕÄÁÌÅÎÉÑ ÆÁÊÌÁ ÎÁÂÅÒÉÔÅ rm filename ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ $HOME Ñ×ÌÑÅÔÓÑ ×ÁÛÉÍ ÄÏÍÁÛÎÉÍ ËÁÔÁÌÏÇÏÍ. úÁÍÅÞÁÎÉÑ, ÓÏ×ÅÔÙ, ×ÁÖÎÁÑ ÉÎÆÏÒÍÁÃÉÑ, ÐÒÅÄÕÐÒÅÖÄÅÎÉÑ É ÐÒÉÍÅÒÙ ÷ÎÕÔÒÉ ÔÅËÓÔÁ ×ÓÔÒÅÞÁÀÔÓÑ ÚÁÍÅÞÁÎÉÑ, ÐÒÅÄÕÐÒÅÖÄÅÎÉÑ É ÐÒÉÍÅÒÙ. úÁÍÅÞÁÎÉÑ ÉÍÅÀÔ ÔÁËÏÊ ×ÉÄ, É ÓÏÄÅÒÖÁÔ ÉÎÆÏÒÍÁÃÉÀ, ËÏÔÏÒÕÀ ×Ù ÄÏÌÖÎÙ ÐÒÉÎÑÔØ Ë Ó×ÅÄÅÎÉÀ, ÔÁË ËÁË ÏÎÁ ÍÏÖÅÔ ÚÁÔÒÏÎÕÔØ ×ÁÛÉ ÄÅÊÓÔ×ÉÑ. óÏ×ÅÔÙ ÉÍÅÀÔ ÔÁËÏÊ ×ÉÄ, É ÓÏÄÅÒÖÁÔ ÉÎÆÏÒÍÁÃÉÀ, ËÏÔÏÒÁÑ ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÐÏÌÅÚÎÏÊ ÄÌÑ ×ÁÓ, ÉÌÉ ÐÒÅÄÌÁÇÁÀÔ ÂÏÌÅÅ ÐÒÏÓÔÏÊ ÓÐÏÓÏ ÓÄÅÌÁÔØ ÞÔÏ-ÌÉÂÏ. ÷ÁÖÎÁÑ ÉÎÆÏÒÍÁÃÉÑ ÉÍÅÅÔ ÔÁËÏÊ ×ÉÄ. ïÂÙÞÎÏ ÚÄÅÓØ ÏÂÒÁÝÁÅÔÓÑ ×ÎÉÍÁÎÉÅ ÎÁ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÄÅÊÓÔ×ÉÑ, ËÏÔÏÒÙÅ ×ÁÍ ÍÏÖÅÔ ÐÏÔÒÅÂÏ×ÁÔØÓÑ ×ÙÐÏÌÎÉÔØ. ðÒÅÄÕÐÒÅÖÄÅÎÉÑ ÉÍÅÀÔ ÐÒÉÍÅÒÎÏ ÔÁËÏÊ ×ÉÄ É ÓÏÄÅÒÖÁÔ ÉÎÆÏÒÍÁÃÉÀ, × ËÏÔÏÒÏÊ ×Ù ÐÒÅÄÕÐÒÅÖÄÁÅÔÅÓØ Ï ×ÏÚÍÏÖÎÙÈ ÐÏÓÌÅÄÓÔ×ÉÑÈ ÔÏÇÏ, ÞÔÏ ×Ù ÎÅ ÂÕÄÅÔÅ ÓÌÅÄÏ×ÁÔØ ÉÎÓÔÒÕËÃÉÑÍ. üÔÉ ÏÐÁÓÎÏÓÔÉ ÍÏÇÕÔ ÂÙÔØ ËÁË ÆÉÚÉÞÅÓËÉÍÉ, Ó×ÑÚÁÎÎÙÍÉ Ó ×ÁÍÉ ÉÌÉ ÏÂÏÒÕÄÏ×ÁÎÉÅÍ, ÔÁË É ÎÅ ÆÉÚÉÞÅÓËÉÍÉ, ÔÁËÉÍÉ, ËÁË ÂÅÚÕÓÌÏ×ÎÏÅ ÕÄÁÌÅÎÉÅ ×ÁÖÎÙÈ ÆÁÊÌÏ×. ðÒÉÍÅÒ ðÒÉÍÅÒÙ ÉÍÅÀÔ ÔÁËÏÊ ×ÉÄ É ÏÂÙÞÎÏ ÓÏÄÅÒÖÁÔ ÐÒÉÍÅÒÙ, ËÏÔÏÒÙÍ ×Ù ÄÏÌÖÎÙ ÓÌÅÄÏ×ÁÔØ, ÉÌÉ ÐÏËÁÚÙ×ÁÀÔ ÒÅÚÕÌØÔÁÔÙ, ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÐÏÌÕÞÉÔØÓÑ ÐÒÉ ×ÙÐÏÌÎÅÎÉÉ ÎÅËÏÔÏÒÙÈ ÄÅÊÓÔ×ÉÊ. âÌÁÇÏÄÁÒÎÏÓÔÉ ñ ÂÌÁÇÏÄÁÒÀ Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn É Christopher Maden, ËÏÔÏÒÙÅ ×ÙÂÒÁÌÉ ×ÒÅÍÑ ÄÌÑ ÞÔÅÎÉÑ ÒÁÎÎÉÈ ÞÅÒÎÏ×ÉËÏ× ÜÔÏÇÏ ÄÏËÕÍÅÎÔÁ É ÄÁÌÉ ÍÎÏÇÏ ÃÅÎÎÙÈ ÚÁÍÅÞÁÎÉÊ É ËÒÉÔÉËÉ. &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/ru_RU.KOI8-R/books/handbook/Makefile b/ru_RU.KOI8-R/books/handbook/Makefile index 8aaeb316e6..fd4036016b 100644 --- a/ru_RU.KOI8-R/books/handbook/Makefile +++ b/ru_RU.KOI8-R/books/handbook/Makefile @@ -1,302 +1,300 @@ # # The FreeBSD Russian Documentation Project # # $FreeBSD$ # $FreeBSDru: frdp/doc/ru_RU.KOI8-R/books/handbook/Makefile,v 1.46 2006/05/19 12:09:01 marck Exp $ # # Original revision: r27853 # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER=phantom@FreeBSD.org DOC?= book FORMATS?= html-split -#HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/desktop.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= install/xf86setup.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif url_relprEFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/ru_RU.KOI8-R/books/handbook/chapters.ent b/ru_RU.KOI8-R/books/handbook/chapters.ent index 45bfeaa687..e5a82213c0 100644 --- a/ru_RU.KOI8-R/books/handbook/chapters.ent +++ b/ru_RU.KOI8-R/books/handbook/chapters.ent @@ -1,75 +1,75 @@ %pgpkeys; - + "> diff --git a/zh_CN.GB2312/articles/contributing/article.xml b/zh_CN.GB2312/articles/contributing/article.xml index ba80c2c4cd..c01f86f58a 100644 --- a/zh_CN.GB2312/articles/contributing/article.xml +++ b/zh_CN.GB2312/articles/contributing/article.xml @@ -1,505 +1,507 @@
Ϊ FreeBSD Ìṩ°ïÖú ÎÞÂÛÊÇ×÷Ϊ¸öÈË»¹ÊÇ×éÖ¯»ú¹¹£¬Èç¹ûÄúÏ£ÍûΪFreeBSDÏîÄ¿Ìṩ°ïÖú£¬ ¶¼¿ÉÒÔÔÚ±¾ÎÄÖÐÕÒµ½ºÏÊʵķ½·¨¡£ Jordan Hubbard Ô­Öø &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ ¹±Ï× ÄúÏ£Íû¸ø FreeBSD ÏîÄ¿×öµãʲôÂ𣿠̫ºÃÁË£¬ ÎÒÃÇ»¶Ó­Äú¡£ FreeBSD ÕýÊÇ ÒÀ¿¿ ¹ã´óÓû§µÄ¹±ÏײŵÃÒÔ·¢Õ¹×³´óµÄ¡£ ÎÒÃDz»½ö·Ç³£¸ÐлÄúËù×öµÄ¹±Ï×£¬¶øÇÒ£¬ÕâЩ¹¤×÷¶ÔÓÚ FreeBSD µÄ³ÖÐø·¢Õ¹Ò²ÖÁ¹ØÖØÒª¡£ Ò²ÐíÓëÄúÏëÏóµÄ²»Í¬£¬ Äú¼È²»±ØÊÇÒ»Ãû³öÉ«µÄ³ÌÐòÔ±£¬ Ò²ÎÞÐëºÍ FreeBSD ºËÐÄÍŶӳÉÔ±ÓкܺõÄ˽½»£¬ ÎÒÃÇ»áÒ»ÊÓͬÈʵĶԴýÄúµÄ¹¤×÷¡£ FreeBSD µÄ¿ª·¢ÈËÔ±±é²¼È«Çò£¬ ´ó¼Ò¼¼Êõר³¤¸÷Ò죬 ÄêÁä·Ö²¼Ò²·Ç³£¹ã·º¡£ ÿÌ죬 ÎÒÃǶ¼ÔÚÃæ¶Ô³ÖÐøÔö³¤µÄ¹¤×÷¶ø¿àÓÚûÓÐ×ã¹»µÄÈËÊÖ£¬ Òò´ËÎÒÃÇËæʱ»¶Ó­ÄúµÄ°ïÖú¡£ FreeBSD ÏîÄ¿´¦ÀíµÄÊÇÒ»¸öÍêÕûµÄ²Ù×÷ϵͳ»·¾³£¬ ¶ø²»Ö»ÊÇÒ»¸öÄں˻òÊÇһЩÁãÉ¢µÄ¹¤¾ß°ü¡£ Òò´Ë£¬ ÎÒÃÇµÄ TODO ÈÎÎñÁбíÀï°üº¬¸÷ÖÖ¸÷ÑùµÄ¹¤×÷£¬ ´ÓÎĵµ¡¢Óû§²âÊÔ¡¢ÑÝʾ£¬ µ½ÏµÍ³°²×°³ÌÐòºÍ¸ß¶ÈרҵµÄÄں˿ª·¢¡£ Òò´ËÎÞÂÛÄúµÄ¼¼ÊõˮƽÈçºÎ£¬ ´ÓʺÎÖÖÁìÓò£¬ ¶¼¿ÉÒÔ°ïÖúÕâ¸öÏîÄ¿¡£ ÎÒÃǹÄÀø´ÓÊÂºÍ FreeBSD Ïà¹Ø¹¤×÷µÄÆóÒµºÍÎÒÃÇÁªÏµ¡£ ÄúÐèҪһЩÌØÊâµÄÀ©Õ¹À´Ê¹ÄúµÄ²úÆ·ÔËתÆðÀ´Ã´£¿ Äú»á·¢ÏÖÎÒÃǺÜÀÖÒâ´ðÓ¦ÄúµÄÇëÇó£¬ ³ý·ÇÊÇÌرðÏ¡Ææ¹Å¹ÖµÄ¡£ ÄúÊÇ·ñÕý´ÓÊÂÏà¹ØµÄÔöÖµÒµÎñ£¿ ÈÃÎÒÃÇÀ´°ïÖúÄú°É£¬ ÎÒÃÇÒ²Ðí¿ÉÒÔÔÚÆäÖеÄijЩ·½ÃæÏ໥Э×÷¡£ ×ÔÓÉÈí¼þÊÀ½çÕýÔÚŬÁ¦´òÆƾÉÓеĹØÓÚÈí¼þ¿ª·¢¡¢ ÏúÊÛºÍά»¤µÄ¿ò¿ò£¬ ÎÒÃÇÏ£Íû¿ÒÇëÄúÖÁÉÙÄܸøËüÒ»´Î»ú»á¡£ ÎÒÃǵÄÐèÇó ÏÂÃæÁгöÁËһЩÐèÒªÍê³ÉµÄÈÎÎñºÍ×ÓÏîÄ¿£¬ ËüÃÇ»ù±¾ÉÏ¿ÉÒÔ±»µÈͬÓÚ TODO(ÈÎÎñÁбí) ÁÐ±í£¬ ÒÔ¼°Óû§µÄÒªÇó¡£ ÕýÔÚ½øÐÐÖеķǿª·¢ÈÎÎñ ºÜ¶à²Î¼ÓFreeBSDÏîÄ¿µÄÈ˲»ÊdzÌÐòÔ±¡£ Õâ¸öÏîÄ¿ÀïÓÐÎĵµ×«Ð´Õß¡¢ ÍøÒ³Éè¼Æʦ¡¢ ÒÔ¼°¼¼ÊõÖ§³ÖÈËÔ±¡£ ¶ÔÓÚÕâЩ־ԸÕßÀ´Ëµ£¬ ËûÃÇÖ»ÐèÒª¹±Ï×һЩʱ¼ä£¬ ²¢ÇÒ¾ßÓÐѧϰµÄÒâÔ¸¡£ Äú¿ÉÒÔ¾­³£Í¨¶ÁFAQºÍÊֲᣬ Èç¹ûÄú·¢ÏÖÁË·±ËöµÄ½âÊÍ£¬ »òÕßÊǹýʱµÄ֪ʶ£¬ ÉõÖÁÍêÈ«²»ÕýÈ·µÄµØ·½£¬ ¶¼Çë¸æËßÎÒÃÇ¡£ Èç¹ûÄúÄÜ˳ÊÖ°ÑËûÃǸĹýÀ´ÄǾ͸üºÃÁË (SGMLÆäʵ²¢²»ÄÑѧ£¬ µ«ÎÒÃÇÒ²²»·´¶ÔÄúÖ±½ÓÌá½» ASCII µÄ°æ±¾)¡£ °ïÖúÎÒÃÇ°Ñ FreeBSD Îĵµ·­Òë³ÉÄúµÄĸÓï¡£ Èç¹ûÄúµÄĸÓï°æ±¾ÒѾ­´æÔÚÁË£¬ ÄúÒ²¿ÉÒÔ·­ÒëһЩÆäËûµÄÎĵµ»òÕß¼ì²éÄÇЩÒÑÓеÄÎĵµÊÇ·ñÊÇ×îиüйýµÄ¡£ Äú¿ÉÒÔÏȼòµ¥¿´¿´ FreeBSD Îĵµ¼Æ»®ÖÐÓÐ¹Ø ·­ÒëµÄ³£¼ûÎÊÌâ¡£ ²Î¼Ó·­Ò빤×÷²¢²»ÊÇ˵ÄúÒª¹Â¾ü·ÜÕ½·­ÒëËùÓÐµÄ FreeBSD Îĵµ¡£ ×÷Ϊһ¸öÖ¾Ô¸Õߣ¬ ×ö¶àÉÙ¹¤×÷ÍêÈ«È¡¾öÓÚÄúµÄÒâÔ¸¡£ Ò»µ©Ä³¸öÈË¿ªÊ¼·­ÒëÁË£¬ ÆäËûÈ˼¸ºõÒ»¶¨»á²ÎÓëµ½ÕâЩ¹¤×÷ÖÐÀ´¡£ Èç¹ûÄúÖ»ÓÐÓÐÏÞµÄʱ¼ä»òÕß¾«Á¦È¥·­Ò벿·ÖÎĵµ£¬ Äú¿ÉÒÔÊ×ÏÈÈ¥·­Òë°²×°Ö¸ÄÏ¡£ ÔĶÁ &a.questions; ²¢Å¼¶û¿´Ò»¿´ &ng.misc; (ÉõÖÁÓйæÂɵØÕâÑù×ö)¡£ Óë±ðÈË·ÖÏíÄúµÄרҵ֪ʶ£¬ ²¢°ïÖúËûÃǽâ¾öÎÊÌâÊÇÒ»¼þÁîÈËÓäÔõÄÊÂÇ飻 ÓÐЩʱºòÄúÉõÖÁ¿ÉÒÔÔÚÕâ¸ö¹ý³ÌÖÐѧµ½Ò»Ð©Ð¶«Î÷£¡ ÕâЩÂÛ̳ÓÐʱҲ»áΪÄúÌṩһЩÓмÛÖµµÄÖ÷Òâ¡£ ÕýÔÚ½øÐеĿª·¢ÈÎÎñ ÁÐÔÚÕâÀïµÄ´ó²¿·ÖÈÎÎñ¶¼ÐèÒªÄúͶÈë¿É¹ÛµÄʱ¼ä£¬ »òÕßÐèÒªÄúÔÚ FreeBSD Äں˷½ÃæÓзḻµÄ֪ʶ£¬ »òÕßÁ½Õ߶¼Òª¡£ µ±È»ÕâÀïÒ²ÓкܶàÖØÒªµÄÈÎÎñÒ²ÐíÄúÒ»¸ö ÖÜÄ©¿ª·¢ÈËÔ± ¾Í¿ÉÒÔ¸ÉÍê¡£ Èç¹ûÄúÕýÔÚÔËÐÐ FreeBSD-CURRENT °æ±¾²¢ÇÒÓÐÒ»Ìõ¸ßËÙµÄ Internet½ÓÈëÏß·£¬ Äú¿ÉÒÔ·ÃÎÊ current.FreeBSD.org£¬ ÕâÀïÿÌì»áÓÐÒ»¸öа汾 — Èç¹ûÄúÓпգ¬ Äú¿ÉÒÔ¸ôÈý²íÎåµØÏÂÔØÒ»·Ý²¢ÇÒ°²×°Ëü£¬ Æä¼äÈç¹û³öÁËʲôÎÊÌ⣬Çë¸æËßÎÒÃÇ¡£ ÔĶÁ &a.bugs;¡£ Äú¿ÉÄÜ»áΪÕâЩÎÊÌâÌṩ¾ßÓн¨ÉèÐÔÒâÒåµÄÆÀÂÛ£¬ »òÕß°ïæ²âÊÔһЩ²¹¶¡¡£ ´ËÍ⣬ ÄúÉõÖÁ¿ÉÒÔ³¢ÊÔÐÞÕýÆäÖеÄһЩÎÊÌâ¡£ Èç¹ûÄúÖªµÀÓÐһЩÐÞÕýÒѾ­ÔÚ -CURRENT Éϳɹ¦µØ½øÐУ¬ µ«ÔÚ¾­¹ýÒ»¶Îʱ¼äÖ®ºóÈÔȻûÓкϲ¢µ½ -STABLE (ͨ³£ÊÇ 2ÖÜ×óÓÒ)£¬ ¸øÏà¹ØµÄ committer ·¢Ò»·âÀñòµÄÌáʾÐÅ¡£ ½«µÚÈý·½Èí¼þ¼ÓÈëµ½Ô´´úÂëÖÐµÄ src/contrib Ŀ¼¡£ È·±£ src/contrib ÖеĴúÂëÊÇ×îÐ嵀 ÒÔ¸ü¸ßµÄ¾¯¸æ¼¶±ð¹¹½¨Ô´´úÂë (»òÒ»²¿·ÖÔ´´úÂë) ²¢ÇåÀíÕâЩ¾¯¸æ¡£ ¸üÐÂÄÇЩÔÚ ports ÖÐʹÓùýʱµÄ¶«Î÷£¬ ÀýÈç gets() »ò°üº¬ malloc.h Ëù²úÉúµÄ¾¯¸æ¡£ Èç¹ûÄúÖÆ×÷ÁË ports£¬ ²¢½øÐÐÁËһЩÕë¶Ô &os; µÄ¸Ä¶¯£¬ ½«ÄúµÄ²¹¶¡·¢»Ø¸øÔ­×÷Õß (ÕâÑùÏ´ÎÉý¼¶Ê±ÄúµÄ¹¤×÷»á±äµÃÇáËÉһЩ)¡£ »ñÈ¡Ò»·ÝÕýʽµÄ±ê×¼£¬ Èç &posix; µÄ¸±±¾¡£ Äú¿ÉÒÔÔÚ FreeBSD C99 & POSIX ±ê׼˳ӦÏîÄ¿ ÍøÕ¾Éϵõ½Ïà¹ØµÄÁ´½Ó¡£ ½« FreeBSD µÄÐÐΪͬ±ê×¼½øÐбȽϡ£ Èç¹ûÓë±ê×¼²»Í¬£¬ ÌرðÊÇÄÇЩϸ½ÚµØ·½µÄ΢С²îÒ죬 Çë·¢ËÍÒ»¸ö¹ØÓÚËüµÄ PR (ÎÊÌⱨ¸æ)¡£ Èç¹û¿ÉÄÜ£¬ ÇëÖ¸³öÈçºÎÐÞÕýËü£¬ ²¢Ëæ PR Ìá½»²¹¶¡¡£ Èç¹ûÄúÈÏΪ±ê×¼ÓÐÎÊÌ⣬ ÇëÏò±ê×¼»¯ÍÅÌåÒªÇó¶ÔÆä½øÐÐÖØеĿ¼ÂÇ¡£ ΪÕâ·ÝÁÐ±í½¨Òé¸ü¶àµÄÄÚÈÝ£¡ ²é¿´Õû¸ö PR Êý¾Ý¿â ÎÊÌⱨ¸æÊý¾Ý¿â FreeBSD PR Áбí չʾÁËËùÓе±Ç°´¦ÓÚ»îԾ״̬µÄÎÊÌⱨ¸æ£¬ ÒÔ¼°ÓÉ FreeBSD Óû§Ìá½»µÄ¸Ä½ø½¨Òé¡£ PR Êý¾Ý¿âͬʱ°üÀ¨ÁË¿ª·¢ÈËÔ±ºÍ·Ç¿ª·¢ÈËÔ±µÄÈÎÎñ¡£ ²é¿´ÄÇЩÉÐδ½â¾öµÄ PR£¬ ²¢¿´¿´ÊÇ·ñÓÐÄú¸ÐÐËȤµÄÈÎÎñ¡£ ÕâÆäÖпÉÄÜÓÐһЩÊǷdz£¼òµ¥µÄÎÊÌ⣬ Ö»ÐèÒª¿´Ò»¿´²¢È·ÈÏ PR ÊÇÕýÈ·µÄ¡£ ÁíÍâһЩ¿ÉÄÜ»á·Ç³£¸´ÔÓ£¬ »òÕßÍêȫûÓаüÀ¨ÈκÎÐÞÕý¡£ Ê×ÏÈ¿´Ò»¿´ÄÇЩ»¹Ã»ÓÐÈ˽ÓÊÖµÄ PR¡£ Èç¹û PR ÒѾ­·ÖÅä¸øÁËÆäËüÈË£¬ µ«¿´ÆðÀ´ÊÇÄúÄܹ»´¦ÀíµÄ£¬ Äú¿ÉÒÔ¸øÄǸöÈË·¢ÐÅ£¬ ²¢Ñ¯ÎÊÄúÊÇ·ñ¿ÉÒÔÌṩ°ïÖú — ËûÃÇ¿ÉÄÜÒѾ­ÓÐÁ˿ɹ©²âÊԵIJ¹¶¡£¬ »òÓÐһЩ¿É¹©ÌÖÂÛµÄÒâ¼û¡£ ´Ó <quote>µã×Ó</quote> ÍøÒ³ÉÏÈÏÁìÏîÄ¿ &os; Ö¾Ô¸ÕßÏîÄ¿ºÍµã×ÓÇåµ¥ Ò²ÊÇÌṩ¸øÔ¸ÒâΪ &os; ÏîÄ¿×ö³ö¹±Ï×µÄÈËÃǵġ£ ÕâÕÅÇåµ¥Ò»Ö±ÔÚ±»¶¨ÆÚ¸üÐÂ×Å£¬ °üº¬Á˶ԳÌÐòÔ±ºÍ·Ç³ÌÐòÔ±ÓÐÓõÄÿ¸öÏîÄ¿µÄÐÅÏ¢¡£ ÈçºÎÌṩ°ïÖú °ïÖú¸Ä½øϵͳ»ù±¾ÉÏ¿ÉÒÔ·ÖΪ 5 Àࣺ ´íÎ󱨸æºÍÒ»°ãµÄ×¢½â ͨ³££¬ Ò»°ãÒâÒåÉ쵀 ¼¼ÊõÏë·¨ºÍ½¨ÒéÓ¦¸Ã·¢µ½ &a.hackers;¡£ ͬÑùµØ£¬ ¶ÔÓÚÕâЩ¶«Î÷ÓÐÐËȤµÄÈË (µ±È»£¬ ËûÃÇͬʱ»¹ÒªÄܹ»ÈÝÈÌ ´óÁ¿µÄ Óʼþ£¡) ¿ÉÒÔ¿¼ÂǶ©ÔÄ &a.hackers;¡£ ²Î¼û FreeBSD ʹÓÃÊÖ²á ÒÔÁ˽â¹ØÓÚÕâ¸öÓʼþÁÐ±í£¬ ÒÔ¼°ÆäËüÓʼþÁбíµÄÏêϸÇé¿ö¡£ Èç¹ûÄú·¢ÏÖÁË bug »òÕßÏëÒªÌύijЩÐ޸ģ¬ Çëͨ¹ý &man.send-pr.1; ³ÌÐò»òʹÓà »ùÓÚ WEB µÄÌá½»Ò³Ãæ À´Ìá½»¡£ ÇëÊÔ×ÅÌîд bug ±¨¸æµÄÿһÏî¡£ Ò»°ãÀ´Ëµ£¬ ÎÒÃǽ¨ÒéÔÚ bug ±¨¸æÖÐÖ±½Ó¸½Éϲ¹¶¡£¬ ³ý·ÇËü³¬¹ýÁË 65KB¡£ Èç¹û²¹¶¡¿ÉÒÔÖ±½ÓÓ¦Óõ½Ô´´úÂëÉÏ£¬ Ôò½¨ÒéÄúÔÚ±¨¸æµÄ synopsis Ò»À¸Ð´ÉÏ [PATCH]¡£ ÔÚ¸½´ø²¹¶¡Ê±£¬ Çë ²»Òª ͨ¹ý¸´ÖƺÍÕ³ÌùÀ´½øÐУ¬ ÒòΪÕâÑù×ö»á°Ñ tab ±ä³É¿Õ¸ñ£¬ ½á¹û²¹¶¡ºÜ¿ÉÄܾͲ»ÄÜÓÃÁË¡£ Èç¹û²¹¶¡³¬¹ý 20KB ºÜ¶à£¬ Ó¦¿¼Âǽ«ÆäѹËõ (ÀýÈçʹÓà &man.gzip.1; »ò &man.bzip2.1;) Ö®ºóÓà &man.uuencode.1; ½øÐбàÂëÖ®ºóÔٷŽøÄúµÄÎÊÌⱨ¸æÖС£ Ò»µ©±¨¸æ±»´æµµ£¬ Äú»áÊÕµ½Ò»·âÈ·ÈÏÓʼþÒÔ¼°Ò»¸öʼþ×·×Ù±àºÅ¡£ Çë±£ÁôÕâ¸ö±àºÅ£¬ ÒòΪÄú¿ÉÒÔÔÚÖ®ºóʹÓÃÕâ¸ö±àºÅ£¬ ·¢Óʼþµ½ &a.bugfollowup; À´Ìṩ¹ØÓÚ¸ÃʼþµÄ½øÒ»²½ÐÅÏ¢¡£ ÄúÐèÒª×öµÄÊǽ«±àºÅ·Åµ½ÓʼþµÄ±êÌâÖУ¬ ÀýÈç "Re: kern/3377"¡£ ¹ØÓÚͬһÎÊÌâ¸ü½øÒ»²½µÄÇé¿öÓ¦¸Ãͨ¹ýÕâÖÖ·½Ê½À´Ìá½»¡£ Èç¹ûÄúÔÚÒ»¶Îʱ¼äÖ®ºóÈÔȻûÓÐÊÕµ½È·ÈÏÐÅ (³¬¹ý 3 ÌìÉõÖÁ 1 ÖÜ£¬ ÕâÈ¡¾öÓÚÄúµÄÓʼþ·þÎñ) »òÕßÓÉÓÚijÖÖÔ­ÒòÎÞ·¨Ê¹Óà &man.send-pr.1; ÃüÁ Ôò¿ÉÒÔ·¢ÐŸø &a.bugs; ÒªÇó±ðÈË´úÄú·¢ËÍËü¡£ Çë²Î¼û ÕâƪÎÄÕ Á˽âÈçºÎ׫дºÃµÄÎÊÌⱨ¸æ¡£ ¶ÔÓÚÎĵµµÄÐÞ¶© Ìá½»Îĵµ ¶ÔÓÚÎĵµµÄÐÞ¸ÄÓÉ &a.doc; À´Éó²é¡£ Çë²Î¼û FreeBSD Îĵµ¼Æ»®³õ¼¶¶Á±¾ À´»ñµÃÍêÕûµÄÖ¸µ¼¡£ Çë°´ÕÕ ÖнéÉܵķ½·¨Ê¹Óà &man.send-pr.1; À´·¢ËÍеÄÎĵµ»òÕ߶ÔÓÚÏÖÓÐÎĵµµÄÍêÉÆ (ÄÄÅÂÊǺÜСµÄ¸Ä½øÒ²ÊÇ»¶Ó­µÄ£¡)¡£ ¶ÔÓÚÏÖÓÐÔ´´úÂëµÄÐÞ¸Ä FreeBSD-CURRENT ÔÚÏÖÓдúÂëÉϽøÐÐÐ޸ĻòÔö¼Ó¹¦ÄÜÔÚijÖ̶ֳÈÉÏÊÇÐèÒª¸ü¶à¼¼ÇɵÄÊÂÇ飬 ²¢ÇÒ»¹ºÍÄú¶ÔÓÚÄ¿Ç° FreeBSD µÄ¿ª·¢ÏÖ×´µÄÁ˽âÓйء£ ÓжàÖÖ·½Ê½¿ÉÒԵõ½±»³Æ×÷ FreeBSD-CURRENT µÄ FreeBSD ¿ª·¢°æ±¾£¬ Äú¿ÉÒÔͨ¹ýËüÀ´Á˽â×î½üµÄ¿ª·¢Çé¿ö¡£ Çë²Î¼û FreeBSD ʹÓÃÊÖ²á À´Á˽âʹÓà FreeBSD-CURRENT µÄ½øÒ»²½ÏêÇé¡£ ÔھɵĴúÂëÉϽøÐÐÐ޸ģ¬ Ôòͨ³£¿ÉÄÜÓÉÓÚ´úÂëÒѾ­¹ýʱ£¬ »òÓëеĿª·¢°æ±¾²îÒìÌ«´ó¶øÎÞ·¨±»ÖØм¯³Éµ½ FreeBSD ÖС£ Èç¹ûÄú¶©ÔÄÁË &a.announce; ÒÔ¼° &a.current; ÓʼþÁÐ±í£¬ Ôò¿ÉÒÔͨ¹ýËüÃÇÀ´´óÌåÁ˽âÄ¿Ç°µÄ¿ª·¢×´Ì¬¡£ ¼ÙÈç˵ÄúÄܹ»»ùÓÚ¾¡¿ÉÄÜеĴúÂëÀ´Íê³ÉÄúµÄÐ޸ģ¬ ÔòÏÂÒ»²½Òª×öµÄÊÂÇé¾ÍÊÇÉú³ÉÄúËù½øÐеÄÐ޸ĵIJîÒìÎļþ£¬ ²¢½«Ëü·¢¸ø FreeBSD µÄά»¤ÈËÔ±¡£ ÕâÏ×÷¿ÉÒÔͨ¹ý &man.diff.1; ÃüÁîÀ´Íê³É¡£ Ìá½»²¹¶¡Ê±ÍƼöµÄ &man.diff.1; ¸ñʽÊÇÒ»Ö²îÒì (unified diff)£¬ Ëü¿ÉÒÔͨ¹ý diff -u À´Éú³É¡£ ²»¹ý£¬ Èç¹ûÄúÐÞ¸ÄÁË´óÁ¿µÄ´úÂ룬 ÔòʹÓà diff -c À´Éú³ÉµÄÉÏÏÂÎĸñʽ (context diff) µÄ²îÒì¿ÉÄܸüÈÝÒ×ÔĶÁ£¬ Òò¶øÍƼöʹÓᣠdiff ÀýÈ磺 &prompt.user; diff -c oldfile newfile »òÕß &prompt.user; diff -c -r olddir newdir ½«·Ö±ðÉú³É¸ø¶¨Îļþ»òĿ¼½á¹¹µÄ context diff¡£ ÀàËƵأ¬ &prompt.user; diff -u oldfile newfile »ò &prompt.user; diff -u -r olddir newdir µÄ×÷ÓÃÓëÇ°ÃæµÄÀàËÆ£¬ µ«²ÉÓõĸñʽÊÇ unified diff¡£ Çë²Î¼û &man.diff.1; Áª»úÊÖ²áÁ˽â¸ü¶àϸ½Ú¡£ Ò»µ©ÄúʹÓà &man.diff.1; Éú³ÉÁ˲îÒ켯 (¿ÉÒÔʹÓà &man.patch.1; ÃüÁîÀ´²âÊÔÒ»ÏÂ)£¬ ¾Í¿ÉÒÔÌá½»ËüÃÇ£¬ ÒԱ㱻 FreeBSD ÊÕ¼¡£ ͨ¹ýʹÓà ÖÐËù½éÉÜµÄ &man.send-pr.1; ³ÌÐò¾Í¿ÉÒÔÍê³ÉÕâÏ×÷¡£ ²»Òª Ö»ÊǰѲîÒ켯·¢µ½ &a.hackers;£¬ ·ñÔòËüÃÇ¿ÉÄܻᱻ¶ªµô£¡ ÎÒÃÇ»á·Ç³£¸Ð¼¤ÄúÌá½»µÄÐÞ¸Ä (ÕâÊÇÒ»¸öÖ¾Ô¸ÕßÏîÄ¿£¡)£» ÒòΪÎÒÃǶ¼ºÜ棬 Òò´ËÓÐʱ²»Ò»¶¨Äܹ»Á¢¼´ÐÞÕýÎÊÌ⣬ µ« PR Êý¾Ý¿â½«Ò»Ö±±£³Ö×ÅÕâЩ¼Ç¼£¬ Òò´ËÖ»ÒªÓÐÈËÓÐÁËʱ¼äËüÃǾÍÄܱ»¸ÄÕýÁË¡£ Èç¹ûÄúµÄÎÊÌⱨ¸æÖаüÀ¨²¹¶¡£¬ Ò»¶¨²»ÒªÍüÁËÔÚ±êÌâÉÏÓà [PATCH] À´Ç¿µ÷һϡ£ uuencode Èç¹ûÄúÈÏΪºÏÊÊ (ÀýÈçÄúÌí¼Ó¡¢ ɾ³ý»òÖØÃüÃûÁËÎļþ)£¬ »¹¿ÉÒÔ¿¼ÂÇʹÓà tar À´½«Îļþ´ò°ü£¬ È»ºóÓà &man.uuencode.1; À´±àÂë¡£ ÎÒÃÇÒ²»¶Ó­Óà &man.shar.1; ´´½¨µÄ°ü¡£ Èç¹ûÄúµÄÐ޸ĿÉÄÜ´æÔÚDZÔÚµÄÕùÒ飬 ÀýÈ磬 Äú²»È·¶¨ÓëÖ®Ïà¹ØµÄ°æȨÎÊÌ⣬ »òÕ߸оõÐèÒª¾­¹ý¸üÑϸñµÄ¸´Éó²Å¿ÉÒÔ·¢²¼ËüÃÇ£¬ ÔòÓ¦Ö±½Ó·¢¸ø &a.core;£¬ ¶ø²»ÊÇͨ¹ý &man.send-pr.1; À´·¢ËÍ¡£ &a.core; ÊÇÒ»¸öС×飬 Æä³ÉÔ±¸ü¶àµÄ´ÓÊ FreeBSD µÄÈÕ³£¹¤×÷¡£ ÐèҪעÒâµÄÊÇ£¬ Õâ¸öС×éÒ²Òò´Ë ºÜ棬 Òò´ËÖ»ÓÐÔڷdz£±ØÒªµÄʱºò²ÅÓ¦¸øËûÃÇдÐÅ¡£ Çë²Î¿¼ &man.intro.9; ºÍ &man.style.9; ÒÔÁ˽â¹ØÓÚ±àÂëÏ°¹ßºÍÔ¼¶¨µÄÏêÇé¡£ Èç¹ûÄúÁ˽âÕâЩԼ¶¨£¬ Ôò¶ÔÎÒÃÇÀ´Ëµ½«ÊǼ«´óµÄ°ïÖú¡£ дúÂë»òÖØÒªµÄÔöÖµÈí¼þ°ü Èç¹ûÄú´òËãÌṩ¹æÄ£½Ï´óµÄ´úÂ룬 »òÕßΪ FreeBSD Ôö¼ÓÖØÒªµÄй¦ÄÜ£¬ Ôò¿ÉÄܱØÐ뽫ËüÃÇͨ¹ý uuencode ½øÐбàÂ룬 »ò´«µ½Ä³¸ö Web »ò FTP Õ¾µã£¬ ÒÔ±ã¸ü¶àµÄÈËÄܹ»µÃµ½Ëü¡£ Èç¹ûÄúûÓÐÕâÑùµÄ·þÎñÆ÷£¬ Çëµ½Ïà¹ØµÄ FreeBSD ÓʼþÁбíÌá³ö£¬ ¿´¿´ÊÇ·ñÓÐÈËÔ¸Òâ°ïÄú·ÅÖÃËüÃÇ¡£ ¶ÔÓÚ´óÁ¿µÄ´úÂë¶øÑÔ£¬ ¹ØÓÚ°æȨµÄÎÊÌâ¿Ï¶¨»á±»Ìá³ö¡£ FreeBSD »ù±¾ÏµÍ³ÖÐÄܹ»Ê¹ÓõİæȨÉùÃ÷°üÀ¨£º BSDBSD °æȨÉùÃ÷ °æȨ¡£ ÎÒÃÇÇãÏòÓÚʹÓÃÕâÀàÊÚȨµÄ´úÂ룬 ÒòΪËü ²»¸½¼Ó¶àÓàµÄÌõ¼þ£¬ Òò¶ø¸üÄܹ»ÎüÒýÉÌÒµÆóҵʹÓᣠFreeBSD ²¢²»·´¶ÔÉÌÒµ¹«Ë¾Ê¹ÓÃËüµÄ´úÂ룬 Ïà·´£¬ ÎÒÃÇ»ý¼«µØ¹ÄÀøÉÌÒµ¹«Ë¾Ê¹ÓÃÎÒÃǵĴúÂ룬 µ±È»£¬ Èç¹ûËüÃÇ×îÖÕ°ÑÒ»²¿·Ö´úÂëÖØоèÔù¸ø FreeBSD ¾Í¸üºÃÁË¡£ GNU General Public License£¬GPLGNU General Public LicenseGNU General Public License »ò¼ò³Æ GPL¡£ ÎÒÃDz¢²»ºÜ»¶Ó­Ê¹ÓÃÕâÑùÊÚȨµÄ´úÂ룬 ÒòΪÉÌÒµ¹«Ë¾Ê¹ÓÃËüÐèÒª×ö¸ü¶àµÄ¹¤×÷¡£ ²»¹ý£¬ ÓÉÓںܶàʹÓà GPL ÊÚȨµÄ´úÂëÄ¿Ç°ÊÇÎÞ·¨±ÜÃâµÄ (±àÒëÆ÷¡¢ »ã±àÆ÷£¬ Îı¾ÅÅ°æ³ÌÐòµÈµÈ)£¬ ¾Ü¾øʹÓÃËùÓвÉÓÃÕâÑùÊÚȨµÄÈí¼þÊǺܲ»Ã÷Öǵġ£ ²ÉÓà GPL ÊÚȨµÄ´úÂë»á±»·Åµ½Ô´´úÂëµÄһЩרÃŵÄλÖ㬠ÀýÈç /sys/gnu »ò /usr/src/gnu£¬ ÒÔ·½±ãÄÇЩʹÓà GPL ´úÂë¿ÉÄÜ»á¸øËûÃÇ´øÀ´ÎÊÌâµÄÈËʶ±ð¡£ ʹÓÃÆäËüÊÚȨµÄ´úÂëÔÚ½øÈë FreeBSD ֮ǰ±ØÐë¾­¹ýÉ÷Öصĸ´ÉóºÍ¿¼ÂÇ¡£ ²ÉÓðüº¬ÑÏÀ÷ÏÞÖƵÄÉÌÒµÊÚȨµÄ´úÂ룬 Ò»°ãÀ´Ëµ»á±»¾Ü¾ø£¬ µ«ÎÒÃǹÄÀøÕâЩ´úÂëµÄ×÷Õßͨ¹ý×Ô¼ºµÄÇþµÀÀ´·¢²¼ËüÃÇ¡£ ÒªÔÚÄúµÄ³É¹ûÉϼÓÈë BSDʽ µÄ°æȨ£¬ Çë°ÑÏÂÁÐÎı¾·Åµ½Ã¿Ò»¸öÔ´ÎļþµÄ×ʼ²¿·Ö£¬ ²¢ÓÃÊʵ±µÄÎÄ×ÖÌæ»» %% Ö®¼äµÄÎÄ×Ö¡£ Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ ΪÁË·½±ãÄúµÄʹÓ㬠ÔÚ /usr/share/examples/etc/bsd-style-copyright Ò²¿ÉÒÔÕÒµ½´ËÊÚȨµÄ¸±±¾¡£ ×ʽ𡢠Ӳ¼þ»ò Internet ½ÓÈë ÎÒÃǷdz£Ô¸Òâ½ÓÊܸ÷ÖÖÐÎʽµÄ¾èÔù£¬ ÒÔ½øÒ»²½ÍØÕ¹ FreeBSD Project µÄÊÂÒµ£¬ ÒòΪÓÐÄúµÄÖ§³Ö£¬ ÏñÎÒÃÇÕâÑùµÄÖ¾Ô¸ÕßŬÁ¦²ÅÄܹ»Óиü´óµÄ³É¾Í£¡ ¾èÔùÓ²¼þÒ²·Ç³£ÖØÒª£¬ ÒòΪÕâÑùÄܹ»°ïÖúÎÒÃÇÔö¼Ó¿ÉÒÔÖ§³ÖµÄÓ²¼þÖÖÀ࣬ ¶øÎÒÃÇÖеĺܶàÈ˲¢Ã»ÓÐ×ã¹»µÄ×ʽðÀ´¹ºÖÃÕâЩӲ¼þ¡£ <anchor id="donations"/>¾è¿î FreeBSD »ù½ð»áÊÇÒ»¸ö·ÇÓªÀûµÄ¡¢ ÓпÎË°»íÃâȨµÄ»ù½ð»á£¬ ½¨Á¢Õâ¸ö»ù½ð»áµÄÄ¿±êÊÇΪÁËÈà FreeBSD Project Äܹ»´ï³É¸ü¼Ó³¤Ô¶µÄÄ¿±ê¡£ ×÷Ϊ 501(c)3 ʵÌ壬 Ò»°ã¶øÑÔ»ù½ð»á¿ÉÒÔÃâÓèÉϽÉÃÀ¹úÁª°îÊÕÈëË°£¬ ÒÔ¼°¿ÆÂÞÀ­¶àÖÝÊÕÈëË°¡£ ͨ³£¶ÔÓÚ¿ÎË°»íÃâµÄʵÌå½øÐоèÔù£¬ ¿ÉÒÔÕÛµÖÁª°îÊÕÈëÖÐÓ¦¿ÎË°²¿·ÖµÄ½ð¶î¡£ Äú¿ÉÒÔ°Ñ֧Ʊ¼ÄÍù£º
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
FreeBSD »ù½ð»áÏÖÔÚ¿ÉÒÔͨ¹ý PayPal ´ÓÍøÉϽÓÊܾè¿î¡£ Èç¹ûÄúÏëÏò»ù½ð»á¾è¿î£¬ Çë·ÃÎÊËüµÄ web Õ¾µã¡£ ¹ØÓÚ FreeBSD »ù½ð»áµÄ¸ü¶àÏêÇ飬 ¿ÉÒÔÔÚ FreeBSD »ù½ð»á -- ½éÉÜ ÕÒµ½¡£ ÒªÁªÂç»ù½ð»á£¬ Çë·¢Ë͵ç×ÓÓʼþµ½ bod@FreeBSDFoundation.org¡£ ¾èÔùÓ²¼þ ¾èÔù FreeBSD ¼Æ»®»¶Ó­ÈκÎÈ˾èÔù¿ÉÒÔʹÓõÄÓ²¼þ¡£ Èç¹ûÄúÓÐÐËȤ¾èÔùÓ²¼þ£¬ ÇëÁªÏµ ¾èÔùÁªÂçÈ˰칫ÊÒ¡£ ¾èÔù Internet ½ÓÈë ÎÒÃÇ»¶Ó­Ð嵀 FTP¡¢ WWW »ò cvsup ¾µÏñ¡£ Èç¹ûÄúÏ£Íû³ÉΪÕâÑùµÄ¾µÏñ£¬ Çë²Î¼û ÈçºÎ¼ÜÉè FreeBSD ¾µÏñ Ò»ÎÄ£¬ ÒÔÁ˽â½øÒ»²½µÄÇé¿ö¡£ + +
diff --git a/zh_CN.GB2312/articles/nanobsd/article.xml b/zh_CN.GB2312/articles/nanobsd/article.xml index 6ad4ed1002..ccebf1a1d4 100644 --- a/zh_CN.GB2312/articles/nanobsd/article.xml +++ b/zh_CN.GB2312/articles/nanobsd/article.xml @@ -1,472 +1,474 @@
NanoBSD ¼ò½é Daniel Gerzo 2006 The FreeBSD Documentation Project $FreeBSD$ $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.general; ÕâƪÎĵµÌṩÁ˹ØÓÚ NanoBSD ¹¤¾ßµÄ½éÉÜÐÅÏ¢£¬ ÕâÒ»¹¤¾ß¿ÉÒÔÓÃÀ´´´½¨ÓÃÓÚǶÈëʽӦÓÃµÄ &os; ϵͳӳÏñ£¬ ÒÔÊÊÓ¦´æ·Åµ½ÐäÕäÉÁ´æ (Compact Flash) ¿¨ (»òÆäËü´óÈÝÁ¿´æ´¢½éÖÊ) ÉϵÄÐèÒª¡£ NanoBSD ¼ò½é NanoBSD NanoBSD ÊÇ &a.phk; Ä¿Ç°ÕýÔÚ¿ª·¢µÄÒ»Ï¾ß¡£ Ëü¿ÉÒÔÓÃÀ´´´½¨ÓÃÓÚǶÈëʽӦÓÃµÄ &os; ϵͳӳÏñ£¬ ÒÔ±ãÅäºÏÐäÕäÉÁ´æ (Compact Flash) ¿¨ (»òÆäËû´óÈÝÁ¿´æ´¢½éÖÊ) ʹÓᣠÕâÒ»¹¤¾ßÒ²¿ÉÒÔÓÃÀ´¹¹½¨¶¨ÖƵݲװӳÏñ£¬ ÒÔ¼ò»¯Í¨³£³ÆΪ ¼ÆËãÉ豸 (computer appliances) µÄϵͳµÄ°²×°ºÍά»¤¹¤×÷¡£ ¼ÆËãÉ豸ͨ³£ÔÚ²úÆ·Öн«À¦°óÓ²¼þºÍÈí¼þ£¬ »òÕß»»ÑÔÖ®£¬ ËùÓеÄÓ¦ÓóÌÐò¶¼ÊÇÔ¤ÏÈ×°ºÃµÄ¡£ ÕâЩÉ豸¿ÉÒÔÖ±½Ó²åµ½ôß´æµÄÍøÂçÖУ¬ ²¢ (¼¸ºõÊÇ) Á¢¼´Í¶ÈëʹÓᣠNanoBSD ÌṩµÄ¹¦ÄÜ°üÀ¨£º ¿ÉÒÔºÍ &os; Ò»ÑùʹÓà Ports ºÍÔ¤±àÒë°ü— ËùÓеÄÓ¦ÓóÌÐò¶¼¿ÉÒÔÔÚ NanoBSD Ó³ÏñÖÐÖ±½ÓʹÓ㬠¶ø·½Ê½Óë &os; ÍêÈ«Ò»Ñù¡£ ²»¼õÉÙ¹¦ÄÜ — Äܹ»Ê¹Óà &os; ×öµÄÈκι¤×÷£¬ ¶¼¿ÉÒÔÔÚ NanoBSD ÖÐʹÓ㬠³ý·ÇÄúÔÚ´´½¨ NanoBSD Ó³Ïñʱ£¬ Ã÷È·µØɾȥËüÃÇ¡£ ËùÓжÔÏóÔÚÔËÐÐʱ¾ùÊÇÖ»¶ÁµÄ — ¿ÉÒÔ°²È«µØ°ÎµôµçÔ´²åÏú¡£ ÔÚϵͳ·ÇÕý³£¹Ø±ÕÖ®ºó£¬ ÎÞÐèÔËÐÐ &man.fsck.8;¡£ ±ãÓÚÁª±àºÍ¶¨ÖÆ — Ö»ÐèʹÓÃÒ»¸ö shell ½Å±¾ºÍÒ»¸öÅäÖÃÎļþ£¬ Äú¿ÉÒÔºÜÈÝÒ׵زüõºÍ¶¨ÖÆÊÊÓÚÈÎÒâÐèÇóµÄÓ³Ïñ¡£ ÈçºÎʹÓà NanoBSD NanoBSD µÄÉè¼Æ Ò»µ©½«Ó³Ïñ´æÈë½éÖÊ£¬ ¾Í¿ÉÒÔÓÃËüÀ´Òýµ¼ NanoBSD ÁË¡£ ĬÈÏÇé¿öÏ£¬ ´óÈÝÁ¿´æ´¢Æ÷»á»®·ÖΪÈý¸öÇø£º Á½¸öÓ³ÏñÇø£º code#1 ºÍ code#2¡£ Ò»¸öÅäÖÃÎļþÇø£¬ ÔËÐл·¾³ÖУ¬ ¿ÉÒÔ½«Æä¹Ò½Óµ½ /cfg Ŀ¼Ï¡£ ÕâЩ·ÖÇøĬÈÏÇé¿öÏÂÒÔÖ»¶Á·½Ê½¹Ò½Ó¡£ /etc ºÍ /var Ŀ¼¾ùΪ &man.md.4; (malloc) ÅÌ¡£ ÅäÖÃÎļþ·ÖÇø±£´æÔÚ /cfg Ŀ¼¡£ Ëü°üº¬ÁËÓÃÓÚ /etc Ŀ¼µÄÎļþ£¬ ÔÚÆô¶¯Ö®ºóÔÝʱÒÔÖ»¶Á·½Ê½¹Ò½Ó¡£ Òò´Ë£¬ ÔÚÐèÒª´Ó /etc Ïò /cfg Ŀ¼¸´ÖÆËù½øÐеġ¢ Ï£ÍûÔÚÖØÆôʱ±£³Ö²»±äµÄÅäÖÃʱ£¬ ÐèÒª½øÐÐһЩ¶îÍâµÄ²Ù×÷¡£ ÔÚ <filename>/etc/resolv.conf</filename> ÖнøÐÐÐèÒª±£³ÖµÄÐÞ¸Ä &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg Ö»ÓÐÔÚϵͳÆô¶¯¹ý³ÌÖУ¬ ÒÔ¼°ÐèÒªÐÞ¸ÄÅäÖÃÎļþµÄ³¡ºÏ£¬ ²ÅÐèÒª¹Ò½Ó°üº¬ /cfg µÄÄǸö·ÖÇø¡£ ÔÚÈκÎʱºò¶¼±£³Ö¹Ò½Ó /cfg ²»ÊÇÒ»¸öºÃÖ÷Ò⣬ ÌرðÊǵ±Äú°Ñ NanoBSD ·ÅÔÚ²»ÊʺϽøÐдóÁ¿Ð´²Ù×÷µÄ·ÖÇøʱ (ÓÉÓÚÎļþϵͳµÄͬ²½½ø³Ì»á¶¨ÆÚÏòϵͳÅÌдһЩÊý¾Ý)¡£ ¹¹½¨ NanoBSD Ó³Ïñ NanoBSD Ó³ÏñÊÇͨ¹ýʹÓ÷dz£¼òµ¥µÄ nanobsd.sh shell ½Å±¾À´¹¹½¨µÄ£¬ Õâ¸ö½Å±¾¿ÉÒÔÔÚ /usr/src/tools/tools/nanobsd Ŀ¼ÖÐÕÒµ½¡£ Õâ¸ö½Å±¾½¨Á¢µÄÓ³ÏñÎļþ£¬ ¿ÉÒÔÓà &man.dd.1; ¹¤¾ß¸´ÖƵ½´æ´¢½éÖÊÉÏ¡£ ¹¹½¨ NanoBSD Ó³ÏñËùÐèµÄÃüÁîÊÇ£º &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k ½øÈë NanoBSD ¹¹½¨½Å±¾µÄÖ÷Ŀ¼¡£ ¿ªÊ¼¹¹½¨¹ý³Ì¡£ ½øÈë¹¹½¨ºÃµÄÓ³ÏñÎļþËùÔÚµÄĿ¼¡£ ÔÚ´æ´¢½éÖÊÉÏ°²×° NanoBSD¡£ ¶¨ÖÆ NanoBSD Ó³Ïñ Õâ¿ÉÄÜÊÇ NanoBSD ×îΪÖØÒª£¬ ͬʱҲÊÇÄú×î¸ÐÐËȤµÄ¹¦ÄÜ¡£ ͬʱ£¬ ÄúÔÚ¿ª·¢ NanoBSD Ó¦ÓÃʱ£¬ ÕâÒ²ÊÇÏ൱ºÄʱµÄ¹ý³Ì¡£ Ö´ÐÐÏÂÃæµÄÃüÁʹ nanobsd.sh ´Óµ±Ç°Ä¿Â¼ÖÐµÄ myconf.nano Îļþ¶ÁÈ¡ÅäÖ㺠&prompt.root; sh nanobsd.sh -c myconf.nano ¶¨Öƹý³Ì°üº¬Á½²½£º ÅäÖÃÑ¡Ïî ¶¨Öƺ¯Êý ÅäÖÃÑ¡Ïî ͨ¹ý¶ÔÅäÖýøÐÐÉèÖ㬠¿ÉÒÔÅäÖÃÓÃÒÔ´«µÝ¸ø NanoBSD ¹¹½¨¹ý³ÌÖÐ buildworld ºÍ installworld ½×¶ÎµÄÁª±àºÍ°²×°Ñ¡Ï ÒÔ¼° NanoBSD µÄÖ÷¹¹½¨¹ý³ÌÖеÄÑ¡Ïî¡£ ͨ¹ýʹÓÃÕâЩѡÏî¿ÉÒÔÏ÷¼õϵͳµÄ³ß´ç£¬ ʹ֮Äܹ»·ÅÈë 64MB µÄ´æ´¢¡£ Äú»¹¿ÉÒÔ½øÒ»²½Í¨¹ýÕâЩѡÏîÀ´Ï÷¼õ &os;£¬ Ö±µ½ËüÖ»°üº¬ÄÚºËÒÔ¼°Á½Èý¸öÓû§»·¾³ÎļþΪֹ¡£ ÅäÖÃÎļþÖаüº¬ÓÃÒÔ´úÌæĬÈÏÖµµÄÅäÖÃÑ¡Ïî¡£ ×îÖØÒªµÄÓï¾ä°üÀ¨£º NANO_NAME — ±¾´Î¹¹½¨µÄÃû³Æ (ÓÃÓÚ´´½¨¹¤×÷Ŀ¼µÄÃû×Ö)¡£ NANO_SRC — ÓÃÒÔÁª±àºÍ¹¹½¨Ó³ÏñµÄÔ´ÂëÊ÷µÄλÖᣠNANO_KERNEL — ÓÃÒÔÁª±àÄں˵ÄÅäÖÃÎļþµÄÃû×Ö¡£ CONF_BUILD — ÓÃÓÚ´«µÝ¸ø buildworld ¹¹½¨½×¶ÎµÄÑ¡Ïî¡£ CONF_INSTALL — ÓÃÓÚ´«µÝ¸ø installworld ¹¹½¨½×¶ÎµÄÑ¡Ïî¡£ CONF_WORLD — ÓÃÒÔ´«µÝ¸ø buildworld ºÍ installworld ÕâÁ½¸ö¹¹½¨½×¶ÎµÄÑ¡Ïî¡£ FlashDevice — ¶¨ÒåËùÓõĽéÖÊÀàÐÍ¡£ ÒªÁ˽â½øÒ»²½µÄϸ½Ú£¬ Çë²Î¿¼ FlashDevice.sub Îļþ¡£ ¶¨Öƺ¯Êý ͨ¹ýÔÚÅäÖÃÎļþÖÐʹÓà shell º¯Êý¿ÉÒÔ½øÒ»²½Î¢µ÷ NanoBSD¡£ ÏÂÃæµÄÀý×ÓչʾÁ˶¨Öƺ¯ÊýµÄ»ù±¾Ä£Ê½£º cust_foo () ( echo "bar=baz" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo ÏÂÃæÊÇÒ»¸ö¸üÌù½üʵ¼ÊµÄÀý×Ó£¬ Ëü½«Ä¬È쵀 /etc Ŀ¼³ß´ç£¬ ´Ó 5MB µ÷ÕûΪ 30MB£º cust_etc_size () ( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size ³ý´ËÖ®Í⣬ »¹Óм¸¸öĬÈϵÄÔ¤¶¨Ò嶨Öƺ¯Êý£º cust_comconsole — ÔÚ VGA É豸ÉϽûÖ¹ &man.getty.8; (/dev/ttyv* É豸½Úµã) ²¢ÆôÓô®¿Ú COM1 ×÷Ϊϵͳ¿ØÖÆ̨¡£ cust_allow_ssh_root — ÔÊÐí root ͨ¹ý &man.sshd.8; µÇ¼¡£ cust_install_files — ´Ó nanobsd/Files Ŀ¼Öа²×°Îļþ£¬ Õâ°üº¬Ò»Ð©ÊµÓõÄϵͳ¹ÜÀí½Å±¾¡£ °²×°Ô¤±àÒëÈí¼þ°ü ͨ¹ýÔö¼Ó×Ô¶¨ÒåµÄº¯Êý£¬ ¿ÉÒÔÔÚ NanoBSD Ôö¼ÓÔ¤±àÒëµÄÈí¼þ°ü¡£ ÏÂÃæµÄº¯Êý»áÌí¼ÓλÓÚ /usr/src/tools/tools/nanobsd/packages µÄÈ«²¿Ô¤±àÒëÈí¼þ°ü£º install_packages () ( mkdir -p ${NANO_WORLDDIR}/packages cp /usr/src/tools/tools/nanobsd/packages/* ${NANO_WORLDDIR}/packages chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg_add -v *;cd ..;' rm -rf ${NANO_WORLDDIR}/packages ) customize_cmd install_packages ÅäÖÃÎļþ¾ÙÀý ÏÂÃæÊÇÒ»¸öÓÃÓÚ¹¹½¨¶¨ÖÆµÄ NanoBSD Ó³ÏñµÄÍêÕûÀý×Ó£º NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie ¸üРNanoBSD ¸üРNanoBSD Ïà¶Ô¶øÑÔ½ÏΪ¼òµ¥£º ºÍ֮ǰһÑù¹¹½¨Ð嵀 NanoBSD Ó³ÏñÎļþ¡£ ½«ÐµÄÓ³Ïñ·ÅÈëÕýÔËÐÐµÄ NanoBSD É豸ÖеÄÒ»¸öδÓõķÖÇø¡£ Óë֮ǰ×î³õ°²×° NanoBSD µÄ²½ÖèÏà±È£¬ ÕâÒ»²½Öè×îÖØÒªµÄÇø±ðÔÚÓÚÕâ´Î²»Ó¦Ê¹Óà _.disk.full Îļþ (Ëü°üº¬Õû¸öÅ̵ÄÓ³Ïñ)£¬ ¶øÓ¦°²×° _.disk.image Ó³Ïñ (Õâ¸öÎļþÖУ¬ Ö»°üº¬Ò»¸öϵͳ·ÖÇø)¡£ ÖØÐÂÆô¶¯£¬ ²¢´Óа²×°µÄ·ÖÇøÖÐÆô¶¯ÏµÍ³¡£ Èç¹ûÒ»ÇÐ˳ÀûµÄ»°£¬ Éý¼¶¹¤×÷¾ÍÍê³ÉÁË¡£ Èç¹û·¢ÉúÁËÈκÎÎÊÌ⣬ Ôò¿ÉÒÔ´ÓÏÈÇ°µÄ·ÖÇøÆô¶¯ (ÆäÖаüº¬Á˾ɵġ¢ ¿ÉÓõÄÓ³Ïñ)£¬ À´¾¡¿ÉÄÜ¿ìµØ»Ö¸´ÏµÍ³¹¦ÄÜ¡£ ½ÓÏÂÀ´¿ÉÒÔÐÞÕýÐÂÁª±àµÄ°æ±¾ÖдæÔÚµÄÎÊÌ⣬ ²¢Öظ´Ç°Êö²½Öè¡£ ÒªÔÚÕýÔÚÔËÐÐµÄ NanoBSD ϵͳÖа²×°ÐµÄÓ³Ïñ£¬ ¿ÉÒÔʹÓÃλÓÚ /root Ŀ¼µÄ updatep1 »ò updatep2 ½Å±¾£¬ ¾ßÌåʹÓÃÄÄÒ»¸ö½Å±¾£¬ È¡¾öÓÚÕýÔÚÔËÐеÄϵͳλÓÚÄǸö·ÖÇø¡£ ËæʱÌṩРNanoBSD Ó³ÏñËùÌṩµÄ·þÎñ£¬ ÒÔ¼°²ÉÓõĴ«Êä·½·¨µÄ²»Í¬£¬ Äú¿ÉÒԲο¼²¢Ê¹ÓÃÏÂÁÐÈýÖÖ·½Ê½Ö®Ò»£º ʹÓà &man.ftp.1; Èç¹û´«ÊäËÙ¶ÈÊǵÚÒ»ÒªÎñ£¬ ²ÉÓÃÏÂÃæµÄÀý×Ó£º &prompt.root; ftp myhost get _.disk.image "| sh updatep1" ʹÓà &man.ssh.1; Èç¹û¸üÇãÏòÓÚ°²È«´«Ê䣬 Ó¦²Î¿¼ÏÂÃæµÄÀý×Ó£º &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 ʹÓà &man.nc.1; Èç¹ûÔ¶³ÌÖ÷»ú¼È²»Ìṩ &man.ftp.1; ·þÎñ£¬ Ò²²»Ìṩ &man.sshd.8; ·þÎñ£º ¿ªÊ¼Ê±£¬ ÔÚÌṩӳÏñµÄÖ÷»úÉÏ¿ªÆô TCP ¼àÌý£¬ ²¢ÁîÆ佫ӳÏñÎļþ·¢¸ø¿Í»§»ú£º myhost&prompt.root; nc -l 2222 < _.disk.image ÇëÈ·ÈÏÄúËùʹÓõĶ˿ÚûÓÐͨ¹ý·À»ðǽ×èÖ¹À´×Ô NanoBSD ¿Í»§»úµÄÁª½ÓÇëÇó¡£ Á¬½Óµ½ÌṩÐÂÓ³Ïñ·þÎñµÄÖ÷»ú£¬ ²¢Ö´ÐÐ updatep1 ½Å±¾£º &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/zh_CN.GB2312/books/arch-handbook/Makefile b/zh_CN.GB2312/books/arch-handbook/Makefile index 84eab680a2..d9a4337a92 100644 --- a/zh_CN.GB2312/books/arch-handbook/Makefile +++ b/zh_CN.GB2312/books/arch-handbook/Makefile @@ -1,60 +1,58 @@ # # Original Revision: 1.25 # $FreeBSD$ # # Build the FreeBSD Architecture Handbook. # MAINTAINER=doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= boot/chapter.xml SRCS+= driverbasics/chapter.xml SRCS+= isa/chapter.xml SRCS+= jail/chapter.xml SRCS+= kobj/chapter.xml SRCS+= locking/chapter.xml SRCS+= mac/chapter.xml SRCS+= newbus/chapter.xml SRCS+= pci/chapter.xml SRCS+= scsi/chapter.xml SRCS+= smp/chapter.xml SRCS+= sound/chapter.xml SRCS+= pccard/chapter.xml SRCS+= sysinit/chapter.xml SRCS+= usb/chapter.xml SRCS+= vm/chapter.xml # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_CN.GB2312/books/arch-handbook/chapters.ent b/zh_CN.GB2312/books/arch-handbook/chapters.ent index 2a1dc3bdeb..b263069164 100644 --- a/zh_CN.GB2312/books/arch-handbook/chapters.ent +++ b/zh_CN.GB2312/books/arch-handbook/chapters.ent @@ -1,40 +1,35 @@ - - - -]]> - +"> diff --git a/zh_CN.GB2312/books/handbook/Makefile b/zh_CN.GB2312/books/handbook/Makefile index 2163726fd9..4fb68e4079 100644 --- a/zh_CN.GB2312/books/handbook/Makefile +++ b/zh_CN.GB2312/books/handbook/Makefile @@ -1,358 +1,356 @@ # # $FreeBSD$ # # Build the FreeBSD Handbook (Simplified Chinese). # # Original revision: r38039 # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ # # To add a new chapter to the Handbook: # # - Update this Makefile, chapters.ent and book.xml # - Add a descriptive entry for the new chapter in preface/preface.xml # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png IMAGES_EN+= bsdinstall/bsdinstall-adduser3.png IMAGES_EN+= bsdinstall/bsdinstall-boot-loader-menu.png IMAGES_EN+= bsdinstall/bsdinstall-choose-mode.png IMAGES_EN+= bsdinstall/bsdinstall-config-components.png IMAGES_EN+= bsdinstall/bsdinstall-config-hostname.png IMAGES_EN+= bsdinstall/bsdinstall-config-keymap.png IMAGES_EN+= bsdinstall/bsdinstall-config-services.png IMAGES_EN+= bsdinstall/bsdinstall-config-crashdump.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface-slaac.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-interface.png IMAGES_EN+= bsdinstall/bsdinstall-configure-network-ipv4-dns.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-accesspoints.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-scan.png IMAGES_EN+= bsdinstall/bsdinstall-configure-wireless-wpa2setup.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-extracting.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-fetching.png IMAGES_EN+= bsdinstall/bsdinstall-distfile-verifying.png IMAGES_EN+= bsdinstall/bsdinstall-final-confirmation.png IMAGES_EN+= bsdinstall/bsdinstall-finalconfiguration.png IMAGES_EN+= bsdinstall/bsdinstall-final-modification-shell.png IMAGES_EN+= bsdinstall/bsdinstall-keymap-select-default.png IMAGES_EN+= bsdinstall/bsdinstall-mainexit.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-files.png IMAGES_EN+= bsdinstall/bsdinstall-netinstall-mirrorselect.png IMAGES_EN+= bsdinstall/bsdinstall-part-entire-part.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-disk.png IMAGES_EN+= bsdinstall/bsdinstall-part-guided-manual.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-addpart.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-create.png IMAGES_EN+= bsdinstall/bsdinstall-part-manual-partscheme.png IMAGES_EN+= bsdinstall/bsdinstall-part-review.png IMAGES_EN+= bsdinstall/bsdinstall-post-root-passwd.png IMAGES_EN+= bsdinstall/bsdinstall-set-clock-local-utc.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-confirm.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-country.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-region.png IMAGES_EN+= bsdinstall/bsdinstall-timezone-zone.png IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/config-keymap.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= bsdinstall/chapter.xml SRCS+= colophon.xml SRCS+= dtrace/chapter.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= filesystems/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} DOC_PREFIX?= ${.CURDIR}/../../.. # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_CN.GB2312/books/handbook/chapters.ent b/zh_CN.GB2312/books/handbook/chapters.ent index 937cf24264..2ef276d566 100644 --- a/zh_CN.GB2312/books/handbook/chapters.ent +++ b/zh_CN.GB2312/books/handbook/chapters.ent @@ -1,72 +1,72 @@ %pgpkeys; - + "> diff --git a/zh_TW.Big5/articles/contributing/article.xml b/zh_TW.Big5/articles/contributing/article.xml index f888dfdf8b..6b2e31f503 100644 --- a/zh_TW.Big5/articles/contributing/article.xml +++ b/zh_TW.Big5/articles/contributing/article.xml @@ -1,483 +1,484 @@
À°§U FreeBSD µL½×¬O­Ó¤H©Î¬O¦UºØ²Õ´¡A¦pªG§Æ±æ¬° FreeBSD ´£¨ÑÀ°§U¡A³£¥i¥H¦b¥»¤å¤¤§ä¨ì¦X¾Aªº¤èªk¡C Jordan Hubbard ­ìµÛ¡G &tm-attrib.freebsd; &tm-attrib.ieee; &tm-attrib.general; $FreeBSD$ $FreeBSD$ °^Äm §A§Æ±æ´À FreeBSD °µÂI¤°»ò¶Ü¡H¤Ó¦n¤F¡A§Ú­ÌÅwªï§A¡CFreeBSD ¥¿¬O¦³¿à©ó¼s¤j¨Ï¥ÎªÌªº°^Äm¤~±o¥Hµo®i§§¤jªº¡C§Ú­Ì¤£¶È«D±`·PÁ±z©Ò°µªº°^Äm¡A¦Ó¥B¡A³o¨Ç¤u§@¹ï©ó FreeBSD ªº«ùÄòµo®i¤]¦ÜÃö­«­n¡C ¤]³\»P±z·Q¹³ªº¤£¦P¡A±z¬J¤£¥²±o¬O¤@¦W¥X¦âªº Programmer¡A¤]µL¶·©M FreeBSD core team ¦¨­û¦³«Ü¦nªº¨p¥æ¡A§Ú­Ì·|¤@µø¦P¤¯ªº¹ï«Ý±zªº¤u§@¡C FreeBSD ªº¶}µo¤H­û¹M¥¬¥þ²y¡A¤j®a§Þ³N±Mªø¦U²§¡A¦~ÄÖ¤À¥¬¤]«D±`¼sªx¡C µM¦Ó¡A¨C¤Ñ§Ú­Ì³£¦b­±¹ï«ùÄò¼W¥[ªº¤u§@¡A¦Ó­W©ó¨S¦³¨¬°÷ªº¤H¤â¡A¦]¦¹§Ú­ÌÀH®ÉÅwªï±zªºÀ°§U¡C FreeBSD ­p¹º©Ò³B²zªº¬O¤@­Ó§¹¾ãªº§@·~¨t²ÎÀô¹Ò¡A¦Ó¤£¥u¬O¤@­Ó kernel ©Î¬O¤@¨Ç¹s´²ªº¤u¨ã¥]¡C ¦]¦¹¡A§Ú­Ìªº TODO «Ý¿ì¥ô°È¦Cªí¸Ì¥]§t¦U¦¡¦U¼Ëªº¤u§@¡G ±q¤å¥ó¡B¨Ï¥ÎªÌ´ú¸Õ¡Bdemo¡A¨ì¨t²Î¦w¸Ëµ{¦¡©M§ó±M·~ªº kernel ¶}µo¡C ¦]¦¹µL½×±zªº§Þ³N¤ô·Ç¦p¦ó¡A±q¨Æ¦óºØ»â°ì¡A³£¥i¥HÀ°§U³o­Ó­p¹º¡C §Ú­Ì¹ªÀy±q¨Æ©M FreeBSD ¬ÛÃö¤u§@ªº¥ø·~©M§Ú­ÌÁpô¡C ±z»Ý­n¤@¨Ç¯S®íªºÂX®i¨Ó¨Ï±zªº²£«~¹BÂà°_¨Ó¶Ü¡H ±z·|µo²{§Ú­Ì«Ü¼Ö·NµªÀ³±zªº½Ð¨D¡A°£«D¬O¯S§Oµ}©_¥j©Çªº¡C ±z¬O§_¥¿±q¨Æ¬ÛÃöªº¼W­È·~°È¡H Åý§Ú­Ì¨ÓÀ°§U±z§a¡A §Ú­Ì¤]³\¥i¥H¦b¬Y¨Ç¤è­±¬Û¤¬¦X§@¡C ¦Û¥Ñ³nÅé¬É¥¿¦b§V¤O¥´¯}¦³ªº®Ø®Ø(¹³¬OÃö©ó³nÅé¶}µo¡B¾P°â©MºûÅ@)¡A §Ú­Ì§Æ±æÀµ½Ð±z¦Ü¤Ö¯àµ¹¥¦¤@¦¸¾÷·|¡C §Ú­Ìªº»Ý¨D ¤U­±¦C¥X¤F¤@¨Ç»Ý­n§¹¦¨ªº¥ô°È©M¤l­p¹º¡A ¥¦­Ì¥Nªí TODO(«Ý¿ì¥ô°È¦Cªí) ¦Cªíªº·N«ä¡A¥H¤Î¨Ï¥ÎªÌªº­n¨D¡C ¥¿¦b¶i¦æ¤¤ªº¥ô°È(«Dµ{¦¡¶}µo¤H­û) «Ü¦h°Ñ¥[ FreeBSD ­p¹ºªº¤H¤£¬O Programmer¡C ³o­Ó­p¹º¸Ì¦³¤å¥ó¼¶¼gªÌ¡Bºô­¶³]­p®v¡B¥H¤Î§Þ³N¤ä´©¤H­û¡C ¹ï©ó³o¨Ç¸q¤u¨Ó»¡¡A¥L­Ì¥u»Ý­n°^Äm¤@¨Ç®É¶¡¡A¨Ã¥B¨ã¦³¾Ç²ßªº·NÄ@¡C ±z¥i¥H®É±`½¾\ FAQ ©M¤â¥U(Handbook) ¡A¦pªGµo²{¦³¸ÑÄÀ¤£²M·¡ªº¦a¤è¡A©Î¬O¤£¦X®É©yªº¤å¥ó¡A¬Æ¦Ü§¹¥þ¤£¥¿½Tªº¦a¤è¡A ³£½Ð§i¶D§Ú­Ì¡C·íµM¡A­Y¯à¶¶¤â§â¥L­Ì­×¥¿¡A¨Ã§â°É»~±Hµ¹§Ú­Ì¡A¨º´N§ó¦n¤F¡C:) (SGML ¨ä¹ê¨Ã¤£Ãø¾Ç¡A¦ý§Ú­Ì¤]¤£¤Ï¹ï±zª½±µ´£¥æ¤@¯ë ASCII ªº¯Â¤å¦rª©¥»)¡C À°§U§Ú­Ì§â FreeBSD ¤å¥ó½Ķ¦¨§Aªº¥À»y¡C ¦pªG§Aªº¥À»yª©¥»¤w¸g¦s¦b¤F¡A ¤]¥i¥H½Ķ¤@¨ÇÃB¥~ªº¤å¥ó¡A©ÎªÌÀˬd¨º¨Ç¤w¦³ªº¤å¥ó¬O§_¬°³Ì·sª©¡C ±z¥i¥H¥ý²³æ¬Ý¬Ý FreeBSD ¤å¥ó­p¹º¤¤¦³Ãö ½Ķ®Éªº±`¨£°ÝÃD¡C °Ñ¥[½Ķ¤u§@¡A¨Ã¤£¬O»¡±z­n©t­x¾Ä¾Ô½Ķ©Ò¦³ FreeBSD ¤å¥ó¡C ¨­¬°¸q¤u¡A­n°µ¦h¤Ö¤u§@§¹¥þ¨ú¨M©ó±zªº·NÄ@¡C¤@¥¹¬Y­Ó¤H¶}©l½Ķ¤F¡A ¤§«á´X¥G¤@©w·|¦³¨ä¥L¤H°Ñ»P¨ì³o¨Ç¤u§@¤¤¨Ó¡C ¦pªG®É¶¡¦³­­¡A©ÎªÌºë¤O¤£°÷¥h½Ķ¾ã¥÷¤å¥ó¡A¨º¥i¥H­º¥ý¥h½Ķ¦w¸Ë«ü«n¡C ¾\Ū &a.questions; ¨Ã°¸º¸Â½¾\(¬Æ¦Ü¦³³W«ß¦a³o¼Ë°µ) &ng.misc; ¡C»P§O¤H¤À¨É±zªº±M·~ª¾ÃÑ¡A ¨ÃÀ°§U¥L­Ì¸Ñ¨M°ÝÃD¡A¬O¥ó¥O¤H´r®®ªº¨Æ±¡¡F ¦³®É­Ô¡A±z¬Æ¦Ü¥i¥H¦b³o­Ó¹Lµ{¤¤¾Ç¨ì¤@¨Ç·sªF¦è¡I ³o¨Ç½×¾Â¦³®É¤]·|¬°±z¿Eµo¥X¤@¨Ç¤£¿ùªº·Qªk¡C ¥¿¦b¶i¦æ¤¤ªº¥ô°È(µ{¦¡¶}µo¤H­û) ¦C¦b³o¸Ìªº¤j³¡¤À¥ô°È³£»Ý­n±z§ë¤J¥iÆ[ªº®É¶¡¡A©ÎªÌ»Ý­n±z¦b FreeBSD kernel ¤è­±¦³Â×´Iªºª¾ÃÑ¡A©ÎªÌ¨âªÌ³£­n¡C·íµM³o¸Ì¤]¦³«Ü¦h­«­nªº¥ô°È¡A¾A¦X¹³¬O weekend hackers ³oÃþ¥u¥Î¶g¥½´N¥i¥H·d©wªº Hacker¡C ¦pªG±z¥¿¦b¶]ªº¬O FreeBSD -CURRENT ª©¥»¡A¨Ã¥Bºô¸ô³t«×ÁÙ¤£¿ù¡A ¨º»ò¥i¥H¨ì current.FreeBSD.org¡A ³o¥x¨C¤Ñ·|¦³¤@­Ó·sª©¥» — ¦pªG±z¦³ªÅ¡A ±z¥i¥H¤T¤£¤­®É¤U¸ü¨Ã¦w¸Ë¡A ¨ä¶¡¦pªG¥X¤F¤°»ò°ÝÃD¡A½Ð§i¶D§Ú­Ì¡C ¾\Ū &a.bugs;¡C³o¨Ç°ÝÃD¡A©Î³\±z¯à´£¨Ñ¦³«Ø³]©Ê·N¸qªº·N¨£¡A ©ÎªÌÀ°¦£´ú¸Õ¤@¨Ç patch ¡C¦¹¥~¡A¬Æ¦Ü¥i¥H¹Á¸Õ­×¥¿¨ä¤¤ªº¤@¨Ç°ÝÃD¡C ¦pªG±zª¾¹D¦³¤@¨Ç­×¥¿¤w¸g¦b -CURRENT ¤W¦¨¥\¦a¨Ï¥Î¡A ¦ý¦b¸g¹L¤@¬q®É¶¡(³q±`¬O 2 ¶g¥ª¥k)¤§«á¡A¤´¥¼¦X¨Ö¨ì -STABLE (³o¨BÆJ´N¬O MFC -- Merged From Current)¡A¨º»ò¥i¥Hµ¹¬ÛÃöªº committer ¤H­ûµo«Ê§»ªªº´£¿ô«H¡C ±N²Ä¤T¤è(3rd party)³nÅé¥[¤J¨ì­ì©l½X¤¤ªº src/contrib ¥Ø¿ý¡C ½T«O src/contrib ¤¤ªº­ì©l½X¬O³Ì·sªº¡C ½sĶ­ì©l½X(©Î¬O³¡¤À­ì©l½X)®É¡A½Ð§ï¥Î§ó°ªªºÄµ§iµ¥¯Å(warning level) ¥H«K°»¿ù(debug)¥Î¡A¨Ã¦b§¹¦¨´ú¸Õ¡B½T»{¥¿±`§¹²¦¤§«á¡A²M°£³o¨Ç½sĶªºÄµ§iµ¥¯Å¡C §ó·s¨º¨Ç¦b ports ¤¤¨Ï¥Î¹L®ÉªºªF¦è¡A ¨Ò¦p gets() ©Î¥]§t malloc.h ©Ò²£¥ÍªºÄµ§i¡C ¦pªG¦³¬° ports §@¤F¥ô¦ó­×¥¿¡A ½Ð°O±o±N±zªº patch µoµ¹­ì§@ªÌ (³o¼Ë¤U¦¸¤É¯Å®É¡A±zªº¤u§@·|Åܱo»´ÃP¤@¨Ç)¡C ¥ý¨ú±o¥¿¦¡ªº¼Ð·Ç¡A¦p &posix; ªº°Æ¥»¡C ¦b FreeBSD C99 & POSIX ¼Ð·Ç¬Û®e­p¹º ºô¯¸¤W¡A¥i¥H±o¨ì¬ÛÃöÃì±µ¡C ½Ð±N FreeBSD ªº¦æ¬°»P¤W­zªº¼Ð·Ç¶i¦æ¤ñ¸û¡A­Y©Ò±oµ²ªG»P C99 & POSIX ¼Ð·Ç¤£¦Pªº¸Ü¡A ¯S§O¬O¨º¨Ç²Ó¸`¦a¤èªº·L¤p®t²§¡A½Ðµo¤@­ÓÃö©ó¥¦ªº PR (°ÝÃD³ø§i)¡C ¦pªG¥i¯à¡A½Ð«ü¥X¦p¦ó­×¥¿¥¦¡A¨ÃÀH PR ´£¥æ patch ¡C ¦pªG±z»{¬°¼Ð·Ç¦³°ÝÃD¡A½Ð¦V³o¨Ç³W®æ¼Ð·Çªº¬ÛÃö¹ÎÅé¡A½Ð¨D¹ï¨ä¶i¦æ­«·sªº¦Ò¼{¡C ¬°³o¥÷¦Cªí´£¨Ñ§ó¦h«Øij¡I ¬d¾\¾ã­Ó PR ¸ê®Æ®w °ÝÃD³ø§i¸ê®Æ®w FreeBSD PR ¦Cªí ³o¸Ì·|Åã¥Ü¥Ø«e©Ò¦³ PR ªº°ÝÃDª¬ºA¡A¥H¤Î¥Ñ FreeBSD ¨Ï¥ÎªÌ´£¥æªº§ï¶i«Øij¡C PR ¸ê®Æ®w¦P®É¥]¬A¤F¶}µo¤H­û©M«D¶}µo¤H­ûªº¥ô°È¡C ¬d¬Ý¨º¨Ç©|¥¼¸Ñ¨Mªº PR¡A¨Ã¬Ý¬Ý¬O§_¦³±z·P¿³½ìªº¥ô°È¡C ³o¨ä¤¤¥i¯à¦³¤@¨Ç¬O«D±`²³æªº°ÝÃD¡A¥u»Ý­n¬Ý¤@¬Ý¨Ã½T»{ PR ¬O¥¿½Tªº¡C ¥t¥~¤@¨Ç¥i¯à·|«D±`½ÆÂø¡A©ÎªÌ§¹¥þ¥¼ªþ¥ô¦ó­×¥¿¡C ­º¥ý¬Ý¤@¬Ý¨º¨ÇÁÙ¨S¦³¤H±µ¤âªº PR¡C ¦pªG PR ¤w¸g¤À°tµ¹¤F¨ä¥¦¤H¡A¦ý¬Ý°_¨Ó¬O±z¯à°÷³B²zªº¡A ±z¥i¥H±H«Hµ¹¨º­Ó¤H¡A¨Ã¸ß°Ý±z¬O§_¥i¥H´£¨ÑÀ°§U — ¥L­Ì¥i¯à¤w¸g¦³¥i¨Ñ´ú¸Õªº patch ¡A©Î¦³¤@¨Ç¥i¨Ñ°Q½×ªº·N¨£¡C ¥Ñ <quote>Ideas</quote> ¤¤¿ï¤@¶µ &os; list of projects and ideas for volunteers ¦P¼Ë¦a¶}©ñµ¹¦³·NÄ@°Ñ»P &os; ­p¹ºªº¤H¡C ³o¥÷²M³æ±N«ùÄò¦a§ó·s¡A¦P®É´£¨Ñ¦U­Ó¶µ¥Øªº¸ê°Tµ¹©Ò¦³¤H ¡]¤£½×¬O§_¬°µ{¦¡³]­p¤H­û¡^¡C ¦p¦ó´£¨ÑÀ°§U °ò¥»¤W¥i¥H¤À¬°¥H¤U 5 ºØ¤è¦¡¡G ¿ù»~³ø§i©M·N¨£µoªí ³q±`¡A¤@¯ë ªº§Þ³N·Qªk©M«ØijÀ³¸Óµo¨ì &a.hackers;¡C ¦P¼Ë¦a¡A¹ï©ó³o¨ÇªF¦è¦³¿³½ìªº¤H (·íµM¡A ¥L­Ì¦P®ÉÁÙ­n¯à°÷®e§Ô ¤j¶qªº ¶l¥ó¡I) ¥i¥H¦Ò¼{­q¾\ &a.hackers;¡C ½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥U ¥H¤F¸ÑÃö©ó³o­Ó¶l»¼½×¾Â¡A ¥H¤Î¨ä¥¦¶l»¼½×¾Âªº¸Ô²Ó±¡ªp¡C ¦pªG±zµo²{¤F bug ©ÎªÌ·Q­n´£¥æ¬Y¨Ç­×§ï¡A ½Ð³z¹L &man.send-pr.1; µ{¦¡©Î¨Ï¥Î ºô­¶¤¶­± ªº¦^³ø ¨Ó´£¥æ¡C½Ð¸ÕµÛ¶ñ¼g PR ªº¨C­Ó¶µ¥Ø¡C ¤@¯ë¨Ó»¡¡A°£«D patch ÀɶW¹L 65 KB¡A§Ú­Ì«Øij¦b PR ¤¤ª½±µªþ¤W patch ´N¥i¥H¤F¡C ­Y¥iª½±µ®M¥Î patch ¨ì­ì©l½Xªº¸Ü¡A¨º»ò«Øij¦b PR ªº Synopsis Äæ¦ìµù©ú [PATCH]¡C ¹ï¤F¡A¦bªþ¤W patch ®É¡A½Ð ¤£­n ³z¹L·Æ¹«ªº¡y½Æ»s¡B¶K¤W¡z¨Ó¶i¦æ¡A¦]¬°³o¼Ë°µ·|§â Tab Åܦ¨ªÅ®æ¡A ·|¾É­P patch ´N¤£¯à¥Î¤F¡C¦pªG patch ¶W¹L 20KB¡A ½Ð¦Ò¼{À£ÁY¥¦¨Ã¨Ï¥Î &man.uuencode.1; ¨Ó¶i¦æ½s½X¡C ¦b¼g§¹ PR ¤§«á¡A±z·|¦¬¨ì¤@«Ê½T»{¶l¥ó¥H¤Î¨Æ¥ó°lÂܽs¸¹¡C ½Ð«O¯d³o­Ó½s¸¹¡A¦]¬°¨Æ«á¥i¥H¥Î³o½s¸¹µo«H¨ì &a.bugfollowup; ¨Ó¦^ÂСB´£¨ÑÃö©ó¸Ó¨Æ¥óªº«áÄò¸ê®Æ¡C±z»Ý­n°µªº¬O±N½s¸¹©ñ¨ì¶l¥óªº¼ÐÃD¤¤¡A ¨Ò¦p "Re: kern/3377"¡C ­Y¬O¦P¤@°ÝÃDªº¦^ÂФ譱¡AÀ³¸Ó³z¹L³oºØ¤è¦¡¨Ó¶i¦æ¡C ¦pªG±z¦b¤@¬q®É¶¡ (¶W¹L 3 ¤Ñ¬Æ¦Ü 1 ¶g¡A³o¨ú¨M©ó±zªº¶l¥óªA°È)¤§«á¤´µM¨S¦³¦¬¨ì½T»{«H ©ÎªÌ¥Ñ©ó¤@¨Ç­ì¦]µLªk¨Ï¥Î &man.send-pr.1; µ{¦¡¡A «h¥i¥Hµo«H¨ì &a.bugs; ¨Ó½Ð§O¤HÀ°§A¥N±H¡C ½Ð°Ñ¾\ ³o½g¤å³¹ ¤F¸Ñ¦p¦ó¼¶¼g¦nªº°ÝÃD³ø§i¡C ¹ï©ó¤å¥óªº­×­q ´£¥æ¤å¥ó ¤å¥óªº­×§ï¤è­±¡A¬O¥Ñ &a.doc; ¨Ó¼f¬d¡C ½Ð°Ñ¾\ FreeBSD Documentation Project Primer ¨ÓÀò±o§¹¾ãªº±Ð¾Ç²Ó¸`¡C ½Ð«ö·Ó ¤¤¤¶²Ðªº¤èªk¨Ï¥Î &man.send-pr.1; ¨Ó´£¥æ·sªº¤å¥ó¡A©ÎªÌ§ïµ½²{¦³ªº¤å¥ó (­þ©È¬O«Ü¤pªº§ï¶i¤]¬OÅwªïªº¡I)¡C ¹ï©ó²{¦³­ì©l½Xªº­×§ï FreeBSD-CURRENT ¦b²{¦³­ì©l½X¤W¶i¦æ­×§ï©Î¼W¥[¥\¯à¡A¦b¬YºØµ{«×¤W¬O»Ý­n§ó¦h§Þ¥©ªº¨Æ¡A ¨Ã¥BÁÙ¸ò±z¹ï©ó¥Ø«e FreeBSD ªº¶}µo²{ª¬¤F¸Ñµ{«×¦³Ãö¡C ¦³¦hºØ¤è¦¡¥i¥H±o¨ì³QºÙ§@ FreeBSD-CURRENT ªº FreeBSD ¶}µoª©¥»¡C ½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥Uªº ¬ÛÃö³¡¥÷ ¡A¨Ó¤F¸Ñ¨Ï¥Î FreeBSD-CURRENT ªº¸Ô±¡¡C ¦bªº­ì©l½X¤W¶i¦æ­×§ï¡A«h³q±`¥i¯à­ì©l½X¤w¹L®É¡A ©Î»P·sªºª©¥»®t²§¤Ó¤j¦ÓµLªk³Q­«·s¾ã¦X¨ì FreeBSD ¤¤¡C ¦pªG±z¦³­q &a.announce; ¥H¤Î &a.current; ªº¸Ü¡A «h¥i¥H³z¹L¥¦­Ì¨Ó¤j­P¤F¸Ñ¥Ø«eªº¶}µoª¬ºA¡C ­Y±z¯à°÷¾¨¶q¥H³Ì·sªº­ì©l½X¨Ó¶i¦æ±zªº­×§ï¡A «h¤U¤@¨B­n°µªº¨Æ±¡´N¬O²£¥Í±z©Ò­×§ïªº diff ÀÉ¡A ¨Ã±N¥¦µoµ¹ FreeBSD ªººûÅ@¤H­û¡C³o¶µ¤u§@¥i¥H³z¹L &man.diff.1; ©R¥O¨Ó§¹¦¨¡C ´£¥æ patch ®É¡A«Øij &man.diff.1; ®æ¦¡±Ä¥Î unified diff (¥i¥H¥Î diff -u ¨Ó²£¥Í)¡C¤£¹L¡A¦pªG±z­×§ï¤F¤j¶qªº­ì©l½X¡A «h¨Ï¥Î diff -c ¨Ó¥Í¦¨ªº context diff ªº diff ¥i¯à§ó®e©ö¾\Ū¡A¦]¦Ó±ÀÂ˨ϥΡC¤@¯ë¦Ó¨¥¡A¤j³£¬O±Ä¥Î diff -ruN §Y¥i¡C diff ¨Ò¦p¡G &prompt.user; diff -c oldfile newfile ©Î &prompt.user; diff -c -r olddir newdir ±N·|¹ï¯S©w¥Ø¿ý¡A²£¥Í context ªº diff ÀÉ¡C ©ÎªÌ¹³¬O... &prompt.user; diff -u oldfile newfile ©Î &prompt.user; diff -u -r olddir newdir ±N²£¥Í¤@¼Ëªº diff ¡A¦ý¬O®æ¦¡¬° unified ¡C §ó¦hªº²Ó¸`³¡¥÷¡A½Ð°Ñ¾\ &man.diff.1;¡C ¤@¥¹±z¨Ï¥Î &man.diff.1; ¨Ó²£¥Í diff ÀÉ (¥i¥H¨Ï¥Î &man.patch.1; ©R¥O¨Ó´ú¸Õ¤@¤U)¡A´N¥i¥H´£¥æ¥¦­Ì¡A¥H«K³Q FreeBSD ¦¬¿ý¡C ³z¹L¨Ï¥Î ¤¤©Ò¤¶²Ðªº &man.send-pr.1; µ{¦¡´N¥i¥H§¹¦¨³o¶µ¤u§@¡C ½Ðª`·N¡G¤£­n¥u§â diff Àɵo¨ì &a.hackers;¡A §_«h¥¦­Ì¥i¯à·|³Q¿ò§Ñ¡I §Ú­Ì·|«D±`·P¿E±z´£¥æªº­×§ï (³o¬O¤@­Ó¸q¤u­p¹º¡I)¡F ¦]¬°§Ú­Ì³£«Ü¦£¡A ¦]¦¹¦³®É¤£¤@©w¯à°÷¥ß§Y­×¥¿°ÝÃD¡A¦ý PR ¸ê®Æ®w±N¤@ª½«O«ùµÛ³o¨Ç°O¿ý¡A ¦]¦¹¥u­n¦³¤H¦³¤F®É¶¡¥¦­Ì´N¯à³Q§ï¥¿¤F¡C ¦pªG±zªº°ÝÃD³ø§i¤¤¥]¬A patch ¡A¤£­n§Ñ¤F¦b¼ÐÃD¥[¤W [PATCH] ¨Ó±j½Õ¤@¤U¡C uuencode ¦pªG±z»{¬°¦X¾A (¨Ò¦p¼W¡B§RÀɮשΧó§ïÀɦW)¡A ÁÙ¥i¥H¦Ò¼{¨Ï¥Î tar ¨Ó±NÀÉ®×¥´¥]¡AµM«á¥Î &man.uuencode.1; ¨Ó½s½X¡C¦¹¥~¡A¤]¥i¥H¥Î &man.shar.1; ²£¥Íªº¤è¦¡¡C ¦pªG±zªº­×§ï¥i¯à¦s¦b¼ç¦bªºª§Ä³¡A¨Ò¦p¡A ±z¤£½T©w¬ÛÃöªºª©Åv°ÝÃD¡A©ÎªÌ·Pı»Ý­n¸g¹L§óÄY®æªº´_¼f¤~¥i¥Hµo§G¥¦­Ì¡A «hÀ³ª½±µµoµ¹ &a.core;¡A¦Ó¤£¬O³z¹L &man.send-pr.1; ¨Óµo°e¡C &a.core; ³o¤p²Õ¦¨­û¤j¦h±q¨Æ FreeBSD ªº¤é±`¤u§@¡C »Ý­nª`·Nªº¬O¡A³o­Ó¤p²Õ¤]¦]¦¹¤Q¤À¦£¸L¡A ¦]¦¹¥u¦³¦b«D±`¥²­nªº®É­Ô¡A¤~À³¼g«Hµ¹¥L­Ì¡C ½Ð°Ñ¦Ò &man.intro.9; ©M &man.style.9; ¥H¤F¸ÑÃö©ó¼¶¼gµ{¦¡½Xªº­·®æ°¾¦n¡C ­Y¯à¦b°e¥X¬ÛÃöµ{¦¡½X¤§«e¡A¥ý¤F¸Ñ³o¨Ç¡A¨º¹ï¤j®a¨Ó»¡±N¬O·¥¤jªºÀ°§U¡C ·s­ì©l½X©Î­«­nªº¥[­È³nÅé¥] ¦pªG±z¥´ºâ´£¨Ñ³W¼Ò¸û¤jªº­ì©l½X¡A©ÎªÌ¬° FreeBSD ¼W¥[­«­nªº·s¥\¯à¡A «h¥i¯à¥²¶·±N¥¦­Ì³z¹L uuencode ¶i¦æ½s½X¡A©Î¶Ç¨ì¬Y­Ó Web ©Î FTP ¯¸ÂI¡A¥H«K§ó¦hªº¤H¯à°÷±o¨ì¥¦¡C¦pªG±z¨S¦³³o¼Ëªº¥D¾÷¡A ½Ð¨ì¬ÛÃöªº FreeBSD ¶l»¼½×¾Â´£¥X¡A¬Ý¬Ý¬O§_¦³¤HÄ@·NÀ°±z©ñ¸m¥¦­Ì¡C ¹ï©ó¤j¶qªº­ì©l½X¦Ó¨¥¡AÃö©óª©Åvªº°ÝÃDªÖ©w·|³Q´£¥X¡C FreeBSD °ò¥»¨t²Î¤¤¯à°÷¨Ï¥Îªºª©ÅvÁn©ú¥]¬A¡G BSDBSD ª©ÅvÁn©ú ª©Åv¡C§Ú­Ì¶É¦V©ó¨Ï¥Î³oÃþ±ÂÅvªº­ì©l½X¡A ¦]¬°¥¦¡y¤£ªþ¥[¦h¾lªº±ø¥ó¡z¡A¦]¦Ó§ó¯à°÷§l¤Þ°Ó·~¥ø·~¨Ï¥Î¡C FreeBSD ¨Ã¤£¤Ï¹ï°Ó·~¤½¥q¨Ï¥Î¥¦ªº­ì©l½X¡A¬Û¤Ï¡A §Ú­Ì¿n·¥¦a¹ªÀy°Ó·~¤½¥q¨Ï¥Î§Ú­Ìªº­ì©l½X¡A ·íµM¡A¦pªG¥¦­Ì­Y³Ì²×¯à§â³¡¤À­ì©l½X¡A­«·s®½Ãص¹ FreeBSD ´N§ó¦n¤F¡C GNU General Public License¡A©Î²ºÙ GPL¡CGPLGNU General Public LicenseGNU General Public License §Ú­Ì¨Ã¤£«ÜÅwªï¨Ï¥Î³o¼Ë±ÂÅvªº­ì©l½X¡A ¦]¬°°Ó·~¤½¥q¨Ï¥Î¥¦»Ý­n°µ§ó¦hªº¤u§@¡C¤£¹L¡A¥Ñ©ó«Ü¦h¨Ï¥Î GPL ±ÂÅvªº­ì©l½X¥Ø«e¬OµLªkÁקKªº (compiler, assembler, text formatterµ¥µ¥) ¡A©Úµ´¨Ï¥Î©Ò¦³±Ä¥Î³o¼Ë±ÂÅvªº³nÅé¬O«Ü¤£©ú´¼ªº¡C ±Ä¥Î GPL ±ÂÅvªº­ì©l½X·|³Q©ñ¨ì­ì©l½Xªº¤@¨Ç¯S©wªº¦ì¸m¡A¨Ò¦p /sys/gnu ©Î /usr/src/gnu¡A¥H«K¨º¨Ç»{¬° GPL ¥i¯à·|³y¦¨³Â·Ðªº¤H¯à°÷§@¥X¾A·íªº§PÂ_¡C ¨Ï¥Î¨ä¥¦±ÂÅvªº­ì©l½X¦b¶i¤J FreeBSD ¤§«e¥²¶·¸g¹L·V­«ªº´_¼f©M¦Ò¼{¡C ±Ä¥Î¥]§tÄY¼F­­¨îªº°Ó·~±ÂÅvªº­ì©l½X¡A¤@¯ë¨Ó»¡·|³Q©Úµ´¡A ¦ý§Ú­Ì¹ªÀy³o¨Ç­ì©l½Xªº§@ªÌ¡A³z¹L¦Û¤vªººÞ¹D¨Óµo¥¬¥¦­Ì¡C ­Y­n¦b±zªº¦¨ªG¤W¥[¤J BSD-based ª©Åvªº¸Ü¡A ½Ð§â¤U¦C¤å¦r©ñ¨ì¨C¥÷­ì©l½Xªº³Ì¶}©l³¡¤À¡A ¨Ã¥Î¾A·íªº¤å¦r´À´« %% ¤§¶¡ªº¤å¦r¡C Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ ¬°¤F¤è«K±zªº¨Ï¥Î¡A¦b /usr/share/examples/etc/bsd-style-copyright ¤]¥i¥H§ä¨ì¦¹±ÂÅvªº°Æ¥»¡C ÃÙ§U¸êª÷¡BµwÅé©Î Internet mirror §Ú­Ì«D±`Ä@·N±µ¨ü¦UºØ§Î¦¡ªº®½ÃØ¡A¥H¶i¤@¨B©Ý®i FreeBSD ­p¹º ¡A¦]¬°¦³±zªº¤ä«ù¡A¹³§Ú­Ì³o¼Ëªº¸q¤u§V¤O¤~¯à°÷¦³§ó¤jªº¦¨´N¡I ®½ÃصwÅé¤]«D±`­«­n¡A¦]¬°³o¼Ë¯à°÷À°§U§Ú­Ì¼W¥[¥i¤ä´©ªºµwÅéºØÃþ¡A ¦Ó§Ú­Ì¤¤ªº«Ü¦h¤H¨Ã¨S¦³¨¬°÷ªº¸êª÷¨ÓÁʸm³o¨ÇµwÅé¡C <anchor id="donations"/>®½´Ú FreeBSD °òª÷·|¬O¤@­Ó«DÀç§Qªº¡B¦³½Òµ|ÁŧKÅvªº°òª÷·|¡A ¤§©Ò¥H·|«Ø¥ß³o­Ó°òª÷·|¡A¬O¬°¤FÅý FreeBSD ­p¹º¯à°÷¥iªø¥i¤[¡C ¦]¬°¸Ó°òª÷·|ÄÝ 501(c)3 ¹êÅé¡A¤@¯ë¦Ó¨¥®½´Úµ¹°òª÷·|ªº¸Ü¡A¥i¥H§Kú¬ü°êÁp¨¹¦¬¤Jµ|¡A ¥H¤Î¬ìù©Ô¦h¦{¦¬¤Jµ|¡C³q±`¹ï©ó¦³½Òµ|ÁŧKÅvªº¹êÅé¶i¦æ®½Ãتº¸Ü¡A ¥i¥H§é©èÁp¨¹¦¬¤J¤¤À³½Òµ|³¡¤Àªºª÷ÃB¡C ±z¥i¥H§â¤ä²¼±H©¹¡G
The FreeBSD Foundation 7321 Brockway Dr. Boulder, CO 80303 USA
FreeBSD °òª÷·|²{¦b¥i¥H³z¹L PayPal ±qºô¤W±µ¨ü®½´Ú¡C ¦pªG±z·Q¦V°òª÷·|®½´Ú¡A½Ð°Ñ¾\ FreeBSD °òª÷·| ºô¯¸¡C Ãö©ó FreeBSD °òª÷·|ªº§ó¦h¸Ô±¡¡A¥i¥H¦b FreeBSD °òª÷·| -- ¤¶²Ð §ä¨ì¡C­nÁpµ¸°òª÷·|¡A ½Ðµo°e¹q¤l¶l¥ó¨ì bod@FreeBSDFoundation.org¡C ®½ÃصwÅé ®½ÃØ FreeBSD ­p¹ºÅwªï¥ô¦ó¤H®½ÃØ¥i¥H¨Ï¥ÎªºµwÅé¡C ¦pªG±z¦³¿³½ì®½ÃصwÅé¡A½ÐÁpô ®½ÃØÁpµ¸¤H¿ì¤½«Ç¡C ¦¨¬° FreeBSD mirror ªººô¯¸ §Ú­ÌÅwªï·sªº FTP¡BWWW ©Î cvsup mirror ¯¸¡C¦pªG±z§Æ±æ¦¨¬°³o¼Ëªº mirror ¯¸¡A ½Ð°Ñ¾\ ¦p¦ó¬[³] FreeBSD mirror ¤@¤å¡A¥H¤F¸Ñ¶i¤@¨Bªº±¡ªp¡C +
diff --git a/zh_TW.Big5/articles/nanobsd/article.xml b/zh_TW.Big5/articles/nanobsd/article.xml index 15ee953eea..b0afa998e7 100644 --- a/zh_TW.Big5/articles/nanobsd/article.xml +++ b/zh_TW.Big5/articles/nanobsd/article.xml @@ -1,438 +1,440 @@
NanoBSD ²¤¶ Daniel Gerzo 2006 The FreeBSD Documentation Project $FreeBSD$ $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.general; ³o½g¤å¥ó´£¨Ñ¤FÃö©ó NanoBSD ¤u¨ãªº±¡³ø¤¶²Ð¡A ³o¤u¨ã¥i¥Î¨Ó«Ø¥ß¥Î©ó´O¤J¦¡Àô¹ÒÀ³¥Îµ{¦¡ªº &os; ¨t²Î¬M¹³ÀÉ¡A ¥H«K¦s©ñ¨ì Compact Flash ¥d(©ÎÀH¨­ºÐ)¡C NanoBSD ²¤¶ NanoBSD NanoBSD ¬O &a.phk; ¥Ø«e¥¿¦b¶}µoªº¤@¶µ¤u¨ã¡C ¥¦¥i¥Î¨Ó«Ø¥ß¥Î©ó´O¤J¦¡Àô¹ÒÀ³¥Îµ{¦¡ªº &os; ¨t²Î¬M¹³ÀÉ¡A ¥H«K¦s©ñ¨ì Compact Flash ¥d(©ÎÀH¨­ºÐ¡Amass storage medium)¡C ³o¤@¤u¨ã¤]¥i¥H¥Î¨Ó¦Û»s¦w¸Ë¬M¹³ÀÉ¡A ¥H²¤Æ«UºÙ¬° ´O¤J¦¡¨t²Î(computer appliances) ªº¨t²Î¦w¸Ë¡BºûÅ@¤u§@¡C ³q±`¡A¨C­Ó´O¤J¦¡¨t²Î²£«~³£¦³­­©wµwÅé©M³nÅé¡A ©ÎªÌ´«¨¥¤§¡A©Ò¦³ªºÀ³¥Îµ{¦¡³£¬O¹w¥ý¸Ë¦nªº¡C ³o¨Ç³]³Æ¥i¥Hª½±µ©ñ¨ì²{¦³ªººô¸ô¤¤¡A¦Ó¥B(´X¥G¬O)¥ß§Y¨Ï¥Î¡C NanoBSD ´£¨Ñªº¥\¯à¥]¬A¡G ¥i¥H©M &os; ¤@¼Ë¨Ï¥Î Ports ©M Packages — ©Ò¦³ªºÀ³¥Îµ{§Ç³£¥i¥H¦b NanoBSD ¤¤ª½±µ¨Ï¥Î¡A ¦Ó¤è¦¡»P &os; §¹¥þ¤@¼Ë¡C ¥\¯àµ·²@¥¼·l — ¦b &os; °µªº¥ô¦ó¤u§@¡A³£¥i¥H¦b NanoBSD ¤¤¨Ï¥Î¡A °£«D±z¦b«Ø¥ß NanoBSD ¬M¹³ÀɮɡA ¦³«ü©w­n®³±¼¥¦­Ì¡C ©Ò¦³ªF¦è¦b¹B¦æ®É³£¬O°ßŪªº — ¥i¥H¦w¥þ¦a©Þ±¼¹q·½´¡ÀY¡C ¨t²Î¤£¥¿±`Ãö¾÷ªº¸Ü¡A¤£¥Î¦A¶] &man.fsck.8; ¤F¡C ¥i»´ÃP½sĶ¡B¦Û¦æ¥´³y — ¥u»Ý¨Ï¥Î¤@­Ó shell script ©M¤@­Ó³]©wÀÉ¡A ±z¥i¥H»´ÃP¨Ì»Ý¨D¨Ó¶q¨­­q°µ¾A¥Îªº¬M¹³ÀÉ¡C ¦p¦ó¨Ï¥Î NanoBSD NanoBSD ªº³]­p ¤@¥¹±N¬M¹³Àɦs¤J´O¤J¦¡µwÅé¡A´N¥i¥H¥Î¥¦¨Ó¤Þ¾É NanoBSD ¤F¡C ¹w³]±¡ªp¤U¡AÀH¨­ºÐ·|¹º¤À¬°¤T³¡¤À¡G ¨â­Ó¬M¹³ÀɤÀ³Î°Ï¡G code#1 ©M code#2¡C ¤@­Ó³]©wÀɤÀ³Î°Ï¡A¦b¹B¦æÀô¹Ò¤¤¡A ¥i¥H±N¨ä±¾¸ü(mount)¨ì /cfg ¥Ø¿ý¤U¡C ³o¨Ç¤À³Î°Ï¡A¦b¹w³]±¡ªp¤U¬O¥H°ßŪ¤è¦¡±¾¸ü¡C /etc ©M /var ¥Ø¿ý§¡¬° &man.md.4;(malloc)ºÏºÐ¡C ³]©wÀɪº¤À³Î°Ï«h¬O¦b /cfg ¥Ø¿ý¡C ¥¦¥]§t¤F¥Î©ó /etc ¥Ø¿ýªºÀɮסA¦b±Ò°Ê¤§«á¼È®É¥H°ßŪ¤è¦¡±¾¸ü¡C ¦]¦¹¡A­Y·Q­n­«¶}¾÷«O¯d·sªº³]©w¡A ¨º»ò­n°O±o±q /etc §â§ï¹LªºÀɮ׽ƻs¦^ /cfg ¥Ø¿ý¤~¦æ¡C §â­×§ï¹L <filename>/etc/resolv.conf</filename> ³]©w«O¦s°_¨Ó &prompt.root; vi /etc/resolv.conf [...] &prompt.root; mount /cfg &prompt.root; cp /etc/resolv.conf /cfg &prompt.root; umount /cfg ¥u¦³¦b¨t²Î±Ò°Ê¹Lµ{¤¤¡A¥H¤Î»Ý­n­×§ï³]©wÀɪº®É­Ô¡A¤~»Ý­n±¾¸ü§t¦³ /cfg ªº¨º­Ó¤À³Î°Ï¡C ¤@ª½³£±¾¸ü /cfg ¤£¬O¤@­Ó¦n¥D·N¡A¯S§O¬O·í±z§â NanoBSD ©ñ¦b¤£¾A¦X¶i¦æ¤j¶q¼g¤J°Ê§@ªº¤À³Î°Ï®É (¤ñ¦p¡G¥Ñ©óÀɮרt²Îªº¦P¨B¤Æ·|©w´Á¦b¨t²ÎºÐ¤º¼g¤J¸ê®Æ)¡C ¥´³y NanoBSD ¬M¹³ÀÉ NanoBSD ¬M¹³ÀɬO³z¹L¨Ï¥Î«D±`²³æªº nanobsd.sh shell script ¨Ó¥´³yªº¡A³o­Ó script ¥i¥H¦b /usr/src/tools/tools/nanobsd ¥Ø¿ý¤¤§ä¨ì¡C ³o­Ó script «Ø¥ßªº¬M¹³ÀÉ¡A¥i¥H¥Î &man.dd.1; ¤u¨ã¨Ó½Æ»s¨ìÀH¨­ºÐ¤W¡C ¥´³y NanoBSD ¬M¹³Àɩһݪº«ü¥O¬O¡G &prompt.root; cd /usr/src/tools/tools/nanobsd &prompt.root; sh nanobsd.sh &prompt.root; cd /usr/obj/nanobsd.full &prompt.root; dd if=_.disk.full of=/dev/da0 bs=64k ¶i¤J NanoBSD ¥´³y script ªº¥D¥Ø¿ý¡C ¶}©l¥´³y¹Lµ{¡C ¶i¤J¥´³y¦nªº¬M¹³ÀÉ©Ò¦bªº¥Ø¿ý¡C ¦bÀH¨­ºÐ¤W¦w¸Ë NanoBSD¡C ¦Û¦æ¥´³y NanoBSD ¬M¹³ÀÉ ³o¥i¯à¬O NanoBSD ³Ì¬°­«­n¡A ¦P®É¤]¬O±z³Ì·P¿³½ìªº¥\¯à¡C ¦P®É¡A¦b¶}µo NanoBSD À³¥Îµ{¦¡®É¡A³o¤]¬O¬Û·í¯Ó®Éªº¹Lµ{¡C °õ¦æ¤U­±ªº«ü¥O±N·| nanobsd.sh Ū¨ú¥Ø«e©Ò¦b¥Ø¿ýªº myconf.nano Àɪº³]©w¡G &prompt.root; sh nanobsd.sh -c myconf.nano ¦Û¦æ¥´³yªº¬yµ{¡A¥u»Ý¨â­Ó¨BÆJ¡G ¦Û­q¿ï¶µ ¦Û­q¥\¯à ¦Û­q¿ï¶µ ³z¹L­×§ï³]©w¡A¥i¥H³]©w¥Î©ó NanoBSD ¥´³y¹Lµ{¤¤ buildworld ©M installworld ¶¥¬qªº½sĶ¡B¦w¸Ë¿ï¶µ¡A¥H¤Î NanoBSD ¥D­n¥´³y¹Lµ{¤¤ªº¿ï¶µ¡C ³z¹L¨Ï¥Î³o¨Ç¿ï¶µ¥i¥H«d´î¨t²Îªº¤Ø¤o¡A¨Ï¤§¯à°÷©ñ¤J 64 MB ªºÀH¨­ºÐ¡C ±zÁÙ¥i¥H¶i¤@¨B³z¹L³o¨Ç¿ï¶µ¨Ó«d´î &os;¡A ª½¨ì¥¦¥u¥]§t kernel ¥H¤Î¨â¤T­Ó userland Àɮ׬°¤î¡C ³]©wÀɮפ¤¥]§t¥Î¥H¥N´À¹w³]­Èªº³]©w¿ï¶µ¡C²¤¶³Ì­«­nªº´X¶µ³]©w¦p¤U¡G NANO_NAME — ¥»¦¸¥´³yªº¦WºÙ(©Ò«Ø¥ß¤u§@¥Ø¿ýªº¦WºÙ)¡C NANO_SRC — ¥Î¥H½sĶ¡B¥´³y¬M¹³Àɪº source tree ªº¦ì¸m¡C NANO_KERNEL — ³]©w¥Î¨Ó½sĶªº kernel ³]©wÀÉÀɦW¡C CONF_BUILD — ¥Î©ó buildworld ¥´³y¶¥¬qªº¿ï¶µ¡C CONF_INSTALL — ¥Î©ó installworld ¥´³y¶¥¬qªº¿ï¶µ¡C CONF_WORLD — ¥Î©ó buildworld ©M installworld ³o¨â­Ó¥´³y¶¥¬qªº¿ï¶µ¡C FlashDevice — ©w¸q©Ò¥Îªº´O¤J¦¡µwÅéÃþ«¬¡C ¸Ô±¡½Ð°Ñ¦Ò FlashDevice.sub ÀÉ¡C ¦Û­q¥\¯à ³z¹L¦b³]©wÀɮפ¤¨Ï¥Î shell ¨ç¼Æ¡A¥i¥H¶i¤@¨B·L½Õ NanoBSD¡C Á|¨Ò»¡©ú¤@¤U¦Û¦æ¥´³y¨ç¼Æªº°ò¥»¤è¦¡¡G cust_foo()( echo "bar=topless" > \ ${NANO_WORLDDIR}/etc/foo ) customize_cmd cust_foo ¤U­±Á|§ó¹ê»ÚÂIªº¨Ò¤l¡A¥¦·|§â¹w³]ªº /etc ¥Ø¿ý¤j¤p¡A±q 5MB ½Õ¾ã¬° 30MB¡G cust_etc_size()( cd ${NANO_WORLDDIR}/conf echo 30000 > default/etc/md_size ) customize_cmd cust_etc_size °£¦¹¤§¥~¡AÁÙ¦³´X­Ó¹w³]ªº¥\¯à©w¸q¥i¥H¥Î¨Ó¦Û­q¡G cust_comconsole — ¦b¹w³] VGA Åã¥Ü¥d¤W°±¥Î &man.getty.8; (/dev/ttyv*)¨Ã±Ò¥Î serial port ªº COM1 ¥H§@¬°¨t²Î console¡C cust_allow_ssh_root — ¤¹³\ &man.sshd.8; ¥i¥H¥Î root ±b¸¹µn¤J¡C cust_install_files — ±q nanobsd/Files ¥Ø¿ý¤¤¦w¸ËÀɮסA³o¥]§t¤@¨Ç¹ê¥Îªº¨t²ÎºÞ²z script ¡C ³]©wÀÉ®×Á|¨Ò ¤U­±¬O¥Î©ó¦Û¦æ¥´³yªº NanoBSD ¬M¹³Àɪº§¹¾ã¨Ò¤l¡G NANO_NAME=custom NANO_SRC=/usr/src NANO_KERNEL=MYKERNEL NANO_IMAGES=2 CONF_BUILD=' NO_KLDLOAD=YES NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_ACPI=YES NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SENDMAIL=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_INSTALLLIB=YES NO_CALENDAR=YES NO_MISC=YES NO_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_MODULES=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_LOCALES=YES NO_SYSCONS=YES NO_INFO=YES ' FlashDevice SanDisk 1G cust_nobeastie()( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) customize_cmd cust_comconsole customize_cmd cust_install_files customize_cmd cust_allow_ssh_root customize_cmd cust_nobeastie §ó·s NanoBSD §ó·s NanoBSD ¬Û¹ï &os; ¦Ó¨¥¸û¬°Â²³æ¡G ©M¤§«e¤@¼Ë¥´³y·sªº NanoBSD ¬M¹³ÀÉ¡C ±N·sªº¬M¹³ÀÉ©ñ¤J¥¿¹B¦æªº NanoBSD ¤¤¥¼¥Îªº¤À³Î°Ï¤§¤@¡C »P¤§«e³Ìªì¦w¸Ë NanoBSD ªº¨BÆJ¬Û¤ñ¡A ³o¤@¨BÆJ³Ì­«­nªº°Ï§O¦b©ó¡G³o¦¸¤£¥Î _.disk.full ÀÉ(¥¦¥]§t¾ã­ÓºÏºÐªº¬M¹³ÀÉ)¡A ¦ÓÀ³¦w¸Ë _.disk.image ¬M¹³ÀÉ(³o­ÓÀɮפ¤¡A¥u¥]§t¤@­Ó¨t²Î¤À³Î°Ï)¡C ­«·s±Ò°Ê¡A¨Ã±q·s¦w¸Ëªº¤À³Î°Ï¤¤±Ò°Ê¨t²Î¡C ¦pªG¤@¤Á¶¶§Qªº¸Ü¡A¤É¯Å¤u§@´N§¹¦¨¤F¡C ¦pªGµo¥Í¤F¥ô¦ó°ÝÃD¡A«h¥i¥H±q¥ý«eªº¤À³Î°Ï±Ò°Ê (¨ä¤¤¥]§t¤Fªº¡B ¥i¥Îªº¬M¹³ÀÉ)¡A¨ÓºÉ§Ö«ì´_¨t²Î¥\¯à¡C ±µ¤U¨Ó¥i¥H­×¥¿·s½sĶªºª©¥»¤¤¦s¦bªº°ÝÃD¡A¨Ã­«½Æ«e­z¨BÆJ¡C ­n¦b¥¿¦b¹B¦æªº NanoBSD ¨t²Î¤¤¦w¸Ë·sªº¬M¹³ÀÉ¡A¥i¥H¨Ï¥Î¦ì©ó /root ¥Ø¿ýªº updatep1 ©Î updatep2 script ¡A ¹ê»Ú¤W­n¥Î­þ¤@­Ó script¡A«h¨ú¨M©ó¥¿¦b¹B¦æªº¨t²Î¬O¦ì©ó­þ­Ó¤À³Î°Ï¦Ó©w¡C ÀH®É´£¨Ñ·s NanoBSD ¬M¹³ÀÉ©Ò´£¨ÑªºªA°È¡A ¥H¤Î±Ä¥Îªº¶Ç¿é¤èªkªº¤£¦P¡A±z¥i¥H°Ñ¦Ò¨Ã¨Ï¥Î¤U¦C¤TºØ¤è¦¡¤§¤@¡G ¨Ï¥Î &man.ftp.1; ¦pªG¶Ç¿é³t«×¬O²Ä¤@­n¨Dªº¸Ü¡A½Ð±Ä¥Î¤U­±¨Ò¤l¡G &prompt.root; ftp myhost get _.disk.image "| sh updatep1" ¨Ï¥Î &man.ssh.1; ¦pªG·Q§ó¦w¥þªº¸Ü¡AÀ³°Ñ¦Ò¤U­±¨Ò¤l¡G &prompt.root; ssh myhost cat _.disk.image.gz | zcat | sh updatep1 ¨Ï¥Î &man.nc.1; ¦pªG»·µ{¥D¾÷¬J¤£´£¨Ñ &man.ftp.1; ªA°È¡A¤]¤£´£¨Ñ &man.sshd.8; ªA°Èªº¸Ü¡G ­º¥ý¡A¦b´£¨Ñ¬M¹³Àɪº¥D¾÷¤W¶}±Ò TCP listen¡A¨ÃÅý¥¦§â¬M¹³Àɶǵ¹ client¡G myhost&prompt.root; nc -l 2222 < _.disk.image ½Ð½T»{±z©Ò¨Ï¥Îªº port ¨S¦³³Q¨¾¤õÀðªý¤î¨Ó¦Û NanoBSD client ªº³s½u½Ð¨D¡C ³s¨ì´£¨Ñ·s¬M¹³ÀɪA°Èªº¥D¾÷¡A¨Ã°õ¦æ updatep1 ³o¤ä script¡G &prompt.root; nc myhost 2222 | sh updatep1 + +
diff --git a/zh_TW.Big5/articles/problem-reports/article.xml b/zh_TW.Big5/articles/problem-reports/article.xml index bdb7d37812..a8feb9856a 100644 --- a/zh_TW.Big5/articles/problem-reports/article.xml +++ b/zh_TW.Big5/articles/problem-reports/article.xml @@ -1,1114 +1,1116 @@
Writing &os; Problem Reports $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.ibm; &tm-attrib.intel; &tm-attrib.sparc; &tm-attrib.sun; &tm-attrib.general; This article describes how to best formulate and submit a problem report to the &os; Project. Dag-Erling Smørgrav Contributed by Mark Linimon $FreeBSD$ problem reports
Introduction One of the most frustrating experiences one can have as a software user is to submit a problem report only to have it summarily closed with a terse and unhelpful explanation like not a bug or bogus PR. Similarly, one of the most frustrating experiences as a software developer is to be flooded with problem reports that are not really problem reports but requests for support, or that contain little or no information about what the problem is and how to reproduce it. This document attempts to describe how to write good problem reports. What, you ask, is a good problem report? Well, to go straight to the bottom line, a good problem report is one that can be analyzed and dealt with swiftly, to the mutual satisfaction of both user and developer. Although the primary focus of this article is on &os; problem reports, most of it should apply quite well to other software projects. Note that this article is organized thematically, not chronologically, so you should read through the entire document before submitting a problem report, rather than treat it as a step-by-step tutorial.
When to submit a problem report There are many types of problems, and not all of them should engender a problem report. Of course, nobody is perfect, and there will be times when you are convinced you have found a bug in a program when in fact you have misunderstood the syntax for a command or made a typographical error in a configuration file (though that in itself may sometimes be indicative of poor documentation or poor error handling in the application). There are still many cases where submitting a problem report is clearly not the right course of action, and will only serve to frustrate you and the developers. Conversely, there are cases where it might be appropriate to submit a problem report about something else than a bug—an enhancement or a feature request, for instance. So how do you determine what is a bug and what is not? As a simple rule of thumb your problem is not a bug if it can be expressed as a question (usually of the form How do I do X? or Where can I find Y?). It is not always quite so black and white, but the question rule covers a large majority of cases. If you are looking for an answer, consider posing your question to the &a.questions;. Some cases where it may be appropriate to submit a problem report about something that is not a bug are: Requests for feature enhancements. It is generally a good idea to air these on the mailing lists before submitting a problem report. Notification of updates to externally maintained software (mainly ports, but also externally maintained base system components such as BIND or various GNU utilities). For unmaintained ports (MAINTAINER contains ports@FreeBSD.org), such update notifications might get picked up by an interested committer, or you might be asked to provide a patch to update the port; providing it upfront will greatly improve your chances that the port will get updated in a timely manner. If the port is maintained, PRs announcing new upstream releases are usually not very useful since they generate supplementary work for the committers, and the maintainer likely knows already there is a new version, they have probably worked with the developers on it, they are probably testing to see there is no regression, etc. In either case, following the process described in Porter's Handbook will yield the best results. A bug that can not be reproduced can rarely be fixed. If the bug only occurred once and you can not reproduce it, and it does not seem to happen to anybody else, chances are none of the developers will be able to reproduce it or figure out what is wrong. That does not mean it did not happen, but it does mean that the chances of your problem report ever leading to a bug fix are very slim. To make matters worse, often these kinds of bugs are actually caused by failing hard drives or overheating processors — you should always try to rule out these causes, whenever possible, before submitting a PR. Next, to decide to whom you should file your problem report, you need to understand that the software that makes up &os; is composed of several different elements: Code in the base system that is written and maintained by &os; contributors, such as the kernel, the C library, and the device drivers (categorized as kern); the binary utilities (bin); the manual pages and documentation (docs); and the web pages (www). All bugs in these areas should be reported to the &os; developers. Code in the base system that is written and maintained by others, and imported into &os; and adapted. Examples include bind, &man.gcc.1;, and &man.sendmail.8;. Most bugs in these areas should be reported to the &os; developers; but in some cases they may need to be reported to the original authors instead if the problems are not &os;-specific. Usually these bugs will fall under either the bin or gnu categories. Individual applications that are not in the base system but are instead part of the &os; Ports Collection (category ports). Most of these applications are not written by &os; developers; what &os; provides is merely a framework for installing the application. Therefore, you should only report a problem to the &os; developers when you believe the problem is &os;-specific; otherwise, you should report it to the authors of the software. Then you should ascertain whether or not the problem is timely. There are few things that will annoy a developer more than receiving a problem report about a bug she has already fixed. If the problem is in the base system, you should first read the FAQ section on &os; versions, if you are not already familiar with the topic. It is not possible for &os; to fix problems in anything other than certain recent branches of the base system, so filing a bug report about an older version will probably only result in a developer advising you to upgrade to a supported version to see if the problem still recurs. The Security Officer team maintains the list of supported versions. If the problem is in a port, note that you must first upgrade to the latest version of the Ports Collection and see if the problem still applies. Due to the rapid pace of changes in these applications, it is infeasible for &os; to support anything other than the absolute latest versions, and problems with older version of applications simply cannot be fixed.
Preparations A good rule to follow is to always do a background search before submitting a problem report. Maybe your problem has already been reported; maybe it is being discussed on the mailing lists, or recently was; it may even already be fixed in a newer version than what you are running. You should therefore check all the obvious places before submitting your problem report. For &os;, this means: The &os; Frequently Asked Questions (FAQ) list. The FAQ attempts to provide answers for a wide range of questions, such as those concerning hardware compatibility, user applications, and kernel configuration. The mailing lists—if you are not subscribed, use the searchable archives on the &os; web site. If your problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something you have overlooked. Optionally, the entire web—use your favorite search engine to locate any references to your problem. You may even get hits from archived mailing lists or newsgroups you did not know of or had not thought to search through. Next, the searchable &os; PR database (GNATS). Unless your problem is recent or obscure, there is a fair chance it has already been reported. Most importantly, you should attempt to see if existing documentation in the source base addresses your problem. For the base &os; code, you should carefully study the contents of the /usr/src/UPDATING file on your system or its latest version at . (This is vital information if you are upgrading from one version to another—especially if you are upgrading to the &os.current; branch). However, if the problem is in something that was installed as a part of the &os; Ports Collection, you should refer to /usr/ports/UPDATING (for individual ports) or /usr/ports/CHANGES (for changes that affect the entire Ports Collection). and are also available via CVSweb.
Writing the problem report Now that you have decided that your issue merits a problem report, and that it is a &os; problem, it is time to write the actual problem report. Before we get into the mechanics of the program used to generate and submit PRs, here are some tips and tricks to help make sure that your PR will be most effective.
Tips and tricks for writing a good problem report Do not leave the Synopsis line empty. The PRs go both onto a mailing list that goes all over the world (where the Synopsis is used for the Subject: line), but also into a database. Anyone who comes along later and browses the database by synopsis, and finds a PR with a blank subject line, tends just to skip over it. Remember that PRs stay in this database until they are closed by someone; an anonymous one will usually just disappear in the noise. Avoid using a weak Synopsis line. You should not assume that anyone reading your PR has any context for your submission, so the more you provide, the better. For instance, what part of the system does the problem apply to? Do you only see the problem while installing, or while running? To illustrate, instead of Synopsis: portupgrade is broken, see how much more informative this seems: Synopsis: port sysutils/portupgrade coredumps on -current. (In the case of ports, it is especially helpful to have both the category and portname in the Synopsis line.) If you have a patch, say so. A PR with a patch included is much more likely to be looked at than one without. If you are including one, put the string [patch] at the beginning of the Synopsis. (Although it is not mandatory to use that exact string, by convention, that is the one that is used.) If you are a maintainer, say so. If you are maintaining a part of the source code (for instance, a port), you might consider adding the string [maintainer update] at the beginning of your synopsis line, and you definitely should set the Class of your PR to maintainer-update. This way any committer that handles your PR will not have to check. Be specific. The more information you supply about what problem you are having, the better your chance of getting a response. Include the version of &os; you are running (there is a place to put that, see below) and on which architecture. You should include whether you are running from a release (e.g. from a CDROM or download), or from a system maintained by &man.cvsup.1; (and, if so, how recently you updated). If you are tracking the &os.current; branch, that is the very first thing someone will ask, because fixes (especially for high-profile problems) tend to get committed very quickly, and &os.current; users are expected to keep up. Include which global options you have specified in your make.conf. Note: specifying -O2 and above to &man.gcc.1; is known to be buggy in many situations. While the &os; developers will accept patches, they are generally unwilling to investigate such issues due to simple lack of time and volunteers, and may instead respond that this just is not supported. If this is a kernel problem, then be prepared to supply the following information. (You do not have to include these by default, which only tends to fill up the database, but you should include excerpts that you think might be relevant): your kernel configuration (including which hardware devices you have installed) whether or not you have debugging options enabled (such as WITNESS), and if so, whether the problem persists when you change the sense of that option a backtrace, if one was generated the fact that you have read src/UPDATING and that your problem is not listed there (someone is guaranteed to ask) whether or not you can run any other kernel as a fallback (this is to rule out hardware-related issues such as failing disks and overheating CPUs, which can masquerade as kernel problems) If this is a ports problem, then be prepared to supply the following information. (You do not have to include these by default, which only tends to fill up the database, but you should include excerpts that you think might be relevant): which ports you have installed any environment variables that override the defaults in bsd.port.mk, such as PORTSDIR the fact that you have read ports/UPDATING and that your problem is not listed there (someone is guaranteed to ask) Avoid vague requests for features. PRs of the form someone should really implement something that does so-and-so are less likely to get results than very specific requests. Remember, the source is available to everyone, so if you want a feature, the best way to ensure it being included is to get to work! Also consider the fact that many things like this would make a better topic for discussion on freebsd-questions than an entry in the PR database, as discussed above. Make sure no one else has already submitted a similar PR. Although this has already been mentioned above, it bears repeating here. It only take a minute or two to use the web-based search engine at . (Of course, everyone is guilty of forgetting to do this now and then.) Avoid controversial requests. If your PR addresses an area that has been controversial in the past, you should probably be prepared to not only offer patches, but also justification for why the patches are The Right Thing To Do. As noted above, a careful search of the mailing lists using the archives at is always good preparation. Be polite. Almost anyone who would potentially work on your PR is a volunteer. No one likes to be told that they have to do something when they are already doing it for some motivation other than monetary gain. This is a good thing to keep in mind at all times on Open Source projects.
Before you begin If you are using the &man.send-pr.1; program, make sure your VISUAL (or EDITOR if VISUAL is not set) environment variable is set to something sensible. You should also make sure that mail delivery works fine. &man.send-pr.1; uses mail messages for the submission and tracking of problem reports. If you cannot post mail messages from the machine you are running &man.send-pr.1; on, your problem report will not reach the GNATS database. For details on the setup of mail on &os;, see the Electronic Mail chapter of the &os; Handbook at . Make sure that your mailer will not mangle the message on its way to GNATS. In particular, if your mailer automatically breaks lines, changes tabs to spaces, or escapes newline characters, any patch that you submit will be rendered unusable. For the text sections, however, we request that you insert manual linebreaks somewhere around 70 characters, so that the web display of the PR will be readable. Similar considerations apply if you are using the web-based PR submittal form instead of &man.send-pr.1;. Note that cut-and-paste operations can have their own side-effects on text formatting. In certain cases it may be necessary to use &man.uuencode.1; to ensure that patches arrive unmodified. Finally, if your submission will be lengthy, you should to prepare your work offline so that nothing will be lost in case there is a problem submitting it. This can be an especial problem with the web form.
Attaching patches or files The following applies to submitting PRs via email: The &man.send-pr.1; program has provisions for attaching files to a problem report. You can attach as many files as you want provided that each has a unique base name (i.e. the name of the file proper, without the path). Just use the command-line option to specify the names of the files you wish to attach: &prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors Do not worry about binary files, they will be automatically encoded so as not to upset your mail agent. If you attach a patch, make sure you use the or option to &man.diff.1; to create a context or unified diff (unified is preferred), and make sure to specify the exact CVS revision numbers of the files you modified so the developers who read your report will be able to apply them easily. For problems with the kernel or the base utilities, a patch against &os.current; (the HEAD CVS branch) is preferred since all new code should be applied and tested there first. After appropriate or substantial testing has been done, the code will be merged/migrated to the &os.stable; branch. If you attach a patch inline, instead of as an attachment, note that the most common problem by far is the tendency of some email programs to render tabs as spaces, which will completely ruin anything intended to be part of a Makefile. Do not send patches as attachments using Content-Transfer-Encoding: quoted-printable. These will perform character escaping and the entire patch will be useless. Also note that while including small patches in a PR is generally all right—particularly when they fix the problem described in the PR—large patches and especially new code which may require substantial review before committing should be placed on a web or ftp server, and the URL should be included in the PR instead of the patch. Patches in email tend to get mangled, especially when GNATS is involved, and the larger the patch, the harder it will be for interested parties to unmangle it. Also, posting a patch on the web allows you to modify it without having to resubmit the entire patch in a followup to the original PR. Finally, large patches simply increase the size of the database, since closed PRs are not actually deleted but instead kept and simply marked as closed. You should also take note that unless you explicitly specify otherwise in your PR or in the patch itself, any patches you submit will be assumed to be licensed under the same terms as the original file you modified.
Filling out the template The next section applies to the email method only: When you run &man.send-pr.1;, you are presented with a template. The template consists of a list of fields, some of which are pre-filled, and some of which have comments explaining their purpose or listing acceptable values. Do not worry about the comments; they will be removed automatically if you do not modify them or remove them yourself. At the top of the template, below the SEND-PR: lines, are the email headers. You do not normally need to modify these, unless you are sending the problem report from a machine or account that can send but not receive mail, in which case you will want to set the From: and Reply-To: to your real email address. You may also want to send yourself (or someone else) a carbon copy of the problem report by adding one or more email addresses to the Cc: header. In the email template you will find the following two single-line fields: Submitter-Id: Do not change this. The default value of current-users is correct, even if you run &os.stable;. Confidential: This is prefilled to no. Changing it makes no sense as there is no such thing as a confidential &os; problem report—the PR database is distributed worldwide by CVSup. The next section describes fields that are common to both the email interface and the web interface: Originator: Please specify your real name, optionally followed by your email address in angle brackets. In the email interface, this is normally prefilled with the gecos field of the currently logged-in user. The email address you use will become public information and may become available to spammers. You should either have spam handling procedures in place, or use a temporary email account. However, please note that if you do not use a valid email account at all, we will not be able to ask you questions about your PR. Organization: Whatever you feel like. This field is not used for anything significant. Synopsis: Fill this out with a short and accurate description of the problem. The synopsis is used as the subject of the problem report email, and is used in problem report listings and summaries; problem reports with obscure synopses tend to get ignored. As noted above, if your problem report includes a patch, please have the synopsis start with [patch]; if this is a ports PR and you are the maintainer, you may consider adding [maintainer update] and set the Class of your PR to maintainer-update. Severity: One of non-critical, serious or critical. Do not overreact; refrain from labeling your problem critical unless it really is (e.g. data corruption issues, serious regression from previous functionality in -CURRENT) or serious unless it is something that will affect many users (kernel panics or freezes; problems with particular device drivers or system utilities). &os; developers will not necessarily work on your problem faster if you inflate its importance since there are so many other people who have done exactly that — in fact, some developers pay little attention to this field because of this. Major security problems should not be filed in GNATS, because all GNATS information is public knowledge. Please send such problems in private email to &a.security-officer;. Priority: One of low, medium or high. high should be reserved for problems that will affect practically every user of &os; and medium for something that will affect many users. This field has become so widely abused that it is almost completely meaningless. Category: Choose an appropriate category. There are a number of "platform" categories into which bugs in the base system that are specific to one particular hardware architecture should be filed. Problems that are generic all across versions of &os; should probably be filed as kern or bin; see discussion of those categories below. Example: you have a common PC-based machine, and think you have encountered a problem specific to a particular chipset or a particular motherboard: i386 is the right category. Example: You are having a problem with an add-in peripheral card on a commonly seen bus, or a problem with a particular type of hard disk drive: in this case, it probably applies to more than one architecture, and kern is the right category. Here is the current list of categories (taken from ): advocacy: problems relating to &os;'s public image. Rarely used. alpha: problems specific to the Alpha platform. amd64: problems specific to the AMD64 platform. bin: problems with userland programs in the base system. If running &man.whereis.1; shows /bin, /usr/sbin, or something similar, then this is probably the right category. (A few contributed programs might instead need to be in gnu; see below.) conf: problems with configuration files, default values, and so forth. Things that affect /usr/share or /etc/rc* belong here. docs: problems with manual pages or on-line documentation. gnu: problems with imported GNU software such as &man.gcc.1; or &man.grep.1;. i386: problems specific to the &i386; platform. ia64: problems specific to the ia64 platform. java: problems related to the &java; Virtual Machine. (Ports that merely depend on &java; to run should be filed under ports.) kern: problems with the kernel, (non-platform-specific) device drivers, or the base libraries. misc: anything that does not fit in any of the other categories. (Note that there is almost nothing that truly belongs in this category, except for problems with the release and build infrastructure. Temporary build failures on HEAD do not belong here. Also note that it is easy for things to get lost in this category). ports: problems relating to the ports tree. powerpc: problems specific to the &powerpc; platform. sparc64: problems specific to the &sparc64; platform. standards: Standards conformance issues. threads: problems related to the &os; threads implementation (especially on &os.current;). usb: problems related to the &os; USB implementation. www: Changes or enhancements to the &os; website. Problems with code found in /usr/ports/www do not belong here, they belong in ports instead. Class: Choose one of the following: sw-bug: software bugs. doc-bug: errors in documentation. change-request: requests for additional features or changes in existing features. update: updates to ports or other contributed software. maintainer-update: updates to ports for which you are the maintainer. Release: The version of &os; that you are running. This is filled out automatically if you are using &man.send-pr.1; and need only be changed if you are sending a problem report from a different system than the one that exhibits the problem. Finally, there is a series of multi-line fields: Environment: This should describe, as accurately as possible, the environment in which the problem has been observed. This includes the operating system version, the version of the specific program or file that contains the problem, and any other relevant items such as system configuration, other installed software that influences the problem, etc.—quite simply everything a developer needs to know to reconstruct the environment in which the problem occurs. Description: A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. How-To-Repeat: A summary of the actions you need to take to reproduce the problem. Fix: Preferably a patch, or at least a workaround (which not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem), but if you do not have any firm ideas for either, it is better to leave this field blank than to speculate.
Sending off the problem report If you are using &man.send-pr.1;: Once you are done filling out the template, have saved it, and exit your editor, &man.send-pr.1; will prompt you with s)end, e)dit or a)bort?. You can then hit s to go ahead and submit the problem report, e to restart the editor and make further modifications, or a to abort. If you choose the latter, your problem report will remain on disk (&man.send-pr.1; will tell you the filename before it terminates), so you can edit it at your leisure, or maybe transfer it to a system with better net connectivity, before sending it with the to &man.send-pr.1;: &prompt.user; send-pr -f ~/my-problem-report This will read the specified file, validate the contents, strip comments and send it off. If you are using the web form: Before you hit submit, you will need to fill in a field containing text that is represented in image form on the page. This unfortunate measure has had to be adopted due to misuse by automated systems and a few misguided individuals. It is a necessary evil that no one likes; please do not ask us to remove it. Note that you are strongly advised to save your work somewhere before hitting submit. A common problem for users is to have their web browser displaying a stale image from its cache. If this happens to you, your submission will be rejected and you may lose your work. If you are unable to view images for any reason, and are also unable to use &man.send-pr.1;, please accept our apologies for the inconvenience and email your problem report to the bugbuster team at freebsd-bugbusters@FreeBSD.org.
Follow-up Once your problem report has been filed, you will receive a confirmation by email which will include the tracking number that was assigned to your problem report and a URL you can use to check its status. With a little luck, someone will take an interest in your problem and try to address it, or, as the case may be, explain why it is not a problem. You will be automatically notified of any change of status, and you will receive copies of any comments or patches someone may attach to your problem report's audit trail. If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please use one of two methods to submit your followup: The easiest way is to use the followup link on the individual PR's web page, which you can reach from the PR search page. Clicking on this link will bring up an an email window with the correct To: and Subject: lines filled in (if your browser is configured to do this). Alternatively, you can just mail it to &a.bugfollowup;, making sure that the tracking number is included in the subject so the bug tracking system will know what problem report to attach it to. If you do not include the tracking number, GNATS will become confused and create an entirely new PR which it then assigns to the GNATS administrator, and then your followup will become lost until someone comes in to clean up the mess, which could be days or weeks afterwards. Wrong way: Subject: that PR I sent Right way: Subject: Re: ports/12345: compilation problem with foo/bar If the problem report remains open after the problem has gone away, just send a follow-up (in the manner prescribed above) saying that the problem report can be closed, and, if possible, explaining how or when the problem was fixed.
If you are having problems Most PRs go through the system and are accepted quickly; however, at times GNATS runs behind and you may not get your email confirmation for 10 minutes or even longer. Please try to be patient. In addition, because GNATS receives all its input via email, it is absolutely vital that &os; runs all its submissions through spam filters. If you do not get a response within an hour or two, you may have fallen afoul of them; if so, please contact the GNATS administrators at bugmeister@FreeBSD.org and ask for help. Among the anti-spam measures is one that weighs against many common abuses seen HTML-based email (although not necessarily the mere inclusion of HTML in a PR). We strongly recommend against the use of HTML-based email when sending PRs: not only is it more likely to fall afoul of the filters, it also tends to merely clutter up the database. Plain old email is strongly preferred. On rare occasions you will encounter a GNATS bug where a PR is accepted and assigned a tracking number but it does not show up on the list of PRs on any of the web query pages. What may have happened is that the database index has gotten out of synchronization with the database itself. The way that you can test whether this has happened is to pull up the view a single PR page and see whether the PR shows up. If it does, please notify the GNATS administrators at bugmeister@FreeBSD.org. Note that there is a cron job that periodically rebuilds the database, so unless you are in a hurry, no action needs to be taken.
Further Reading This is a list of resources relevant to the proper writing and processing of problem reports. It is by no means complete. How to Report Bugs Effectively—an excellent essay by Simon G. Tatham on composing useful (non-&os;-specific) problem reports. Problem Report Handling Guidelines—valuable insight into how problem reports are handled by the &os; developers.
+ +
diff --git a/zh_TW.Big5/books/developers-handbook/Makefile b/zh_TW.Big5/books/developers-handbook/Makefile index 8fa12fe44a..81fed7b836 100644 --- a/zh_TW.Big5/books/developers-handbook/Makefile +++ b/zh_TW.Big5/books/developers-handbook/Makefile @@ -1,44 +1,42 @@ # # $FreeBSD$ # # Build the FreeBSD Developers' Handbook. # MAINTAINER=doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= # Images IMAGES_EN= sockets/layers.eps sockets/sain.eps sockets/sainfill.eps sockets/sainlsb.eps sockets/sainmsb.eps sockets/sainserv.eps sockets/serv.eps sockets/serv2.eps sockets/slayers.eps # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS= book.xml SRCS+= introduction/chapter.xml SRCS+= ipv6/chapter.xml SRCS+= kerneldebug/chapter.xml SRCS+= l10n/chapter.xml SRCS+= policies/chapter.xml SRCS+= secure/chapter.xml SRCS+= sockets/chapter.xml SRCS+= testing/chapter.xml SRCS+= tools/chapter.xml SRCS+= x86/chapter.xml # Entities URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_TW.Big5/books/developers-handbook/chapters.ent b/zh_TW.Big5/books/developers-handbook/chapters.ent index 9958b94e6b..7771b27862 100644 --- a/zh_TW.Big5/books/developers-handbook/chapters.ent +++ b/zh_TW.Big5/books/developers-handbook/chapters.ent @@ -1,38 +1,33 @@ - - - -]]> - +"> diff --git a/zh_TW.Big5/books/fdp-primer/book.xml b/zh_TW.Big5/books/fdp-primer/book.xml index 6f40f1e56a..fb25d55eb2 100644 --- a/zh_TW.Big5/books/fdp-primer/book.xml +++ b/zh_TW.Big5/books/fdp-primer/book.xml @@ -1,238 +1,236 @@ %chapters; ]> FreeBSD ¤å¥ó­pµe¤Jªù®Ñ FreeBSD ¤å¥ó­p¹º 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 DocEng $FreeBSD$ $FreeBSD$ &legalnotice; ·PÁ±z°Ñ»P FreeBSD ¤å¥ó­p¹º(²ºÙ¡GFDP, FreeBSD Documentation Project)¡A±zªºÂIºw°^Äm¡A³£¬Û·íÄ_¶Q¡C ¥»¤J¤â®Ñ¤º®e¥]¬A¡G¦p¦ó¶}©lµÛ¤â½Ķªº¦U¶µ²Ó¸`¡A¥H¤Î·|¥Î¨ìªº¤@¨Ç¦n¥Î¤u¨ã(¥]¬A¡G¥²³Æ¤u¨ã¡B»²§U¤u¨ã) ¡A¥H¤Î¤å¥ó­pµeªº©v¦®¡C ¥»¤å¥óÁÙ¦b¯ó½Z¡A©|¥¼§¹½Z¡C¥¼§¹¦¨ªº³¹¸`¡A§Ú­Ì·|¦b³¹¸`¦WºÙ®ÇÃä¥[µù¡y* ¡z¥H§@ÃѧO¡C §Ç¨¥ Shell ´£¥Ü²Å¸¹(Prompts) ¤UªíÅã¥Ü¥X¤@¯ë±b¸¹»P root ªº´£¥Ü²Å¸¹¡A¦b©Ò¦³ªº¤å¥ó¨Ò¤l¤¤·|¥Î´£¥Ü²Å¸¹(prompt) ¡A¨Ó´£¿ô±z¸Ó¥Î­þºØ±b¸¹¤~¹ï¡C ±b¸¹ ´£¥Ü²Å¸¹(Prompt) ´¶³q±b¸¹ &prompt.user; root &prompt.root; ®Ñ¤¤©Ò¥Îªº½s±Æ­·®æ ¤Uªí¬°¥»®Ñ¤¤©Ò¨Ï¥Î½s±Æ­·®æ¤è¦¡¡G ¥Nªí·N¸q Á|¨Ò «ü¥O ¨Ï¥Î ls -a ¨Ó¦C¥X©Ò¦³ªºÀɮסC ÀɦW ­×§ï .login ÀÉ¡C ¿Ã¹õ¤W·|¥X²{ªº°T®§ You have mail. ¿é¤J«ü¥O«á¡A¿Ã¹õ¤W·|¥X²{ªº¹ïÀ³¤º®e¡C &prompt.user; su Password: ­n°Ñ¦Òªº½u¤W¤â¥U(manual) ¥H su 1 ¨Ó¤Á´«±b¸¹¡C ¦bÁ¿¨ì±b¸¹(user)¡B¸s²Õ(group)ªº¦WºÙªº®É­Ô... ¥u¦³ root ¤~¥i¥H°µ³o¥ó¨Æ¡C »y®ðªº±j½Õ §A¡y¥²¶·¡z³o»ò°µ¤~¦æ¡C ¥´«ü¥O®É¡A¥i´À´«ªº³¡¥÷ ­n§R°£Àɮתº¸Ü¡A½Ð¥´ rm ­n§R°£ªºÀɦW Àô¹ÒÅܼƳ]©w $HOME ¬O«ü±b¸¹ªº®a¥Ø¿ý©Ò¦b³B¡C ¡yNote¡BTip¡BImportant¡BWarning¡BExample¡zªº¹B¥Î ¥H¤U¤å¦r¬O¡yª`·N¡z¡B¡y§Þ¥©¡z¡B¡y­«­n°T®§¡z¡B¡yĵ§i¡z¡B¡y½d¨Ò¡zªº¹B¥Î¡C ªí¥Ü»Ý­nª`·Nªº¨Æ¶µ¡A¨ä¤¤¥]¬A±z»Ý­nª`·Nªº¨Æ±¡¡A¦]¬°³o¨Ç¨Æ±¡¥i¯à·|¼vÅT¨ì¾Þ§@µ²ªG¡C ´£¨Ñ¥i¯à¹ï±z¦³¥Î©Î²¤Æ¾Þ§@¤è¦¡ªº§Þ¥©»¡©ú¡C ªí¥Ü­n¯S§Oª`·Nªº¨Æ±¡¡C¤@¯ë¨Ó»¡¡A¥¦­Ì·|¥]¬A¾Þ§@«ü¥O®É»Ý­n¥[ªºÃB¥~°Ñ¼Æ¡C ªí¥Üĵ§i¨Æ¶µ¡A¤ñ¦p¦pªG±z¤£ª`·N«h¥i¯à¾É­Pªº·l¥¢¡C³o¨Ç·l¥¢¥i¯à¬O¹ï±z©ÎµwÅé³y¦¨¹ê»Ú¶Ë®`¡A ¤]¥i¯à¬OµLªk¦ô­pªº·l®`¡A¨Ò¦p¤@®É²¨©¿¦Ó§R°£­«­nÀÉ®×...¡C ³o¬OÁ|¨Ò»¡©ú ³o¬OÁ|¨Ò»¡©ú¦Ó¤w¡A³q±`¥]§tÀ³¿í´`ªº«ü¥O½d¨Ò¡A©ÎÅã¥Ü¬Y¨Ç¯S©w°Ê§@©Ò¥i¯àµo¥Íªºµ²ªG¡C ·PÁ ¦b¦¹­n·PÁ Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn, Christopher Maden ³o¨Ç¤Hªº¨ó§U»P¾\Ūªì´Á¯ó½Z¡A¨Ã´£¨Ñ³\¦hÄ_¶Qªº¼í½Z·N¨£»Pµû½×¡C &chap.overview; &chap.tools; &chap.xml-primer; &chap.xml-markup; &chap.stylesheets; &chap.structure; &chap.doc-build; &chap.the-website; &chap.translations; &chap.writing-style; &chap.psgml-mode; &chap.see-also; &app.examples; - diff --git a/zh_TW.Big5/books/handbook/Makefile b/zh_TW.Big5/books/handbook/Makefile index a86b5c2c8f..37593e0104 100644 --- a/zh_TW.Big5/books/handbook/Makefile +++ b/zh_TW.Big5/books/handbook/Makefile @@ -1,301 +1,299 @@ # # $FreeBSD$ # Original revision: 1.108 # # Build the FreeBSD Handbook. # # ------------------------------------------------------------------------ # # Handbook-specific variables # # WITH_PGPKEYS The print version of the handbook only prints PGP # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. # # Handbook-specific targets # # pgpkeyring This target will read the contents of # pgpkeys/chapter.xml and will extract all of # the pgpkeys to standard out. This output can then # be redirected into a file and distributed as a # public keyring of FreeBSD developers that can # easily be imported into PGP/GPG. # # ------------------------------------------------------------------------ .PATH: ${.CURDIR}/../../share/xml/glossary MAINTAINER= doc@FreeBSD.org DOC?= book FORMATS?= html-split -HAS_INDEX= true - INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= IMAGES_EN = advanced-networking/isdn-bus.eps IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= geom/striping.pic IMAGES_EN+= install/adduser1.scr IMAGES_EN+= install/adduser2.scr IMAGES_EN+= install/adduser3.scr IMAGES_EN+= install/boot-loader-menu.scr IMAGES_EN+= install/boot-mgr.scr IMAGES_EN+= install/config-country.scr IMAGES_EN+= install/console-saver1.scr IMAGES_EN+= install/console-saver2.scr IMAGES_EN+= install/console-saver3.scr IMAGES_EN+= install/console-saver4.scr IMAGES_EN+= install/disklabel-auto.scr IMAGES_EN+= install/disklabel-ed1.scr IMAGES_EN+= install/disklabel-ed2.scr IMAGES_EN+= install/disklabel-fs.scr IMAGES_EN+= install/disklabel-root1.scr IMAGES_EN+= install/disklabel-root2.scr IMAGES_EN+= install/disklabel-root3.scr IMAGES_EN+= install/disk-layout.eps IMAGES_EN+= install/dist-set.scr IMAGES_EN+= install/dist-set2.scr IMAGES_EN+= install/docmenu1.scr IMAGES_EN+= install/ed0-conf.scr IMAGES_EN+= install/ed0-conf2.scr IMAGES_EN+= install/edit-inetd-conf.scr IMAGES_EN+= install/fdisk-drive1.scr IMAGES_EN+= install/fdisk-drive2.scr IMAGES_EN+= install/fdisk-edit1.scr IMAGES_EN+= install/fdisk-edit2.scr IMAGES_EN+= install/ftp-anon1.scr IMAGES_EN+= install/ftp-anon2.scr IMAGES_EN+= install/hdwrconf.scr IMAGES_EN+= install/keymap.scr IMAGES_EN+= install/main1.scr IMAGES_EN+= install/mainexit.scr IMAGES_EN+= install/main-std.scr IMAGES_EN+= install/main-options.scr IMAGES_EN+= install/main-doc.scr IMAGES_EN+= install/main-keymap.scr IMAGES_EN+= install/media.scr IMAGES_EN+= install/mouse1.scr IMAGES_EN+= install/mouse2.scr IMAGES_EN+= install/mouse3.scr IMAGES_EN+= install/mouse4.scr IMAGES_EN+= install/mouse5.scr IMAGES_EN+= install/mouse6.scr IMAGES_EN+= install/mta-main.scr IMAGES_EN+= install/net-config-menu1.scr IMAGES_EN+= install/net-config-menu2.scr IMAGES_EN+= install/nfs-server-edit.scr IMAGES_EN+= install/ntp-config.scr IMAGES_EN+= install/options.scr IMAGES_EN+= install/pkg-cat.scr IMAGES_EN+= install/pkg-confirm.scr IMAGES_EN+= install/pkg-install.scr IMAGES_EN+= install/pkg-sel.scr IMAGES_EN+= install/probstart.scr IMAGES_EN+= install/routed.scr IMAGES_EN+= install/security.scr IMAGES_EN+= install/sysinstall-exit.scr IMAGES_EN+= install/timezone1.scr IMAGES_EN+= install/timezone2.scr IMAGES_EN+= install/timezone3.scr IMAGES_EN+= install/userconfig.scr IMAGES_EN+= install/userconfig2.scr IMAGES_EN+= mail/mutt1.scr IMAGES_EN+= mail/mutt2.scr IMAGES_EN+= mail/mutt3.scr IMAGES_EN+= mail/pine1.scr IMAGES_EN+= mail/pine2.scr IMAGES_EN+= mail/pine3.scr IMAGES_EN+= mail/pine4.scr IMAGES_EN+= mail/pine5.scr IMAGES_EN+= install/example-dir1.eps IMAGES_EN+= install/example-dir2.eps IMAGES_EN+= install/example-dir3.eps IMAGES_EN+= install/example-dir4.eps IMAGES_EN+= install/example-dir5.eps IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic IMAGES_EN+= vinum/vinum-concat.pic IMAGES_EN+= vinum/vinum-mirrored-vol.pic IMAGES_EN+= vinum/vinum-raid10-vol.pic IMAGES_EN+= vinum/vinum-raid5-org.pic IMAGES_EN+= vinum/vinum-simple-vol.pic IMAGES_EN+= vinum/vinum-striped-vol.pic IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png IMAGES_EN+= virtualization/parallels-freebsd4.png IMAGES_EN+= virtualization/parallels-freebsd5.png IMAGES_EN+= virtualization/parallels-freebsd6.png IMAGES_EN+= virtualization/parallels-freebsd7.png IMAGES_EN+= virtualization/parallels-freebsd8.png IMAGES_EN+= virtualization/parallels-freebsd9.png IMAGES_EN+= virtualization/parallels-freebsd10.png IMAGES_EN+= virtualization/parallels-freebsd11.png IMAGES_EN+= virtualization/parallels-freebsd12.png IMAGES_EN+= virtualization/parallels-freebsd13.png IMAGES_EN+= virtualization/virtualpc-freebsd1.png IMAGES_EN+= virtualization/virtualpc-freebsd2.png IMAGES_EN+= virtualization/virtualpc-freebsd3.png IMAGES_EN+= virtualization/virtualpc-freebsd4.png IMAGES_EN+= virtualization/virtualpc-freebsd5.png IMAGES_EN+= virtualization/virtualpc-freebsd6.png IMAGES_EN+= virtualization/virtualpc-freebsd7.png IMAGES_EN+= virtualization/virtualpc-freebsd8.png IMAGES_EN+= virtualization/virtualpc-freebsd9.png IMAGES_EN+= virtualization/virtualpc-freebsd10.png IMAGES_EN+= virtualization/virtualpc-freebsd11.png IMAGES_EN+= virtualization/virtualpc-freebsd12.png IMAGES_EN+= virtualization/virtualpc-freebsd13.png IMAGES_EN+= virtualization/vmware-freebsd01.png IMAGES_EN+= virtualization/vmware-freebsd02.png IMAGES_EN+= virtualization/vmware-freebsd03.png IMAGES_EN+= virtualization/vmware-freebsd04.png IMAGES_EN+= virtualization/vmware-freebsd05.png IMAGES_EN+= virtualization/vmware-freebsd06.png IMAGES_EN+= virtualization/vmware-freebsd07.png IMAGES_EN+= virtualization/vmware-freebsd08.png IMAGES_EN+= virtualization/vmware-freebsd09.png IMAGES_EN+= virtualization/vmware-freebsd10.png IMAGES_EN+= virtualization/vmware-freebsd11.png IMAGES_EN+= virtualization/vmware-freebsd12.png # Images from the cross-document image library IMAGES_LIB= callouts/1.png IMAGES_LIB+= callouts/2.png IMAGES_LIB+= callouts/3.png IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png IMAGES_LIB+= callouts/6.png IMAGES_LIB+= callouts/7.png IMAGES_LIB+= callouts/8.png IMAGES_LIB+= callouts/9.png IMAGES_LIB+= callouts/10.png IMAGES_LIB+= callouts/11.png IMAGES_LIB+= callouts/12.png IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png # # SRCS lists the individual XML files that make up the document. Changes # to any of these files will force a rebuild # # XML content SRCS+= audit/chapter.xml SRCS+= book.xml SRCS+= colophon.xml SRCS+= advanced-networking/chapter.xml SRCS+= basics/chapter.xml SRCS+= bibliography/chapter.xml SRCS+= boot/chapter.xml SRCS+= config/chapter.xml SRCS+= cutting-edge/chapter.xml SRCS+= desktop/chapter.xml SRCS+= disks/chapter.xml SRCS+= eresources/chapter.xml SRCS+= firewalls/chapter.xml SRCS+= geom/chapter.xml SRCS+= install/chapter.xml SRCS+= introduction/chapter.xml SRCS+= jails/chapter.xml SRCS+= kernelconfig/chapter.xml SRCS+= l10n/chapter.xml SRCS+= linuxemu/chapter.xml SRCS+= mac/chapter.xml SRCS+= mail/chapter.xml SRCS+= mirrors/chapter.xml SRCS+= multimedia/chapter.xml SRCS+= network-servers/chapter.xml SRCS+= pgpkeys/chapter.xml SRCS+= ports/chapter.xml SRCS+= ppp-and-slip/chapter.xml SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml SRCS+= users/chapter.xml SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml # Entities SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html # Turn on all the chapters. CHAPTERS?= ${SRCS:M*chapter.xml} XMLFLAGS+= ${CHAPTERS:S/\/chapter.xml//:S/^/-i chap./} XMLFLAGS+= -i chap.freebsd-glossary pgpkeyring: pgpkeys/chapter.xml @${JADE} -V nochunks ${OTHERFLAGS} ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC} # # Handbook-specific variables # .if defined(WITH_PGPKEYS) JADEFLAGS+= -V withpgpkeys .endif URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. # # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ mirrors-cvsup:::mirrors.xml.cvsup.inc \ eresources-index:::eresources.xml.www.index.inc \ eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} PARAMS.lastmod+= --param 'target' "'lastmod'" PARAMS.mirrors-ftp-index+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'index'" PARAMS.mirrors-ftp+= --param 'type' "'ftp'" \ --param 'proto' "'ftp'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.mirrors-cvsup-index+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'index'" PARAMS.mirrors-cvsup+= --param 'type' "'cvsup'" \ --param 'proto' "'cvsup'" \ --param 'target' "'handbook/mirrors/chapter.xml'" PARAMS.eresources-index+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'index'" PARAMS.eresources+= --param 'type' "'www'" \ --param 'proto' "'http'" \ --param 'target' "'handbook/eresources/chapter.xml'" SRCS+= mirrors.lastmod.inc \ mirrors.xml.ftp.inc \ mirrors.xml.ftp.index.inc \ mirrors.xml.cvsup.inc \ mirrors.xml.cvsup.index.inc \ eresources.xml.www.inc \ eresources.xml.www.index.inc .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_TW.Big5/books/handbook/chapters.ent b/zh_TW.Big5/books/handbook/chapters.ent index dfe7f04d24..dea4e0b760 100644 --- a/zh_TW.Big5/books/handbook/chapters.ent +++ b/zh_TW.Big5/books/handbook/chapters.ent @@ -1,71 +1,71 @@ %pgpkeys; - + ">