- Strip unnecessary trailing spaces
Approved by: doceng (implicit)
This commit is contained in:
parent
b2153405c5
commit
2e51ec7022
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/projects/sgml2xml/; revision=39416
1363 changed files with 63242 additions and 63242 deletions
da_DK.ISO8859-1
de_DE.ISO8859-1
articles
books
developers-handbook
handbook
htdocs
share/sgml
el_GR.ISO8859-7
articles
compiz-fusion
dialup-firewall
formatting-media
gjournal-desktop
laptop
new-users
books
faq
handbook
Makefile
advanced-networking
cutting-edge
disks
eresources
kernelconfig
linuxemu
mac
multimedia
network-servers
security
htdocs/doc
share/sgml
en_US.ISO8859-1/articles
5-roadmap
Makefile.incbsdl-gpl
casestudy-argentina.com
committers-guide
compiz-fusion
console-server
contributing
contributors
custom-gcc
cvsup-advanced
dialup-firewall
diskless-x
euro
explaining-bsd
fonts
formatting-media
freebsd-questions
geom-class
gjournal-desktop
hubs
laptop
ldap-auth
linux-comparison
linux-emulation
linux-users
mailing-list-faq
mh
nanobsd
new-users
p4-primer
portbuild
problem-reports
rc-scripting
relaydelay
releng-packages
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
-- ...................................................................... --
|
||||
-- FreeBSD SGML Public Identifiers ...................................... --
|
||||
|
||||
|
||||
-- $FreeBSD$
|
||||
--
|
||||
|
||||
|
|
|
@ -1,22 +1,22 @@
|
|||
<!--
|
||||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
The FreeBSD Danish Documentation Project
|
||||
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<para>DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS
|
||||
PROJEKTET "SOM DET ER" OG UDEN NOGLE UDTRYKTE ELLER ANTYDEDE
|
||||
GARANTIER, INKLUDERENDE MEN IKKE BEGRÆNSET TIL: ANTYDEDE GARANTIER
|
||||
FOR SALGBARHED OG EGNETHED FOR ET SPECIFIKT FORMÅL. UNDER INGEN
|
||||
<para>DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS
|
||||
PROJEKTET "SOM DET ER" OG UDEN NOGLE UDTRYKTE ELLER ANTYDEDE
|
||||
GARANTIER, INKLUDERENDE MEN IKKE BEGRÆNSET TIL: ANTYDEDE GARANTIER
|
||||
FOR SALGBARHED OG EGNETHED FOR ET SPECIFIKT FORMÅL. UNDER INGEN
|
||||
OMSTÆNDIGHEDER SKAL FREEBSD DOKUMENTATIONS PROJEKTET VÆRE
|
||||
HÆFTENDE, FOR NOGLE DIREKTE, INDIREKTE, TILFÆLDIGE,
|
||||
SPECIELLE, EKSEMPLARISKE, ELLER FØLGENDE SKADER (INKLUDERENDE,
|
||||
MEN IKKE BEGRÆNSET TIL:
|
||||
FREMSKAFFELSE AF ERSTATNINGS VARER ELLER SERVICEYELSER; TAB AF
|
||||
BRUGBARHED, DATA, ELLER UDBYTTE; ELLER AFBRYDELSE AF FORRETNING)
|
||||
HVORDAN END DEN ER OPSTÅET OG UNDER EN HVILKEN SOM HELST TEORI
|
||||
OM ANSVARLIGHED, HVAD ENTEN DET ER I KONTRAKT, STRIKS ANSVARLIGHED
|
||||
MEN IKKE BEGRÆNSET TIL:
|
||||
FREMSKAFFELSE AF ERSTATNINGS VARER ELLER SERVICEYELSER; TAB AF
|
||||
BRUGBARHED, DATA, ELLER UDBYTTE; ELLER AFBRYDELSE AF FORRETNING)
|
||||
HVORDAN END DEN ER OPSTÅET OG UNDER EN HVILKEN SOM HELST TEORI
|
||||
OM ANSVARLIGHED, HVAD ENTEN DET ER I KONTRAKT, STRIKS ANSVARLIGHED
|
||||
ELLER TORT (INKLUDERENDE FORSØMMELIGHED ELLER PÅ ANDEN VIS)
|
||||
OPSTÅENDE PÅ NOGEN MÅDE UD AF BRUGEN AF DENNE
|
||||
DOKUMENTATION, SELV HVIS GJORT OPMÆRKSOM PÅ MULIGHEDEN FOR
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
|
||||
<!ENTITY freebsd.dsl PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" CDATA DSSSL>
|
||||
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.print "IGNORE">
|
||||
]>
|
||||
|
||||
|
@ -11,8 +11,8 @@
|
|||
<style-specification use="docbook">
|
||||
<style-specification-body>
|
||||
<!-- HTML only .................................................... -->
|
||||
|
||||
<![ %output.html; [
|
||||
|
||||
<![ %output.html; [
|
||||
|
||||
(define ($email-footer$)
|
||||
(make sequence
|
||||
|
@ -26,7 +26,7 @@
|
|||
(literal ".")))
|
||||
(make element gi: "p"
|
||||
attributes: (list (list "align" "center"))
|
||||
(make element gi: "small"
|
||||
(make element gi: "small"
|
||||
(literal "For spørgsmål om FreeBSD, læs ")
|
||||
(create-link
|
||||
(list (list "HREF" "http://www.FreeBSD.org/docs.html"))
|
||||
|
|
|
@ -648,7 +648,7 @@
|
|||
zu antworten, selbst wenn Sie nur mitteilen können,
|
||||
dass Sie noch etwas Zeit brauchen, bevor Sie den PR
|
||||
bearbeiten können.</para>
|
||||
|
||||
|
||||
<para>Sollten Sie nicht innerhalb von 14 Tagen geantwortet haben,
|
||||
darf jeder Committer via <literal>maintainer-timeout</literal>
|
||||
auf einen PR, den Sie nicht beantwortet haben, reagieren.</para>
|
||||
|
|
|
@ -187,7 +187,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>Stellen Sie sicher, dass der Code in
|
||||
<filename class="directory">src/contrib</filename> aktuell
|
||||
<filename class="directory">src/contrib</filename> aktuell
|
||||
ist.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -205,10 +205,10 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Wenn Sie einen Port beigetragen und dabei irgendwelche
|
||||
&os;-spezifischen Änderungen getätigt haben, senden Sie
|
||||
<para>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
|
||||
einfacher machen, wenn die nächste Version des Ports
|
||||
erscheint).</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
#
|
||||
# The FreeBSD Documentation Project
|
||||
# The FreeBSD German Documentation Project
|
||||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
# $FreeBSDde: de-docproj/articles/solid-state/Makefile,v 1.2 2011/12/31 12:33:27 bcr Exp $
|
||||
# basiert auf: 1.5
|
||||
|
|
|
@ -34,14 +34,14 @@
|
|||
<year>2007</year>
|
||||
<year>2008</year>
|
||||
<year>2009</year>
|
||||
<year>2010</year>
|
||||
<year>2010</year>
|
||||
<holder>The FreeBSD Documentation Project</holder>
|
||||
</copyright>
|
||||
|
||||
<copyright>
|
||||
<year>2008</year>
|
||||
<year>2009</year>
|
||||
<year>2010</year>
|
||||
<year>2010</year>
|
||||
<holder>The FreeBSD German Documentation Project</holder>
|
||||
</copyright>
|
||||
|
||||
|
|
|
@ -78,10 +78,10 @@
|
|||
den gesamten Inhalt des physischen Speichers beinhalten, Miniauszüge
|
||||
(minidumps), die nur die gerade verwendeten Speicherseiten des Kernels
|
||||
enthalten (&os; 6.2 und höhere Versionen) und Textauszüge
|
||||
(textdumps), welche geskriptete oder Debugger-Ausgaben enthalten
|
||||
(textdumps), welche geskriptete oder Debugger-Ausgaben enthalten
|
||||
(&os; 7.1 und höher). Miniauszüge sind der Standardtyp
|
||||
der Abzüge seit &os; 7.0 und fangen in den meisten Fällen
|
||||
alle nötigen Informationen ein, die in einem kompletten
|
||||
alle nötigen Informationen ein, die in einem kompletten
|
||||
Kernel-Speicherabzug enthalten sind, da die meisten Probleme nur durch
|
||||
den Zustand des Kernels isoliert werden können.</para>
|
||||
|
||||
|
@ -570,7 +570,7 @@
|
|||
Befehl ab:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sysctl debug.kdb.enter=1</userinput></screen>
|
||||
|
||||
|
||||
<note>
|
||||
<para>Um eine schnelle Panic zu erzwingen, geben Sie das folgende
|
||||
Kommando ein:</para>
|
||||
|
|
|
@ -40,7 +40,7 @@
|
|||
<sect1 id="policies-style">
|
||||
<title>Stil-Richtlinien</title>
|
||||
<indexterm><primary>style</primary></indexterm>
|
||||
|
||||
|
||||
<para>Ein konsistenter Code-Stil ist extrem wichtig, besonders
|
||||
in einem so grossen Projekt wie &os;. Der Code sollte dem
|
||||
&os; Code-Stil entsprechen, welcher in &man.style.9; und
|
||||
|
@ -51,7 +51,7 @@
|
|||
<title><makevar>MAINTAINER</makevar> eines Makefiles</title>
|
||||
<indexterm><primary>Ports-Maintainer</primary></indexterm>
|
||||
|
||||
<para>Wenn ein bestimmter Bereich der &os;
|
||||
<para>Wenn ein bestimmter Bereich der &os;
|
||||
<filename>src/</filename>-Distribution von einer Person oder Gruppe
|
||||
gepflegt wird, kann dies durch einen Eintrag in die Datei
|
||||
<filename>src/MAINTAINERS</filename> der Öffentlichkeit
|
||||
|
@ -59,7 +59,7 @@
|
|||
können ihre Verantwortung über den Port durch einen Eintrag in
|
||||
die <makevar>MAINTAINER</makevar>-Zeile im <filename>Makefile</filename>
|
||||
des Ports der Welt mitteilen.</para>
|
||||
|
||||
|
||||
<programlisting><makevar>MAINTAINER</makevar>= <replaceable>email-addresses</replaceable></programlisting>
|
||||
|
||||
<tip>
|
||||
|
@ -68,10 +68,10 @@
|
|||
sind, wer der Maintainer ist, sehen Sie sich die Commit-Historie des
|
||||
betreffenden Ports an. Es ist recht häufig der Fall, dass ein
|
||||
Maintainer nicht explizit aufgeführt ist, aber trotzdem diejenigen
|
||||
Personen, die den Port seit den letzten paar Jahren aktiv betreuen,
|
||||
Personen, die den Port seit den letzten paar Jahren aktiv betreuen,
|
||||
daran interessiert sind, Änderungen zu begutachten. Selbst wenn
|
||||
dies nicht explizit in der Dokumentation oder im Quellcode erwähnt
|
||||
ist, wird es trotzdem als höfliche Geste angesehen, wenn man
|
||||
ist, wird es trotzdem als höfliche Geste angesehen, wenn man
|
||||
nach einer Überprüfung der eigenen Änderungen
|
||||
fragt.</para>
|
||||
</tip>
|
||||
|
@ -123,7 +123,7 @@
|
|||
<author>
|
||||
<firstname>Gavin</firstname>
|
||||
<surname>Atkinson</surname>
|
||||
</author>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<!-- June 1996 -->
|
||||
</sect1info>
|
||||
|
@ -142,7 +142,7 @@
|
|||
|
||||
<para>Über die Jahre wurden verschiedene Methoden genutzt,
|
||||
um solche Software zu verwalten, und jede hat Vor-
|
||||
wie auch Nachteile. So hat sich kein eindeutiger Gewinner
|
||||
wie auch Nachteile. So hat sich kein eindeutiger Gewinner
|
||||
herauskristallisiert.</para>
|
||||
|
||||
<para>Es wurde viel über diesen Umstand diskutiert und
|
||||
|
@ -155,7 +155,7 @@
|
|||
einfach Diffs bezüglich der
|
||||
<quote>offiziellen</quote> Quelltext-Versionen erzeugen kann
|
||||
(auch ohne direkten Repository-Zugang). Dies wird es deutlich
|
||||
vereinfachen, Änderungen an die Hauptentwickler
|
||||
vereinfachen, Änderungen an die Hauptentwickler
|
||||
zurückfließen zu lassen.</para>
|
||||
|
||||
<para>Letztendlich kommt es jedoch auf die Menschen an, welche die
|
||||
|
@ -181,7 +181,7 @@
|
|||
</note>
|
||||
|
||||
<sect2 id="vendor-imports-cvs">
|
||||
|
||||
|
||||
<title>Herstellerimports mit CVS</title>
|
||||
|
||||
<para>Das <application>file</application>-Werkzeug soll als Beispiel
|
||||
|
@ -276,19 +276,19 @@
|
|||
<para>Ein Beispielinhalt von
|
||||
<filename>src/contrib/groff/FREEBSD-upgrade</filename> ist hier
|
||||
aufgelistet:</para>
|
||||
|
||||
|
||||
<programlisting>$FreeBSD: src/contrib/groff/FREEBSD-upgrade,v 1.5.12.1 2005/11/15 22:06:18 ru Exp $
|
||||
|
||||
This directory contains virgin sources of the original distribution files
|
||||
on a "vendor" branch. Do not, under any circumstances, attempt to upgrade
|
||||
the files in this directory via patches and a cvs commit.
|
||||
the files in this directory via patches and a cvs commit.
|
||||
|
||||
To upgrade to a newer version of groff, when it is available:
|
||||
1. Unpack the new version into an empty directory.
|
||||
[Do not make ANY changes to the files.]
|
||||
|
||||
2. Use the command:
|
||||
cvs import -m 'Virgin import of FSF groff v<version>' \
|
||||
cvs import -m 'Virgin import of FSF groff v<version>' \
|
||||
src/contrib/groff FSF v<version>
|
||||
|
||||
For example, to do the import of version 1.19.2, I typed:
|
||||
|
@ -340,7 +340,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
Import hinzufügen.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="vendor-import-svn">
|
||||
<sect2info>
|
||||
<authorgroup>
|
||||
|
@ -351,7 +351,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
</author>
|
||||
</authorgroup>
|
||||
</sect2info>
|
||||
|
||||
|
||||
<title>Herstellerimports mit SVN</title>
|
||||
|
||||
<para>Dieser Abschnitt beschreibt die Prozedur für Herstellerimports
|
||||
|
@ -360,18 +360,18 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
<procedure>
|
||||
<step>
|
||||
<title>Vorbereiten des Quellbaums</title>
|
||||
|
||||
|
||||
<para>Wenn dies Ihr erster Import nach dem Wechsel zu
|
||||
<acronym>SVN</acronym> ist, sollen Sie den Herstellerbaum
|
||||
aufräumen, verflachen und die Merge-Historie in den Hauptzweig
|
||||
vorbereiten. Falls das nicht Ihr erster Import ist, können
|
||||
Sie diesen Schritt ohne Probleme überspringen.</para>
|
||||
|
||||
|
||||
<para>Während der Konvertierung von <acronym>CVS</acronym> zu
|
||||
<acronym>SVN</acronym> wurden Herstellerzweige mit der gleichen
|
||||
Struktur wie der Hauptzweig importiert. Beispielsweise wurden die
|
||||
<application>foo</application> Herstellerquellen in
|
||||
<filename>vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename>
|
||||
<filename>vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename>
|
||||
abgelegt, jedoch ist dies unpraktisch und zwecklos. Was wir wirklich
|
||||
wollen, ist dass die Herstellerquellen direkt in
|
||||
<filename>vendor/<replaceable>foo</replaceable>/dist</filename>
|
||||
|
@ -424,20 +424,20 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
|
||||
<step>
|
||||
<title>Neue Quellen importieren</title>
|
||||
|
||||
|
||||
<para>Bereiten Sie einen kompletten, sauberen Baum mit
|
||||
Herstellerquellen vor. Mit <acronym>SVN</acronym> können wir
|
||||
eine komplette Distribution in dem Herstellerzweig aufbewahren, ohne
|
||||
den Hauptzweig aufzublähen. Importieren Sie alles, aber mergen
|
||||
Sie nur das, was wirklich benötigt wird.</para>
|
||||
|
||||
|
||||
<para>Beachten Sie, dass Sie alle Dateien, die seit dem letzten
|
||||
Herstellerimport hinzugefügt wurden, auch einbeziehen und
|
||||
diejenigen, welche entfernt wurden, auch löschen
|
||||
müssen. Um dies zu bewerkstelligen, sollten Sie sortierte
|
||||
Listen der Bestandteile des Herstellerbaums und von den Quellen,
|
||||
Sie die vorhaben zu importieren, vorbereiten:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>cd</command> <filename>vendor/<replaceable>foo</replaceable>/dist</filename></userinput>
|
||||
&prompt.user; <userinput><command>svn list</command> <option>-R</option> | <command>grep</command> <option>-v</option> '/$' | <command>sort</command> > <filename>../<replaceable>old</replaceable></filename></userinput>
|
||||
&prompt.user; <userinput><command>cd</command> <filename>../<replaceable>foo-9.9</replaceable></filename></userinput>
|
||||
|
@ -446,17 +446,17 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
<para>Mit diesen beiden Dateien, wird Ihnen das folgende Kommando alle
|
||||
Dateien auflisten, die entfernt wurden (nur die Dateien in
|
||||
<filename><replaceable>old</replaceable></filename>):</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>comm <option>-23</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
|
||||
|
||||
|
||||
<para>Der folgende Befehl wird die hinzugefügten Dateien auflisten
|
||||
(nur diejenigen Dateien in
|
||||
<filename><replaceable>new</replaceable></filename>):</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>comm <option>-13</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
|
||||
|
||||
|
||||
<para>Wir führen dies nun zusammen:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">vendor/<replaceable>foo</replaceable>/<replaceable>foo-9.9</replaceable></filename></userinput>
|
||||
&prompt.user; <userinput><command>tar</command> cf - <filename>.</filename> | <command>tar</command> xf - <option>-C</option> <filename>../dist</filename></userinput>
|
||||
&prompt.user; <userinput><command>cd</command> <filename class="directory">../dist</filename></userinput>
|
||||
|
@ -472,26 +472,26 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
</warning>
|
||||
|
||||
<para>Prüfen Sie die Eigenschaften jeder neuen Datei:</para>
|
||||
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Alle Textdateien sollten <literal>svn:eol-style</literal> auf
|
||||
den Wert <literal>native</literal> gesetzt haben.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Alle Binärdateien sollten
|
||||
<literal>svn:mime-type</literal> auf
|
||||
<literal>application/octet-stream</literal> gesetzt haben,
|
||||
ausser es existiert ein passenderer Medientyp.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Ausführbare Dateien sollten
|
||||
<literal>svn:executable</literal> auf <literal>*</literal>
|
||||
gesetzt haben.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Es sollten keine anderen Eigenschaften auf den Dateien im
|
||||
Baum gesetzt sein.</para>
|
||||
|
@ -507,7 +507,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
|
||||
<para>Sobald Sie den die neue Release-Version des Herstellers
|
||||
committed haben, sollten Sie Ihn für zukünftige Referenzen
|
||||
taggen. Die beste und schnellste Methode ist, dies direkt im
|
||||
taggen. Die beste und schnellste Methode ist, dies direkt im
|
||||
Repository zu tun:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput><command>svn copy</command> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/<replaceable>9.9</replaceable></filename></userinput></screen>
|
||||
|
@ -523,16 +523,16 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
entfernen.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
||||
|
||||
<step>
|
||||
<title>Mit <emphasis>-HEAD</emphasis> mergen</title>
|
||||
|
||||
|
||||
<para>Nachdem Sie Ihren Import vorbereitet haben, wird es Zeit zu
|
||||
mergen. Die Option <option>--accept=postpone</option> weist
|
||||
<acronym>SVN</acronym> an, noch keine merge-Konflikte
|
||||
aufzulösen, weil wir uns um diese manuell kümmern
|
||||
werden:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">head/contrib/<replaceable>foo</replaceable></filename></userinput>
|
||||
&prompt.user; <userinput><command>svn update</command></userinput>
|
||||
&prompt.user; <userinput><command>svn merge</command> <option>--accept=postpone</option> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename></userinput></screen>
|
||||
|
@ -542,13 +542,13 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
wurden, auch sauber im Hauptzweig hinzugefügt bzw. gelöscht
|
||||
wurden. Es ist immer ratsam, diese Unterschiede gegen den
|
||||
Herstellerbaum zu prüfen:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput><command>svn diff</command> <option>--no-diff-deleted</option> <option>--old=</option><filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <option>--new=</option><filename>.</filename></userinput></screen>
|
||||
|
||||
|
||||
<para>Die Option <option>--no-diff-deleted</option> weist
|
||||
<acronym>SVN</acronym> an, keine Dateien zu prüfen, die sich
|
||||
zwar im Herstellerbaum, aber nicht im Hauptzweig befinden.</para>
|
||||
|
||||
|
||||
<note>
|
||||
<para>Bei <acronym>SVN</acronym> gibt es das Konzept von innerhalb
|
||||
und ausserhalb des Herstellerbaums nicht. Wenn eine Datei, die
|
||||
|
@ -557,7 +557,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
Versionstags, damit diese nicht länger in den diffs gegen
|
||||
den Herstellerbaum erscheinen.</para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>Wenn irgendwelche Änderungen notwendig sind, um die Welt
|
||||
mit den neuen Quellen zu bauen, machen Sie diese jetzt und testen
|
||||
Sie diese bis Sie sicher sind, dass alles korrekt gebaut wird und
|
||||
|
@ -566,7 +566,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
|
|||
|
||||
<step>
|
||||
<title>Commit</title>
|
||||
|
||||
|
||||
<para>Nun sind Sie bereit für den Commit. Stellen Sie sicher,
|
||||
dass Sie alles in einem einzigen Schritt durchführen.
|
||||
Idealerweise sollten Sie alle diese Schritte in einem sauberen Baum
|
||||
|
|
|
@ -75,7 +75,7 @@
|
|||
<indexterm><primary>Morris Internetwurm</primary></indexterm>
|
||||
|
||||
funktioniert der gleiche grundlegende Angriff noch heute. Die bei weitem
|
||||
häufigste Form eines Puffer-Überlauf-Angriffs basiert darauf,
|
||||
häufigste Form eines Puffer-Überlauf-Angriffs basiert darauf,
|
||||
den Stack zu korrumpieren.</para>
|
||||
|
||||
<indexterm><primary>Stack</primary></indexterm>
|
||||
|
@ -309,7 +309,7 @@ return 0;
|
|||
Quelltext, der allgemein verwendet wird und blind Speicher
|
||||
umherkopiert, ohne eine der gerade besprochenen Funktionen,
|
||||
die Begrenzungen unterstützen, zu verwenden.
|
||||
Glücklicherweise gibt es einen Weg, um solche Angriffe zu
|
||||
Glücklicherweise gibt es einen Weg, um solche Angriffe zu
|
||||
verhindern - Überprüfung der Grenzen zur Laufzeit, die in
|
||||
verschiedenen C/C++ Compilern eingebaut ist.</para>
|
||||
|
||||
|
@ -319,19 +319,19 @@ return 0;
|
|||
|
||||
<para>ProPolice ist eine solche Compiler-Eigenschaft und ist in den
|
||||
&man.gcc.1; Versionen 4.1 und höher integriert. Es ersetzt und
|
||||
erweitert die &man.gcc.1; StackGuard-Erweiterung von
|
||||
erweitert die &man.gcc.1; StackGuard-Erweiterung von
|
||||
früher.</para>
|
||||
|
||||
<para>ProPolice schützt gegen stackbasierte
|
||||
|
||||
<para>ProPolice schützt gegen stackbasierte
|
||||
Pufferüberläufe und andere Angriffe durch das Ablegen von
|
||||
Pseudo-Zufallszahlen in Schlüsselbereichen des Stacks bevor es
|
||||
irgendwelche Funktionen aufruft. Wenn eine Funktion beendet wird,
|
||||
irgendwelche Funktionen aufruft. Wenn eine Funktion beendet wird,
|
||||
werden diese <quote>Kanarienvögel</quote> überprüft
|
||||
und wenn festgestellt wird, dass diese verändert wurden wird das
|
||||
Programm sofort abgebrochen. Dadurch wird jeglicher Versuch, die
|
||||
Rücksprungadresse oder andere Variablen, die auf dem Stack
|
||||
gespeichert werden, durch die Ausführung von Schadcode zu
|
||||
manipulieren, nicht funktionieren, da der Angreifer auch die
|
||||
manipulieren, nicht funktionieren, da der Angreifer auch die
|
||||
Pseudo-Zufallszahlen unberührt lassen müsste.</para>
|
||||
|
||||
<indexterm><primary>Puffer-Überlauf</primary></indexterm>
|
||||
|
|
|
@ -54,12 +54,12 @@
|
|||
<title>Zusammenfassung</title>
|
||||
|
||||
<para>FreeBSD bietet eine exzellente Entwicklungsumgebung.
|
||||
Compiler für C und C++, sowie ein Assembler sind im
|
||||
Compiler für C und C++, sowie ein Assembler sind im
|
||||
Basissystem enthalten. Natürlich finden
|
||||
sich auch klassische &unix;-Werkzeuge wie <command>sed</command>
|
||||
sich auch klassische &unix;-Werkzeuge wie <command>sed</command>
|
||||
und <command>awk</command>. Sollte das nicht genug sein, finden sich
|
||||
zahlreiche weitere Compiler und Interpreter in der Ports-Sammlung.
|
||||
Der folgende Abschnitt, <link
|
||||
Der folgende Abschnitt, <link
|
||||
linkend="tools-programming">Einführung in die Programmierung</link>,
|
||||
zählt ein paar der verfügbaren Optionen auf. FreeBSD ist
|
||||
kompatibel zu vielen Standards wie <acronym>&posix;</acronym>
|
||||
|
@ -167,7 +167,7 @@
|
|||
für viele Programmierer die erste
|
||||
Programmiersprache. <acronym>BASIC</acronym> ist auch
|
||||
die Grundlage für Visual Basic.</para>
|
||||
|
||||
|
||||
<para>Der Bywater Basic Interpreter findet sich in der
|
||||
Ports-Sammlung unter <filename
|
||||
role="package">lang/bwbasic</filename> und Phil
|
||||
|
@ -1631,7 +1631,7 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
|
|||
|
||||
<para>Falls Sie den textbasierten Kommandozeilen-Stil
|
||||
abstoßend finden gibt es ein graphisches Front-End
|
||||
dafür (<filename
|
||||
dafür (<filename
|
||||
role="package">devel/xxgdb</filename>) in der Ports-Sammlung.</para>
|
||||
|
||||
<para>Dieser Abschnitt ist als Einführung in die
|
||||
|
@ -1659,9 +1659,9 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
|
|||
<para>Geben Sie in der Eingabeaufforderung des
|
||||
<command>gdb</command> <userinput>break main</userinput> ein.
|
||||
Dies weist den Debugger an, dass Sie nicht daran interessiert sind,
|
||||
den einleitenden Schritten beim Programmstart zuzusehen und dass
|
||||
am Anfang Ihres Codes die Ausführung beginnen soll. Geben Sie
|
||||
nun <userinput>run</userinput> ein, um das Programm zu starten -
|
||||
den einleitenden Schritten beim Programmstart zuzusehen und dass
|
||||
am Anfang Ihres Codes die Ausführung beginnen soll. Geben Sie
|
||||
nun <userinput>run</userinput> ein, um das Programm zu starten -
|
||||
es wird starten und beim Aufruf von <function>main()</function> vom
|
||||
Debugger angehalten werden. (Falls Sie sich jemals gewundert haben von
|
||||
welcher Stelle <function>main()</function> aufgerufen wird, dann
|
||||
|
@ -1994,7 +1994,7 @@ else if (pid == 0) { /* child */
|
|||
<para>Und zweifelsfrei viele weitere Punkte, die ich
|
||||
übersehen habe.</para>
|
||||
|
||||
<para>Emacs kann unter &os; über den <filename
|
||||
<para>Emacs kann unter &os; über den <filename
|
||||
role="package">editors/emacs</filename> Port installiert werden.</para>
|
||||
|
||||
<para>Sobald er installiert ist starten Sie ihn, und geben
|
||||
|
|
|
@ -43,7 +43,7 @@
|
|||
<surname>Reuschling</surname>
|
||||
<contrib>Übersetzt von </contrib>
|
||||
</author>
|
||||
</authorgroup>
|
||||
</authorgroup>
|
||||
</chapterinfo>
|
||||
|
||||
<title>&os; 9.<replaceable>x</replaceable> (und neuer)
|
||||
|
@ -262,7 +262,7 @@
|
|||
mag etwas unhandlich erscheinen und das ist auch der
|
||||
Fall.</para>
|
||||
|
||||
<para>Die <firstterm>GUID-Partitionstabelle</firstterm> (<acronym
|
||||
<para>Die <firstterm>GUID-Partitionstabelle</firstterm> (<acronym
|
||||
role="GUID Partition Table">GPT</acronym>) ist eine neuere und
|
||||
einfachere Methode zur Partition einer Festplatte. <acronym
|
||||
role="GUID Partition Table">GPT</acronym> ist weitaus flexibler
|
||||
|
@ -317,14 +317,14 @@
|
|||
|
||||
<para>Die Veränderung der Grösse von
|
||||
µsoft; Vista-Partitionen kann schwierig sein. Eine
|
||||
Vista Installations-CD-ROM kann hilfreich sein, wenn eine solche
|
||||
Vista Installations-CD-ROM kann hilfreich sein, wenn eine solche
|
||||
Aktion versucht wird.</para>
|
||||
|
||||
<example>
|
||||
<title>Eine existierende Partition verändern</title>
|
||||
|
||||
<para>Ein &windows;-Computer besitzt eine einzelne 40 GB
|
||||
Platte, die in zwei 20 GB Partitionen aufgeteilt wurde.
|
||||
Platte, die in zwei 20 GB Partitionen aufgeteilt wurde.
|
||||
&windows; nennt diese <devicename>C:</devicename> und
|
||||
<devicename>D:</devicename>. Die <devicename>C:</devicename>
|
||||
Partition enthält 10 GB und the
|
||||
|
@ -527,10 +527,10 @@
|
|||
|
||||
<warning>
|
||||
<para>Das Beispiel unten verwendet <filename
|
||||
class="devicefile">/dev/da0</filename> als das
|
||||
class="devicefile">/dev/da0</filename> als das
|
||||
Zielgerät, auf welches das Image geschrieben werden
|
||||
soll. Seien Sie vorsichtig, dass das richtige Gerät
|
||||
als das Ausgabe benutzt wird oder Sie zerstören
|
||||
soll. Seien Sie vorsichtig, dass das richtige Gerät
|
||||
als das Ausgabe benutzt wird oder Sie zerstören
|
||||
wichtige Daten.</para>
|
||||
</warning>
|
||||
|
||||
|
@ -538,7 +538,7 @@
|
|||
<title>Das Image mit &man.dd.1; schreiben</title>
|
||||
|
||||
<para>Die <filename>.img</filename>-Datei ist
|
||||
<emphasis>keine</emphasis> gewöhnliche Datei. Es ist
|
||||
<emphasis>keine</emphasis> gewöhnliche Datei. Es ist
|
||||
ein <emphasis>Image</emphasis> des kompletten
|
||||
späteren Inhalts des USB-Sticks. Es kann
|
||||
<emphasis>nicht</emphasis> einfach wie eine
|
||||
|
@ -566,7 +566,7 @@
|
|||
|
||||
<para><application>Image Writer für
|
||||
&windows;</application> ist eine frei verfügbare
|
||||
Anwendung, welche eine Imagedatei korrekt auf einen
|
||||
Anwendung, welche eine Imagedatei korrekt auf einen
|
||||
SB-Stick schreiben kann. Laden Sie diese von <ulink
|
||||
url="https://launchpad.net/win32-image-writer/"></ulink>
|
||||
herunter und entpacken Sie sie in einen Ordner.</para>
|
||||
|
@ -585,7 +585,7 @@
|
|||
Sie auf das Ordnersymbol und wählen Sie das Image
|
||||
aus, welches auf den USB-Stick geschrieben werden soll.
|
||||
Um den Image-Dateinamen zu akzeptieren, klicken Sie auf
|
||||
<guibutton>[ Save ]</guibutton>.
|
||||
<guibutton>[ Save ]</guibutton>.
|
||||
Überprüfen Sie erneut, ob alles stimmt und dass
|
||||
keine Ordner auf dem USB-Stick in anderen Fenstern
|
||||
geöffnet sind. Sobald alles bereit ist, klicken Sie
|
||||
|
@ -610,7 +610,7 @@
|
|||
<title>Die Installation starten</title>
|
||||
|
||||
<important>
|
||||
<para>Es werden durch die Installation keine Änderungen an
|
||||
<para>Es werden durch die Installation keine Änderungen an
|
||||
Ihren Festplatten durchgeführt, so lange Sie nicht die
|
||||
folgende Meldung sehen:</para>
|
||||
|
||||
|
@ -795,7 +795,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
<command>BREAK</command>-Kommando (indem Sie z.B.
|
||||
<command>~#</command> in &man.tip.1; oder &man.cu.1; absetzen)
|
||||
über die serielle Konsole senden, um zur <acronym
|
||||
role="Programmable Read Only Memory">PROM</acronym>
|
||||
role="Programmable Read Only Memory">PROM</acronym>
|
||||
Befehlszeile zu gelangen. Es sieht dann so aus:</para>
|
||||
|
||||
<screenco>
|
||||
|
@ -835,7 +835,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
|
||||
<para>Um diesen Puffer anzusehen, drücken Sie
|
||||
<keycap>Scroll Lock</keycap>. Das bewirkt, dass Sie die
|
||||
Bildschirmanzeige hoch und runter bewegen (scrollen) können.
|
||||
Bildschirmanzeige hoch und runter bewegen (scrollen) können.
|
||||
Sie können dann die Pfeiltasten oder <keycap>PageUp</keycap>
|
||||
und <keycap>PageDown</keycap> benutzen, um die Meldungen zu
|
||||
sehen. Drücken Sie <keycap>Scroll Lock</keycap> erneut, um
|
||||
|
@ -1312,7 +1312,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
|
|||
<para>Nachdem das Partitionslayout nun erstellt wurde, sollten Sie
|
||||
es danach noch einmal auf Korrektheit prüfen. Sollten Sie
|
||||
einen Fehler gemacht haben, können Sie durch Auswahl von
|
||||
<guibutton>[ Revert ]</guibutton> wieder die
|
||||
<guibutton>[ Revert ]</guibutton> wieder die
|
||||
ursprünglichen Partitionen setzen oder durch
|
||||
<guibutton>[ Auto ]</guibutton> die automatischen
|
||||
&os; Partitionen wiederherstellen. Partitionen können
|
||||
|
@ -1346,7 +1346,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
|
|||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>Durch hervorheben einer Platte (in diesem Fall
|
||||
<para>Durch hervorheben einer Platte (in diesem Fall
|
||||
<devicename>ada0</devicename>) und die Auswahl von
|
||||
<guibutton>[ Create ]</guibutton>, wird ein Menü
|
||||
zur Wahl des <firstterm>Partitionierungsschemas</firstterm>
|
||||
|
@ -1557,7 +1557,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
|
|||
<entry><filename>/</filename></entry>
|
||||
<entry><literal>bsprootfs</literal></entry>
|
||||
</row>
|
||||
|
||||
|
||||
<row>
|
||||
<entry><literal>freebsd-swap</literal></entry>
|
||||
<entry><literal>4G</literal></entry>
|
||||
|
@ -1615,7 +1615,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
|
|||
|
||||
<para>Wählen Sie <guibutton>[ Commit ]</guibutton> und
|
||||
drücken Sie <keycap>Enter</keycap>, um fortzufahren. Fall noch
|
||||
Änderungen zu machen sind, wählen Sie
|
||||
Änderungen zu machen sind, wählen Sie
|
||||
<guibutton>[ Back ]</guibutton>, um zum Partitionseditor
|
||||
zurück zu gelangen. Mittels
|
||||
<guibutton>[ Revert & Exit ]</guibutton>
|
||||
|
@ -2262,7 +2262,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><literal>Home directory permissions</literal> -
|
||||
<para><literal>Home directory permissions</literal> -
|
||||
Zugriffsrechte auf das Heimatverzeichnis des Benutzers. Die
|
||||
Vorgabe ist normalerweise die passende.</para>
|
||||
</listitem>
|
||||
|
@ -2674,7 +2674,7 @@ login:</screen>
|
|||
<primary>installation</primary>
|
||||
<secondary>troubleshooting</secondary>
|
||||
</indexterm>
|
||||
|
||||
|
||||
<para>Der folgende Abschnitt behandelt einfache Fehlerbehebungen
|
||||
für die Installation, wie beispielsweise häufig
|
||||
auftretende Fehler, die von Anwendern berichtet wurden.</para>
|
||||
|
@ -2755,7 +2755,7 @@ login:</screen>
|
|||
<screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen>
|
||||
|
||||
<para>Dies wird nach jedem Neustart des Systems wieder
|
||||
zurückgesetzt, also ist es notwendig, die Zeile
|
||||
zurückgesetzt, also ist es notwendig, die Zeile
|
||||
<literal>hint.acpi.0.disabled="1"</literal> zu der Datei
|
||||
<filename>/boot/loader.conf</filename> hinzuzufügen.
|
||||
Weitere Informationen über den Bootloader lassen sich
|
||||
|
|
|
@ -2634,7 +2634,7 @@ kern.maxvnodes: 100000</screen>
|
|||
Kernel-Konfigurationsdatei enthalten ist:</para>
|
||||
|
||||
<programlisting>device md</programlisting>
|
||||
|
||||
|
||||
<para>Informationen, wie man einen eigenen Kernel erstellen kann,
|
||||
erhalten Sie in <xref linkend="kernelconfig"/>.</para>
|
||||
</listitem>
|
||||
|
|
|
@ -174,7 +174,7 @@
|
|||
<entry>hoch</entry>
|
||||
<entry><application>KDE</application>-Biliotheken</entry>
|
||||
</row>
|
||||
|
||||
|
||||
<row>
|
||||
<entry><application>Chromium</application></entry>
|
||||
<entry>mittel</entry>
|
||||
|
@ -454,13 +454,13 @@
|
|||
url="http://freebsd.kde.org/howtos/konqueror-flash.php"></ulink>
|
||||
nachlesen.</para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Chromium</title>
|
||||
<indexterm>
|
||||
<primary><application>Chromium</application></primary>
|
||||
</indexterm>
|
||||
|
||||
|
||||
<para><application>Chromium</application> ist ein quelloffenes
|
||||
Browserprojekt mit dem Ziel ein sicheres, schnelleres und
|
||||
stabileres Surferlebnis im Web zu ermöglichen.
|
||||
|
@ -468,18 +468,18 @@
|
|||
Tabs, Blockieren von Pop-Ups, Erweiterungen und vieles mehr.
|
||||
<application>Chromium</application> ist das Open Source Projekt,
|
||||
welches auf dem Google Chrome Webbrowser basiert.</para>
|
||||
|
||||
|
||||
<para><application>Chromium</application> kann als Paket durch die Eingabe des folgenden Befehls installiert werden:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>pkg_add -r chromium</userinput></screen>
|
||||
|
||||
|
||||
<para>Als Alternative kann <application>Chromium</application>
|
||||
aus dem Quellcode durch die Ports Collection übersetzt
|
||||
werden:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/www/chromium</userinput>
|
||||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
||||
|
||||
<note>
|
||||
<para><application>Chromium</application> wird als
|
||||
<filename>/usr/local/bin/chrome</filename> installiert und
|
||||
|
@ -487,7 +487,7 @@
|
|||
<filename>/usr/local/bin/chromium</filename>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="chromium-java-plugin">
|
||||
<title>Chromium und das &java;-Plug-In</title>
|
||||
|
||||
|
@ -496,25 +496,25 @@
|
|||
<application>Chromium</application> bereits installiert
|
||||
ist.</para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>Installieren Sie <application>OpenJDK 6</application>
|
||||
mit Hilfe der Ports Collection durch Eingabe von:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/java/openjdk6
|
||||
&prompt.root; make install clean</userinput></screen>
|
||||
|
||||
|
||||
<para>Als nächstes installieren Sie <filename
|
||||
role="package">java/icedtea-web</filename> aus der Ports
|
||||
Collection:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/java/icedtea-web
|
||||
&prompt.root; make install clean</userinput></screen>
|
||||
|
||||
|
||||
<para>Starten Sie <application>Chromium</application> und geben Sie
|
||||
<literal>about:plugins</literal> in die Addresszeile ein.
|
||||
IcedTea-Web sollte dort als eines der installierten Plug-Ins
|
||||
aufgelistet sein.</para>
|
||||
|
||||
|
||||
<para>Falls <application>Chromium</application> das IcedTea-Web
|
||||
Plug-In nicht anzeigt, geben Sie das folgende Kommando ein und
|
||||
starten Sie den Webbrowser anschliessend neu:</para>
|
||||
|
@ -523,16 +523,16 @@
|
|||
&prompt.root; ln -s /usr/local/lib/IcedTeaPlugin.so \
|
||||
/usr/local/share/chromium/plugins/</userinput></screen>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="chromium-flash-plugin">
|
||||
<title>Chromium und das &adobe; &flash;-Plug-In</title>
|
||||
|
||||
|
||||
<note>
|
||||
<para>Dieser Abschnitt setzt voraus, dass
|
||||
<application>Chromium</application> bereits installiert
|
||||
ist.</para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>Die Konfiguration von <application>Chromium</application>
|
||||
und &adobe; &flash; ist ähnlich zur <link
|
||||
linkend="moz-flash-plugin">Anleitung für Firefox</link>.
|
||||
|
@ -541,7 +541,7 @@
|
|||
Abschnitt. Es sollte keine weitere Konfiguration notwendig
|
||||
sein, da <application>Chromium</application> in der Lage ist,
|
||||
Plug-Ins von anderen Browsern mit zu benutzen.</para>
|
||||
</sect2>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="desktop-productivity">
|
||||
|
@ -569,7 +569,7 @@
|
|||
</row>
|
||||
</thead>
|
||||
|
||||
<tbody>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry><application>KOffice</application></entry>
|
||||
<entry>niedrig</entry>
|
||||
|
|
|
@ -3500,7 +3500,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
|
||||
<para>Seit &os; 8.0-RELEASE und dessen Nachfolger fügen
|
||||
Sie stattdessen die folgende Zeile hinzu:</para>
|
||||
|
||||
|
||||
<programlisting>quota_enable="YES"</programlisting>
|
||||
<indexterm>
|
||||
<primary>Disk Quotas</primary>
|
||||
|
|
|
@ -145,7 +145,7 @@ that might make this chapter too large.
|
|||
Kürze erfahren Sie, wie Sie dies für den Kernel und den Bau von
|
||||
&os; aktivieren.</para>
|
||||
|
||||
<para>Einige Provider in &os; unterscheiden sich von der
|
||||
<para>Einige Provider in &os; unterscheiden sich von der
|
||||
&solaris;-Implementierung. Am deutlichsten wird das beim
|
||||
<literal>dtmalloc</literal>-Provider, welcher das Aufzeichnen von
|
||||
<function>malloc()</function> nach Typen im &os;-Kernel
|
||||
|
@ -215,7 +215,7 @@ options DDB_CTF</programlisting>
|
|||
Korn-Shell hinzugefügt werden. Dies wird benötigt, da die
|
||||
Sammlung von &dtrace;-Werkzeugen mehrere Dienstprogramme enthält,
|
||||
die in <command>ksh</command> implementiert sind. Installieren Sie
|
||||
<filename role="package">shells/ksh93</filename>. Es ist auch
|
||||
<filename role="package">shells/ksh93</filename>. Es ist auch
|
||||
möglich, diese Werkzeuge unter <filename
|
||||
role="package">shells/pdksh</filename> oder <filename
|
||||
role="package">shells/mksh</filename> laufen zu lassen.</para>
|
||||
|
|
|
@ -587,7 +587,7 @@
|
|||
|
||||
<row>
|
||||
<entry>&a.zope.name;</entry>
|
||||
<entry><application>Zope</application> für &os; -
|
||||
<entry><application>Zope</application> für &os; -
|
||||
Portierung und Wartung</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
|
@ -1125,7 +1125,7 @@
|
|||
|
||||
<para>Dies ist ein Forum für Diskussionen um &os; auf dem
|
||||
Desktop. Es wird primär von Desktop-Portierern und
|
||||
Nutzern verwendet, um Probleme und Verbesserungen zu &os;s
|
||||
Nutzern verwendet, um Probleme und Verbesserungen zu &os;s
|
||||
Einsatz auf dem Desktop zu besprechen.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
|
@ -36,17 +36,17 @@
|
|||
<see>MAC</see>
|
||||
</indexterm>
|
||||
|
||||
<para> In &os; 5.X wurden neue Sicherheits-Erweiterungen
|
||||
<para> In &os; 5.X wurden neue Sicherheits-Erweiterungen
|
||||
verfügbar, die aus dem TrustedBSD-Projekt übernommen wurden
|
||||
und auf dem Entwurf &posix;.1e basieren. Die beiden
|
||||
bedeutendsten neuen Sicherheits-Mechanismen sind Berechtigungslisten
|
||||
(Access Control Lists, <acronym>ACL</acronym>) und die verbindliche
|
||||
Zugriffskontrolle (Mandatory Access Control, <acronym>MAC</acronym>).
|
||||
Durch die MAC können Module geladen werden, die neue
|
||||
Sicherheitsrichtlinien bereitstellen. Mit Hilfe einiger Module kann
|
||||
Sicherheitsrichtlinien bereitstellen. Mit Hilfe einiger Module kann
|
||||
beispielsweise ein eng umgrenzter Bereich des Betriebssystems gesichert
|
||||
werden, indem die Sicherheitsfunktionen spezieller Dienste
|
||||
unterstützt bzw. verstärkt werden. Andere Module wiederum
|
||||
werden, indem die Sicherheitsfunktionen spezieller Dienste
|
||||
unterstützt bzw. verstärkt werden. Andere Module wiederum
|
||||
betreffen in ihrer Funktion das gesamte System - alle vorhandenen
|
||||
Subjekte und Objekte. Das "Verbindliche" in der Namensgebung
|
||||
erwächst aus dem Fakt, dass die Kontrolle allein Administratoren
|
||||
|
@ -56,7 +56,7 @@
|
|||
gar der System V <acronym>IPC</acronym> in &os;, normalerweise umgesetzt
|
||||
wird.</para>
|
||||
|
||||
<para>Dieses Kapitel wird sich auf die Grundstruktur der Verbindlichen
|
||||
<para>Dieses Kapitel wird sich auf die Grundstruktur der Verbindlichen
|
||||
Zugriffskontrolle und eine Auswahl der Module, die verschiedenste
|
||||
Sicherheitsfunktionen zur Verfügung stellen, konzentrieren.</para>
|
||||
|
||||
|
@ -82,18 +82,18 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Wie die verschiedenen Richtlinienmodule einer MAC konfiguriert
|
||||
<para>Wie die verschiedenen Richtlinienmodule einer MAC konfiguriert
|
||||
werden.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Wie mit einer <acronym>MAC</acronym> und den gezeigten Beispielen
|
||||
<para>Wie mit einer <acronym>MAC</acronym> und den gezeigten Beispielen
|
||||
eine sicherere Umgebung erstellt werden kann.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Wie die Konfiguration einer <acronym>MAC</acronym> auf korrekte
|
||||
Einrichtung getestet wird.</para>
|
||||
Einrichtung getestet wird.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
@ -105,12 +105,12 @@
|
|||
(<xref linkend="basics"/>).</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Mit den Grundzügen der Kernelkonfiguration und -kompilierung
|
||||
<para>Mit den Grundzügen der Kernelkonfiguration und -kompilierung
|
||||
vertraut sein (<xref linkend="kernelconfig"/>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Einige Vorkenntnisse über Sicherheitskonzepte im Allgemeinen
|
||||
<para>Einige Vorkenntnisse über Sicherheitskonzepte im Allgemeinen
|
||||
und deren Umsetzung in &os; im Besonderen mitbringen (<xref
|
||||
linkend="security"/>).</para>
|
||||
</listitem>
|
||||
|
@ -118,8 +118,8 @@
|
|||
|
||||
<warning>
|
||||
<para>Der unsachgemäße Gebrauch der in diesem Kapitel
|
||||
enthaltenen Informationen kann den Verlust des Systemzugriffs,
|
||||
Ärger mit Nutzern oder die Unfähigkeit, grundlegende
|
||||
enthaltenen Informationen kann den Verlust des Systemzugriffs,
|
||||
Ärger mit Nutzern oder die Unfähigkeit, grundlegende
|
||||
Funktionen des X-Windows-Systems zu nutzen, verursachen. Wichtiger
|
||||
noch ist, dass man sich nicht allein auf die <acronym>MAC</acronym>
|
||||
verlassen sollte, um ein System zu sichern. Die <acronym>MAC</acronym>
|
||||
|
@ -149,7 +149,7 @@
|
|||
abgedeckt. Einige weitere Module, die im MAC Framework enthalten sind,
|
||||
haben besondere Charakteristika, die zum Testen und Entwickeln neuer
|
||||
Module gedacht sind. Dies sind unter anderem &man.mac.test.4;,
|
||||
&man.mac.stub.4; und &man.mac.none.4;. Für weitere Informationen
|
||||
&man.mac.stub.4; und &man.mac.none.4;. Für weitere Informationen
|
||||
zu diesen Modulen und den entsprechend angebotenen Funktionen lesen Sie
|
||||
bitte die Manpages.</para>
|
||||
</sect2>
|
||||
|
@ -157,10 +157,10 @@
|
|||
|
||||
<sect1 id="mac-inline-glossary">
|
||||
<title>Schlüsselbegriffe</title>
|
||||
|
||||
|
||||
<para>Bevor Sie weiterlesen, müssen noch einige Schlüsselbegriffe
|
||||
geklärt werden. Dadurch soll jegliche auftretende Verwirrung von
|
||||
vornherein beseitigt und die plötzliche Einführung neuer
|
||||
vornherein beseitigt und die plötzliche Einführung neuer
|
||||
Begriffe und Informationen vermieden werden.</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
@ -180,10 +180,10 @@
|
|||
<para><emphasis>Hochwassermarkierung</emphasis>: Eine solche Richtlinie
|
||||
erlaubt die Erhöhung der Sicherheitsstufe in Abhängigkeit
|
||||
der Klassifikation der gesuchten bzw. bereitzustellenden Information.
|
||||
Normalerweise wird nach Abschluss des Prozesses die
|
||||
ursprüngliche Sicherheitsstufe wieder hergestellt. Derzeit
|
||||
enthält die <acronym>MAC</acronym> Grundstruktur keine
|
||||
Möglichkeit, eine solche Richtlinie umzusetzen, der
|
||||
Normalerweise wird nach Abschluss des Prozesses die
|
||||
ursprüngliche Sicherheitsstufe wieder hergestellt. Derzeit
|
||||
enthält die <acronym>MAC</acronym> Grundstruktur keine
|
||||
Möglichkeit, eine solche Richtlinie umzusetzen, der
|
||||
Vollständigkeit halber ist die Definition hier jedoch
|
||||
aufgeführt.</para>
|
||||
</listitem>
|
||||
|
@ -204,7 +204,7 @@
|
|||
derart gekennzeichnet werden, bezeichnen diese Label die
|
||||
sicherheitsrelevanten Eigenschaften. Zugriff ist nur noch dann
|
||||
möglich, wenn das zugreifende Subjekt eine korrespondierende
|
||||
Kennzeichnung trägt. Die Bedeutung und Verarbeitung der
|
||||
Kennzeichnung trägt. Die Bedeutung und Verarbeitung der
|
||||
Label-Werte ist von der Einrichtung der Richtlinie abhängig:
|
||||
Während einige Richtlinien das Label zum Kennzeichnen der
|
||||
Vertraulichkeit oder Geheimhaltungsstufe eines Objekts nutzen,
|
||||
|
@ -232,7 +232,7 @@
|
|||
<para><emphasis>Multilabel</emphasis>: Die Eigenschaft
|
||||
<option>multilabel</option> ist eine Dateisystemoption, die entweder
|
||||
im Einzelbenutzermodus mit Hilfe des Werkzeugs &man.tunefs.8;,
|
||||
während des Bootvorgangs in der Datei &man.fstab.5; oder aber
|
||||
während des Bootvorgangs in der Datei &man.fstab.5; oder aber
|
||||
beim Erstellen einen neues Dateisystems aktiviert werden kann. Diese
|
||||
Option erlaubt einem Administrator, verschiedenen Objekten
|
||||
unterschiedliche Labels zuzuordnen - kann jedoch nur zusammen mit
|
||||
|
@ -304,7 +304,7 @@
|
|||
verwendet werden, um das Netzwerk oder Dateisysteme zu schützen,
|
||||
Nutzern den Zugang zu bestimmten Ports oder Sockets zu verbieten und
|
||||
vieles mehr. Die vielleicht beste Weise, die Module zu verwenden, ist,
|
||||
sie miteinander zu kombinieren, indem mehrere
|
||||
sie miteinander zu kombinieren, indem mehrere
|
||||
Sicherheitsrichtlinienmodule gleichzeitig eine mehrschichtige
|
||||
Sicherheitsumgebung schaffen. Das ist etwas anderes als singuläre
|
||||
Richtlinien wie zum Beispiel die Firewall, die typischerweise Elemente
|
||||
|
@ -316,7 +316,7 @@
|
|||
|
||||
<para>Solche Nachteile sind allerdings gering im Vergleich zum bleibenden
|
||||
Effekt der erstellten Struktur. Die Möglichkeit zum Beispiel,
|
||||
für konkrete Anwendungen genau die passenden Richtlinien
|
||||
für konkrete Anwendungen genau die passenden Richtlinien
|
||||
auszuwählen und einzurichten, senkt gleichzeitig die Arbeitskosten.
|
||||
Wenn man unnötige Richtlinien aussortiert, kann man die
|
||||
Gesamtleistung des Systems genauso steigern wie auch eine höhere
|
||||
|
@ -330,7 +330,7 @@
|
|||
Sicherheitsmerkmale nach eigenem Ermessen zu verändern; dass
|
||||
Arbeitswerkzeuge, Programme und Skripte, innerhalb der
|
||||
Beschränkungen arbeiten können, welche die Zugriffsregeln der
|
||||
ausgewählten Module dem System auferlegen; und dass die volle
|
||||
ausgewählten Module dem System auferlegen; und dass die volle
|
||||
Kontrolle über die Regeln der <acronym>MAC</acronym> beim
|
||||
Administrator ist und bleibt.</para>
|
||||
|
||||
|
@ -383,7 +383,7 @@
|
|||
Zeile</para>
|
||||
|
||||
|
||||
<programlisting>options MAC</programlisting>
|
||||
<programlisting>options MAC</programlisting>
|
||||
|
||||
<para>der Kernelkonfiguration hinzugefügt und der Kernel neu
|
||||
übersetzt und installiert werden.</para>
|
||||
|
@ -391,24 +391,24 @@
|
|||
<caution>
|
||||
<para>Verschiedenen Anleitungen für die <acronym>MAC</acronym>
|
||||
empfehlen, die einzelnen Module direkt in den Kernel einzuarbeiten.
|
||||
Dabei ist es jedoch möglich, das System aus dem Netzwerk
|
||||
Dabei ist es jedoch möglich, das System aus dem Netzwerk
|
||||
auszusperren oder gar schlimmeres. Die Arbeit mit der
|
||||
<acronym>MAC</acronym> ist ähnlich der Arbeit mit einer Firewall -
|
||||
man muß, wenn man sich nicht selbst aus dem System aussperren
|
||||
will, genau aufpassen. Man sollte sich eine Möglichkeit
|
||||
zurechtlegen, wie man eine Implementation einer <acronym>MAC</acronym>
|
||||
rückgängig machen kann - genauso wie eine Ferninstallation
|
||||
über das Netzwerk nur mit äußerster Vorsicht
|
||||
über das Netzwerk nur mit äußerster Vorsicht
|
||||
vorgenommen werden sollte. Es wird daher empfohlen,
|
||||
die Module nicht in den Kernel einzubinden, sondern sie beim
|
||||
Systemstart via <filename>/boot/loader.conf</filename> zu
|
||||
laden.</para>
|
||||
</caution>
|
||||
</caution>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="mac-understandlabel">
|
||||
<title>MAC Labels verstehen</title>
|
||||
|
||||
|
||||
<para>MAC Label sind Sicherheitsmerkmale, die, wenn sie zum Einsatz kommen,
|
||||
allen Subjekten und Objekten im System zugeordnet werden.</para>
|
||||
|
||||
|
@ -472,7 +472,7 @@
|
|||
<acronym>DAC</acronym>! Ich dachte, <acronym>MAC</acronym> würde die
|
||||
Kontrolle strengstens an den Administrator binden!</emphasis> Diese
|
||||
Aussage hält immer noch stand - <username>root</username> ist
|
||||
derjenige, der die Kontrolle ausübt und die Richtlinie konfiguriert,
|
||||
derjenige, der die Kontrolle ausübt und die Richtlinie konfiguriert,
|
||||
so dass Nutzer in die entsprechenden, angemessenen Kategorien /
|
||||
Zugriffsklassen eingeordnet werden. Nunja, einige Module schränken
|
||||
<username>root</username> selbst ein. Die Kontrolle über Objekte
|
||||
|
@ -507,10 +507,10 @@
|
|||
bereits (Zugriffs-)Beschränkungen
|
||||
unterliegt.<footnote><para>Andere Vorbedingungen führen
|
||||
natürlich zu anderen Fehlern. Zum Beispiel wenn das Objekt nicht
|
||||
dem Nutzer gehört, der das Label ändern möchte, das
|
||||
dem Nutzer gehört, der das Label ändern möchte, das
|
||||
Objekt vielleicht gar nicht existiert oder es sich um ein nur lesbares
|
||||
Objekt handelt. Oder eine verbindliche Richtlinie erlaubt dem
|
||||
Prozeß die Veränderung des Labels nicht, weil die
|
||||
Prozeß die Veränderung des Labels nicht, weil die
|
||||
Eigenschaften der Datei, die Eigenschaften des Prozesses oder der
|
||||
Inhalt des neuen Labels nicht akzeptiert werden. Beispiel: Ein
|
||||
Anwender mit geringer Vertraulichkeit versucht, das Label einer Datei
|
||||
|
@ -519,7 +519,7 @@
|
|||
zu machen.</para></footnote> Der Systemadministrator kann so eine
|
||||
Situation mit Hilfe der folgenden Kommandos überwinden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>setfmac biba/high test</userinput>
|
||||
<screen>&prompt.root; <userinput>setfmac biba/high test</userinput>
|
||||
<errorname>Permission denied</errorname>
|
||||
&prompt.root; <userinput>setpmac biba/low setfmac biba/high test</userinput>
|
||||
&prompt.root; <userinput>getfmac test</userinput>
|
||||
|
@ -538,15 +538,15 @@ test: biba/high</screen>
|
|||
not permitted</errorname> durch die Funktion
|
||||
<function>mac_set_link</function> angezeigt.</para>
|
||||
|
||||
<sect3>
|
||||
<sect3>
|
||||
<title>Übliche Typen von Labeln</title>
|
||||
|
||||
<para>Wenn man die Module &man.mac.biba.4;, &man.mac.mls.4; und
|
||||
&man.mac.lomac.4; verwendet, hat man die Möglichkeit, einfache
|
||||
Label zu vergeben. Diese nennen sich <literal>high</literal>,
|
||||
Label zu vergeben. Diese nennen sich <literal>high</literal>,
|
||||
<literal>low</literal> und <literal>equal</literal>. Es folgt eine
|
||||
kurze Beschreibung, was diese Labels bedeuten:</para>
|
||||
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Das Label <literal>low</literal> ist
|
||||
|
@ -556,7 +556,7 @@ test: biba/high</screen>
|
|||
zugreifen, die das Label <literal>high</literal> tragen.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<listitem>
|
||||
<para>Das Label <literal>equal</literal> wird Entitäten
|
||||
verliehen, die von der Richtlinie ausgenommen sein sollen.</para>
|
||||
</listitem>
|
||||
|
@ -576,13 +576,13 @@ test: biba/high</screen>
|
|||
|
||||
<sect4>
|
||||
<title>Fortgeschrittene Label-Konfiguration</title>
|
||||
|
||||
|
||||
<para>Numerische klassifizierte Labels werden verwendet in der Form
|
||||
<literal>Klasse:Verbund+Verbund</literal>. Demnach ist das
|
||||
Label</para>
|
||||
|
||||
<programlisting>biba/10:2+3+6(5:2+3-15:2+3+4+5+6)</programlisting>
|
||||
|
||||
|
||||
<para>folgendermaßen zu lesen:</para>
|
||||
|
||||
<para><quote>Biba Policy Label</quote>/<quote>effektive Klasse
|
||||
|
@ -616,7 +616,7 @@ test: biba/high</screen>
|
|||
Der Fall, dass sich beide dominieren, tritt dann ein, wenn die beiden
|
||||
Labels gleich sind. Wegen der Natur des Informationsflusses in Biba
|
||||
kann man einem Nutzer Rechte für einen Reihe von Abteilungen
|
||||
zuordnen, die zum Beispiel mit entsprechenden Projekten
|
||||
zuordnen, die zum Beispiel mit entsprechenden Projekten
|
||||
korrespondieren. Genauso können aber auch Objekten mehrere
|
||||
Abteilungen zugeordnet sein. Die Nutzer müssen eventuell ihre
|
||||
gegenwärtigen Rechte mithilfe von <command>su</command> or
|
||||
|
@ -686,7 +686,7 @@ test: biba/high</screen>
|
|||
</note>
|
||||
|
||||
<para>Nach einer Änderung der Datei
|
||||
<filename>login.conf</filename> muß in jedem Fall die
|
||||
<filename>login.conf</filename> muß in jedem Fall die
|
||||
Befähigungsdatenbank mit dem Kommando
|
||||
<command>cap_mkdb</command> neu erstellt werden - und das gilt
|
||||
für alle im weiteren Verlauf gezeigten Beispiele und
|
||||
|
@ -695,7 +695,7 @@ test: biba/high</screen>
|
|||
<para>Es ist nützlich anzumerken, dass viele Einsatzorte eine
|
||||
große Anzahl von Nutzern haben, die wiederum viele
|
||||
verschiedenen Nutzerklassen angehören sollen. Hier ist eine
|
||||
Menge Planungsarbeit notwendig, da die Verwaltung sehr
|
||||
Menge Planungsarbeit notwendig, da die Verwaltung sehr
|
||||
unübersichtlich und schwierig ist.</para>
|
||||
</sect3>
|
||||
|
||||
|
@ -741,7 +741,7 @@ test: biba/high</screen>
|
|||
label</option> und <option>multilabel</option>. In ihrer ureigenen
|
||||
Weise bieten beide Vor- und Nachteile bezogen auf die Flexibilität
|
||||
bei der Modellierung der Systemsicherheit.</para>
|
||||
|
||||
|
||||
<para>Die Option <option>single label</option> gibt jedem Subjekt oder
|
||||
Objekt genau ein einziges Label, zum Beispiel
|
||||
<literal>biba/high</literal>. Mit dieser Option hat man einen
|
||||
|
@ -804,12 +804,12 @@ test: biba/high</screen>
|
|||
|
||||
<para>Wenn Richtlinien benutzt werden sollen, die ohne Labels auskommen,
|
||||
wird die Option <option>multilabel</option> nicht benötigt. Dies
|
||||
betrifft die Richtlinien <literal>seeotheruids</literal>,
|
||||
betrifft die Richtlinien <literal>seeotheruids</literal>,
|
||||
<literal>portacl</literal> und <literal>partition</literal>.</para>
|
||||
|
||||
<para>Man sollte sich dessen bewußt sein, dass die Verwendung der
|
||||
Option <option>multilabel</option> auf einer Partition und die
|
||||
Erstellung eines Sicherheitsmodells auf der Basis der &os;
|
||||
Erstellung eines Sicherheitsmodells auf der Basis der &os;
|
||||
<option>multilevel</option> Funktionalität einen hohen
|
||||
Verwaltungsaufwand bedeutet, da alles im Dateisystem ein Label bekommt.
|
||||
Jedes Verzeichnis, jede Datei und genauso jede Schnittstelle.</para>
|
||||
|
@ -889,7 +889,7 @@ test: biba/high</screen>
|
|||
Konfiguration der einzelnen Module beschreiben; und in einigen
|
||||
Fällen Einblicke gewähren, für welche Situationen welche
|
||||
Module besonders geeignet sind. Zum Beispiel ein Webserver kann von der
|
||||
Verwendung der &man.mac.biba.4; oder der &man.mac.bsdextended.4;
|
||||
Verwendung der &man.mac.biba.4; oder der &man.mac.bsdextended.4;
|
||||
Richtlinie profitieren. In anderen Fällen, an einem Rechner mit nur
|
||||
wenigen lokalen Benutzern, ist die &man.mac.partition.4; die Richtlinie
|
||||
der Wahl.</para>
|
||||
|
@ -909,16 +909,16 @@ test: biba/high</screen>
|
|||
Module und ihre jeweiligen Vor- und Nachteile vorstellen. Außerdem
|
||||
wird erklärt, wie sie in bestimmte Umgebungen eingearbeitet werden
|
||||
können. Einige Module unterstützen die Verwendung von
|
||||
<literal>Labels</literal>, das heißt Zugriffskontrolle durch
|
||||
<literal>Labels</literal>, das heißt Zugriffskontrolle durch
|
||||
hinzufügen einer Kennzeichnung in der Art von <quote>dieses ist
|
||||
erlaubt, jenes aber nicht</quote>. Eine Label-Konfigurationdatei
|
||||
kontrolliert unter anderem, wie auf Dateien zugegriffen oder wie
|
||||
kontrolliert unter anderem, wie auf Dateien zugegriffen oder wie
|
||||
über das Netzwerk kommuniziert werden darf. Im vorangehenden
|
||||
Abschnitt wurde bereits erläutert, wie die Option
|
||||
<option>multilabel</option> auf Dateisysteme angewendet wird, um eine
|
||||
Zugriffskontrolle auf einzelne Dateien oder ganze Dateisysteme zu
|
||||
konfigurieren.</para>
|
||||
|
||||
|
||||
<para>Eine <option>single label</option> Konfiguration erzwingt ein
|
||||
einzelnes Label für das gesamte System. Daher wird die
|
||||
<command>tunefs</command>-Option <option>multilabel</option> genannt.
|
||||
|
@ -926,8 +926,8 @@ test: biba/high</screen>
|
|||
</sect1>
|
||||
|
||||
<sect1 id="mac-seeotheruids">
|
||||
<title>Das MAC Modul seeotheruids</title>
|
||||
|
||||
<title>Das MAC Modul seeotheruids</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>MAC See Other UIDs Policy</primary>
|
||||
</indexterm>
|
||||
|
@ -942,7 +942,7 @@ test: biba/high</screen>
|
|||
|
||||
<para>Das Modul &man.mac.seeotheruids.4; erweitert die
|
||||
<command>sysctl</command>-Variablen
|
||||
<literal>security.bsd.see_other_uids</literal> und
|
||||
<literal>security.bsd.see_other_uids</literal> und
|
||||
<literal>security.bsd.see_other_gids</literal>. Diese Optionen
|
||||
benötigen keine im Vorhinein zu setzenden Labels und können
|
||||
leicht durchschaubar mit den anderen MAC-Modulen zusammenarbeiten.</para>
|
||||
|
@ -958,7 +958,7 @@ test: biba/high</screen>
|
|||
die ihnen nicht selbst gehöen.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<literal>security.mac.seeotheruids.specificgid_enabled</literal> kann
|
||||
eine spezifizierte Nutzergruppe von dieser Richtlinie ausnehmen. Die
|
||||
|
@ -1000,12 +1000,12 @@ test: biba/high</screen>
|
|||
das Dateisystem und ist eine Erweiterung des sonst üblichen
|
||||
Rechtemodells. Es erlaubt einem Administrator einen Regelsatz zum
|
||||
Schutz von Dateien, Werkzeugen und Verzeichnissen in der
|
||||
Dateisystemhierarchie zu erstellen, der einer Firewall ähnelt.
|
||||
Dateisystemhierarchie zu erstellen, der einer Firewall ähnelt.
|
||||
Sobald auf ein Objekt im Dateisystem zugegriffen werden soll, wird eine
|
||||
Liste von Regel abgearbeitet, bis eine passende Regel gefunden wird
|
||||
oder die Liste zu Ende ist. Das Verhalten kann durch die Änderung
|
||||
des &man.sysctl.8; Parameters
|
||||
<literal>security.mac.bsdextended.firstmatch_enabled</literal>
|
||||
des &man.sysctl.8; Parameters
|
||||
<literal>security.mac.bsdextended.firstmatch_enabled</literal>
|
||||
eingestellt werden. Ähnlich wie bei den anderen Firewallmodulen
|
||||
in &os; wird eine Datei erstellt, welche die Zugriffsregeln
|
||||
enthält. Diese wird beim Systemstart durch eine Variable in
|
||||
|
@ -1047,11 +1047,11 @@ test: biba/high</screen>
|
|||
&prompt.root; <userinput>ugidfw set 3 subject uid <replaceable>user1</replaceable> object gid <replaceable>user2</replaceable> mode n</userinput></screen>
|
||||
|
||||
<para>Diese Befehle bewirken, dass <username>user1</username> keinen
|
||||
Zugriff mehr auf Dateien und Programme hat, die
|
||||
Zugriff mehr auf Dateien und Programme hat, die
|
||||
<username><replaceable>user2</replaceable></username> gehören.
|
||||
Dies schließt das Auslesen von Verzeichniseinträgen ein.
|
||||
</para>
|
||||
|
||||
|
||||
<para>Anstelle <option>uid</option> <username>user1</username>
|
||||
könnte auch <option>not uid
|
||||
<replaceable>user2</replaceable></option> als Parameter übergeben
|
||||
|
@ -1065,7 +1065,7 @@ test: biba/high</screen>
|
|||
|
||||
<para>Dies sollte als Überblick ausreichen, um zu verstehen, wie das
|
||||
Modul &man.mac.bsdextended.4; helfen kann, das Dateisystem
|
||||
abzuschotten. Weitere Informationen bieten die Manpages
|
||||
abzuschotten. Weitere Informationen bieten die Manpages
|
||||
&man.mac.bsdextended.4; und &man.ugidfw.8;.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
@ -1085,9 +1085,9 @@ test: biba/high</screen>
|
|||
|
||||
<para>Bootparameter: <literal>mac_ifoff_load="YES"</literal></para>
|
||||
|
||||
<para>Das Modul &man.mac.ifoff.4; ist einzig dazu da,
|
||||
<para>Das Modul &man.mac.ifoff.4; ist einzig dazu da,
|
||||
Netzwerkschnittstellen im laufenden Betrieb zu deaktivieren oder zu
|
||||
verhindern, das Netzwerkschnittstellen während der Bootphase
|
||||
verhindern, das Netzwerkschnittstellen während der Bootphase
|
||||
gestartet werden. Dieses Modul benötigt für seinen Betrieb
|
||||
weder Labels, die auf dem System eingerichtet werden müssen, noch
|
||||
hat es Abhängigkeiten zu anderen MAC Modulen.</para>
|
||||
|
@ -1113,11 +1113,11 @@ test: biba/high</screen>
|
|||
Netzwerkschnittstellen.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
||||
<para>Die wahrscheinlich häufigste Nutzung von &man.mac.ifoff.4; ist
|
||||
die Überwachung des Netzwerks in einer Umgebung, in der kein
|
||||
die Überwachung des Netzwerks in einer Umgebung, in der kein
|
||||
Netzwerkverkehr während des Bootvorgangs erlaubt werden soll. Eine
|
||||
andere mögliche Anwendung wäre ein Script, das mit Hilfe von
|
||||
andere mögliche Anwendung wäre ein Script, das mit Hilfe von
|
||||
<filename role="package">security/aide</filename> automatisch alle
|
||||
Schnittstellen blockiert, sobald Dateien in geschützten
|
||||
Verzeichnissen angelegt oder verändert werden.</para>
|
||||
|
@ -1132,8 +1132,8 @@ test: biba/high</screen>
|
|||
|
||||
<para>Modulname: <filename>mac_portacl.ko</filename></para>
|
||||
|
||||
<para>Parameter für die Kernelkonfiguration:
|
||||
<literal>options MAC_PORTACL</literal></para>
|
||||
<para>Parameter für die Kernelkonfiguration:
|
||||
<literal>options MAC_PORTACL</literal></para>
|
||||
|
||||
<para>Bootparameter: <literal>mac_portacl_load="YES"</literal></para>
|
||||
|
||||
|
@ -1176,7 +1176,7 @@ test: biba/high</screen>
|
|||
|
||||
<para>Die eigentliche Konfiguration der <literal>mac_portacl</literal>
|
||||
Richtlinie wird der <command>sysctl</command>-Variablen
|
||||
<literal>security.mac.portacl.rules</literal> als Zeichenkette der Form
|
||||
<literal>security.mac.portacl.rules</literal> als Zeichenkette der Form
|
||||
<literal>rule[,rule,...]</literal> übergeben. Jede einzelne Regel
|
||||
hat die Form <literal>idtype:id:protocol:port</literal>. Der Parameter
|
||||
<parameter>idtype</parameter> ist entweder <literal>uid</literal> oder
|
||||
|
@ -1188,7 +1188,7 @@ test: biba/high</screen>
|
|||
<literal>udp</literal> setzt). Und der letzte Parameter,
|
||||
<parameter>port</parameter>, enthält die Nummer des Ports, auf den
|
||||
der angegebene Nutzer bzw. die angegebene Gruppe Zugriff erhalten
|
||||
soll.</para>
|
||||
soll.</para>
|
||||
|
||||
<note>
|
||||
<para>Da der Regelsatz direkt vom Kernel ausgewertet wird, können
|
||||
|
@ -1201,10 +1201,10 @@ test: biba/high</screen>
|
|||
privilegierten Prozessen vorbehalten, müssen also mit als/von
|
||||
<username>root</username> gestartet werden und weiterhin laufen. Damit
|
||||
&man.mac.portacl.4; die Vergabe von Ports kleiner als 1024 an nicht
|
||||
privilegierte Prozesse übernehmen kann, muß die &unix;
|
||||
privilegierte Prozesse übernehmen kann, muß die &unix;
|
||||
Standardeinstellung deaktiviert werden. Dazu ändert man die
|
||||
&man.sysctl.8; Variablen
|
||||
<literal>net.inet.ip.portrange.reservedlow</literal> und
|
||||
<literal>net.inet.ip.portrange.reservedlow</literal> und
|
||||
<literal>net.inet.ip.portrange.reservedhigh</literal> auf den Wert
|
||||
<quote>0</quote>.</para>
|
||||
|
||||
|
@ -1229,7 +1229,7 @@ test: biba/high</screen>
|
|||
<literal>security.mac.portacl.suser_exempt</literal> auf einen Wert
|
||||
ungleich Null. Das Modul &man.mac.portacl.4; ist nun so eingerichtet,
|
||||
wie es &unix;-artige Betriebssysteme normal ebenfalls tun.</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>sysctl security.mac.portacl.rules=uid:80:tcp:80</userinput></screen>
|
||||
|
||||
<para>Nun erlauben wir dem Nutzer mit der <acronym>UID</acronym> 80,
|
||||
|
@ -1240,7 +1240,7 @@ test: biba/high</screen>
|
|||
<screen>&prompt.root; <userinput>sysctl security.mac.portacl.rules=uid:1001:tcp:110,uid:1001:tcp:995</userinput></screen>
|
||||
|
||||
<para>Hier wird dem Nutzer mit der <acronym>UID</acronym> 1001 erlaubt,
|
||||
die <acronym>TCP</acronym> Ports 110 (<quote>pop3</quote>) und 995
|
||||
die <acronym>TCP</acronym> Ports 110 (<quote>pop3</quote>) und 995
|
||||
(<quote>pop3s</quote>) zu verwenden. Dadurch kann dieser Nutzer einen
|
||||
Server starten, der Verbindungen an diesen beiden Ports annehmen
|
||||
kann.</para>
|
||||
|
@ -1290,14 +1290,14 @@ test: biba/high</screen>
|
|||
Partition zugreifen. Das bedeutet unter anderem, das ein Nutzer, der
|
||||
einer Klasse <literal>insecure</literal> zugeordnet ist, nicht auf das
|
||||
Kommando <command>top</command> zugreifen kann - wie auch auf viele
|
||||
anderen Befehle, die einen eigenen Prozeß erzeugen.</para>
|
||||
anderen Befehle, die einen eigenen Prozeß erzeugen.</para>
|
||||
|
||||
<para>Um einen Befehl einer Prozeß-Partition zuzuordnen, muß
|
||||
dieser durch das Kommando <command>setpmac</command> mit einem Label
|
||||
versehen werden:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>setpmac partition/13 top</userinput></screen>
|
||||
|
||||
|
||||
<para>Diese Zeile fügt das Kommando <command>top</command> dem
|
||||
Labelsatz für Nutzer der Klasse <literal>insecure</literal> hinzu,
|
||||
sofern die Partition 13 mit der Klasse <literal>insecure</literal>
|
||||
|
@ -1392,7 +1392,7 @@ test: biba/high</screen>
|
|||
<listitem>
|
||||
<para>Das Label <literal>mls/high</literal> verkörpert das
|
||||
höchstmögliche Freigabe-Level. Objekte, denen dieses Label
|
||||
zugeordnet wird, dominieren alle anderen Objekte des Systems.
|
||||
zugeordnet wird, dominieren alle anderen Objekte des Systems.
|
||||
Trotzdem können sie Objekten mit einem niedrigeren
|
||||
Freigabe-Level keine Informationen zuspielen.</para>
|
||||
</listitem>
|
||||
|
@ -1512,7 +1512,7 @@ test: biba/high</screen>
|
|||
<para>Ein Dateiserver, der vertrauliche Informationen einer Firma
|
||||
oder eines Konzerns speichert</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Umgebungen in Finanzeinrichtungen</para>
|
||||
</listitem>
|
||||
|
@ -1538,21 +1538,21 @@ test: biba/high</screen>
|
|||
<para>Bootparameter: <literal>mac_biba_load="YES"</literal></para>
|
||||
|
||||
<para>Das Modul &man.mac.biba.4; lädt die <acronym>MAC</acronym> Biba
|
||||
Richtlinie. Diese ähnelt stark der <acronym>MLS</acronym>
|
||||
Richtlinie. Diese ähnelt stark der <acronym>MLS</acronym>
|
||||
Richtlinie, nur das die Regeln für den Informationsfluß ein
|
||||
wenig vertauscht sind. Es wird in diesem Fall der absteigende Fluß
|
||||
sicherheitskritischer Information geregelt, während die
|
||||
sicherheitskritischer Information geregelt, während die
|
||||
<acronym>MLS</acronym> Richtlinie den aufsteigenden Fluß regelt.
|
||||
In gewissen Sinne treffen dieses und das vorangegangene Unterkapitel also
|
||||
auf beide Richtlinien zu.</para>
|
||||
|
||||
<para>In einer Biba-Umgebung wird jedem Subjekt und jedem Objekt ein
|
||||
<para>In einer Biba-Umgebung wird jedem Subjekt und jedem Objekt ein
|
||||
<quote>Integritäts</quote>-Label zugeordnet. Diese Labels sind in
|
||||
hierarchischen Klassen und nicht-hierarchischen Komponenten geordnet. Je
|
||||
höher die Klasse, um so höher die Integrität.</para>
|
||||
|
||||
<para>Die unterstützten Labels heißen
|
||||
<literal>biba/low</literal>, <literal>biba/equal</literal> und
|
||||
<literal>biba/low</literal>, <literal>biba/equal</literal> und
|
||||
<literal>biba/high</literal>. Sie werden im Folgenden
|
||||
erklärt:</para>
|
||||
|
||||
|
@ -1613,7 +1613,7 @@ test: biba/high</screen>
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><literal>security.mac.biba.enabled</literal> zum
|
||||
<para><literal>security.mac.biba.enabled</literal> zum
|
||||
Aktivieren/Deaktivieren der Richtlinie auf dem Zielsystem.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -1643,7 +1643,7 @@ test: biba/low</screen>
|
|||
|
||||
<para>Integrität garantiert, im Unterschied zu Sensitivität,
|
||||
dass Informationen nur durch vertraute Parteien verändert werden
|
||||
können. Dies schließt Informationen ein, die zwischen
|
||||
können. Dies schließt Informationen ein, die zwischen
|
||||
Subjekten ausgetauscht werden, zwischen Objekt, oder auch zwischen den
|
||||
beiden. Durch Integrität wird gesichert, das Nutzer nur
|
||||
Informationen verändern, oder gar nur lesen können, die sie
|
||||
|
@ -1664,7 +1664,7 @@ test: biba/low</screen>
|
|||
<literal>biba/high</literal> sobald das Modul aktiviert wird - und
|
||||
es liegt allein am Administrator, die verschiedenen Klassen und Stufen
|
||||
für die einzelnen Nutzer zu konfigurieren. Anstatt mit Freigaben
|
||||
zu arbeiten, wie weiter oben gezeigt wurde, könnte man auch
|
||||
zu arbeiten, wie weiter oben gezeigt wurde, könnte man auch
|
||||
Überbegriffe für Projekte oder Systemkomponenten entwerfen.
|
||||
Zum Beispiel, ausschließlich Entwicklern den Vollzugriff auf
|
||||
Quellcode, Compiler und Entwicklungswerkzeuge gewähren,
|
||||
|
@ -1695,13 +1695,13 @@ test: biba/low</screen>
|
|||
</indexterm>
|
||||
<para>Modulname: <filename>mac_lomac.ko</filename></para>
|
||||
|
||||
<para>Parameter für die Kernelkonfiguration:
|
||||
<para>Parameter für die Kernelkonfiguration:
|
||||
<literal>options MAC_LOMAC</literal></para>
|
||||
|
||||
<para>Bootparameter: <literal>mac_lomac_load="YES"</literal></para>
|
||||
<para>Bootparameter: <literal>mac_lomac_load="YES"</literal></para>
|
||||
|
||||
<para>Anders als die Biba Richtlinie erlaubt die &man.mac.lomac.4;
|
||||
Richtlinie den Zugriff auf Objekte niedrigerer Integrität nur,
|
||||
Richtlinie den Zugriff auf Objekte niedrigerer Integrität nur,
|
||||
nachdem das Integritätslevel gesenkt wurde. Dadurch wird eine
|
||||
Störung derIntegritätsregeln verhindert.</para>
|
||||
|
||||
|
@ -1719,7 +1719,7 @@ test: biba/low</screen>
|
|||
Integritätslabeln, die Subjekten das Lesen von Objekten niedriger
|
||||
Integrität gestatten und dann das Label des Subjektes herunterstufen
|
||||
- um zukünftige Schreibvorgänge auf Objekte hoher
|
||||
Integrität zu unterbinden. Dies ist die Funktion der Option
|
||||
Integrität zu unterbinden. Dies ist die Funktion der Option
|
||||
<literal>[auxgrade]</literal>, die eben vorgestellt wurde. Durch sie
|
||||
erhält diese Richtlinie eine bessere Kompatibilität und die
|
||||
Initialisierung ist weniger aufwändig als bei der Richtlinie
|
||||
|
@ -1727,7 +1727,7 @@ test: biba/low</screen>
|
|||
<sect2>
|
||||
|
||||
<title>Beispiele</title>
|
||||
|
||||
|
||||
<para>Wie schon bei den Richtlinien Biba und <acronym>MLS</acronym>
|
||||
werden die Befehle <command>setfmac</command> und
|
||||
<command>setpmac</command> verwendet, um die Labels an den
|
||||
|
@ -1836,14 +1836,14 @@ mac_seeotheruids_load="YES"</programlisting>
|
|||
<screen>&prompt.root; <userinput>for x in `awk -F: '($3 >= 1001) && ($3 != 65534) { print $1 }' \</userinput>
|
||||
<userinput>/etc/passwd`; do pw usermod $x -L default; done;</userinput></screen>
|
||||
|
||||
<para>Verschieben Sie die Nutzer <username>nagios</username> und
|
||||
<para>Verschieben Sie die Nutzer <username>nagios</username> und
|
||||
<username>www</username> in die <literal>insecure</literal>
|
||||
Klasse:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pw usermod nagios -L insecure</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Die Kontextdatei erstellen</title>
|
||||
|
||||
|
@ -1927,7 +1927,7 @@ default_labels socket ?biba
|
|||
<programlisting>security.mac.biba.trust_all_interfaces=1</programlisting>
|
||||
|
||||
<para>Und das Folgende gehört in Datei <filename>rc.conf</filename>
|
||||
zu den Optionen für die Netzwerkkarte. Falls die
|
||||
zu den Optionen für die Netzwerkkarte. Falls die
|
||||
Netzwerkverbindung(-en) via <acronym>DHCP</acronym>
|
||||
konfiguriert werden, muß man dies nach jedem Systemstart
|
||||
eigenhändig nachtragen:</para>
|
||||
|
@ -1954,7 +1954,7 @@ default_labels socket ?biba
|
|||
|
||||
<para>Wenn alles gut aussieht, können
|
||||
<application>Nagios</application>,
|
||||
<application>Apache</application> und
|
||||
<application>Apache</application> und
|
||||
<application>Sendmail</application> gestartet werden - allerdings auf
|
||||
eine Weise, die unserer Richtlinie gerecht wird. Zum Beispiel durch die
|
||||
folgenden Kommandos:</para>
|
||||
|
@ -1978,7 +1978,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
|
||||
<para>Um dies zu vermeiden, werden die Nutzer durch &man.login.conf.5;
|
||||
eingeschränkt. Wenn &man.setpmac.8; einen Befehl
|
||||
außerhalb der definierten Schranken ausführen soll, wird
|
||||
außerhalb der definierten Schranken ausführen soll, wird
|
||||
ein Fehler zurückgeliefert. In so einem Fall muß
|
||||
<username>root</username> auf <literal>biba/high(high-high)</literal>
|
||||
gesetzt werden.</para>
|
||||
|
@ -2033,7 +2033,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
|
||||
<note>
|
||||
<para>Wenn ein neuer Benutzer hinzugefügt wird, ist für diesen
|
||||
zunächst keine &man.mac.bsdextended.4; Regel im Regelsatz
|
||||
zunächst keine &man.mac.bsdextended.4; Regel im Regelsatz
|
||||
vorhanden. Schnelle Abhilfe schafft hier, einfach das Kernelmodul mit
|
||||
&man.kldunload.8; zu entladen und mit &man.kldload.8; erneut
|
||||
einzubinden.</para>
|
||||
|
@ -2062,8 +2062,8 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
dieser Fehler auftritt - er kann mit folgender Prozedur behoben
|
||||
werden:</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Öffnen Sie die Datei <filename>/etc/fstab</filename> und
|
||||
setzen Sie die Rootpartition auf <option>ro</option> wie
|
||||
<quote>read-only</quote>.</para>
|
||||
|
@ -2095,8 +2095,8 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
<command>mount</command> um sich zu versichern, dass die
|
||||
<option>multilabel</option> korrekt für das root-Dateisystem
|
||||
gesetzt wurde.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
@ -2121,7 +2121,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
<step>
|
||||
<para>Gehen Sie die Label-Richtlinien Schritt für Schritt
|
||||
nocheinmal durch. Achten Sie darauf, dass für den Nutzer, bei
|
||||
dem das Problem auftritt, für X11 und das Verzeichnis
|
||||
dem das Problem auftritt, für X11 und das Verzeichnis
|
||||
<filename class="directory">/dev</filename> alle Einstellungen
|
||||
korrekt sind.</para>
|
||||
</step>
|
||||
|
@ -2131,11 +2131,11 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
Fehlermeldung und eine Beschreibung ihrer Arbeitsumgebung an die
|
||||
(englisch-sprachige) TrustedBSD Diskussionsliste auf der <ulink
|
||||
url="http://www.TrustedBSD.org">TrustedBSD</ulink> Webseite oder an
|
||||
die &a.questions; Mailingliste.</para>
|
||||
die &a.questions; Mailingliste.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Error: &man..secure.path.3; cannot stat
|
||||
<filename>.login_conf</filename></title>
|
||||
|
@ -2157,7 +2157,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
nicht, da das Label sich nicht ändert. Hier haben wir also einen
|
||||
Fall, in dem das Gewährleistungsmodell von Biba verhindert, das
|
||||
der Superuser Objekte einer niedrigeren Integrität betrachten
|
||||
kann.</para>
|
||||
kann.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
|
@ -407,7 +407,7 @@ kld snd_ich (1p/2r/0v channels duplex default)</screen>
|
|||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
|
||||
|
||||
<para>Ein weiterer Fall ist der, dass moderne Graphikkarten oft auch
|
||||
ihre eigenen Soundtreiber mit sich führen, um
|
||||
<acronym>HDMI</acronym> oder ähnliches zu verwenden. Diese
|
||||
|
@ -444,16 +444,16 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digital> at cad 2 nid 1 on hdac1
|
|||
<literal>hw.snd.default_unit</literal> auf die Einheit,
|
||||
welche für das Abspielen benutzt werden soll, wie
|
||||
folgt:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>sysctl hw.snd.default_unit=<replaceable>n</replaceable></userinput></screen>
|
||||
|
||||
|
||||
<para>Hier repräsentiert <literal>n</literal> die Nummer
|
||||
der Soundkarte, die verwendet werden soll, in diesem Beispiel
|
||||
also <literal>4</literal>. Sie können diese
|
||||
Änderung dauerhaft machen, indem Sie die folgende Zeile
|
||||
zu der <filename>/etc/sysctl.conf</filename> Datei
|
||||
hinzufügen:</para>
|
||||
|
||||
|
||||
<programlisting>hw.snd.default_unit=<replaceable>4</replaceable></programlisting>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
@ -1675,7 +1675,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
|
|||
werden, weil <application>webcamd</application> eine
|
||||
<acronym role="Video for Linux">V4L</acronym>-Anwendung zur
|
||||
Verfügung stellt, die als Benutzerprogramm läft. Jede
|
||||
<acronym role="Digital Video Broadcasting">DVB</acronym>-Karte,
|
||||
<acronym role="Digital Video Broadcasting">DVB</acronym>-Karte,
|
||||
welche von <application>webcamd</application> unterstützt
|
||||
wird, sollte mit MythTV funktionieren, jedoch gibt es eine Liste
|
||||
von Karten, die <ulink
|
||||
|
@ -1695,7 +1695,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
|
|||
|
||||
<sect2>
|
||||
<title>Abhängigkeiten</title>
|
||||
|
||||
|
||||
<para>Da MythTV flexibel und modular aufgebaut ist, ist der Benutzer
|
||||
in der Lage, das Frontend und Backend auf unterschiedlichen
|
||||
Rechnern laufen zu lassen.</para>
|
||||
|
@ -1723,7 +1723,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
|
|||
<title>MythTV einrichten</title>
|
||||
|
||||
<para>Um MythTV zu installieren, befolgen Sie die hier
|
||||
aufgeführten Schritte. Zuerst installieren Sie MythTV aus
|
||||
aufgeführten Schritte. Zuerst installieren Sie MythTV aus
|
||||
der Ports-Sammlung:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/multimedia/mythtv</userinput>
|
||||
|
|
|
@ -2916,7 +2916,7 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
|
|||
<firstterm>asynchron</firstterm>. Andere Startskripte laufen
|
||||
weiter, während DHCP fertig abgearbeitet wird, was den
|
||||
Systemstart beschleunigt.</para>
|
||||
|
||||
|
||||
<para>DHCP im Hintergrund funktioniert gut, wenn der DHCP-Server
|
||||
schnell auf Anfragen antwortet und der
|
||||
DHCP-Konfigurationsprozess ebenso schnell abläuft.
|
||||
|
@ -2927,21 +2927,21 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
|
|||
<firstterm>asynchronen</firstterm>-Modus wird das Problem
|
||||
verhindert, so dass die Startskripte pausiert werden, bis
|
||||
die DHCP-Konfiguration abgeschlossen ist.</para>
|
||||
|
||||
|
||||
<para>Um sich zu einem DHCP-Server im Hintergrund zu verbinden,
|
||||
während andere Startskripte fortfahren
|
||||
(asynchroner Modus), benutzen Sie den
|
||||
<quote><literal>DHCP</literal></quote>-Wert in
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
|
||||
<programlisting>ifconfig_<replaceable>fxp0</replaceable>="DHCP"</programlisting>
|
||||
|
||||
<para>Um den Start zu pausieren, damit DHCP vorher
|
||||
abgeschlossen werden kann, benutzen Sie den synchronen Modus
|
||||
mit dem Eintrag
|
||||
<quote><literal>SYNCDHCP</literal></quote>:</para>
|
||||
|
||||
<programlisting>ifconfig_<replaceable>fxp0</replaceable>="SYNCDHCP"</programlisting>
|
||||
|
||||
<programlisting>ifconfig_<replaceable>fxp0</replaceable>="SYNCDHCP"</programlisting>
|
||||
|
||||
<note>
|
||||
<para>Ersetzen Sie <replaceable>fxp0</replaceable>, das
|
||||
|
@ -3749,7 +3749,7 @@ zone "." { type hint; file "/etc/namedb/named.root"; };
|
|||
|
||||
To use this mechanism, uncomment the entries below, and comment
|
||||
the hint zone above.
|
||||
|
||||
|
||||
As documented at http://dns.icann.org/services/axfr/ these zones:
|
||||
"." (the root), ARPA, IN-ADDR.ARPA, IP6.ARPA, and ROOT-SERVERS.NET
|
||||
are availble for AXFR from these servers on IPv4 and IPv6:
|
||||
|
@ -4264,7 +4264,7 @@ www IN CNAME example.org.</programlisting>
|
|||
<primary>BIND</primary>
|
||||
<secondary>DNS security extensions</secondary>
|
||||
</indexterm>
|
||||
|
||||
|
||||
<para>Domain Name System Security Extensions, oder kurz <acronym
|
||||
role="Domain Name Security Extensions">DNSSEC</acronym>, ist eine
|
||||
Sammlung von Spezifikationen, um auflösende Nameserver von
|
||||
|
@ -4290,7 +4290,7 @@ www IN CNAME example.org.</programlisting>
|
|||
<acronym>DNSSEC</acronym> sind die dazugehörigen
|
||||
<acronym>RFC</acronym>s ein guter Einstieg in die Thematik. Sehen
|
||||
Sie sich dazu die Liste in <xref linkend="dns-read"/> an.</para>
|
||||
|
||||
|
||||
<para>Der folgende Abschnitt wird zeigen, wie man
|
||||
<acronym>DNSSEC</acronym> für einen autoritativen
|
||||
<acronym>DNS</acronym>-Server und einen rekursiven (oder cachenden)
|
||||
|
@ -4310,10 +4310,10 @@ www IN CNAME example.org.</programlisting>
|
|||
automatisch Zonen signieren zu lassen und Signaturen aktuell zu
|
||||
halten. Unterschiede zwischen den Versionen 9.6.2 und 9.7 und
|
||||
höher werden an den betreffenden Stellen angesprochen.</para>
|
||||
|
||||
|
||||
<sect3>
|
||||
<title>Rekursive <acronym>DNS</acronym>-Server Konfiguration</title>
|
||||
|
||||
|
||||
<para>Die Aktivierung der
|
||||
<acronym>DNSSEC</acronym>-Überprüfung von Anfragen,
|
||||
die von einem rekursiven <acronym>DNS</acronym>-Server
|
||||
|
@ -4328,13 +4328,13 @@ www IN CNAME example.org.</programlisting>
|
|||
durch Abfrage an die Root-Zone erhalten werden, indem man dazu
|
||||
<application>dig</application> verwendet. Durch Aufruf
|
||||
von</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dig +multi +noall +answer DNSKEY . > root.dnskey</userinput></screen>
|
||||
|
||||
|
||||
<para>wird der Schlüssel in
|
||||
<filename>root.dnskey</filename> abgelegt. Der Inhalt sollte
|
||||
so ähnlich wie folgt aussehen:</para>
|
||||
|
||||
|
||||
<programlisting>. 93910 IN DNSKEY 257 3 8 (
|
||||
AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQ
|
||||
bSEW0O8gcCjFFVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh
|
||||
|
@ -4368,7 +4368,7 @@ www IN CNAME example.org.</programlisting>
|
|||
role="Zone Signing Key">ZSK</acronym>) bezeichnet. Weitere
|
||||
Schlüsselarten werden später in <xref
|
||||
linkend="dns-dnssec-auth"/> erläutert.</para>
|
||||
|
||||
|
||||
<para>Nun muss der Schlüssel verifiziert und so formatiert
|
||||
werden, dass <acronym>BIND</acronym> diesen verwenden kann.
|
||||
Um den Schlüssel zu verifizieren, erzeugen Sie einen
|
||||
|
@ -4377,16 +4377,16 @@ www IN CNAME example.org.</programlisting>
|
|||
Datei, welche die <acronym
|
||||
role="Resource Record">RR</acronym>s enthält,
|
||||
mittels</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dnssec-dsfromkey -f root-dnskey . > root.ds</userinput></screen>
|
||||
|
||||
|
||||
<para>Diese Einträge verwenden SHA-1 sowie SHA-256 und
|
||||
sollten ähnlich zu folgendem Beispiel aussehen, in dem
|
||||
der längere, SHA-256, benutzt wird.</para>
|
||||
|
||||
|
||||
<programlisting>. IN DS 19036 8 1 B256BD09DC8DD59F0E0F0D8541B8328DD986DF6E
|
||||
. IN DS 19036 8 2 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5</programlisting>
|
||||
|
||||
|
||||
<para>Der SHA-256 <acronym>RR</acronym> kann nun mit dem Abriss
|
||||
in <ulink
|
||||
url="https://data.iana.org/root-anchors/root-anchors.xml">https://data.iana.org/root-anchors/root-anchors.xml</ulink> verglichen werden. Um
|
||||
|
@ -4395,7 +4395,7 @@ www IN CNAME example.org.</programlisting>
|
|||
wurde, kann die Datei mittels der <acronym>PGP</acronym>
|
||||
Signatur in <ulink
|
||||
url="https://data.iana.org/root-anchors/root-anchors.asc">https://data.iana.org/root-anchors/root-anchors.asc</ulink> überprüft werden.</para>
|
||||
|
||||
|
||||
<para>Als nächstes muss der Schlüssel in das passende
|
||||
Format gebracht werden. Dies unterscheidet sich ein bisschen
|
||||
von den <acronym>BIND</acronym> Versionen 9.6.2 und 9.7 und
|
||||
|
@ -4409,7 +4409,7 @@ www IN CNAME example.org.</programlisting>
|
|||
werden und die Aktualisierung muss händisch erfolgen.
|
||||
In <acronym>BIND</acronym> 9.6.2 sollte das Format
|
||||
folgendermassen aussehen:</para>
|
||||
|
||||
|
||||
<programlisting>trusted-keys {
|
||||
"." 257 3 8
|
||||
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
|
||||
|
@ -4420,10 +4420,10 @@ www IN CNAME example.org.</programlisting>
|
|||
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
|
||||
QxA+Uk1ihz0=";
|
||||
};</programlisting>
|
||||
|
||||
|
||||
<para>In 9.7 wird das Format stattdessen wie folgt
|
||||
aussehen:</para>
|
||||
|
||||
|
||||
<programlisting>managed-keys {
|
||||
"." initial-key 257 3 8
|
||||
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
|
||||
|
@ -4434,7 +4434,7 @@ www IN CNAME example.org.</programlisting>
|
|||
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
|
||||
QxA+Uk1ihz0=";
|
||||
};</programlisting>
|
||||
|
||||
|
||||
<para>Der Root-Schlüssel kann nun zu
|
||||
<filename>named.conf</filename> hinzugefügt werden,
|
||||
entweder direkt oder durch Inkludierung der Datei, die den
|
||||
|
@ -4445,10 +4445,10 @@ www IN CNAME example.org.</programlisting>
|
|||
<filename>named.conf</filename> bearbeitet und die folgende
|
||||
<literal>options</literal>-Direktive hinzugefügt
|
||||
wird:</para>
|
||||
|
||||
|
||||
<programlisting>dnssec-enable yes;
|
||||
dnssec-validation yes;</programlisting>
|
||||
|
||||
|
||||
<para>Um zu prüfen, dass es tatsächlich funktioniert,
|
||||
benutzen Sie <application>dig</application>, um eine Anfrage
|
||||
zu einer signierten Zone durch den Resolver, der gerade
|
||||
|
@ -4456,28 +4456,28 @@ dnssec-validation yes;</programlisting>
|
|||
wird den <literal>AD</literal>-Eintrag aufweisen, um
|
||||
anzudeuten, dass die Daten authentisiert sind. Eine Anfrage
|
||||
wie</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dig @<replaceable>resolver</replaceable> +dnssec se ds </userinput></screen>
|
||||
|
||||
|
||||
<para>sollte den <acronym>DS</acronym> <acronym>RR</acronym>
|
||||
für die <literal>.se</literal>-Zone zurückgeben. In
|
||||
dem Abschnitt <literal>flags:</literal> sollte der
|
||||
<literal>AD</literal>-Eintrag gesetzt sein, wie im folgenden
|
||||
zu sehen ist:</para>
|
||||
|
||||
|
||||
<programlisting>...
|
||||
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
|
||||
...</programlisting>
|
||||
|
||||
|
||||
<para>Der Resolver ist nun in der Lage, Anfragen ans
|
||||
<acronym>DNS</acronym> zu authentisieren.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
|
||||
<sect3 id="dns-dnssec-auth">
|
||||
<title>Autoritative <acronym>DNS</acronym>-Server
|
||||
Konfiguration</title>
|
||||
|
||||
|
||||
<para>Um einen autoritativen Nameserver dazu zu bringen, als
|
||||
eine <acronym>DNSSEC</acronym>-signierte Zone zu fungieren,
|
||||
ist ein wenig mehr Aufwand nötig. Eine Zone ist durch
|
||||
|
@ -4513,7 +4513,7 @@ dnssec-validation yes;</programlisting>
|
|||
role="Zone Signing Key">ZSK</acronym> wird verwendet, um die
|
||||
Zone zu signieren und muss nur dort öffentlich
|
||||
zugänglich gemacht werden.</para>
|
||||
|
||||
|
||||
<para>Um <acronym>DNSSEC</acronym> für die <hostid
|
||||
role="domainname">example.com</hostid>-Zone, welche in den
|
||||
vorherigen Beispielen verwendet wird, zu aktivieren, muss
|
||||
|
@ -4527,14 +4527,14 @@ dnssec-validation yes;</programlisting>
|
|||
Um den <acronym>KSK</acronym> für <hostid
|
||||
role="domainname">example.com</hostid> zu generieren, geben
|
||||
Sie</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dnssec-keygen -f KSK -a RSASHA256 -b 2048 -n ZONE example.com</userinput></screen>
|
||||
|
||||
|
||||
<para>ein und um den <acronym>ZSK</acronym> zu erzeugen, setzen
|
||||
Sie folgenden Befehl ab:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dnssec-keygen -a RSASHA256 -b 2048 -n ZONE example.com</userinput></screen>
|
||||
|
||||
|
||||
<para><application>dnssec-keygen</application> gibt zwei
|
||||
Dateien aus, den öffentlichen und den privaten
|
||||
Schlüssel und zwar in Dateinamen, die ähnlich
|
||||
|
@ -4548,31 +4548,31 @@ dnssec-validation yes;</programlisting>
|
|||
Schlüssel in einer Zone vorliegen. Es ist auch
|
||||
möglich, die Schlüssel umzubenennen. Für
|
||||
jede <acronym>KSK</acronym>-Datei tun Sie folgendes:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>mv Kexample.com.+005+nnnnn.key Kexample.com.+005+nnnnn.KSK.key</userinput>
|
||||
&prompt.user; <userinput>mv Kexample.com.+005+nnnnn.private Kexample.com.+005+nnnnn.KSK.private</userinput></screen>
|
||||
|
||||
|
||||
<para>Für die <acronym>ZSK</acronym>-Dateien ersetzen Sie
|
||||
<literal>KSK</literal> für <literal>ZSK</literal> wenn
|
||||
nötig. Die Dateien können nun in der Zonendatei
|
||||
inkludiert werden, indem die <literal>$include</literal>
|
||||
Anweisung verwendet wird. Es sollte folgendermassen
|
||||
aussehen:</para>
|
||||
|
||||
|
||||
<programlisting>$include Kexample.com.+005+nnnnn.KSK.key ; KSK
|
||||
$include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
|
||||
|
||||
|
||||
<para>Schliesslich signieren Sie die Zone und weisen
|
||||
<acronym>BIND</acronym> an, die signierte Zonendatei zu
|
||||
benutzen. Um eine Zone zu signieren, wird
|
||||
benutzen. Um eine Zone zu signieren, wird
|
||||
<application>dnssec-signzone</application> eingesetzt. Der
|
||||
Befehl, um eine Zone <hostid
|
||||
role="domainname">example.com</hostid> zu signieren, die in
|
||||
<filename>example.com.db</filename> liegt, sollte
|
||||
wie folgt aussehen:</para>
|
||||
|
||||
|
||||
<screen>&prompt.user; <userinput>dnssec-signzone -o example.com -k Kexample.com.+005+nnnnn.KSK example.com.db Kexample.com.+005+nnnnn.ZSK.key</userinput></screen>
|
||||
|
||||
|
||||
<para>Der Schlüssel, welcher mit dem Argument
|
||||
<option>-k</option> übergeben wird, ist der
|
||||
<acronym>KSK</acronym> und die andere Schlüsseldatei ist
|
||||
|
@ -4601,7 +4601,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
|
|||
zwischenspeichern. Es ist möglich, ein Skript und einen
|
||||
cron-Job zu schreiben, um dies zu erledigen. Lesen Sie dazu
|
||||
die relevanten Anleitungen, um Details zu erfahren.</para>
|
||||
|
||||
|
||||
<para>Stellen Sie sicher, dass die privaten Schlüssel
|
||||
vertraulich bleiben, genau wie mit allen anderen
|
||||
kryptographischen Schlüsseln auch. Wenn ein
|
||||
|
@ -4621,11 +4621,11 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
|
|||
url="http://www.ietf.org/rfc/rfc4641.txt"><acronym>RFC</acronym>
|
||||
4641: <acronym>DNSSEC</acronym> Operational practices</ulink>.</para>
|
||||
</sect3>
|
||||
|
||||
|
||||
<sect3>
|
||||
<title>Automatisierung mittels <acronym>BIND</acronym> 9.7 oder
|
||||
höher</title>
|
||||
|
||||
|
||||
<para>Beginnend mit der Version 9.7 von <acronym>BIND</acronym>
|
||||
wurde eine neue Eigenschaft vorgestellt, die
|
||||
<emphasis>Smart Signing</emphasis> genannt wird. Diese zielt
|
||||
|
@ -4648,15 +4648,15 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
|
|||
role="domainname">example.com</hostid> zu nutzen, fügen
|
||||
Sie die folgenden Zeilen zur <filename>named.conf</filename>
|
||||
hinzu:</para>
|
||||
|
||||
|
||||
<programlisting>zone example.com {
|
||||
type master;
|
||||
key-directory "/etc/named/keys";
|
||||
update-policy local;
|
||||
auto-dnssec maintain;
|
||||
file "/etc/named/dynamic/example.com.zone";
|
||||
};</programlisting>
|
||||
|
||||
};</programlisting>
|
||||
|
||||
<para>Nachdem diese Änderungen durchgeführt wurden,
|
||||
erzeugen Sie die Schlüssel für die Zone wie in
|
||||
<xref linkend="dns-dnssec-auth"/> beschrieben wird, legen
|
||||
|
@ -4774,7 +4774,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
|
|||
<para><ulink url="http://tools.ietf.org/html/rfc5011">RFC 5011
|
||||
- Automated Updates of DNS Security (<acronym>DNSSEC</acronym>)
|
||||
Trust Anchors</ulink></para>
|
||||
</listitem>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
|
@ -64,7 +64,7 @@
|
|||
Installation von &os; in verschiedenen
|
||||
Virtualisierungs-Programmen.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para><xref linkend="bsdinstall"/>,
|
||||
&os; 9.<replaceable>x</replaceable> (und neuer) installieren,
|
||||
|
|
|
@ -1,14 +1,14 @@
|
|||
<?xml version="1.0" encoding="ISO8859-1"?>
|
||||
<!--
|
||||
Creates entities for each .txt screenshot that is included in the
|
||||
<!--
|
||||
Creates entities for each .txt screenshot that is included in the
|
||||
Handbook.
|
||||
|
||||
Each entity is named txt.dir.foo, where dir is the directory in
|
||||
which it is stored, and foo is its filename, without the '.txt'
|
||||
which it is stored, and foo is its filename, without the '.txt'
|
||||
extension.
|
||||
|
||||
Entities should be listed in alphabetical order.
|
||||
|
||||
|
||||
$FreeBSD$
|
||||
$FreeBSDde: de-docproj/books/handbook/txtfiles.ent,v 1.2 2009/11/26 17:47:10 bcr Exp $
|
||||
basiert auf: 1.4
|
||||
|
|
|
@ -1065,14 +1065,14 @@ teamtwo:*:1100:jru</screen>
|
|||
<filename>/etc/passwd</filename> zu lesen.</para>
|
||||
|
||||
<example>
|
||||
<title>Hinzufügen eines neuen Gruppenmitglieds mittels
|
||||
<title>Hinzufügen eines neuen Gruppenmitglieds mittels
|
||||
&man.pw.8;</title>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>pw groupmod teamtwo -m db</userinput>
|
||||
&prompt.root; <userinput>pw groupshow teamtwo</userinput>
|
||||
teamtwo:*:1100:jru,db</screen>
|
||||
</example>
|
||||
|
||||
|
||||
<para>Die Argumente zur Option <option>-m</option> ist eine durch Komma
|
||||
getrennte Liste von Benutzern, die der Gruppe hinzugefügt werden
|
||||
sollen. Anders als im vorherigen Beispiel werden diese Benutzer in die
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
<head>
|
||||
<meta http-equiv="refresh" content="5;url=&base;/index.html"/>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
|
||||
|
||||
|
||||
<title>&title;</title>
|
||||
|
||||
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
|
||||
|
|
|
@ -484,7 +484,7 @@
|
|||
<day>
|
||||
<name>30</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:mezz@FreeBSD.org">Jeremy Messenger</a>
|
||||
(ports)</p>
|
||||
</event>
|
||||
|
@ -493,7 +493,7 @@
|
|||
<day>
|
||||
<name>19</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:tackerman@FreeBSD.org">Tony Ackerman</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -502,7 +502,7 @@
|
|||
<day>
|
||||
<name>17</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:marius@FreeBSD.org">Marius Strobl</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -511,7 +511,7 @@
|
|||
<day>
|
||||
<name>5</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:dhartmei@FreeBSD.org">Daniel Hartmeier</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -599,7 +599,7 @@
|
|||
<day>
|
||||
<name>26</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:vkashyap@FreeBSD.org">Vinod Kashyap</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -633,7 +633,7 @@
|
|||
<day>
|
||||
<name>17</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:rees@FreeBSD.org">Jim Rees</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -642,7 +642,7 @@
|
|||
<day>
|
||||
<name>15</name>
|
||||
<event>
|
||||
<p>Core-Mitglied zurückgetreten: <a
|
||||
<p>Core-Mitglied zurückgetreten: <a
|
||||
href="mailto:grog@FreeBSD.org">Greg Lehey</a> </p>
|
||||
</event>
|
||||
</day>
|
||||
|
@ -650,7 +650,7 @@
|
|||
<day>
|
||||
<name>10</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:mlaier@FreeBSD.org">Max Laier</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -659,13 +659,13 @@
|
|||
<day>
|
||||
<name>2</name>
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:le@FreeBSD.org">Lukas Ertl</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:pjd@FreeBSD.org">Pawel Jakub Dawidek</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -691,7 +691,7 @@
|
|||
<name>21</name>
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:philip@FreeBSD.org">Philip Paeps</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
|
@ -701,7 +701,7 @@
|
|||
href="mailto:cperciva@FreeBSD.org">Colin Percival</a>
|
||||
(src)</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>15</name>
|
||||
|
|
|
@ -34,7 +34,7 @@
|
|||
derzeit die sichersten Betriebssysteme im Internet sind.</p>
|
||||
</story>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>9</name>
|
||||
|
||||
|
|
|
@ -260,11 +260,11 @@
|
|||
werden.</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>10</name>
|
||||
|
||||
|
||||
<day>
|
||||
<name>30</name>
|
||||
|
||||
|
@ -272,7 +272,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:aaron@FreeBSD.org">Aaron Dalton</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>18</name>
|
||||
|
@ -281,7 +281,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:ariff@FreeBSD.org">Ariff Abdullah</a> (src)</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>11</name>
|
||||
|
@ -297,8 +297,8 @@
|
|||
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">
|
||||
FreeBSD Spiegelseiten</a> vorhanden.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>6</name>
|
||||
|
||||
|
@ -310,8 +310,8 @@
|
|||
argentina.com</a>, beschreibt einen Internetprovider, der in einem
|
||||
umkämpften Markt mit Hilfe von FreeBSD erfolgreich ist.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>5</name>
|
||||
|
||||
|
@ -327,8 +327,8 @@
|
|||
Kommentare und Vorschläge zu den neuen Seiten haben, senden
|
||||
Sie diese bitte an die Mailingliste freebsd-www@FreeBSD.org.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>3</name>
|
||||
|
||||
|
@ -347,8 +347,8 @@
|
|||
href="mailto:az@FreeBSD.org">Andrej Zverev</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>9</name>
|
||||
|
||||
|
@ -359,8 +359,8 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:tmclaugh@FreeBSD.org">Tom McLaughlin</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>15</name>
|
||||
|
||||
|
@ -380,7 +380,7 @@
|
|||
6.0-BETA4-Ankündigung</a>.</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>8</name>
|
||||
|
@ -486,7 +486,7 @@
|
|||
</month>
|
||||
|
||||
<month>
|
||||
|
||||
|
||||
<name>7</name>
|
||||
|
||||
<day>
|
||||
|
@ -639,7 +639,7 @@
|
|||
|
||||
<day>
|
||||
<name>11</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Code Freeze für 6.0-RELEASE</title>
|
||||
|
||||
|
@ -682,7 +682,7 @@
|
|||
|
||||
<day>
|
||||
<name>26</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:thompsa@FreeBSD.org">Andrew Thompson</a> (src)</p>
|
||||
|
@ -759,7 +759,7 @@
|
|||
</day>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<month>
|
||||
<name>4</name>
|
||||
|
||||
<day>
|
||||
|
@ -858,11 +858,11 @@
|
|||
>FreeBSD Spiegelseiten</a> vorhanden.</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<month>
|
||||
<name>3</name>
|
||||
|
||||
|
||||
<day>
|
||||
<name>31</name>
|
||||
|
||||
|
@ -874,7 +874,7 @@
|
|||
|
||||
<day>
|
||||
<name>20</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>FreeBSD 5.4-BETA1 ist verfügbar</title>
|
||||
|
||||
|
@ -906,7 +906,7 @@
|
|||
der
|
||||
<a href="&enbase;/snapshots/index.html">Snapshot-Seite</a>.</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>12</name>
|
||||
|
|
|
@ -92,7 +92,7 @@
|
|||
<p>Ein Vergleich der Betriebssicherheit von Windows(r), Linux und
|
||||
FreeBSD.</p>
|
||||
</story>
|
||||
|
||||
|
||||
<story>
|
||||
<name>A Comparison of Solaris, Linux, and FreeBSD Kernels</name>
|
||||
<url>http://www.opensolaris.org/os/article/2005-10-14_a_comparison_of_solaris__linux__and_freebsd_kernels/</url>
|
||||
|
@ -118,7 +118,7 @@
|
|||
von drahtlosen Geräten.</p>
|
||||
</story>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>9</name>
|
||||
|
||||
|
@ -144,7 +144,7 @@
|
|||
</story>
|
||||
</month>
|
||||
|
||||
|
||||
|
||||
<month>
|
||||
<name>8</name>
|
||||
|
||||
|
@ -155,7 +155,7 @@
|
|||
<site-url>http://www.zdnet.co.uk/</site-url>
|
||||
<date>19. August 2005</date>
|
||||
<author>Ingrid Marson</author>
|
||||
<p>Ein Interview mit Scott Long, dem FreeBSD Release Engineer,
|
||||
<p>Ein Interview mit Scott Long, dem FreeBSD Release Engineer,
|
||||
über das bevorstehende FreeBSD-Release 6.0.</p>
|
||||
</story>
|
||||
</month>
|
||||
|
@ -184,7 +184,7 @@
|
|||
<date>19. Juli 2005</date>
|
||||
<author>Frank Pohlmann</author>
|
||||
<p>Ein kurzer Überblick über die BSD-Familie.</p>
|
||||
</story>
|
||||
</story>
|
||||
|
||||
<story>
|
||||
<name>Project Evil: Windows network drivers on FreeBSD</name>
|
||||
|
@ -194,7 +194,7 @@
|
|||
<date>15. Juli 2005</date>
|
||||
<author>David Chisnall</author>
|
||||
<p>Ein Artikel zur Nutzung von Windows(R)-Netzwerktreibern unter FreeBSD.</p>
|
||||
</story>
|
||||
</story>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
|
@ -264,7 +264,7 @@
|
|||
nun die aktuelle FreeBSD Version 5.4.</p>
|
||||
</story>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>4</name>
|
||||
|
||||
|
@ -277,7 +277,7 @@
|
|||
<author>Ed Hurst</author>
|
||||
<p>Ein Artikel über die Nutzung von FreeBSD 5.4 auf Notebooks.</p>
|
||||
</story>
|
||||
|
||||
|
||||
<story>
|
||||
<name>Large Web Hosting Provider Switches to FreeBSD</name>
|
||||
<url>http://www.w3reports.com/index.php?itemid=869</url>
|
||||
|
@ -336,5 +336,5 @@
|
|||
Core Teams, über die SMPng-Implementierung von FreeBSD.</p>
|
||||
</story>
|
||||
</month>
|
||||
</year>
|
||||
</year>
|
||||
</press>
|
||||
|
|
|
@ -118,7 +118,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:nivit@FreeBSD.org">Nicola Vitale</a> (ports)</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Neuer Committer: <a
|
||||
href="mailto:gabor@FreeBSD.org">Gábor Kövesdán</a>
|
||||
|
@ -557,7 +557,7 @@
|
|||
weitere Informationen lesen Sie bitte die <a
|
||||
href="http://www.freebsdfoundation.org/press/20060705-PRrelease.shtml">
|
||||
Presseerklärung</a> der FreeBSD Foundation.</p>
|
||||
</event>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
@ -902,7 +902,7 @@
|
|||
href="&enbase;/news/status/report-jan-2006-mar-2006.html">
|
||||
verfügbar</a>.</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Summer of Code 2006</title>
|
||||
|
||||
|
|
|
@ -50,7 +50,7 @@
|
|||
<site-url>http://www.openaddict.com/</site-url>
|
||||
<date>08. Dezember 2006</date>
|
||||
<author>Rich Morgan</author>
|
||||
<p>Eine Anleitung zur Konfiguration von FreeBSD 6.1 als
|
||||
<p>Eine Anleitung zur Konfiguration von FreeBSD 6.1 als
|
||||
Server mit Apache, Webmin, PHP 5, MySQL 5.0, Sendmail mit
|
||||
SMTP-AUTH, Bind DNS, SNMP, sowie einem Zeitserver.</p>
|
||||
</story>
|
||||
|
|
|
@ -394,7 +394,7 @@
|
|||
Budget von $ 80.000,-- zur Verfügung. Die
|
||||
eingereichten
|
||||
Projekte werden danach im Hinblick auf Notwendigkeit,
|
||||
technischen Anspruch und Kosteneffektivität evaluiert
|
||||
technischen Anspruch und Kosteneffektivität evaluiert
|
||||
werden.</p>
|
||||
|
||||
<p>Weitere Informationen zu diesem Thema finden Sie in der
|
||||
|
@ -411,7 +411,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:rnoland@FreeBSD.org">Robert Noland</a> (ports)</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:vanhu@FreeBSD.org">Yvan Vanhullebus</a> (src)</p>
|
||||
|
@ -489,7 +489,7 @@
|
|||
Services Division angekündigt, die Enterprise-Level-Support,
|
||||
-Beratung und -Entwicklung für &os; sowie PC-BSD bietet.</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:sson@FreeBSD.org">Stacey Son</a> (src)</p>
|
||||
|
@ -516,7 +516,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:erik@FreeBSD.org">Erik Cederstrand</a> (projects)</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<title>FreeBSD-Technologie in Firefox 3</title>
|
||||
|
||||
|
@ -683,7 +683,7 @@
|
|||
href="http://wiki.FreeBSD.org/SummerOfCode2008">
|
||||
Summer of Code Wiki</a> mit weiteren Informationen.</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:pgj@FreeBSD.org">Gábor Páli</a>
|
||||
|
|
|
@ -133,7 +133,7 @@
|
|||
|
||||
<event>
|
||||
<title>&os; 8.0-RC3 verfügbar</title>
|
||||
|
||||
|
||||
<p>Der dritte Release Candidate des &os;-8.0-Entwicklungszyklusses
|
||||
ist ab sofort <a
|
||||
href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052699.html">verfügbar</a>.
|
||||
|
@ -304,7 +304,7 @@
|
|||
|
||||
<day>
|
||||
<name>7</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 8.0-BETA1 verfügbar</title>
|
||||
|
||||
|
@ -366,7 +366,7 @@
|
|||
Martin und Ion-Mihai alles Gute für ihre neuen Aufgaben.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>3</name>
|
||||
|
||||
|
@ -399,7 +399,7 @@
|
|||
href="mailto:kmoore@FreeBSD.org">Kris Moore</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>23</name>
|
||||
|
||||
|
@ -451,45 +451,45 @@
|
|||
<ul>
|
||||
<li><a href="http://wiki.FreeBSD.org/AdityaSarawgi">Aditya Sarawgi</a>, <a href="http://wiki.FreeBSD.org/SOC2009AdityaSarawgi">Improving
|
||||
Second Extended File system (ext2fs) and making it GPL free</a>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/UlfLilleengen">Ulf Lilleengen</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/UlfLilleengen">Ulf Lilleengen</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/AlejandroPulver">Alejandro Pulver</a>, <em>Ports license
|
||||
infrastructure (part 2: integration)</em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/ErwinLansing">Erwin Lansing</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/ErwinLansing">Erwin Lansing</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/AnaKukec">Ana Kukec</a>, <em>IPv6 Secure Neighbor Discovery
|
||||
- native kernel APIs for FreeBSD</em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/BjoernZeeb">Bjoern Zeeb</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/BjoernZeeb">Bjoern Zeeb</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/DavidForsythe">David Forsythe</a>, <em><a href="http://wiki.FreeBSD.org/SoC2009DavidForsythe">Package
|
||||
tools rewrite via a new package library, with new
|
||||
features</a></em> (Mentor: <a href="http://wiki.FreeBSD.org/TimKientzle">Tim Kientzle</a>)
|
||||
features</a></em> (Mentor: <a href="http://wiki.FreeBSD.org/TimKientzle">Tim Kientzle</a>)
|
||||
</li><li><a class="nonexistent"
|
||||
href="http://wiki.FreeBSD.org/EdwardTomaszNapierala">Edward Tomasz Napierala</a>, <em>Hierarchical
|
||||
Resource Limits</em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/BrooksDavis">Brooks Davis</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/BrooksDavis">Brooks Davis</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/FabioChecconi">Fabio Checconi</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009FabioChecconi">Geom-based
|
||||
Disk Schedulers</a></em> (Mentor: <a class="nonexistent"
|
||||
href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
|
||||
href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/FangWang">Fang Wang</a>, <em>Implement TCP UTO</em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/RuiPaulo">Rui Paulo</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/RuiPaulo">Rui Paulo</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/G%C3%A1borK%C3%B6vesd%C3%A1n">Gábor Kövesdán</a>, <em><a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2009">BSD-licensed
|
||||
libiconv in base system</a></em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/XinLi">Xin Li</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/XinLi">Xin Li</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/GlebKurtsov">Gleb Kurtsov</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009GlebKurtsov">In
|
||||
kernel stackable cryptographic filesystem (pefs)</a></em>
|
||||
(Mentor: <a class="nonexistent"
|
||||
href="http://wiki.FreeBSD.org/StanislavSedov">Stanislav Sedov</a>)
|
||||
href="http://wiki.FreeBSD.org/StanislavSedov">Stanislav Sedov</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/IliasMarinos">Ilias Marinos</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009IliasMarinos">Application-Specific
|
||||
Audit Trails</a></em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/RobertWatson">Robert Watson</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/RobertWatson">Robert Watson</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/MartaCarbone">Marta Carbone</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009MartaCarbone">Ipfw
|
||||
and dummynet improvements</a></em> (Mentor: <a class="nonexistent"
|
||||
href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
|
||||
href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/NikhilBysani">Nikhil Bysani</a>, <em>Porting <a class="nonexistent"
|
||||
href="http://wiki.FreeBSD.org/NetworkManager">NetworkManager</a> to FreeBSD</em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/EdSchouten">Ed Schouten</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/EdSchouten">Ed Schouten</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/P%C3%A1liG%C3%A1borJ%C3%A1nos">Páli Gábor János</a>, <em><a href="http://wiki.FreeBSD.org/PGJSoC2009">Design
|
||||
and Implementation of Subsystem Support Libraries for Monitoring
|
||||
and Management</a></em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/OleksandrTymoshenko">Oleksandr Tymoshenko</a>)
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/OleksandrTymoshenko">Oleksandr Tymoshenko</a>)
|
||||
</li><li><a href="http://wiki.FreeBSD.org/PrashantVaibhav">Prashant Vaibhav</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009PrashantVaibhav">Reworking
|
||||
the callout scheme: towards a tickless kernel</a></em>
|
||||
(Mentor: <a href="http://wiki.FreeBSD.org/EdMaste">Ed Maste</a>)
|
||||
|
@ -528,7 +528,7 @@
|
|||
</event>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<day>
|
||||
<name>7</name>
|
||||
|
||||
<event>
|
||||
|
@ -540,7 +540,7 @@
|
|||
</event>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<day>
|
||||
<name>5</name>
|
||||
|
||||
<event>
|
||||
|
@ -596,7 +596,7 @@
|
|||
|
||||
<event>
|
||||
<title>DCBSDCon-Videos geposted</title>
|
||||
|
||||
|
||||
<p>Alle technischen Vorträge der kürzlich abgehaltenen <a
|
||||
href="http://www.dcbsdcon.org">DCBSDCon 2009</a>-Konferenz wurden
|
||||
aufgezeichnet und sind ab sofort im <a
|
||||
|
@ -725,7 +725,7 @@
|
|||
|
||||
<event>
|
||||
<title>FreeBSD auf Twitter</title>
|
||||
|
||||
|
||||
<p>Auf Twitter gibt es inzwischen eine Anzahl halb-offizieller
|
||||
Streams mit aktuellen Nachrichten zum FreeBSD Project. Der
|
||||
Stream <a
|
||||
|
@ -833,7 +833,7 @@
|
|||
<event>
|
||||
<title>Video "FreeBSD Kernel Internals"
|
||||
veröffentlicht</title>
|
||||
|
||||
|
||||
<p>Die erste Vorlesung von Kirk McKusick's <a
|
||||
href="http://www.youtube.com/watch?v=nwbqBdghh6E">FreeBSD
|
||||
Kernel Internals</a> wurde in voller Länge im <a
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
<head>
|
||||
<meta http-equiv="refresh" content="5;url=&base;/platforms/amd64.html"/>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
|
||||
|
||||
|
||||
<title>&title;</title>
|
||||
|
||||
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
#
|
||||
# $FreeBSD$
|
||||
# $FreeBSDde: de-www/projects/Makefile,v 1.3 2007/08/29 08:47:34 as Exp $
|
||||
# basiert auf: 1.31
|
||||
# basiert auf: 1.31
|
||||
|
||||
.if exists(../Makefile.conf)
|
||||
.include "../Makefile.conf"
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
|
||||
-- ...................................................................... --
|
||||
-- German specific ...................................................... --
|
||||
|
||||
|
||||
-- $FreeBSD$ --
|
||||
-- $FreeBSDde: de-docproj/share/sgml/catalog,v 1.10 2004/11/28 18:16:45 jkois Exp $ --
|
||||
-- basiert auf: 1.5 --
|
||||
|
|
|
@ -10,15 +10,15 @@
|
|||
<!ENTITY % freebsd.l10n PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN">
|
||||
%freebsd.l10n;
|
||||
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.print "IGNORE">
|
||||
]>
|
||||
|
||||
<style-sheet>
|
||||
<style-specification use="docbook">
|
||||
<style-specification-body>
|
||||
|
||||
<![ %output.html; [
|
||||
|
||||
<![ %output.html; [
|
||||
|
||||
(define ($email-footer$)
|
||||
(make sequence
|
||||
|
|
|
@ -50,7 +50,7 @@
|
|||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>7</name>
|
||||
|
||||
|
@ -82,8 +82,8 @@
|
|||
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">&os;
|
||||
Spiegelservern</a> vorhanden.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>11</name>
|
||||
|
||||
|
@ -117,7 +117,7 @@
|
|||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>6</name>
|
||||
|
||||
|
@ -167,11 +167,11 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:tj@FreeBSD.org">Tom Judge</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>12</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport Januar-März 2012</title>
|
||||
|
||||
|
@ -181,7 +181,7 @@
|
|||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>4</name>
|
||||
|
||||
|
@ -268,7 +268,7 @@
|
|||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>3</name>
|
||||
|
||||
|
@ -313,7 +313,7 @@
|
|||
</event>
|
||||
</day>
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>2</name>
|
||||
|
||||
|
@ -376,7 +376,7 @@
|
|||
<p>Neuer Committer: <a
|
||||
href="mailto:davide@FreeBSD.org">Davide Italiano</a> (src)</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport Oktober-Dezember 2011</title>
|
||||
|
||||
|
@ -385,13 +385,13 @@
|
|||
href="&enbase;/news/status/report-2011-10-2011-12.html">verfügbar</a>.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>12</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 9.0-RELEASE verfügbar</title>
|
||||
|
||||
|
||||
<p><a href="&enbase;/releases/9.0R/announce.html">FreeBSD
|
||||
9.0-RELEASE</a> ist verfügbar. Lesen Sie
|
||||
bitte die <a
|
||||
|
@ -408,7 +408,7 @@
|
|||
</day>
|
||||
</month>
|
||||
</year>
|
||||
|
||||
|
||||
<year>
|
||||
<name>2011</name>
|
||||
|
||||
|
@ -444,7 +444,7 @@
|
|||
aktualisieren.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>8</name>
|
||||
|
||||
|
@ -453,7 +453,7 @@
|
|||
href="mailto:pfg@FreeBSD.org">Pedro Giffuni</a> (src)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>2</name>
|
||||
|
||||
|
@ -496,7 +496,7 @@
|
|||
aktualisieren.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>12</name>
|
||||
|
||||
|
@ -734,7 +734,7 @@
|
|||
href="mailto:gavin@FreeBSD.org">Gavin Atkinson</a> (src, doc)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>15</name>
|
||||
|
||||
|
@ -780,7 +780,7 @@
|
|||
|
||||
<event>
|
||||
<title>IPv6-Test-Images für &os;</title>
|
||||
|
||||
|
||||
<p>Die &os; Foundation und iXsystems haben reine
|
||||
IPv6-Test-Images für &os; und PC-BSD <a
|
||||
href="http://www.prweb.com/releases/2011/6/prweb8529718.htm">
|
||||
|
@ -831,10 +831,10 @@
|
|||
|
||||
<month>
|
||||
<name>4</name>
|
||||
|
||||
|
||||
<day>
|
||||
<name>27</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport Januar-März 2011</title>
|
||||
|
||||
|
@ -859,7 +859,7 @@
|
|||
|
||||
<day>
|
||||
<name>27</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Das FreeBSD Project nimmt am Google Summer of
|
||||
Code 2011 teil</title>
|
||||
|
@ -939,7 +939,7 @@
|
|||
|
||||
<event>
|
||||
<title>FreeBSD 8.2-RELEASE verfügbar</title>
|
||||
|
||||
|
||||
<p><a href="&enbase;/releases/8.2R/announce.html">FreeBSD
|
||||
8.2-RELEASE</a> wurde veröffentlicht. Lesen Sie
|
||||
bitte die <a
|
||||
|
@ -1142,7 +1142,7 @@
|
|||
|
||||
<day>
|
||||
<name>27</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport Juli-September 2010 verfügbar</title>
|
||||
|
||||
|
@ -1217,7 +1217,7 @@
|
|||
href="mailto:swills@FreeBSD.org">Steve Wills</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>8</name>
|
||||
|
@ -1248,7 +1248,7 @@
|
|||
href="mailto:ohauer@FreeBSD.org">Oliver Hauer</a> (ports)</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>7</name>
|
||||
|
@ -1295,10 +1295,10 @@
|
|||
|
||||
<day>
|
||||
<name>22</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport April-Juni 2010 verfügbar</title>
|
||||
|
||||
|
||||
<p>Der Statusreport für die Monate April bis Juni 2010
|
||||
mit 47 Einträgen ist ab sofort <a
|
||||
href="&enbase;/news/status/report-2010-04-2010-06.html">verfügbar</a>.</p>
|
||||
|
@ -1335,7 +1335,7 @@
|
|||
|
||||
<day>
|
||||
<name>17</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:tijl@FreeBSD.org">Tijl Coosemans</a> (src)</p>
|
||||
|
@ -1353,7 +1353,7 @@
|
|||
|
||||
<day>
|
||||
<name>14</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Neues &os; Core Team gewählt</title>
|
||||
|
||||
|
@ -1388,20 +1388,20 @@
|
|||
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">&os;
|
||||
Spiegelservern</a> vorhanden. Lesen Sie bitte auch die offizielle <a
|
||||
href="&lists.stable;/2010-July/057552.html">Ankündigung</a>
|
||||
für weitere Informationen zu dieser neuen Version.</p>
|
||||
für weitere Informationen zu dieser neuen Version.</p>
|
||||
</event>
|
||||
</day>
|
||||
</month>
|
||||
</month>
|
||||
|
||||
<month>
|
||||
<name>6</name>
|
||||
|
||||
<day>
|
||||
<name>18</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 8.1-RC1 verfügbar</title>
|
||||
|
||||
|
||||
<p>Der erste Release Candidate aus dem
|
||||
&os;-8.1-Releasezyklus ist nun verfügbar. ISO-Images
|
||||
für Tier-1-Architekturen finden Sie wie immer auf den
|
||||
|
@ -1433,21 +1433,21 @@
|
|||
|
||||
<day>
|
||||
<name>4</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:mdf@FreeBSD.org">Matthew Fleming</a> (src)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>3</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:ae@FreeBSD.org">Andrey V. Elsukov</a> (src)</p>
|
||||
</event>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:taras@FreeBSD.org">Taras Korenko</a> (doc/ru, www/ru)</p>
|
||||
|
@ -1506,7 +1506,7 @@
|
|||
|
||||
<day>
|
||||
<name>19</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:jchandra@FreeBSD.org">Jayachandran C.</a> (src)</p>
|
||||
|
@ -1528,7 +1528,7 @@
|
|||
|
||||
<day>
|
||||
<name>22</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Statusreport Januar-März 2010 verfügbar</title>
|
||||
|
||||
|
@ -1616,7 +1616,7 @@
|
|||
|
||||
<day>
|
||||
<name>31</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:decke@FreeBSD.org">Bernhard Fröhlich</a> (ports)</p>
|
||||
|
@ -1625,7 +1625,7 @@
|
|||
|
||||
<day>
|
||||
<name>23</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 7.3-RELEASE verfügbar</title>
|
||||
|
||||
|
@ -1670,7 +1670,7 @@
|
|||
|
||||
<day>
|
||||
<name>4</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 7.3-RC2 verfügbar</title>
|
||||
|
||||
|
@ -1686,7 +1686,7 @@
|
|||
|
||||
<day>
|
||||
<name>3</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:neel@FreeBSD.org">Neel Natu</a> (src)</p>
|
||||
|
@ -1718,7 +1718,7 @@
|
|||
|
||||
<day>
|
||||
<name>15</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 7.3-RC1 verfügbar</title>
|
||||
|
||||
|
@ -1744,16 +1744,16 @@
|
|||
|
||||
<day>
|
||||
<name>6</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:bschmidt@FreeBSD.org">Bernhard Schmidt</a> (src)</p>
|
||||
</event>
|
||||
</day>
|
||||
|
||||
|
||||
<day>
|
||||
<name>2</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>Erweiterte Commit-Privilegien: <a
|
||||
href="mailto:gabor@FreeBSD.org">Gábor
|
||||
|
@ -1775,7 +1775,7 @@
|
|||
|
||||
<day>
|
||||
<name>30</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>&os; 7.3-BETA1 verfügbar</title>
|
||||
|
||||
|
@ -1790,7 +1790,7 @@
|
|||
|
||||
<day>
|
||||
<name>29</name>
|
||||
|
||||
|
||||
<event>
|
||||
<p>Neuer Committer: <a
|
||||
href="mailto:brucec@FreeBSD.org">Bruce Cran</a> (src)</p>
|
||||
|
|
|
@ -288,16 +288,16 @@
|
|||
</orderedlist>
|
||||
|
||||
<important>
|
||||
<para>THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION
|
||||
PROJECT "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
|
||||
THE FREEBSD DOCUMENTATION PROJECT 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
|
||||
<para>THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION
|
||||
PROJECT "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
|
||||
THE FREEBSD DOCUMENTATION PROJECT 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 DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
|
||||
DAMAGE.</para>
|
||||
</important>
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
Installing and Using compiz-fusion in FreeBSD
|
||||
|
||||
The FreeBSD Greek Documentation Project
|
||||
|
||||
|
||||
%SOURCE% en_US.ISO8859-1/articles/compiz-fusion/article.sgml
|
||||
%SRCID% 1.6
|
||||
|
||||
|
@ -66,8 +66,8 @@
|
|||
<title>ÅéóáãùãÞ</title>
|
||||
|
||||
<para>H åãêáôÜóôáóç ôïõ <application>Compiz Fusion</application>
|
||||
από την συλλογή των Ports, είναι μια σχετικά απλή διαδικασία.
|
||||
Χρειάζονται, όμως, και κάποιες επιπλέον ρυθμίσεις, οι οποίες δεν
|
||||
από την συλλογή των Ports, είναι μια σχετικά απλή διαδικασία.
|
||||
Χρειάζονται, όμως, και κάποιες επιπλέον ρυθμίσεις, οι οποίες δεν
|
||||
ðåñéãñÜöïíôáé óôçí ôåêìçñßùóç ôïõ port. Ôï Üñèñï áõôü èá óáò âïçèÞóåé
|
||||
íá ñõèìßóåôå ôïí <application>&xorg;</application> server ãéá
|
||||
ôñéóäéÜóôáôç ëåéôïõñãßá, íá ñõèìßóåôå ôçí nVidia êÜñôá ãñáöéêþí óáò,
|
||||
|
|
|
@ -213,7 +213,7 @@ fwcmd="/sbin/ipfw"
|
|||
oif="tun0"
|
||||
|
||||
# Define our inside interface. This is usually your network
|
||||
# card. Be sure to change this to match your own network
|
||||
# card. Be sure to change this to match your own network
|
||||
# interface.
|
||||
iif="fxp0"
|
||||
|
||||
|
|
|
@ -74,7 +74,7 @@
|
|||
|
||||
<para>Υπάρχουν δύο πιθανοί τρόποι (modes) μορφοποίησης:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><firstterm>συμβατή λειτουργία (compatibility
|
||||
mode)</firstterm>: Διαμόρφωση του δίσκου ώστε να έχει ένα πίνακα
|
||||
|
@ -109,7 +109,7 @@
|
|||
(τίτλος) και στα τμήματα (partitions) των δίσκων. Επιπλέον σας
|
||||
επιτρέπει να αποθηκεύσετε τις αλλαγές μόνο στον συγκεκριμένο δίσκο
|
||||
χωρίς να επηρεάζει τους υπόλοιπους. Ο δεύτερος τρόπος είναι να
|
||||
εκτελέσετε διάφορες εντολές με το χέρι απο την γραμμή εντολών ως root.
|
||||
εκτελέσετε διάφορες εντολές με το χέρι απο την γραμμή εντολών ως root.
|
||||
Αν επιλέξετε την αποκλειστική λειτουργία χρειάζετε να εκτελέσετε μόνο
|
||||
2-3 εντολές ενώ με το <command>sysinstall</command> πρέπει δουλέψετε
|
||||
λιγάκι παραπάνω.</para>
|
||||
|
@ -128,7 +128,7 @@
|
|||
<listitem>
|
||||
<para>συμβατή λειτουργία (compatibility mode): η διαμόρφωση του
|
||||
δίσκου ώστε να έχει ένα πίνακα τμήματων (slice table) και να
|
||||
μπορεί να χρησιμοποιηθεί παράλληλα με άλλα λειτουργικά συστήματα.
|
||||
μπορεί να χρησιμοποιηθεί παράλληλα με άλλα λειτουργικά συστήματα.
|
||||
Αντίθετο της αποκλειστικής λειτουργίας.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -157,8 +157,8 @@
|
|||
|
||||
<listitem>
|
||||
<para>τμήμα (slice): Μία υποδιαίρεση ενός δίσκου. Σύμφωνα με τα
|
||||
πρότυπα των PC μπορούν να υπάρχουν μέχρι 4 τμήματα σε έναν δίσκο.
|
||||
Τα τμήματα αποτελούνται απο συνεχόμενους τομείς (sectors).
|
||||
πρότυπα των PC μπορούν να υπάρχουν μέχρι 4 τμήματα σε έναν δίσκο.
|
||||
Τα τμήματα αποτελούνται απο συνεχόμενους τομείς (sectors).
|
||||
Υπάρχει ένας <quote>πίνακας τμημάτων</quote> (slice table) που
|
||||
περιέχει πληροφορίες για τα τμήματα και χρησιμοποιείται από το
|
||||
BIOS για να βρεί από πού μπορεί να ξεκινήσει το σύστημα. Ο
|
||||
|
@ -175,7 +175,7 @@
|
|||
βρίσκεται σε ένα κομμάτι. Τα κομμάτια φτιάχνονται με το εργαλείο
|
||||
disklabel.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>τομέας (sector): Η μικρότερη υποδιαίρεση ενός δίσκου. Συνήθως
|
||||
έχει μέγεθος 512 bytes.</para>
|
||||
|
@ -246,11 +246,11 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Ξεκινήστε το sysinstall ώς root γράφοντας
|
||||
<para>Ξεκινήστε το sysinstall ώς root γράφοντας
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
|
||||
</informalexample>
|
||||
</informalexample>
|
||||
|
||||
στην γραμμή εντολών.</para>
|
||||
</step>
|
||||
|
@ -271,12 +271,12 @@
|
|||
<step>
|
||||
<para>Αν θα χρησιμοποιήσετε όλο το δίσκο για το FreeBSD, επιλέξτε
|
||||
<command>A</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Μόλις σας ρωτήσει αν όντως θέλετε να το κάνετε αυτό (Do you
|
||||
still want to do this) απαντήστε <command>Yes</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Επιλέξτε <command>Write</command>.</para>
|
||||
|
@ -359,7 +359,7 @@
|
|||
|
||||
<para>Αν χρειάζεται να αλλάξετε το disklabel για να χρησιμοποιήσετε
|
||||
πολλαπλά partitions (για παράδειγμα αν θέλετε swap) τότε κάντε:</para>
|
||||
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
|
||||
&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
|
||||
|
@ -397,7 +397,7 @@
|
|||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
|
||||
</informalexample>
|
||||
</informalexample>
|
||||
|
||||
στην γραμμή εντολών.</para>
|
||||
</step>
|
||||
|
@ -418,10 +418,10 @@
|
|||
<step>
|
||||
<para>Αν θα χρησιμοποιήσετε όλο τον δίσκο για το FreeBSD,
|
||||
επιλέξτε <command>A</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Όταν σας ζητηθεί:
|
||||
<para>Όταν σας ζητηθεί:
|
||||
|
||||
<informalexample>
|
||||
<screen>Do you want to do this with a true partition entry so as to remain
|
||||
|
@ -454,7 +454,7 @@ drive(s)?</screen>
|
|||
|
||||
<step>
|
||||
<para>Επιλέξτε <command>Label</command> απο το Index menu.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Ονομάστε το δίσκο όπως θέλετε (εδώ θα ορίσετε τα
|
||||
|
@ -469,7 +469,7 @@ drive(s)?</screen>
|
|||
συμφέρει να το κάνετε! Θα σας δώσει το λάθος:
|
||||
|
||||
<informalexample>
|
||||
<screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
|
||||
<screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
|
||||
</informalexample>
|
||||
|
||||
Αγνοήστε το.</para>
|
||||
|
@ -508,7 +508,7 @@ drive(s)?</screen>
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>Όταν κάνετε newfs στον δίσκο, ΜΗΝ το κάνετε στο κομμάτι `c'.
|
||||
<para>Όταν κάνετε newfs στον δίσκο, ΜΗΝ το κάνετε στο κομμάτι `c'.
|
||||
Αντίθετα, κάντε το μόνο στο κομμάτι που δεν είναι swap.</para>
|
||||
</step>
|
||||
|
||||
|
@ -519,7 +519,7 @@ drive(s)?</screen>
|
|||
<informalexample>
|
||||
<programlisting>/dev/ad0b none swap sw 0 0</programlisting>
|
||||
</informalexample>
|
||||
|
||||
|
||||
<para>Αλλάξτε το <filename>/dev/ad0b</filename> στο όνομα της
|
||||
καινούργιας σας συσκευής.</para>
|
||||
</step>
|
||||
|
@ -540,7 +540,7 @@ swapon: added /dev/da0b as swap space</screen>
|
|||
<sect2>
|
||||
<title>Αντιγράφοντας τα περιεχόμενα δίσκων</title>
|
||||
<!-- Should have specific tag -->
|
||||
|
||||
|
||||
<para>Από τον: Renaud Waldura
|
||||
(<email>renaud@softway.com</email>)</para>
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
# $FreeBSD$
|
||||
#
|
||||
# Article: Implementing UFS journaling on a desktop PC
|
||||
#
|
||||
#
|
||||
# %SOURCE% en_US.ISO8859-1/articles/gjournal-desktop/Makefile
|
||||
# %SRCID% 1.1
|
||||
#
|
||||
|
|
|
@ -72,9 +72,9 @@
|
|||
υπολογιστές θα βρείτε και στη
|
||||
σελίδα <ulink url="http://tuxmobil.org/mobile_bsd.html"></ulink>.</para>
|
||||
|
||||
<sect1 id="xorg">
|
||||
<sect1 id="xorg">
|
||||
<title>Το γραφικό περιβάλλον &xorg;</title>
|
||||
|
||||
|
||||
<para>Οι πρόσφατες εκδόσεις των <application>&xorg;</application> δουλεύουν με τις
|
||||
περισσότερες μοντέρνες κάρτες οθόνης που χρησιμοποιούνται σε
|
||||
φορητούς υπολογιστές. Η επιτάχυνση (acceleration) μπορεί να μην
|
||||
|
@ -119,9 +119,9 @@
|
|||
|
||||
<para>στο αρχείο <filename>xorg.conf</filename>, στο
|
||||
τμήμα <literal>InputDevice</literal>.</para>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="modems">
|
||||
<sect1 id="modems">
|
||||
<title>Modems</title>
|
||||
|
||||
<para>Οι φορητοί έρχονται συνήθως με εσωτερικά (on-board) μόντεμ.
|
||||
|
@ -139,9 +139,9 @@
|
|||
φτηνά USB ή σειριακά μόντεμ που μπορεί να σας κοστίσουν
|
||||
λιγότερο. Γενικά, τα κανονικά (όχι win-μόντεμ) μόντεμ πρέπει να
|
||||
δουλεύουν χωρίς κανένα πρόβλημα.</para>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="pcmcia">
|
||||
<sect1 id="pcmcia">
|
||||
<title>Συσκευές PCMCIA (PC Card)</title>
|
||||
|
||||
<para>Οι πιο πολλοί φορητοί έρχονται με υποδοχές PCMCIA (γνωστές
|
||||
|
@ -199,9 +199,9 @@
|
|||
χρησιμοποιήσει το PCI BIOS). Αν έχετε προβλήματα με αυτή την
|
||||
έκδοση του &os;, δοκιμάστε να την αναβαθμίσετε σε κάποια πιο
|
||||
καινούρια.</para>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="power-management">
|
||||
<sect1 id="power-management">
|
||||
<title>Power management</title>
|
||||
|
||||
<para>Δυστυχώς, το power management δεν υποστηρίζεται πολύ καλά
|
||||
|
|
|
@ -1017,7 +1017,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
|
|||
να δουλεύει όταν το σύστημα ξεκινήσει σε κατάσταση ενός χρήστη (single
|
||||
user mode). Η λύση είναι να χρησιμοποιείτε την εντολή <command>su
|
||||
-m</command> για να γίνετε <username>root</username>, που θα σας δώσει ένα <command>tcsh</command> φλοιό σαν
|
||||
<username>root</username>, αφού το ποιος είναι ο φλοιός είναι μέρος του περιβάλλοντος.
|
||||
<username>root</username>, αφού το ποιος είναι ο φλοιός είναι μέρος του περιβάλλοντος.
|
||||
Μπορείτε να κάνετε μόνιμη μια τέτοια αλλαγή προσθέτοντας στο
|
||||
<filename>.tcshrc</filename> σας μια συντόμευση</para>
|
||||
<programlisting>alias su su -m</programlisting>
|
||||
|
@ -1045,7 +1045,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
|
|||
<para>set prompt = "%h %t %~ %# "</para>
|
||||
|
||||
<para>Αυτό μπορεί να πάει στο ίδιο μέρος που υπάρχει η παλιά set prompt
|
||||
γραμμή αν υπάρχει, ή κάτω από την "if($?prompt) then" αν δεν υπάρχει.
|
||||
γραμμή αν υπάρχει, ή κάτω από την "if($?prompt) then" αν δεν υπάρχει.
|
||||
Μετατρέψτε την παλιά σε σχόλιο, ώστε να μπορείτε να επιστρέψετε στο
|
||||
παλιό σας prompt αν το προτιμάτε. Μην ξεχάσετε στην καινούρια γραμμή τα
|
||||
κενά και τα εισαγωγικά. Μπορείτε να κάνετε το tcsh να ξαναδιαβάσει το
|
||||
|
@ -1068,12 +1068,12 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
|
|||
<command>/sbin/umount /cdrom</command>, να βγάλετε το δίσκο από τον
|
||||
οδηγό, να βάλετε ένα καινούριο και να το συνδέσετε με την εντολή
|
||||
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</command> υποθέτοντας ότι
|
||||
<hardware>cd0a</hardware> είναι το όνομα της συσκευής του οδηγού CDROM.
|
||||
<hardware>cd0a</hardware> είναι το όνομα της συσκευής του οδηγού CDROM.
|
||||
Οι πιο πρόσφατες εκδόσεις του FreeBSD σας αφήνουν να συνδέσετε το CDROM
|
||||
γράφοντας απλά <command>/sbin/mount /cdrom</command>.</para>
|
||||
|
||||
<para>Το live σύστημα—το δεύτερο CDROM από τους δίσκους εγκατάστασης
|
||||
του FreeBSD— μπορεί να φανεί χρήσιμο αν έχετε περιορισμένο χώρο.
|
||||
του FreeBSD— μπορεί να φανεί χρήσιμο αν έχετε περιορισμένο χώρο.
|
||||
Το τι υπάρχει στο live σύστημα διαφέρει από έκδοση σε έκδοση. Μπορείτε
|
||||
να δοκιμάσετε να παίξετε ακόμα και παιχνίδια από το CDROM. Αυτό απαιτεί
|
||||
να χρησιμοποιήσετε την εντολή <command>lndir</command>, που εγκαθίσταται
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Μορφοποίηση του FreeBSD FAQ
|
||||
|
@ -18,8 +18,8 @@ INSTALL_ONLY_COMPRESSED?=
|
|||
|
||||
WITH_BIBLIOXREF_TITLE?=YES
|
||||
|
||||
#
|
||||
# Η λίστα SRCS περιέχει όλα τα SGML αρχεία που αποτελούν μέρη του κειμένου.
|
||||
#
|
||||
# Η λίστα SRCS περιέχει όλα τα SGML αρχεία που αποτελούν μέρη του κειμένου.
|
||||
# Αλλαγές σε οποιοδήποτε από αυτά τα αρχεία προκαλούν rebuild.
|
||||
#
|
||||
|
||||
|
|
|
@ -5286,7 +5286,7 @@ kern.sched.name: 4BSD</screen>
|
|||
for both, move the parent partition as described above,
|
||||
then move the child partition into the empty directory
|
||||
that the first move created:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
|
||||
&prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
|
||||
&prompt.root; <userinput>cd /mnt</userinput>
|
||||
|
@ -5753,7 +5753,7 @@ C:\="DOS"</programlisting>
|
|||
<para>Booting &os; using GRUB is very simple. Just
|
||||
add the following to your configuration file
|
||||
<filename>/boot/grub/grub.conf</filename>.</para>
|
||||
|
||||
|
||||
<programlisting>title FreeBSD 6.1
|
||||
root (hd0,a)
|
||||
kernel /boot/loader
|
||||
|
@ -5926,7 +5926,7 @@ C:\="DOS"</programlisting>
|
|||
<para>I burned a CD under FreeBSD and now I can not read it
|
||||
under any other operating system. Why?</para>
|
||||
</question>
|
||||
|
||||
|
||||
<answer>
|
||||
<para>You most likely burned a raw file to your CD, rather
|
||||
than creating an ISO 9660 filesystem. Take a look at the
|
||||
|
@ -6022,7 +6022,7 @@ C:\="DOS"</programlisting>
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>If you are running &os; 5.X or later, you will need to alter
|
||||
<para>If you are running &os; 5.X or later, you will need to alter
|
||||
<filename>/etc/devfs.conf</filename> to make these changes
|
||||
permanent across reboots.</para>
|
||||
|
||||
|
@ -6161,7 +6161,7 @@ perm /dev/acd0 0660</programlisting>
|
|||
<para>Disk manufacturers calculate gigabytes as a billion bytes
|
||||
each, whereas &os; calculates them as 1,073,741,824 bytes
|
||||
each. This explains why, for example, &os;'s boot messages
|
||||
will report a disk that supposedly has 80GB as holding
|
||||
will report a disk that supposedly has 80GB as holding
|
||||
76319MB.</para>
|
||||
<para>Also note that &os; will (by default)
|
||||
<link linkend="disk-more-than-full">reserve</link> 8% of the disk
|
||||
|
@ -6910,7 +6910,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
<answer>
|
||||
<para>The reason why <filename>.shosts</filename>
|
||||
authentication does not work by default in more recent
|
||||
versions of FreeBSD is because &man.ssh.1;
|
||||
versions of FreeBSD is because &man.ssh.1;
|
||||
is not installed suid <username>root</username> by default. To
|
||||
<quote>fix</quote> this, you can do one of the
|
||||
following:</para>
|
||||
|
@ -7104,7 +7104,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
period, it was basically only provided as a reference
|
||||
platform, as it had suffered greatly from bitrot over
|
||||
the years.</para>
|
||||
|
||||
|
||||
<para>However, early in 2004, some XFree86 developers left
|
||||
that project
|
||||
over issues including the pace of code changes, future
|
||||
|
@ -7715,7 +7715,7 @@ UserConfig> <userinput>quit</userinput></screen>
|
|||
<application>&xorg;</application>.
|
||||
If you want to run a different X11 implementation
|
||||
than the default one, add the following line to
|
||||
<filename>/etc/make.conf</filename>, (if you
|
||||
<filename>/etc/make.conf</filename>, (if you
|
||||
do not have this file, create it):</para>
|
||||
|
||||
<programlisting>X_WINDOW_SYSTEM= xorg</programlisting>
|
||||
|
@ -8053,7 +8053,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
|
|||
|
||||
<answer>
|
||||
<para>If the alias is on the same subnet as an address
|
||||
already configured on the interface, then add
|
||||
already configured on the interface, then add
|
||||
<literal>netmask 0xffffffff</literal> to your
|
||||
&man.ifconfig.8; command-line, as in the following:</para>
|
||||
|
||||
|
@ -11213,7 +11213,7 @@ raisechar=^^</programlisting>
|
|||
<para><emphasis>And then I was enlightened :-)</emphasis></para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
||||
<qandaentry>
|
||||
<question id="dev-null">
|
||||
<para>Where does data written to <filename>/dev/null</filename>
|
||||
|
@ -11286,7 +11286,7 @@ raisechar=^^</programlisting>
|
|||
<para>At this time, there is only one book on FreeBSD-specific OS
|
||||
internals, namely <quote>The Design and Implementation of the
|
||||
FreeBSD Operating System</quote> by Marshall Kirk McKusick and
|
||||
George V. Neville-Neil, ISBN 0-201-70245-2, which
|
||||
George V. Neville-Neil, ISBN 0-201-70245-2, which
|
||||
focuses on version 5.X of FreeBSD.</para>
|
||||
|
||||
<para>Additionally, much general &unix; knowledge is directly
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
# pgpkeyring This target will read the contents of
|
||||
# pgpkeys/chapter.sgml and will extract all of
|
||||
# the pgpkeys to standard out. This output can then
|
||||
# be redirected into a file and distributed as a
|
||||
# be redirected into a file and distributed as a
|
||||
# public keyring of FreeBSD developers that can
|
||||
# easily be imported into PGP/GPG.
|
||||
#
|
||||
|
|
|
@ -2165,7 +2165,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:
|
|||
<para>SDP involves communication between a SDP server and a SDP client.
|
||||
The server maintains a list of service records that describe the
|
||||
characteristics of services associated with the server. Each service
|
||||
record contains information about a single service. A client may
|
||||
record contains information about a single service. A client may
|
||||
retrieve information from a service record maintained by the SDP server
|
||||
by issuing a SDP request. If the client, or an application associated
|
||||
with the client, decides to use a service, it must open a separate
|
||||
|
@ -2179,7 +2179,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:
|
|||
server's service records without any a priori information about the
|
||||
services. This process of looking for any offered services is called
|
||||
<emphasis>browsing</emphasis>.</para>
|
||||
|
||||
|
||||
<para>The Bluetooth SDP server &man.sdpd.8; and command line client
|
||||
&man.sdpcontrol.8; are included in the standard &os; installation.
|
||||
The following example shows how to perform a SDP browse query.</para>
|
||||
|
@ -2595,7 +2595,7 @@ net.link.ether.bridge_cfg=<replaceable>if1</replaceable>,<replaceable>if2</repla
|
|||
net.link.ether.bridge_ipfw=1</programlisting>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Other Information</title>
|
||||
|
||||
|
@ -2610,7 +2610,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
|
|||
|
||||
<para>A bridge can add latency to your &man.ping.8; times, especially for
|
||||
traffic from one segment to another.</para>
|
||||
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
@ -2743,7 +2743,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
|
|||
|
||||
<para>Several operations need to be performed for a successful
|
||||
bootstrap:</para>
|
||||
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>The machine needs to obtain initial parameters such as its IP
|
||||
|
|
|
@ -1272,7 +1272,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<![ IGNORE [
|
||||
<![ IGNORE [
|
||||
<sect2 id="docsnap">
|
||||
<sect2info>
|
||||
<authorgroup>
|
||||
|
|
|
@ -1288,7 +1288,7 @@ scsibus1:
|
|||
charset you use with the <option>-C</option> option. For more
|
||||
information, consult the &man.mount.cd9660.8; manual
|
||||
page.</para>
|
||||
|
||||
|
||||
<note>
|
||||
<para>To be able to do this character conversion with the help
|
||||
of the <option>-C</option> option, the kernel will require
|
||||
|
@ -3924,7 +3924,7 @@ device crypto</screen>
|
|||
the data source for key file will be
|
||||
<filename>/dev/random</filename>. The sector size of
|
||||
<filename>/dev/da2.eli</filename>, which we call provider,
|
||||
will be 4kB.</para>
|
||||
will be 4kB.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dd if=/dev/random of=/root/da2.key bs=64 count=1</userinput>
|
||||
&prompt.root; <userinput>geli init -s 4096 -K /root/da2.key /dev/da2</userinput>
|
||||
|
@ -4017,7 +4017,7 @@ geli_da2_flags="-p -k /root/da2.key"</screen>
|
|||
<link linkend="configtuning-rcd">rc.d</link> section of the
|
||||
Handbook.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
||||
|
|
|
@ -1915,7 +1915,7 @@
|
|||
περιβάλλοντος <application>Zope</application> στο &os;.
|
||||
Πρόκειται για λίστα τεχνικών συζητήσεων. Απευθύνεται κυρίως
|
||||
σε άτομα που συμμετέχουν ενεργά στη μεταφορά του
|
||||
<application>Zope</application> óôï &os; êáé óõæçôïýíôáé
|
||||
<application>Zope</application> óôï &os; êáé óõæçôïýíôáé
|
||||
προβλήματα και εναλλακτικές λύσεις. Η λίστα είναι επίσης
|
||||
ανοικτή σε όσους ενδιαφέρονται για τεχνική συζήτηση αυτού
|
||||
του είδους.</para>
|
||||
|
|
|
@ -1086,7 +1086,7 @@ device splash # Splash screen and screen saver support</programlist
|
|||
|
||||
<para>Γραφική οθόνη (splash) κατά την εκκίνηση! Η συσκευή αυτή
|
||||
χρησιμοποιείται επίσης από τα προγράμματα προφύλαξης οθόνης (κονσόλας).
|
||||
</para>
|
||||
</para>
|
||||
|
||||
<programlisting># syscons is the default console driver, resembling an SCO console
|
||||
device sc</programlisting>
|
||||
|
@ -1450,7 +1450,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
|
|||
<acronym>KVA</acronym>). Εξαιτίας αυτού του περιορισμού, η Intel
|
||||
πρόσθεσε υποστήριξη για 36bit φυσικών διευθύνσεων, από τον
|
||||
επεξεργαστή &pentium; Pro και μετά.</para>
|
||||
|
||||
|
||||
<para>Η δυνατότητα Επέκτασης Φυσικών Διευθύνσεων, (Physical Address
|
||||
Extension, <acronym>PAE</acronym>) των &intel; &pentium; Pro και
|
||||
μεταγενέστερων CPU, επιτρέπει χρήση μνήμης ως 64 gigabytes. To &os;
|
||||
|
@ -1465,7 +1465,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
|
|||
<para>Για να ενεργοποιήσετε την υποστήριξη <acronym>PAE</acronym>
|
||||
στον πυρήνα, απλώς προσθέστε την ακόλουθη γραμμή στο αρχείο
|
||||
των ρυθμίσεων σας:</para>
|
||||
|
||||
|
||||
<programlisting>options PAE</programlisting>
|
||||
|
||||
<note>
|
||||
|
@ -1479,7 +1479,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
|
|||
|
||||
<para>Η υποστήριξη <acronym>PAE</acronym> στο &os; υπόκειται σε
|
||||
κάποιους περιορισμούς:</para>
|
||||
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Μια διαδικασία δεν έχει πρόσβαση σε περισσότερα από 4
|
||||
|
|
|
@ -1235,7 +1235,7 @@ export PATH</programlisting>
|
|||
ως <username>root</username>, καταγράφονται σε ένα shell script που
|
||||
λέγεται <filename>root.sh</filename>. Το script αυτό δημιουργείται
|
||||
στον κατάλογο <filename>orainst</filename>. Εφαρμόστε το παρακάτω
|
||||
patch στο <filename>root.sh</filename>, για να μπορέσει να βρει και
|
||||
patch στο <filename>root.sh</filename>, για να μπορέσει να βρει και
|
||||
να χρησιμοποιήσει το <command>chown</command>. Εναλλακτικά, τρέξτε
|
||||
το script μέσα από ένα κέλυφος Linux.</para>
|
||||
|
||||
|
@ -1314,7 +1314,7 @@ export PATH</programlisting>
|
|||
<title>Πως Λειτουργεί;</title>
|
||||
<indexterm><primary>execution class loader</primary></indexterm>
|
||||
|
||||
<para>Το &os; περιέχει ένα επίπεδο αφαίρεσης (abstraction) που
|
||||
<para>Το &os; περιέχει ένα επίπεδο αφαίρεσης (abstraction) που
|
||||
ονομάζεται <quote>execution class loader</quote>. Αυτό βασίζεται στο
|
||||
&man.execve.2;.</para>
|
||||
|
||||
|
|
|
@ -712,7 +712,7 @@ test: biba/high</screen>
|
|||
implement the labeling feature, including the Biba, Lomac,
|
||||
<acronym>MLS</acronym> and <acronym>SEBSD</acronym>
|
||||
policies.</para>
|
||||
|
||||
|
||||
<para>In many cases, the <option>multilabel</option> may not need
|
||||
to be set at all. Consider the following situation and
|
||||
security model:</para>
|
||||
|
@ -1586,7 +1586,7 @@ test: biba/low</screen>
|
|||
utilities. While other users would be grouped into other
|
||||
categories such as testers, designers, or just ordinary
|
||||
users and would only be permitted read access.</para>
|
||||
|
||||
|
||||
<para>With its natural security control, a lower integrity subject
|
||||
is unable to write to a higher integrity subject; a higher
|
||||
integrity subject cannot observe or read a lower integrity
|
||||
|
@ -1749,7 +1749,7 @@ mac_seeotheruids_load="YES"</programlisting>
|
|||
<username>www</username> users into the insecure class:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pw usermod nagios -L insecure</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
|
@ -111,7 +111,7 @@
|
|||
<para>Αν προσπαθήσετε να προσαρτήσετε μουσικά CD
|
||||
με την εντολή &man.mount.8; θα προκληθεί κατ' ελάχιστον
|
||||
σφάλμα, ή στη χειρότερη περίπτωση <emphasis>kernel
|
||||
panic</emphasis>. Τέτοια μέσα έχουν εξειδικευμένες κωδικοποιήσεις
|
||||
panic</emphasis>. Τέτοια μέσα έχουν εξειδικευμένες κωδικοποιήσεις
|
||||
που διαφέρουν από το συνηθισμένο σύστημα αρχείων ISO.</para>
|
||||
</warning>
|
||||
</sect1>
|
||||
|
@ -137,7 +137,7 @@
|
|||
</sect1info>
|
||||
|
||||
<title>Ρύθμιση της Κάρτας Ήχου</title>
|
||||
|
||||
|
||||
<sect2 id="sound-device">
|
||||
<title>Ρυθμίζοντας το Σύστημα</title>
|
||||
|
||||
|
@ -175,7 +175,7 @@
|
|||
&soundblaster; Live!. Υπάρχουν διαθέσιμα και άλλα modules για κάρτες
|
||||
ήχου και μπορείτε να τα δείτε στο αρχείο
|
||||
<filename>/boot/defaults/loader.conf</filename>.
|
||||
Αν δεν είστε σίγουρος για το πρόγραμμα οδήγησης που πρέπει να
|
||||
Αν δεν είστε σίγουρος για το πρόγραμμα οδήγησης που πρέπει να
|
||||
χρησιμοποιήσετε, μπορείτε να προσπαθήσετε να φορτώσετε το module
|
||||
<filename>snd_driver</filename>:</para>
|
||||
|
||||
|
@ -586,7 +586,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
|
|||
MP3, θα πρέπει να αντιγράψετε τα μουσικά δεδομένα από το CD στο σκληρό
|
||||
σας δίσκο. Αυτό γίνεται γράφοντας τα δεδομένα τύπου CDDA (CD Digital
|
||||
Audio) σε αρχεία WAV.</para>
|
||||
|
||||
|
||||
<para>Το εργαλείο <command>cdda2wav</command>, το οποίο ανήκει στη
|
||||
συλλογή εργαλείων
|
||||
<filename role="package">sysutils/cdrtools</filename> μπορεί να
|
||||
|
@ -602,7 +602,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
|
|||
<para>Το <application>cdda2wav</application> υποστηρίζει οδηγούς CDROM
|
||||
τύπου ATAPI (IDE). Για να διαβάσετε δεδομένα από μια συσκευή IDE,
|
||||
χρησιμοποιήστε το όνομα συσκευής αντί για τον αριθμό μονάδας SCSI. Για
|
||||
παράδειγμα, για να αποθηκεύσετε το κομμάτι 7 από ένα οδηγό IDE:</para>
|
||||
παράδειγμα, για να αποθηκεύσετε το κομμάτι 7 από ένα οδηγό IDE:</para>
|
||||
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>/dev/acd0</replaceable> -t 7</userinput></screen>
|
||||
|
||||
<para>Το <option>-D <replaceable>0,1,0</replaceable></option>
|
||||
|
@ -618,7 +618,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
|
|||
<para>Το παράδειγμα αυτό διαβάζει το κομμάτι επτά του μουσικού CD. Για
|
||||
να διαβάσετε μια σειρά από κομμάτια, για παράδειγμα από το ένα ως το
|
||||
επτά, καθορίστε μια περιοχή:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
|
||||
|
||||
<para>Μπορείτε επίσης να χρησιμοποιήσετε το βοηθητικό πρόγραμμα
|
||||
|
@ -875,7 +875,7 @@ screen #0
|
|||
Adaptor #0: "Savage Streams Engine"
|
||||
number of ports: 1
|
||||
port base: 43
|
||||
operations supported: PutImage
|
||||
operations supported: PutImage
|
||||
supported visuals:
|
||||
depth 16, visualID 0x22
|
||||
depth 16, visualID 0x23
|
||||
|
@ -1010,7 +1010,7 @@ no adaptors present</screen>
|
|||
video που εκτελούνται στο &os; αναπτύχθηκαν αρχικά ως εφαρμογές Linux.
|
||||
Πολλές από αυτές τις εφαρμογές είναι ακόμα ποιότητας beta. Κάποια από τα
|
||||
προβλήματα που μπορεί να συναντήσετε στις εφαρμογές video του &os;
|
||||
περιλαμβάνουν:</para>
|
||||
περιλαμβάνουν:</para>
|
||||
|
||||
<orderedlist>
|
||||
|
||||
|
@ -1058,7 +1058,7 @@ no adaptors present</screen>
|
|||
υπάρχουν στο Linux. Τα προβλήματα αυτά δεν είναι σίγουρο ότι
|
||||
ανακαλύπτονται και διορθώνονται πάντα από τους συντηρητές του port, το
|
||||
οποίο μπορεί να οδηγήσει σε προβλήματα όπως τα παρακάτω:</para>
|
||||
|
||||
|
||||
<orderedlist>
|
||||
|
||||
<listitem>
|
||||
|
@ -1318,7 +1318,7 @@ zoom=yes</programlisting>
|
|||
την ίδια στιγμή, δεν επιτρέπει τόσο λεπτομερειακό έλεγχο. Το
|
||||
<application>xine</application> αποδίδει καλύτερα σε λειτουργία XVideo.
|
||||
</para>
|
||||
|
||||
|
||||
<para>Από προεπιλογή, το <application>xine</application> θα ξεκινήσει σε
|
||||
γραφικό περιβάλλον (GUI). Μπορείτε να χρησιμοποιήσετε το μενού για να
|
||||
ανοίξετε ένα συγκεκριμένο αρχείο:</para>
|
||||
|
@ -1495,7 +1495,7 @@ WITH_MJPEG=yes -DWITH_XVID=yes</userinput></screen>
|
|||
<para>Εναλλακτικά, μπορείτε να προσθέσετε στατική υποστήριξη για την
|
||||
κάρτα στο πυρήνα σας, και για το σκοπό αυτό προσθέστε τις ακόλουθες
|
||||
γραμμές στο αρχείο ρυθμίσεων του πυρήνα:</para>
|
||||
|
||||
|
||||
<programlisting>device bktr
|
||||
device iicbus
|
||||
device iicbb
|
||||
|
@ -1725,7 +1725,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
|
|||
<para>Όπως είπαμε παραπάνω, υποστηρίζονται σαρωτές τόσο SCSI όσο και
|
||||
USB. Ανάλογα με το τρόπο διασύνδεσης του σαρωτή σας, θα χρειαστείτε
|
||||
διαφορετικούς οδηγούς συσκευών.</para>
|
||||
|
||||
|
||||
<sect3 id="scanners-kernel-usb">
|
||||
<title>Διασύνδεση USB</title>
|
||||
|
||||
|
|
|
@ -3463,7 +3463,7 @@ zone "1.168.192.in-addr.arpa" {
|
|||
<primary>BIND</primary>
|
||||
<secondary>zone files</secondary>
|
||||
</indexterm>
|
||||
|
||||
|
||||
<para>An example master zone file for <hostid
|
||||
role="domainname">example.org</hostid> (existing within
|
||||
<filename>/etc/namedb/master/example.org</filename>) is as
|
||||
|
|
File diff suppressed because it is too large
Load diff
|
@ -1,7 +1,7 @@
|
|||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
#
|
||||
#
|
||||
# The FreeBSD Greek Documentation Project
|
||||
#
|
||||
# Build the FreeBSD documentation *outside* of the www tree, and install it
|
||||
|
|
|
@ -15,7 +15,7 @@
|
|||
<!ENTITY % freebsd.l10n PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN">
|
||||
%freebsd.l10n;
|
||||
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.html "IGNORE">
|
||||
<!ENTITY % output.print "IGNORE">
|
||||
<!ENTITY % lang.el.dsssl "IGNORE">
|
||||
]>
|
||||
|
@ -39,7 +39,7 @@
|
|||
(literal ".")))
|
||||
(make element gi: "p"
|
||||
attributes: (list (list "align" "center"))
|
||||
(make element gi: "small"
|
||||
(make element gi: "small"
|
||||
(literal "Ãéá åñùôÞóåéò ó÷åôéêÜ ìå ôï FreeBSD, äéáâÜóôå ôçí ")
|
||||
(create-link
|
||||
(list (list "HREF" "http://www.FreeBSD.org/docs.html"))
|
||||
|
|
|
@ -104,10 +104,10 @@
|
|||
<li><a href="&u.rel.announce;">ÓôáèåñÞ ¸êäïóç: &rel.current;</a></li>
|
||||
<li><a href="&u.rel2.announce;">ÓôáèåñÞ ¸êäïóç (Legacy): &rel2.current;</a></li>
|
||||
<li><a href="&base;/snapshots/">Åêäüóåéò Snapshot</a></li>
|
||||
<![ %beta.testing; [
|
||||
<![ %beta.testing; [
|
||||
<li><a href="&u.betarel.schedule;">Ç Åðüìåíç ¸êäïóç: &betarel.current;</a></li>
|
||||
]]>
|
||||
<![ %beta2.testing; [
|
||||
<![ %beta2.testing; [
|
||||
<li><a href="&u.betarel2.schedule;">Ç Åðüìåíç ¸êäïóç: &betarel2.current;</a></li>
|
||||
]]>
|
||||
</ul></li>
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: FreeBSD 5-STABLE roadmap
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# BSDL vs GPL article.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: Casestudy from Argentina.com
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: The FreeBSD Committers Guide
|
||||
|
|
|
@ -236,7 +236,7 @@ Option "AddARGBGLXVisuals" "True"</programlisting>
|
|||
<programlisting>SubSection "Display"
|
||||
Viewport 0 0
|
||||
Modes "1280x1024"
|
||||
EndSubSection</programlisting>
|
||||
EndSubSection</programlisting>
|
||||
|
||||
<para>A color depth of 24 bits is needed for desktop composition,
|
||||
change the above subsection to:</para>
|
||||
|
@ -371,7 +371,7 @@ emerald --replace &</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="xorg-crash">
|
||||
<para>When I run the command to start
|
||||
<para>When I run the command to start
|
||||
<application>Compiz Fusion</application>, the X server
|
||||
crashes and I am back at the console. What is wrong?</para>
|
||||
</question>
|
||||
|
|
|
@ -371,13 +371,13 @@
|
|||
<title>Compiling conserver</title>
|
||||
|
||||
<note>
|
||||
<para>See the section on <application>conserver</application> versions
|
||||
<para>See the section on <application>conserver</application> versions
|
||||
<xref linkend="conserver-versions"/>; the version I use is
|
||||
available in the &os; ports collection; however, it is not the only
|
||||
one.)</para>
|
||||
</note>
|
||||
|
||||
<para>There are two ways to install <application>conserver</application>.
|
||||
<para>There are two ways to install <application>conserver</application>.
|
||||
You can either compile
|
||||
from the source or use the &os; ports framework.</para>
|
||||
|
||||
|
@ -398,7 +398,7 @@
|
|||
is compiled will avoid having to either specify it each time the
|
||||
program is run on remote hosts or having to maintain a
|
||||
<filename>conserver.cf</filename> file on every host. This command
|
||||
will fetch, patch, configure, compile and install the
|
||||
will fetch, patch, configure, compile and install the
|
||||
<application>conserver</application> application.</para>
|
||||
|
||||
<para>You can then run <command>make package</command> to create a
|
||||
|
@ -424,7 +424,7 @@
|
|||
<title>From the source tarball</title>
|
||||
|
||||
<para>If you prefer, you can download <application>conserver</application>
|
||||
and compile it yourself.
|
||||
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
|
||||
|
@ -560,10 +560,10 @@ $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/</screen>
|
|||
|
||||
<programlisting>cuaE0 "/usr/local/sbin/conserver" unknown on insecure</programlisting>
|
||||
|
||||
<para>This has two advantages: <application>init</application> will restart
|
||||
<para>This has two advantages: <application>init</application> 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
|
||||
crashes so far), and it arranges for standard output of the
|
||||
<application>conserver</application>
|
||||
process to be directed to the named tty (in this case
|
||||
<devicename>cuaE0</devicename>). This is useful because you
|
||||
|
@ -574,14 +574,14 @@ $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/</screen>
|
|||
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
|
||||
<application>conserver</application>
|
||||
<application>conserver</application>
|
||||
from the ttys file is that it cannot run in daemon
|
||||
mode (else &man.init.8; would continually restart it). This means
|
||||
<application>conserver</application> will not write a PID file,
|
||||
<application>conserver</application> will not write a PID file,
|
||||
which makes it hard to rotate the log files.</para>
|
||||
|
||||
<para>So we start <application>conserver</application> from an rc.d script.
|
||||
If you installed <application>conserver</application> via the port,
|
||||
If you installed <application>conserver</application> via the port,
|
||||
there will be a
|
||||
<filename>conserver.sh.sample</filename> file installed in
|
||||
<filename>/usr/local/etc/rc.d</filename>. Copy and/or rename this to
|
||||
|
@ -1217,11 +1217,11 @@ exit 0</programlisting>
|
|||
|
||||
<para>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 <literal>BREAK</literal> as a command to halt the
|
||||
recognises a serial <literal>BREAK</literal> as a command to halt the
|
||||
OS and return to the ROM monitor prompt. A serial <literal>BREAK</literal>
|
||||
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).
|
||||
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 <literal>BREAK</literal> 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
|
||||
|
@ -1232,7 +1232,7 @@ exit 0</programlisting>
|
|||
|
||||
<para>Fortunately, Sun have come up with a set of fixes for this. For
|
||||
&solaris; 2.6 and later, the <command>kbd(1)</command> command can be used
|
||||
to disable the <literal>ROM-on-BREAK</literal> behaviour. This is a good start,
|
||||
to disable the <literal>ROM-on-BREAK</literal> 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.</para>
|
||||
|
||||
|
@ -1342,7 +1342,7 @@ exit 0</programlisting>
|
|||
<application>conserver</application> is not really suitable for use
|
||||
across untrusted networks (such as the Internet). Use of conserver-only
|
||||
passwords (in the <filename>conserver.passwd</filename> file) slightly
|
||||
mitigate this problem, but anyone sniffing a
|
||||
mitigate this problem, but anyone sniffing a
|
||||
<application>conserver</application> connection can
|
||||
easily get console access, and from there prang your machine using the
|
||||
console break sequence. For operating across the Internet, use
|
||||
|
@ -1370,12 +1370,12 @@ exit 0</programlisting>
|
|||
idiosyncratic manner (using a preprocessor to generate C code). Version
|
||||
8.5 is maintained by Kevin S. Braunsdorf
|
||||
<email>ksb+conserver@sa.fedex.com</email> who did most of the original
|
||||
work on <application>conserver</application>,
|
||||
work on <application>conserver</application>,
|
||||
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).</para>
|
||||
|
||||
|
||||
<para>Beginning with December 2001, Brian's version (currently 8.1.9) is
|
||||
also presented in ports collection at
|
||||
<filename role="package">comms/conserver-com</filename>. We therefore
|
||||
|
|
|
@ -482,7 +482,7 @@
|
|||
information:</para>
|
||||
|
||||
<programlisting>Copyright (c) %%proper_years_here%%
|
||||
%%your_name_here%%, %%your_state%% %%your_zip%%.
|
||||
%%your_name_here%%, %%your_state%% %%your_zip%%.
|
||||
All rights reserved.
|
||||
|
||||
Redistribution and use in source and binary forms, with or without
|
||||
|
|
|
@ -330,7 +330,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Alex Steiner
|
||||
<para>Alex Steiner
|
||||
<email>ast@treibsand.com</email></para>
|
||||
</listitem>
|
||||
|
||||
|
@ -4558,7 +4558,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>Jesse Kempf
|
||||
<email>jessekempf@gmail.com</email></para>
|
||||
<email>jessekempf@gmail.com</email></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -8295,7 +8295,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Philippe Pepiot
|
||||
<para>Philippe Pepiot
|
||||
<email>phil@philpep.org</email></para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
@ -567,7 +567,7 @@
|
|||
<para>&a.chinsan;</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<listitem>
|
||||
<para>&a.davide;</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@
|
|||
|
||||
<abstract>
|
||||
<para>The present article assumes a basic understanding of <application>CVSup</application>
|
||||
operation. It documents several delicate issues connected with
|
||||
operation. It documents several delicate issues connected with
|
||||
source synchronization via <application>CVSup</application>, viz. effective solutions to
|
||||
the problem of stale files as well as special source updating
|
||||
cases; which issues are likely to cause apparently inexplicable
|
||||
|
@ -42,17 +42,17 @@
|
|||
|
||||
<sect1 id="preface">
|
||||
<title>Preface</title>
|
||||
|
||||
<para>This document is the fruit of the author's attempts to
|
||||
|
||||
<para>This document is the fruit of the author's attempts to
|
||||
fully understand the niceties of <application>CVSup</application> & source updating. :-)
|
||||
While the author has made every effort to make these pages
|
||||
as informative and correct as possible, he is only human and
|
||||
While the author has made every effort to make these pages
|
||||
as informative and correct as possible, he is only human and
|
||||
may have made all sorts of typos, mistakes, etc. He will be
|
||||
very grateful for any comments and/or suggestions you send to
|
||||
his e-mail address, <email>bartequi@neomedia.it</email>.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
|
||||
<sect1 id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
|
@ -63,7 +63,7 @@
|
|||
FAQ</ulink>,
|
||||
you may have noticed Question 12 & 13.</para>
|
||||
|
||||
<para>When updating any collection of sources (eg
|
||||
<para>When updating any collection of sources (eg
|
||||
<filename>/usr/ports</filename>), &man.cvsup.1; makes use of
|
||||
the related checkouts file in order to perform the updating
|
||||
process in the most efficient and correct way. In this example
|
||||
|
@ -72,12 +72,12 @@ FAQ</ulink>,
|
|||
your base is <filename>/usr</filename>.</para>
|
||||
|
||||
<para>A checkouts file contains information on the current status
|
||||
of your sources—in a way, a sort of <quote>photograph</quote>. This
|
||||
of your sources—in a way, a sort of <quote>photograph</quote>. This
|
||||
significant information enables <command>cvsup</command> to retrieve updates most
|
||||
effectively. Further, and maybe more important, it enables <command>cvsup</command>
|
||||
to correctly manage your sources by locally deleting any files
|
||||
no longer present in the repository, thus leaving no stale files
|
||||
on your system. In fact, without a checkouts file, <command>cvsup</command> would
|
||||
on your system. In fact, without a checkouts file, <command>cvsup</command> would
|
||||
<emphasis>not</emphasis> know which files your collection was composed of (cf
|
||||
&man.cvsup.1; and the fallback method for details); as a result,
|
||||
it could not delete on your system those files no longer present
|
||||
|
@ -95,9 +95,9 @@ FAQ</ulink>,
|
|||
<sect1 id="script">
|
||||
<title>A useful python script: <command>cvsupchk</command></title>
|
||||
|
||||
<para>Alternatively, in order to examine your sources for
|
||||
inconsistencies, you may wish to utilize the <command>cvsupchk</command> python
|
||||
script; which script is currently found in
|
||||
<para>Alternatively, in order to examine your sources for
|
||||
inconsistencies, you may wish to utilize the <command>cvsupchk</command> python
|
||||
script; which script is currently found in
|
||||
<filename>/usr/ports/net/cvsup/work/cvsup-16.1/contrib/cvsupchk</filename>,
|
||||
together with a nice <filename>README</filename>. Prerequisites:</para>
|
||||
|
||||
|
@ -127,9 +127,9 @@ FAQ</ulink>,
|
|||
|
||||
<screen>&prompt.user; <filename>/path/to/</filename><userinput>cvsupchk -d /usr -c /usr/sup/src-all/checkouts.cvs:RELENG_4 | more</userinput></screen>
|
||||
|
||||
<para>In each case, <command>cvsupchk</command> will inspect your sources for
|
||||
inconsistencies by utilizing the information contained in the
|
||||
related checkouts file. Such anomalies as deleted files being
|
||||
<para>In each case, <command>cvsupchk</command> will inspect your sources for
|
||||
inconsistencies by utilizing the information contained in the
|
||||
related checkouts file. Such anomalies as deleted files being
|
||||
present (aka stale files), missing checked-out files, extra RCS
|
||||
files, and dead directories will be printed to standard output.</para>
|
||||
|
||||
|
@ -147,15 +147,15 @@ FAQ</ulink>,
|
|||
<literal>src-all</literal></title>
|
||||
|
||||
<para>If you specify eg <literal>tag=A</literal> in your <filename>supfile</filename>, <command>cvsup</command> will create
|
||||
a checkouts file called <filename>checkouts.cvs:A</filename>:
|
||||
a checkouts file called <filename>checkouts.cvs:A</filename>:
|
||||
for instance, if <literal>tag=RELENG_4</literal>, a checkouts file called
|
||||
<filename>checkouts.cvs:RELENG_4</filename> is generated.
|
||||
<filename>checkouts.cvs:RELENG_4</filename> is generated.
|
||||
This file will be used to retrieve and/or store information
|
||||
identifying your 4-STABLE sources.</para>
|
||||
|
||||
<para>When tracking <literal>src-all</literal>, if you wish to
|
||||
pass from <literal>tag=A</literal> to <literal>tag=B</literal> (A less/greater than B not making
|
||||
any difference) and if your checkouts file is
|
||||
pass from <literal>tag=A</literal> to <literal>tag=B</literal> (A less/greater than B not making
|
||||
any difference) and if your checkouts file is
|
||||
<filename>checkouts.cvs:A</filename>, the following actions
|
||||
should be performed:</para>
|
||||
|
||||
|
@ -178,8 +178,8 @@ checkouts.cvs:B</userinput>
|
|||
</orderedlist>
|
||||
|
||||
<para>The <command>cvsup</command> utility will look for <filename>checkouts.cvs:B</filename>—in
|
||||
that the target is B; that is, <command>cvsup</command> will make use of
|
||||
the information contained therein to correctly manage your
|
||||
that the target is B; that is, <command>cvsup</command> will make use of
|
||||
the information contained therein to correctly manage your
|
||||
sources.</para>
|
||||
|
||||
<para>The benefits:</para>
|
||||
|
@ -191,17 +191,17 @@ checkouts.cvs:B</userinput>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>less load is placed on the server, in that <command>cvsup</command>
|
||||
<para>less load is placed on the server, in that <command>cvsup</command>
|
||||
operates in the most efficient way.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
||||
<para>For example, <literal>A=RELENG_4</literal>, <literal>B=.</literal>. The period in <literal>B=.</literal> means
|
||||
-CURRENT. This is a rather typical update, from 4-STABLE
|
||||
to -CURRENT. While it is straightforward to <quote>downgrade</quote> your
|
||||
sources (e.g., from -CURRENT to -STABLE), downgrading a system
|
||||
is quite another matter. You are STRONGLY advised not to
|
||||
<para>For example, <literal>A=RELENG_4</literal>, <literal>B=.</literal>. The period in <literal>B=.</literal> means
|
||||
-CURRENT. This is a rather typical update, from 4-STABLE
|
||||
to -CURRENT. While it is straightforward to <quote>downgrade</quote> your
|
||||
sources (e.g., from -CURRENT to -STABLE), downgrading a system
|
||||
is quite another matter. You are STRONGLY advised not to
|
||||
attempt such an operation, unless you know exactly what you
|
||||
are doing.</para>
|
||||
</sect2>
|
||||
|
@ -209,8 +209,8 @@ checkouts.cvs:B</userinput>
|
|||
<sect2>
|
||||
<title>Updating to the same tag as of a different date</title>
|
||||
|
||||
<para>If you wish to switch from <literal>tag=A</literal> to <literal>tag=A</literal> as of a
|
||||
different GMT date (say, <literal>date=D</literal>), you will execute the
|
||||
<para>If you wish to switch from <literal>tag=A</literal> to <literal>tag=A</literal> as of a
|
||||
different GMT date (say, <literal>date=D</literal>), you will execute the
|
||||
following:</para>
|
||||
|
||||
<orderedlist>
|
||||
|
@ -225,25 +225,25 @@ checkouts.cvs:B</userinput>
|
|||
</orderedlist>
|
||||
|
||||
<para>Whether the new date precedes that of the last sync
|
||||
operation with <literal>tag=A</literal> or not, it is immaterial. For example,
|
||||
in order to specify the date <quote>August 27, 2000, 10:00:00 GMT</quote>
|
||||
operation with <literal>tag=A</literal> or not, it is immaterial. For example,
|
||||
in order to specify the date <quote>August 27, 2000, 10:00:00 GMT</quote>
|
||||
you write the line:</para>
|
||||
|
||||
|
||||
<programlisting>src-all tag=RELENG_4 date=2000.08.27.10.00.00</programlisting>
|
||||
|
||||
<note><para>The format of a date is rigid. You have to specify
|
||||
all the components of the date: century (<quote>20</quote>, i.e., the 21st
|
||||
century, must be supplied whereas <quote>19</quote>, the past century, can
|
||||
be omitted), year, month, day, hour, minutes, seconds—as
|
||||
shown in the above example. For more information, please
|
||||
<note><para>The format of a date is rigid. You have to specify
|
||||
all the components of the date: century (<quote>20</quote>, i.e., the 21st
|
||||
century, must be supplied whereas <quote>19</quote>, the past century, can
|
||||
be omitted), year, month, day, hour, minutes, seconds—as
|
||||
shown in the above example. For more information, please
|
||||
see &man.cvsup.1;.</para></note>
|
||||
|
||||
<para>Whether or not a date is specified, the checkouts file
|
||||
<para>Whether or not a date is specified, the checkouts file
|
||||
is called <filename>checkouts.cvs:A</filename> (e.g.,
|
||||
<filename>checkouts.cvs:RELENG_4</filename>). As a result,
|
||||
no particular action is needed in order to revert to the
|
||||
previous state: you have to modify the date in the <filename>supfile</filename>,
|
||||
no particular action is needed in order to revert to the
|
||||
previous state: you have to modify the date in the <filename>supfile</filename>,
|
||||
and run <command>csvup</command> again.</para>
|
||||
</sect2>
|
||||
|
||||
|
@ -264,9 +264,9 @@ checkouts.cvs:B</userinput>
|
|||
<programlisting>ports-all tag=.</programlisting>
|
||||
All subsequent updates will be carried out smoothly.</para>
|
||||
|
||||
<para>If you have been reading the apparently nit-picking
|
||||
remarks in these sections, you will probably have recognized
|
||||
the potential for trouble in a source updating process.
|
||||
<para>If you have been reading the apparently nit-picking
|
||||
remarks in these sections, you will probably have recognized
|
||||
the potential for trouble in a source updating process.
|
||||
A number of people have actually run into problems. You have
|
||||
been warned. :-)</para>
|
||||
</sect2>
|
||||
|
|
|
@ -72,7 +72,7 @@
|
|||
support. &os; 4.X users should consult the &man.ipfw.8;
|
||||
manual page for more information on using IPFW2 on their
|
||||
systems, and should pay particular attention to the
|
||||
<emphasis>USING IPFW2 IN FreeBSD-STABLE</emphasis>
|
||||
<emphasis>USING IPFW2 IN FreeBSD-STABLE</emphasis>
|
||||
section.</para></note>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
@ -180,7 +180,7 @@ fwcmd="/sbin/ipfw"
|
|||
oif="tun0"
|
||||
|
||||
# Define our inside interface. This is usually your network
|
||||
# card. Be sure to change this to match your own network
|
||||
# card. Be sure to change this to match your own network
|
||||
# interface.
|
||||
iif="fxp0"
|
||||
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
<article lang='en'>
|
||||
<articleinfo>
|
||||
<title>Diskless X Server: a how to guide</title>
|
||||
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Jerry</firstname>
|
||||
|
@ -25,16 +25,16 @@
|
|||
</address>
|
||||
</affiliation>
|
||||
</author></authorgroup>
|
||||
|
||||
|
||||
<pubdate>28-December-1996</pubdate>
|
||||
|
||||
<releaseinfo>$FreeBSD$</releaseinfo>
|
||||
|
||||
|
||||
<copyright>
|
||||
<year>1996</year>
|
||||
<holder>Jerry Kendall</holder>
|
||||
</copyright>
|
||||
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.3com;
|
||||
|
@ -56,15 +56,15 @@
|
|||
system is a 486DX2-66. I set up a diskless FreeBSD (complete) that
|
||||
uses no local disk. The server in that case is a Sun 670MP running
|
||||
&sunos; 4.1.3. The same setup configuration was needed for both.</para>
|
||||
|
||||
|
||||
<para>I am sure that there is stuff that needs to be added
|
||||
to this. Please send me any comments.</para>
|
||||
</abstract>
|
||||
</articleinfo>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title>Creating the boot floppy (On the diskless system)</title>
|
||||
|
||||
|
||||
<para>Since the network boot loaders will not work with some of the TSR's
|
||||
and such that &ms-dos; uses, it is best to create a dedicated boot floppy
|
||||
or, if you can, create an &ms-dos; menu that will (via the
|
||||
|
@ -72,7 +72,7 @@
|
|||
ask what configuration to load when the system starts. The later is the
|
||||
method that I use and it works great. My &ms-dos; (6.x) menu is
|
||||
below.</para>
|
||||
|
||||
|
||||
<example>
|
||||
<title><filename>config.sys</filename></title>
|
||||
|
||||
|
@ -105,10 +105,10 @@ nb8390.com
|
|||
:end</programlisting>
|
||||
</example>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title>Getting the network boot programs (On the server)</title>
|
||||
|
||||
|
||||
<para>Compile the <quote>net-boot</quote> programs that are located in
|
||||
<filename>/usr/src/sys/i386/boot/netboot</filename>. You should read
|
||||
the comments at the top of the <filename>Makefile</filename>. Adjust as
|
||||
|
@ -119,10 +119,10 @@ nb8390.com
|
|||
server. It will load the kernel from the boot server. At this point,
|
||||
put both programs on the &ms-dos; boot floppy created earlier.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title>Determine which program to run (On the diskless system)</title>
|
||||
|
||||
|
||||
<para>If you know the chipset that your Ethernet adapter uses, this is
|
||||
easy. If you have the NS8390 chipset, or a NS8390 based chipset, use
|
||||
<filename>nb8390.com</filename>. If you have a &tm.3com; 509 based chipset,
|
||||
|
@ -134,13 +134,13 @@ nb8390.com
|
|||
|
||||
<sect1>
|
||||
<title>Booting across the network</title>
|
||||
|
||||
|
||||
<para>Boot the diskless system with out any config.sys/autoexec.bat
|
||||
files. Try running the boot program for your Ethernet adapter.</para>
|
||||
|
||||
<para>My Ethernet adapter is running in WD8013 16bit mode so I run
|
||||
<filename>nb8390.com</filename></para>
|
||||
|
||||
|
||||
<screen><prompt>C:></prompt> <userinput>cd \netboot</userinput>
|
||||
<prompt>C:></prompt> <userinput>nb8390</userinput>
|
||||
|
||||
|
@ -165,18 +165,18 @@ Searching for server...</screen>
|
|||
message, verify that you did indeed set the compile time defines in the
|
||||
<filename>Makefile</filename> correctly.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title>Allowing systems to boot across the network (On the server)</title>
|
||||
|
||||
|
||||
<para>Make sure the <filename>/etc/inetd.conf</filename> file has entries
|
||||
for tftp and bootps. Mine are listed below:</para>
|
||||
|
||||
|
||||
<programlisting>tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot
|
||||
#
|
||||
# Additions by who ever you are
|
||||
bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab</programlisting>
|
||||
|
||||
|
||||
<para>If you have to change the <filename>/etc/inetd.conf</filename> file,
|
||||
send a <literal>HUP</literal> signal to &man.inetd.8;. To do this, get the
|
||||
process ID of <command>inetd</command> with <command>ps -ax | grep inetd | grep -v
|
||||
|
@ -200,7 +200,7 @@ bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab</progra
|
|||
:ip=199.246.76.2:\
|
||||
:gw=199.246.76.1:\
|
||||
:vm=rfc1048:</programlisting>
|
||||
|
||||
|
||||
<para>The lines are as follows:</para>
|
||||
|
||||
<informaltable frame="none" pgwide="1">
|
||||
|
@ -280,10 +280,10 @@ hostname altair.example.com</programlisting>
|
|||
<para>The NFS mounted root filesystem will be mounted <emphasis>read
|
||||
only</emphasis>.</para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>The hierarchy for the diskless system can be re-mounted allowing
|
||||
read-write operations if required.</para>
|
||||
|
||||
|
||||
<para>I use my spare 386DX-40 as a dedicated X terminal.</para>
|
||||
|
||||
<para>The hierarchy for <hostid>altair</hostid> is:</para>
|
||||
|
@ -314,7 +314,7 @@ hostname altair.example.com</programlisting>
|
|||
-r-xr-xr-x 1 root bin 73728 Dec 13 22:38 ./sbin/mount
|
||||
-r-xr-xr-x 1 root wheel 1992 Jun 10 1995 ./dev/MAKEDEV.local
|
||||
-r-xr-xr-x 1 root wheel 24419 Jun 10 1995 ./dev/MAKEDEV</screen>
|
||||
|
||||
|
||||
<para>If you are not using &man.devfs.5; (which is the default
|
||||
in FreeBSD 5.X), you should make sure that you
|
||||
do not forget to run <command>MAKEDEV all</command> in the
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
|
||||
<article lang='en'>
|
||||
<articleinfo>
|
||||
<title>The Euro symbol on
|
||||
<title>The Euro symbol on
|
||||
<systemitem class="osname">FreeBSD</systemitem></title>
|
||||
|
||||
<authorgroup>
|
||||
|
@ -29,7 +29,7 @@
|
|||
<year>2003</year>
|
||||
<holder>The FreeBSD Documentation Project</holder>
|
||||
</copyright>
|
||||
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.general;
|
||||
|
@ -46,7 +46,7 @@
|
|||
will first focus on the more important parts like being able to
|
||||
correctly display the symbol on the console. Later sections will deal
|
||||
with configuring particular programs like
|
||||
<application>X11</application>.
|
||||
<application>X11</application>.
|
||||
</para>
|
||||
|
||||
<para>Lots of helpful input came from Oliver Fromme, Tom Rhodes and
|
||||
|
@ -59,16 +59,16 @@
|
|||
<sect1>
|
||||
<title>The Euro in a nutshell</title>
|
||||
|
||||
<para>If you already feel comfortable with
|
||||
<ulink url="&url.books.handbook;/l10n.html">localization</ulink> as
|
||||
described in the <systemitem class="osname">FreeBSD</systemitem>
|
||||
Handbook you might be only interested in the following facts which
|
||||
will get you started quickly:</para>
|
||||
<para>If you already feel comfortable with
|
||||
<ulink url="&url.books.handbook;/l10n.html">localization</ulink> as
|
||||
described in the <systemitem class="osname">FreeBSD</systemitem>
|
||||
Handbook you might be only interested in the following facts which
|
||||
will get you started quickly:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>ISO8859-15</term>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>This is a slight modification of the commonly used ISO8859-1
|
||||
character map. It includes the Euro symbol. Used for the
|
||||
|
@ -89,8 +89,8 @@
|
|||
<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
|
||||
|
||||
<listitem>
|
||||
<para>Appropriate keyboard maps depending on your language. Set your
|
||||
<literal>keymap</literal> entry in <filename>rc.conf</filename> to
|
||||
<para>Appropriate keyboard maps depending on your language. Set your
|
||||
<literal>keymap</literal> entry in <filename>rc.conf</filename> to
|
||||
one of these.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
@ -124,7 +124,7 @@
|
|||
|
||||
<sect1 id="general">
|
||||
<title>A general remark</title>
|
||||
|
||||
|
||||
<para>In the following sections we will often refer to
|
||||
<emphasis>ISO8859-15</emphasis>. This is the standard notation starting
|
||||
with <systemitem class="osname">FreeBSD</systemitem> 4.5. In older
|
||||
|
@ -132,23 +132,23 @@
|
|||
<emphasis>ISO_8859-15</emphasis> or <emphasis>DIS_8859-15</emphasis>.
|
||||
</para>
|
||||
|
||||
<para>If you are using an older version of
|
||||
<systemitem class="osname">FreeBSD</systemitem>, be sure to take a
|
||||
<para>If you are using an older version of
|
||||
<systemitem class="osname">FreeBSD</systemitem>, be sure to take a
|
||||
look at <filename>/usr/share/locale/</filename> in order to find out
|
||||
which naming convention is in place.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="console">
|
||||
<title>The console</title>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Setting up your console font</title>
|
||||
|
||||
<para>Depending on your console resolution and size you will need one of
|
||||
the following lines in <filename>rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
|
||||
font8x14="iso15-8x14.fnt"
|
||||
<programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
|
||||
font8x14="iso15-8x14.fnt"
|
||||
font8x8="iso15-8x8.fnt"</programlisting>
|
||||
|
||||
<para>This will effectively select the ISO8859-15 also known as Latin-9
|
||||
|
@ -200,8 +200,8 @@ BEGIN {
|
|||
combination is necessary (e.g.: <keycombo action="simul"><keycap>Alt
|
||||
Gr</keycap><keycap>e</keycap></keycombo>) to decimal value 164.
|
||||
If running into problems, the best way to check is to take a look at
|
||||
<filename>/usr/share/syscons/keymaps/*.kbd</filename>. The format of
|
||||
the key mapping files is described in &man.keyboard.4;.
|
||||
<filename>/usr/share/syscons/keymaps/*.kbd</filename>. The format of
|
||||
the key mapping files is described in &man.keyboard.4;.
|
||||
&man.kbdcontrol.1; can be used to load a custom keymap.</para>
|
||||
|
||||
<para>Once the correct keyboard map is selected, it should be added to
|
||||
|
@ -210,13 +210,13 @@ BEGIN {
|
|||
<programlisting>keymap="<replaceable>german.iso</replaceable>" # or another map</programlisting>
|
||||
|
||||
<para>As stated above, this step has most probably already been taken
|
||||
by you at installation time (with
|
||||
<application>sysinstall</application>). If not, either reboot or
|
||||
by you at installation time (with
|
||||
<application>sysinstall</application>). If not, either reboot or
|
||||
load the new keymap via &man.kbdcontrol.1;.</para>
|
||||
|
||||
<para>To verify the keyboard mapping, switch to a new console and at
|
||||
<para>To verify the keyboard mapping, switch to a new console and at
|
||||
the login prompt, <emphasis>instead of logging</emphasis> in, try to
|
||||
type the <keycap>Euro</keycap> key. If it is not working, either
|
||||
type the <keycap>Euro</keycap> key. If it is not working, either
|
||||
file a bug report via &man.send-pr.1; or make sure you in fact chose
|
||||
the right keyboard map.</para>
|
||||
|
||||
|
@ -226,13 +226,13 @@ BEGIN {
|
|||
<application>tcsh</application>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Fixing the environment variables</title>
|
||||
|
||||
<para>The shells (<application>bash</application>, <application>tcsh</application>) revert to the &man.readline.3; library
|
||||
which in turn respects the <envar>LC_CTYPE</envar> environment
|
||||
variable. <envar>LC_CTYPE</envar> must be set before the shell is
|
||||
<para>The shells (<application>bash</application>, <application>tcsh</application>) revert to the &man.readline.3; library
|
||||
which in turn respects the <envar>LC_CTYPE</envar> environment
|
||||
variable. <envar>LC_CTYPE</envar> must be set before the shell is
|
||||
completely running. Luckily it suffices to add the line:</para>
|
||||
|
||||
<programlisting>export LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
|
||||
|
@ -250,11 +250,11 @@ BEGIN {
|
|||
however.</para>
|
||||
|
||||
<note>
|
||||
<para>An alternative to modifying <filename>.login</filename> and
|
||||
<para>An alternative to modifying <filename>.login</filename> and
|
||||
<filename>.bash_profile</filename> is to set the environment
|
||||
variables through the &man.login.conf.5; mechanism. This approach
|
||||
has the advantage of assigning login classes to certain users (e.g.
|
||||
French users, Italian users, etc) <emphasis>in one
|
||||
French users, Italian users, etc) <emphasis>in one
|
||||
place</emphasis>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
@ -294,14 +294,14 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
|
|||
<filename>/usr/X11R6/lib/X11/app-defaults</filename> and add the correct
|
||||
font. Let us demonstrate this with
|
||||
<application>xterm</application>.</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
|
||||
&prompt.root; vi XTerm</screen>
|
||||
|
||||
<para>Add the following line to the beginning of the file:</para>
|
||||
|
||||
<programlisting>*font: -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
|
||||
|
||||
|
||||
<para>Finally, restart X and make sure, fonts can be displayed by
|
||||
executing the above <link linkend="awk-test">awk script</link>. All
|
||||
major applications should respect the keyboard mapping and the font
|
||||
|
@ -310,7 +310,7 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
|
|||
|
||||
<sect1 id="problems">
|
||||
<title>Open problems</title>
|
||||
|
||||
|
||||
<para>Of course, the author would like to receive feedback. In addition,
|
||||
at least let me know if you have fixes for one of these open
|
||||
problems:</para>
|
||||
|
@ -320,7 +320,7 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
|
|||
<para>Describe alternative way of setting up <application>Xorg</application>:
|
||||
<filename role="package">x11/xkeycaps</filename></para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Settings in <application>GNOME</application></para>
|
||||
</listitem>
|
||||
|
|
|
@ -118,9 +118,9 @@
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="what-a-real-unix">
|
||||
<title>What, a real &unix;?</title>
|
||||
<title>What, a real &unix;?</title>
|
||||
|
||||
<para>The BSD operating systems are not clones, but open source
|
||||
derivatives of AT&T's Research &unix; operating system, which is also
|
||||
|
@ -189,7 +189,7 @@
|
|||
<ulink url="http://www.dragonflybsd.org/">DragonFlyBSD</ulink> split
|
||||
off from FreeBSD.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="why-is-bsd-not-better-known">
|
||||
<title>Why is BSD not better known?</title>
|
||||
|
||||
|
|
|
@ -539,7 +539,7 @@ GS><userinput>quit</userinput></screen>
|
|||
<title>Using type 1 fonts with Groff</title>
|
||||
|
||||
<para>Now that the new font can be used by both <application>X11</application> and
|
||||
<application>Ghostscript</application>, how can one use the new font
|
||||
<application>Ghostscript</application>, how can one use the new font
|
||||
with <application>groff</application>? First of
|
||||
all, since we are dealing with type 1 &postscript; fonts, the
|
||||
<application>groff</application> device that is applicable is the <emphasis>ps</emphasis>
|
||||
|
@ -852,7 +852,7 @@ Converting 3of9.ttf to A.pfa and B.afm.
|
|||
fonts available in this format.</para>
|
||||
|
||||
<para>Unfortunately, there are few applications that I am aware of
|
||||
that can use this format: <application>Ghostscript</application>
|
||||
that can use this format: <application>Ghostscript</application>
|
||||
and <application>Povray</application> come to mind.
|
||||
<application>Ghostscript's</application> support, according to the documentation, is
|
||||
rudimentary and the results are likely to be inferior to type 1
|
||||
|
@ -879,7 +879,7 @@ Converting 3of9.ttf to A.pfa and B.afm.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><application>xfstt</application> is another font server for
|
||||
<para><application>xfstt</application> is another font server for
|
||||
<application>X11</application>,
|
||||
available under <ulink url="
|
||||
ftp://sunsite.unc.edu/pub/Linux/X11/fonts/"></ulink>.</para>
|
||||
|
@ -916,7 +916,7 @@ Converting 3of9.ttf to A.pfa and B.afm.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Checkout the fonts that come with the Ports Collection in
|
||||
<para>Checkout the fonts that come with the Ports Collection in
|
||||
<filename>x11-fonts/</filename></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
@ -65,7 +65,7 @@
|
|||
|
||||
<para>There are two possible modes of disk formatting:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><firstterm>compatibility mode</firstterm>: Arranging a
|
||||
disk so that it has a slice table for use with other
|
||||
|
@ -95,7 +95,7 @@
|
|||
allowing access to the Label and Partition editors and a Write
|
||||
feature which will update just the selected disk and slice
|
||||
without affecting other disks. The other method is running
|
||||
the tools manually from a root command line. For
|
||||
the tools manually from a root command line. For
|
||||
dedicated mode, only three or four commands are involved while
|
||||
<command>sysinstall</command> requires some
|
||||
manipulation.</para>
|
||||
|
@ -155,7 +155,7 @@ now. -->
|
|||
Each filesystem and swap area on a disk resides in a
|
||||
partition. Maintained using the disklabel utility.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>sector: Smallest subdivision of a disk. One sector
|
||||
usually represents 512 bytes of data.</para>
|
||||
|
@ -188,7 +188,7 @@ now. -->
|
|||
to the system and a disk placed in the drive during startup,
|
||||
so the kernel can determine the drive's geometry. Check the
|
||||
<command>dmesg</command> output and make sure your device and
|
||||
the disk's size is listed. If the kernel reports
|
||||
the disk's size is listed. If the kernel reports
|
||||
|
||||
<informalexample>
|
||||
<screen>Can't get the size</screen>
|
||||
|
@ -224,11 +224,11 @@ now. -->
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Start sysinstall as root by typing
|
||||
<para>Start sysinstall as root by typing
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
|
||||
</informalexample>
|
||||
</informalexample>
|
||||
|
||||
from the command prompt.</para>
|
||||
</step>
|
||||
|
@ -249,12 +249,12 @@ now. -->
|
|||
<step>
|
||||
<para>If you are using this entire disk for FreeBSD, select
|
||||
<command>A</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>When asked if you still want to do this, answer
|
||||
<command>Yes</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Select <command>Write</command>.</para>
|
||||
|
@ -263,7 +263,7 @@ now. -->
|
|||
<step>
|
||||
<para>When warned about writing on installed systems, answer
|
||||
<command>Yes</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>When asked about installing a boot loader, select
|
||||
|
@ -293,13 +293,13 @@ now. -->
|
|||
<command>C</command> to Create a partition, accept the
|
||||
default size, partition type Filesystem, and a mountpoint
|
||||
(which is not used).</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Enter <command>W</command> when done and confirm to
|
||||
continue. The filesystem will be newfs'd for you, unless
|
||||
you select otherwise (for new partitions you will want to
|
||||
do this!). You will get the error:
|
||||
do this!). You will get the error:
|
||||
|
||||
<informalexample>
|
||||
<screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
|
||||
|
@ -330,7 +330,7 @@ now. -->
|
|||
|
||||
<para>If you need to edit the disklabel to create multiple
|
||||
partitions (such as swap), use the following: </para>
|
||||
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
|
||||
&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
|
||||
|
@ -363,11 +363,11 @@ now. -->
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Start sysinstall as root by typing
|
||||
<para>Start sysinstall as root by typing
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
|
||||
</informalexample>
|
||||
</informalexample>
|
||||
|
||||
from the command prompt.</para>
|
||||
</step>
|
||||
|
@ -388,10 +388,10 @@ now. -->
|
|||
<step>
|
||||
<para>If you are using this entire disk for FreeBSD, select
|
||||
<command>A</command>.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>When asked:
|
||||
<para>When asked:
|
||||
|
||||
<informalexample>
|
||||
<screen>Do you want to do this with a true partition entry so as to remain
|
||||
|
@ -419,18 +419,18 @@ drive(s)?</screen>
|
|||
<step>
|
||||
<para>You will be asked about the boot manager, select
|
||||
<command>None</command> again. </para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Select <command>Label</command> from the Index
|
||||
menu.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Label as desired. For a single partition, accept the
|
||||
default size, type filesystem, and a mountpoint (which
|
||||
is not used).</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>The filesystem will be newfs'd for you, unless you
|
||||
|
@ -438,7 +438,7 @@ drive(s)?</screen>
|
|||
this!). You will get the error:
|
||||
|
||||
<informalexample>
|
||||
<screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
|
||||
<screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
|
||||
</informalexample>
|
||||
|
||||
Ignore.</para>
|
||||
|
@ -479,7 +479,7 @@ drive(s)?</screen>
|
|||
<para>When newfsing the drive, do NOT newfs the `c'
|
||||
partition. Instead, newfs the partition where the
|
||||
non-swap space lies.</para>
|
||||
</step>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Add an entry to <filename>/etc/fstab</filename> as
|
||||
|
@ -489,7 +489,7 @@ drive(s)?</screen>
|
|||
<programlisting>/dev/ad0b none swap sw 0 0
|
||||
</programlisting>
|
||||
</informalexample>
|
||||
|
||||
|
||||
<para>Change <filename>/dev/ad0b</filename> to the device of the newly added
|
||||
space.</para>
|
||||
</step>
|
||||
|
@ -510,7 +510,7 @@ swapon: added /dev/da0b as swap space</screen>
|
|||
<sect2>
|
||||
<title>Copying the Contents of Disks</title>
|
||||
<!-- Should have specific tag -->
|
||||
|
||||
|
||||
<para>Submitted By: Renaud Waldura
|
||||
(<email>renaud@softway.com</email>) </para>
|
||||
|
||||
|
|
|
@ -42,10 +42,10 @@
|
|||
list.</para>
|
||||
</abstract>
|
||||
</articleinfo>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title id="Introduction">Introduction</title>
|
||||
|
||||
|
||||
<para><literal>FreeBSD-questions</literal> is a mailing list maintained by
|
||||
the FreeBSD project to help people who have questions about the normal
|
||||
use of FreeBSD. Another group, <literal>FreeBSD-hackers</literal>,
|
||||
|
@ -62,7 +62,7 @@
|
|||
url="http://www.catb.org/~esr/faqs/hacker-howto.html">How To Become
|
||||
A Hacker</ulink></para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>This is a regular posting aimed to help both those seeking advice
|
||||
from FreeBSD-questions (the <quote>newcomers</quote>), and also those
|
||||
who answer the questions (the <quote>hackers</quote>).</para>
|
||||
|
@ -80,7 +80,7 @@
|
|||
FreeBSD-questions. In the following section, I recommend how to submit
|
||||
a question; after that, we will look at how to answer one.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title id="subscribe">How to subscribe to FreeBSD-questions</title>
|
||||
|
||||
|
@ -107,7 +107,7 @@
|
|||
If you ever should want to leave the list, you will need the information
|
||||
there. See the next section for more details.</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title id="unsubscribe">How to unsubscribe from FreeBSD-questions</title>
|
||||
|
||||
|
@ -129,7 +129,7 @@ General information about the mailing list is at:
|
|||
If you ever want to unsubscribe or change your options (e.g., switch to
|
||||
or from digest mode, change your password, etc.), visit your
|
||||
subscription page at:
|
||||
|
||||
|
||||
http://lists.freebsd.org/mailman/options/freebsd-questions/grog%40lemsi.de
|
||||
|
||||
You can also make such adjustments via email by sending a message to:
|
||||
|
@ -175,7 +175,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
<literal>FreeBSD-hackers</literal>. In some cases, it is not really
|
||||
clear which group you should ask. The following criteria should help
|
||||
for 99% of all questions, however:</para>
|
||||
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>If the question is of a general nature, ask
|
||||
|
@ -183,13 +183,13 @@ your options page that will email your current password to you.</literallayout>
|
|||
about installing FreeBSD or the use of a particular &unix;
|
||||
utility.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>If you think the question relates to a bug, but you are not sure,
|
||||
or you do not know how to look for it, send the message to
|
||||
<literal>FreeBSD-questions</literal>.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>If the question relates to a bug, and you are
|
||||
<emphasis>sure</emphasis> that it is a bug (for example, you can
|
||||
|
@ -216,7 +216,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
|
||||
<sect1>
|
||||
<title id="before">Before submitting a question</title>
|
||||
|
||||
|
||||
<para>You can (and should) do some things yourself before asking a question
|
||||
on one of the mailing lists:</para>
|
||||
|
||||
|
@ -260,10 +260,10 @@ your options page that will email your current password to you.</literallayout>
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title id="submit">How to submit a question</title>
|
||||
|
||||
|
||||
<para>When submitting a question to FreeBSD-questions, consider the
|
||||
following points:</para>
|
||||
|
||||
|
@ -280,7 +280,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
you do not. In the rest of this document, we will look at how to get
|
||||
the most out of your question to FreeBSD-questions.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Not everybody who answers FreeBSD questions reads every message:
|
||||
they look at the subject line and decide whether it interests them.
|
||||
|
@ -297,7 +297,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
speak English as their first language, and we try to make
|
||||
allowances for that, but it is really painful to try to read a
|
||||
message written full of typos or without any line breaks.</para>
|
||||
|
||||
|
||||
<para>Do not underestimate the effect that a poorly formatted mail
|
||||
message has, not just on the FreeBSD-questions mailing list.
|
||||
Your mail message is all people see of you, and if it is poorly
|
||||
|
@ -347,7 +347,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
use mailers which do not get on very well with
|
||||
<acronym>MIME</acronym>.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Make sure your time and time zone are set correctly. This may
|
||||
seem a little silly, since your message still gets there, but many
|
||||
|
@ -377,7 +377,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
sources, though of course you should not be sending questions
|
||||
about -CURRENT to FreeBSD-questions.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem><para>With any problem which <emphasis>could</emphasis> be
|
||||
hardware related, tell us about your hardware. In case of
|
||||
doubt, assume it is possible that it is hardware. What kind of
|
||||
|
@ -389,7 +389,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
tells not just what hardware you are running, but what version of
|
||||
FreeBSD as well.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>If you get error messages, do not say <quote>I get error
|
||||
messages</quote>, say (for example) <quote>I get the error
|
||||
|
@ -435,7 +435,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
<para>This redirects the information to the file
|
||||
<filename>/tmp/dmesg.out</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>If you do all this, and you still do not get an answer, there
|
||||
could be other reasons. For example, the problem is so complicated
|
||||
|
@ -447,7 +447,7 @@ your options page that will email your current password to you.</literallayout>
|
|||
only make you unpopular.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
||||
<para>To summarize, let's assume you know the answer to the following
|
||||
question (yes, it is the same one in each case).
|
||||
You choose which of these two questions you would be more prepared to
|
||||
|
@ -490,7 +490,7 @@ fine, but when I try to reboot the system, I get the message
|
|||
you are talking about. Do not forget to trim unnecessary text out,
|
||||
though.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>The text in the subject line stays the same (you did remember to
|
||||
put one in, did you not?). Many mailers will sort messages by
|
||||
|
@ -506,7 +506,7 @@ fine, but when I try to reboot the system, I get the message
|
|||
</listitem>
|
||||
</orderedlist>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1>
|
||||
<title id="answer">How to answer a question</title>
|
||||
|
||||
|
@ -524,7 +524,7 @@ fine, but when I try to reboot the system, I get the message
|
|||
check this is to sort your incoming mail by subject: then
|
||||
(hopefully) you will see the question followed by any answers, all
|
||||
together.</para>
|
||||
|
||||
|
||||
<para>If somebody has already answered it, it does not automatically
|
||||
mean that you should not send another answer. But it makes sense to
|
||||
read all the other answers first.</para>
|
||||
|
@ -570,14 +570,14 @@ fine, but when I try to reboot the system, I get the message
|
|||
send messages with hundreds of CCs. If this is the case, be sure to
|
||||
trim the Cc: lines appropriately.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Include relevant text from the original message. Trim it to the
|
||||
minimum, but do not overdo it. It should still be possible for
|
||||
somebody who did not read the original message to understand what
|
||||
you are talking about.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>Use some technique to identify which text came from the original
|
||||
message, and which text you add. I personally find that prepending
|
||||
|
@ -599,7 +599,7 @@ fine, but when I try to reboot the system, I get the message
|
|||
text such as <quote>Re: </quote>. If your mailer does not do it
|
||||
automatically, you should do it manually.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>If the submitter did not abide by format conventions (lines too
|
||||
long, inappropriate subject line), <emphasis>please</emphasis> fix
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: Writing a GEOM Class
|
||||
|
|
|
@ -69,7 +69,7 @@
|
|||
system and data). It should be followed during a fresh installation of
|
||||
&os;. The steps are simple enough and do not require overly complex
|
||||
interaction with the command line.</para>
|
||||
|
||||
|
||||
<para>After reading this article, you will know:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
@ -77,7 +77,7 @@
|
|||
<para>How to reserve space for journaling during a new installation of
|
||||
&os;.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para>How to load and enable the <literal>geom_journal</literal>
|
||||
module (or build support for it in your custom kernel).</para>
|
||||
|
@ -194,7 +194,7 @@
|
|||
</note>
|
||||
|
||||
<para>For more information about journaling, please read the manual
|
||||
page of &man.gjournal.8;.</para>
|
||||
page of &man.gjournal.8;.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="reserve-space">
|
||||
|
@ -221,7 +221,7 @@
|
|||
<para>In our example, an 80 GB disk is used. The following screenshot
|
||||
shows the default partitions created by <application>Disklabel</application> during
|
||||
installation:</para>
|
||||
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="disklabel1.png"/>
|
||||
|
@ -250,7 +250,7 @@
|
|||
on a typical desktop will cause no harm. If the file system is
|
||||
lightly used (quite probable for a desktop) you may wish to
|
||||
allocate less disk space for its journal.</para>
|
||||
|
||||
|
||||
<para>In our example, we journal both <filename>/usr</filename> and
|
||||
<filename>/var</filename>. You may of course adjust the procedure
|
||||
to your own needs.</para>
|
||||
|
@ -283,7 +283,7 @@
|
|||
partitions to provide for the journals of <filename>/usr</filename> and
|
||||
<filename>/var</filename>. The final result is shown in the following
|
||||
screenshot:</para>
|
||||
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="disklabel2.png"/>
|
||||
|
@ -470,7 +470,7 @@ GEOM_JOURNAL: Journal ad0s1f clean.</screen>
|
|||
was created. Creating the journal would be as simple as:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>gjournal label ad1s1d</userinput></screen>
|
||||
|
||||
|
||||
<para>The journal size will be 1 GB by default. You may adjust it by
|
||||
using the <option>-s</option> option. The value can be given in
|
||||
bytes, or appended by <literal>K</literal>, <literal>M</literal> or
|
||||
|
@ -500,7 +500,7 @@ GEOM_JOURNAL: Journal ad0s1f clean.</screen>
|
|||
<programlisting>options UFS_GJOURNAL # Note: This is already in GENERIC
|
||||
|
||||
options GEOM_JOURNAL # You will have to add this one</programlisting>
|
||||
|
||||
|
||||
<para>Rebuild and reinstall your kernel following the relevant
|
||||
<ulink url="&url.books.handbook;/kernelconfig.html">instructions in
|
||||
the &os; Handbook.</ulink></para>
|
||||
|
@ -586,7 +586,7 @@ GEOM_JOURNAL: Journal ad0s1f clean.
|
|||
can then be used for other purposes, if you so wish.</para>
|
||||
|
||||
<para>Login as <username>root</username> and switch to single user mode:</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>shutdown now</userinput></screen>
|
||||
|
||||
<para>Unmount the journaled partitions:</para>
|
||||
|
@ -639,7 +639,7 @@ tunefs: soft updates set</screen>
|
|||
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</qandaset>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="further-reading">
|
||||
|
@ -659,7 +659,7 @@ tunefs: soft updates set</screen>
|
|||
<para><ulink url="http://lists.freebsd.org/pipermail/freebsd-current/2006-June/064043.html">This post</ulink>
|
||||
in &a.current.name; by &man.gjournal.8;'s developer, &a.pjd;.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://lists.freebsd.org/pipermail/freebsd-questions/2008-April/173501.html">This post</ulink>
|
||||
in &a.questions.name; by &a.ivoras;.</para>
|
||||
|
|
|
@ -512,7 +512,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
Please have look at the <application>CVSup</application> documentation
|
||||
like &man.cvsup.1; and consider using the <option>-s</option>
|
||||
option. This reduces I/O operations by assuming the
|
||||
recorded information about each file is correct.</para>
|
||||
recorded information about each file is correct.</para>
|
||||
</note>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
|
@ -56,7 +56,7 @@
|
|||
|
||||
<sect1 id="xorg">
|
||||
<title>&xorg;</title>
|
||||
|
||||
|
||||
<para>Recent versions of <application>&xorg;</application> work with most display adapters
|
||||
available on laptops these days. Acceleration may not be
|
||||
supported, but a generic SVGA configuration should work.</para>
|
||||
|
@ -81,9 +81,9 @@
|
|||
hardware.</para>
|
||||
|
||||
<para>Most laptops come with two buttons on their pointing
|
||||
devices, which is rather problematic in X (since the middle
|
||||
button is commonly used to paste text); you can map a
|
||||
simultaneous left-right click in your X configuration to
|
||||
devices, which is rather problematic in X (since the middle
|
||||
button is commonly used to paste text); you can map a
|
||||
simultaneous left-right click in your X configuration to
|
||||
a middle button click with the line</para>
|
||||
|
||||
<programlisting>
|
||||
|
@ -92,24 +92,24 @@
|
|||
|
||||
<para>in the <filename>xorg.conf</filename> file in the <literal>InputDevice</literal>
|
||||
section.</para>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="modems">
|
||||
<title>Modems</title>
|
||||
<para>
|
||||
<para>
|
||||
Laptops usually come with internal (on-board) modems.
|
||||
Unfortunately, this almost always means they are
|
||||
Unfortunately, this almost always means they are
|
||||
<quote>winmodems</quote> whose
|
||||
functionality is implemented in software, for which only &windows;
|
||||
drivers are normally available (though a few drivers are beginning
|
||||
drivers are normally available (though a few drivers are beginning
|
||||
to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the <filename role="package">comms/ltmdm</filename> port). If that is the case, you
|
||||
need to buy an external modem: the most compact option is
|
||||
probably a PC Card (PCMCIA) modem, discussed below, but
|
||||
serial or USB modems may be cheaper. Generally, regular
|
||||
modems (non-winmodems) should work fine.
|
||||
probably a PC Card (PCMCIA) modem, discussed below, but
|
||||
serial or USB modems may be cheaper. Generally, regular
|
||||
modems (non-winmodems) should work fine.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="pcmcia">
|
||||
<title>PCMCIA (PC Card) devices</title>
|
||||
|
@ -124,24 +124,24 @@
|
|||
|
||||
<para>&os; 4.X supports 16-bit PCMCIA cards, and
|
||||
&os; 5.X supports both 16-bit and
|
||||
32-bit (<quote>CardBus</quote>) cards. A database of supported
|
||||
cards is in the file <filename>/etc/defaults/pccard.conf</filename>.
|
||||
32-bit (<quote>CardBus</quote>) cards. A database of supported
|
||||
cards is in the file <filename>/etc/defaults/pccard.conf</filename>.
|
||||
Look through it, and preferably buy cards listed there. Cards not
|
||||
listed may also work as <quote>generic</quote> devices: in
|
||||
particular most modems (16-bit) should work fine, provided they
|
||||
are not winmodems (these do exist even as PC Cards, so watch out).
|
||||
listed may also work as <quote>generic</quote> devices: in
|
||||
particular most modems (16-bit) should work fine, provided they
|
||||
are not winmodems (these do exist even as PC Cards, so watch out).
|
||||
If your card is recognised as a generic modem, note that the
|
||||
default <filename>pccard.conf</filename> file specifies a delay time of 10 seconds
|
||||
(to avoid freezes on certain modems); this may well be
|
||||
over-cautious for your modem, so you may want to play with it,
|
||||
reducing it or removing it totally.</para>
|
||||
|
||||
<para>Some parts of <filename>pccard.conf</filename> may need
|
||||
editing. Check the irq line, and be sure to remove any number
|
||||
already being used: in particular, if you have an on board sound
|
||||
card, remove irq 5 (otherwise you may experience hangs when you
|
||||
insert a card). Check also the available memory slots; if your
|
||||
card is not being detected, try changing it to one of the other
|
||||
<para>Some parts of <filename>pccard.conf</filename> may need
|
||||
editing. Check the irq line, and be sure to remove any number
|
||||
already being used: in particular, if you have an on board sound
|
||||
card, remove irq 5 (otherwise you may experience hangs when you
|
||||
insert a card). Check also the available memory slots; if your
|
||||
card is not being detected, try changing it to one of the other
|
||||
allowed values (listed in the manual page &man.pccardc.8;).
|
||||
</para>
|
||||
|
||||
|
@ -156,8 +156,8 @@
|
|||
(including ISA routing of interrupts, for machines where
|
||||
&os; is not able to use the PCI BIOS) before the &os; 4.4
|
||||
release. If you have problems, try upgrading your system.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="power-management">
|
||||
|
||||
|
@ -294,7 +294,7 @@ apm_event NORMRESUME, STANDBYRESUME {
|
|||
|
||||
<para>The X window system (<application>&xorg;</application>) also includes display power
|
||||
management (look at the &man.xset.1; manual page, and search for
|
||||
<quote>dpms</quote> there). You may want to investigate this. However, this,
|
||||
<quote>dpms</quote> there). You may want to investigate this. However, this,
|
||||
too, works inconsistently on laptops: it
|
||||
often turns off the display but does not turn off the
|
||||
backlight.</para>
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: LDAP Authentication
|
||||
|
|
|
@ -52,7 +52,7 @@
|
|||
explanation of <filename role="package">net/nss_ldap</filename>
|
||||
and <filename role="package">security/pam_ldap</filename> for use with
|
||||
client machines services for use with the LDAP server.</para>
|
||||
|
||||
|
||||
<para>When finished, the reader should be able to configure and
|
||||
deploy a &os; server that can host an LDAP directory, and to
|
||||
configure and deploy a &os; server which can authenticate against
|
||||
|
@ -397,7 +397,7 @@ cn: tuser</programlisting>
|
|||
|
||||
<para><filename role="package">security/pam_ldap</filename> is
|
||||
configured via <filename>/usr/local/etc/ldap.conf</filename>.</para>
|
||||
|
||||
|
||||
<note>
|
||||
<para>This is a <emphasis>different file</emphasis> than the
|
||||
<application>OpenLDAP</application> library functions'
|
||||
|
@ -616,7 +616,7 @@ ldappasswd -D uid="$USER",ou=people,dc=example,dc=org \
|
|||
|
||||
<example id="chpw-ruby">
|
||||
<title>Ruby script for changing passwords</title>
|
||||
|
||||
|
||||
<programlisting><![CDATA[require 'ldap'
|
||||
require 'base64'
|
||||
require 'digest'
|
||||
|
@ -632,7 +632,7 @@ def get_password
|
|||
|
||||
raise if pwd1 != pwd2
|
||||
pwd1.check # check password strength
|
||||
|
||||
|
||||
salt = rand.to_s.gsub(/0\./, '')
|
||||
pass = pwd1.to_s
|
||||
hash = "{SSHA}"+Base64.encode64(Digest::SHA1.digest("#{pass}#{salt}")+salt).chomp!
|
||||
|
|
|
@ -310,7 +310,7 @@ Copyright (c) 2005 Dru Lavigne
|
|||
<varlistentry>
|
||||
<term>MAC</term>
|
||||
|
||||
<listitem><para><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/mac.html">MAC</ulink>,
|
||||
<listitem><para><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/mac.html">MAC</ulink>,
|
||||
or Mandatory Access Control, provides fine-tuned access to
|
||||
files and is meant to augment traditional operating system
|
||||
authorization provided by file permissions. Since MAC is
|
||||
|
|
|
@ -106,7 +106,7 @@
|
|||
SysV interprocess communication primitives, copy-on-write, etc. &unix;
|
||||
itself does not exist any more but its ideas have been used by many
|
||||
other operating systems world wide thus forming the so called &unix;-like
|
||||
operating systems. These days the most influential ones are &linux;,
|
||||
operating systems. These days the most influential ones are &linux;,
|
||||
Solaris, and possibly (to some extent) &os;. There are in-company
|
||||
&unix; derivatives (AIX, HP-UX etc.), but these have been more and
|
||||
more migrated to the aforementioned systems. Let us summarize typical
|
||||
|
@ -345,7 +345,7 @@
|
|||
<literal>ERESTART</literal> and <literal>EJUSTRETURN</literal>
|
||||
errors). Finally an <literal>userret()</literal> is scheduled,
|
||||
switching the process back to the users-pace. The parameters to
|
||||
the actual syscall handler are passed in the form of
|
||||
the actual syscall handler are passed in the form of
|
||||
<literal>struct thread *td</literal>,
|
||||
<literal>struct syscall args *</literal> arguments where the second
|
||||
parameter is a pointer to the copied in structure of
|
||||
|
@ -627,17 +627,17 @@
|
|||
program.</para>
|
||||
|
||||
<para>The code that implements &man.pthread.create.3; in NPTL defines
|
||||
the clone flags like this:</para>
|
||||
the clone flags like this:</para>
|
||||
|
||||
<programlisting>int clone_flags = (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGNAL
|
||||
|
||||
| CLONE_SETTLS | CLONE_PARENT_SETTID
|
||||
| CLONE_SETTLS | CLONE_PARENT_SETTID
|
||||
|
||||
| CLONE_CHILD_CLEARTID | CLONE_SYSVSEM
|
||||
#if __ASSUME_NO_CLONE_DETACHED == 0
|
||||
| CLONE_CHILD_CLEARTID | CLONE_SYSVSEM
|
||||
#if __ASSUME_NO_CLONE_DETACHED == 0
|
||||
|
||||
| CLONE_DETACHED
|
||||
#endif
|
||||
| CLONE_DETACHED
|
||||
#endif
|
||||
|
||||
| 0);</programlisting>
|
||||
|
||||
|
@ -1223,7 +1223,7 @@
|
|||
|
||||
<programlisting>...
|
||||
AUE_FORK STD { int linux_fork(void); }
|
||||
...
|
||||
...
|
||||
AUE_CLOSE NOPROTO { int close(int fd); }
|
||||
...</programlisting>
|
||||
|
||||
|
@ -1257,15 +1257,15 @@
|
|||
<para>The <filename>linux_proto.h</filename> contains structure
|
||||
definitions of arguments to every syscall, e.g.:</para>
|
||||
|
||||
<programlisting>struct linux_fork_args {
|
||||
register_t dummy;
|
||||
<programlisting>struct linux_fork_args {
|
||||
register_t dummy;
|
||||
};</programlisting>
|
||||
|
||||
<para>And finally, <filename>linux_sysent.c</filename> contains
|
||||
structure describing the system entry table, used to actually
|
||||
dispatch a syscall, e.g.:</para>
|
||||
|
||||
<programlisting>{ 0, (sy_call_t *)linux_fork, AUE_FORK, NULL, 0, 0 }, /* 2 = linux_fork */
|
||||
<programlisting>{ 0, (sy_call_t *)linux_fork, AUE_FORK, NULL, 0, 0 }, /* 2 = linux_fork */
|
||||
{ AS(close_args), (sy_call_t *)close, AUE_CLOSE, NULL, 0, 0 }, /* 6 = close */</programlisting>
|
||||
|
||||
<para>As you can see <function>linux_fork</function> is implemented
|
||||
|
@ -1349,7 +1349,7 @@
|
|||
instruction or between system entries (syscalls and traps).
|
||||
&man.ptrace.2; also lets you set various information in the traced
|
||||
process (registers etc.). &man.ptrace.2; is a &unix;-wide standard
|
||||
implemented in most &unix;es around the world.</para>
|
||||
implemented in most &unix;es around the world.</para>
|
||||
|
||||
<para>&linux; emulation in &os; implements the &man.ptrace.2; facility
|
||||
in <filename>linux_ptrace.c</filename>. The routines for converting
|
||||
|
@ -1379,11 +1379,11 @@
|
|||
trap is so this is dealt with here. The code is actually very
|
||||
short:</para>
|
||||
|
||||
<programlisting>static int
|
||||
translate_traps(int signal, int trap_code)
|
||||
{
|
||||
<programlisting>static int
|
||||
translate_traps(int signal, int trap_code)
|
||||
{
|
||||
|
||||
if (signal != SIGBUS)
|
||||
if (signal != SIGBUS)
|
||||
return signal;
|
||||
|
||||
switch (trap_code) {
|
||||
|
@ -1394,9 +1394,9 @@ translate_traps(int signal, int trap_code)
|
|||
case T_PAGEFLT:
|
||||
return SIGSEGV;
|
||||
|
||||
default:
|
||||
return signal;
|
||||
}
|
||||
default:
|
||||
return signal;
|
||||
}
|
||||
}</programlisting>
|
||||
</sect2>
|
||||
|
||||
|
@ -1523,17 +1523,17 @@ translate_traps(int signal, int trap_code)
|
|||
emulation specific structure attached to the process. The
|
||||
structure attached to the process looks like:</para>
|
||||
|
||||
<programlisting>struct linux_emuldata {
|
||||
pid_t pid;
|
||||
<programlisting>struct linux_emuldata {
|
||||
pid_t pid;
|
||||
|
||||
int *child_set_tid; /* in clone(): Child.s TID to set on clone */
|
||||
int *child_clear_tid;/* in clone(): Child.s TID to clear on exit */
|
||||
int *child_set_tid; /* in clone(): Child.s TID to set on clone */
|
||||
int *child_clear_tid;/* in clone(): Child.s TID to clear on exit */
|
||||
|
||||
struct linux_emuldata_shared *shared;
|
||||
struct linux_emuldata_shared *shared;
|
||||
|
||||
int pdeath_signal; /* parent death signal */
|
||||
int pdeath_signal; /* parent death signal */
|
||||
|
||||
LIST_ENTRY(linux_emuldata) threads; /* list of linux threads */
|
||||
LIST_ENTRY(linux_emuldata) threads; /* list of linux threads */
|
||||
};</programlisting>
|
||||
|
||||
<para>The PID is used to identify the &os; process that attaches this
|
||||
|
@ -1547,13 +1547,13 @@ translate_traps(int signal, int trap_code)
|
|||
to the list of threads. The <literal>linux_emuldata_shared</literal>
|
||||
structure looks like:</para>
|
||||
|
||||
<programlisting>struct linux_emuldata_shared {
|
||||
<programlisting>struct linux_emuldata_shared {
|
||||
|
||||
int refs;
|
||||
int refs;
|
||||
|
||||
pid_t group_pid;
|
||||
pid_t group_pid;
|
||||
|
||||
LIST_HEAD(, linux_emuldata) threads; /* head of list of linux threads */
|
||||
LIST_HEAD(, linux_emuldata) threads; /* head of list of linux threads */
|
||||
};</programlisting>
|
||||
|
||||
<para>The <varname>refs</varname> is a reference counter being used
|
||||
|
@ -1860,8 +1860,8 @@ void * child_tidptr);</programlisting>
|
|||
counter, which is very fast, as presented by the following
|
||||
example:</para>
|
||||
|
||||
<programlisting>pthread_mutex_lock(&mutex);
|
||||
....
|
||||
<programlisting>pthread_mutex_lock(&mutex);
|
||||
....
|
||||
pthread_mutex_unlock(&mutex);</programlisting>
|
||||
|
||||
<para>1:1 threading forces us to perform two syscalls for those mutex
|
||||
|
@ -1908,7 +1908,7 @@ pthread_mutex_unlock(&mutex);</programlisting>
|
|||
<listitem>
|
||||
<para><literal>FUTEX_WAKE_OP</literal></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</itemizedlist>
|
||||
|
||||
<sect4 id="futex-wait">
|
||||
<title>FUTEX_WAIT</title>
|
||||
|
@ -1952,7 +1952,7 @@ pthread_mutex_unlock(&mutex);</programlisting>
|
|||
<para>This operation does the same as
|
||||
<literal>FUTEX_REQUEUE</literal> but it checks that
|
||||
<varname>val3</varname> equals to <varname>val</varname>
|
||||
first.</para>
|
||||
first.</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="futex-wake-op">
|
||||
|
@ -2017,13 +2017,13 @@ pthread_mutex_unlock(&mutex);</programlisting>
|
|||
|
||||
<para>And the structure <literal>waiting_proc</literal> is:</para>
|
||||
|
||||
<programlisting>struct waiting_proc {
|
||||
<programlisting>struct waiting_proc {
|
||||
|
||||
struct thread *wp_t;
|
||||
struct thread *wp_t;
|
||||
|
||||
struct futex *wp_new_futex;
|
||||
struct futex *wp_new_futex;
|
||||
|
||||
TAILQ_ENTRY(waiting_proc) wp_list;
|
||||
TAILQ_ENTRY(waiting_proc) wp_list;
|
||||
};</programlisting>
|
||||
|
||||
<sect4 id="futex-get">
|
||||
|
@ -2135,7 +2135,7 @@ pthread_mutex_unlock(&mutex);</programlisting>
|
|||
<literal>AT_FDCWD</literal>. So for example the
|
||||
<function>openat</function> syscall can be like this:</para>
|
||||
|
||||
<programlisting>file descriptor 123 = /tmp/foo/, current working directory = /tmp/
|
||||
<programlisting>file descriptor 123 = /tmp/foo/, current working directory = /tmp/
|
||||
|
||||
openat(123, /tmp/bah\, flags, mode) /* opens /tmp/bah */
|
||||
openat(123, bah\, flags, mode) /* opens /tmp/foo/bah */
|
||||
|
@ -2246,7 +2246,7 @@ openat(stdio, bah\, flags, mode) /* returns error because stdio is not a directo
|
|||
sysctl). For printing we have LMSG and ARGS macros. Those are used
|
||||
for altering a printable string for uniform debugging messages.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="conclusion">
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: FreeBSD Quickstart for Linux Users
|
||||
|
|
|
@ -12,7 +12,7 @@ INSTALL_ONLY_COMPRESSED?=
|
|||
|
||||
WITH_ARTICLE_TOC?=YES
|
||||
|
||||
#
|
||||
#
|
||||
# SRCS lists the individual SGML files that make up the document. Changes
|
||||
# to any of these files will force a rebuild
|
||||
#
|
||||
|
|
|
@ -278,7 +278,7 @@ Incorporating new mail into inbox...
|
|||
|
||||
36+ 01/19 Stephen L. Lange Request...<<Please remove me as contact for pind
|
||||
37 01/19 Matt Thomas Re: kern/950: Two PCI bridge chips fail (multipl
|
||||
38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In
|
||||
38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In
|
||||
&prompt.user;</screen>
|
||||
</informalexample>
|
||||
|
||||
|
@ -310,10 +310,10 @@ X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO pro
|
|||
tocol
|
||||
To: hsu@clinet.fi
|
||||
Cc: hackers@FreeBSD.org
|
||||
Subject: Re: kern/950: Two PCI bridge chips fail (multiple multiport ethernet
|
||||
boards)
|
||||
Subject: Re: kern/950: Two PCI bridge chips fail (multiple multiport ethernet
|
||||
boards)
|
||||
In-Reply-To: Your message of "Fri, 19 Jan 1996 00:18:36 +0100."
|
||||
<199601182318.AA11772@Sysiphos>
|
||||
<199601182318.AA11772@Sysiphos>
|
||||
X-Mailer: exmh version 1.5omega 10/6/94
|
||||
Date: Fri, 19 Jan 1996 17:56:40 +0000
|
||||
From: Matt Thomas <matt@lkg.dec.com>
|
||||
|
@ -332,16 +332,16 @@ which I am probably the guilty party).</screen>
|
|||
|
||||
<informalexample>
|
||||
<screen>&prompt.user; <userinput>scan last:10</userinput>
|
||||
26 01/16 maddy Re: Testing some stuff<<yeah, well, Trinity has
|
||||
26 01/16 maddy Re: Testing some stuff<<yeah, well, Trinity has
|
||||
27 01/17 Automatic digest NET-HAPPENINGS Digest - 16 Jan 1996 to 17 Jan 19
|
||||
28 01/17 Evans A Criswell Re: Hey dude<<>From matt@tempest.garply.com Tue
|
||||
28 01/17 Evans A Criswell Re: Hey dude<<>From matt@tempest.garply.com Tue
|
||||
29 01/16 Karl Heuer need configure/make volunteers<<The FSF is looki
|
||||
30 01/18 Paul Stephanouk Re: [alt.religion.scientology] Raw Meat (humor)<
|
||||
31 01/18 Bill Lenherr Re: Linux NIS Solaris<<--- On Thu, 18 Jan 1996 1
|
||||
34 01/19 John Fieber Re: Stuff for the email section?<<On Fri, 19 Jan
|
||||
35 01/19 support@foo.garpl [garply.com #1138] parlor<<Hello. This is the Ne
|
||||
37+ 01/19 Matt Thomas Re: kern/950: Two PCI bridge chips fail (multipl
|
||||
38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In
|
||||
38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In
|
||||
&prompt.user;</screen>
|
||||
</informalexample>
|
||||
|
||||
|
@ -508,7 +508,7 @@ which I am probably the guilty party).</screen>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
|
||||
<para>This allows you to do things like
|
||||
|
||||
<informalexample>
|
||||
|
@ -551,7 +551,7 @@ which I am probably the guilty party).</screen>
|
|||
necessary as in the following example</para>
|
||||
|
||||
<informalexample>
|
||||
<screen>&prompt.user; <userinput>pick -lbrace -to freebsd-hackers -and
|
||||
<screen>&prompt.user; <userinput>pick -lbrace -to freebsd-hackers -and
|
||||
-not -cc freebsd-questions -rbrace -and -subject pci</userinput></screen>
|
||||
</informalexample>
|
||||
|
||||
|
@ -618,7 +618,7 @@ which I am probably the guilty party).</screen>
|
|||
|
||||
TOTAL= 199 messages in 13 folders.</screen>
|
||||
</informalexample>
|
||||
|
||||
|
||||
<para>The <command>refile</command> command is what you use to move
|
||||
messages between folders. When you do something like
|
||||
<command>refile 23 +netfuture</command> message number 23 is moved
|
||||
|
@ -799,13 +799,13 @@ X-Home-Page: http://www.FreeBSD.org/
|
|||
original message. So that might be translated this way:</para>
|
||||
|
||||
<informalexample>
|
||||
<screen>%<<emphasis remap="bf">if</emphasis> {reply-to} <emphasis remap="bf">the original message has a reply-to</emphasis>
|
||||
<screen>%<<emphasis remap="bf">if</emphasis> {reply-to} <emphasis remap="bf">the original message has a reply-to</emphasis>
|
||||
then give that to formataddr, %? <emphasis remap="bf">else</emphasis> {from} <emphasis remap="bf">take the
|
||||
from address</emphasis>, %? <emphasis remap="bf">else</emphasis> {sender} <emphasis remap="bf">take the sender address</emphasis>, %?
|
||||
<emphasis remap="bf">else</emphasis> {return-path} <emphasis remap="bf">take the return-path from the original
|
||||
message</emphasis>, %> <emphasis remap="bf">endif</emphasis>.</screen>
|
||||
</informalexample>
|
||||
|
||||
|
||||
<para>As you can tell <application>MH</application> formatting
|
||||
can get rather involved. You can probably decipher what most
|
||||
of the other functions and variables mean. All of the
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: Introduction to NanoBSD
|
||||
|
|
|
@ -431,7 +431,7 @@
|
|||
the long run the text editor <command>vi</command> is worth
|
||||
learning. There is an excellent tutorial on vi in
|
||||
<filename>/usr/src/contrib/nvi/docs/tutorial</filename>, if you
|
||||
have the system sources installed.</para>
|
||||
have the system sources installed.</para>
|
||||
|
||||
<para>Before you edit a file, you should probably back it up.
|
||||
Suppose you want to edit <filename>/etc/rc.conf</filename>. You
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Perforce in FreeBSD Development article.
|
||||
|
|
|
@ -2670,7 +2670,7 @@ ln -s ../<replaceable>arch</replaceable>/archive/errorlogs <replaceable>arch</re
|
|||
<para>(Only necessary for old codebase):
|
||||
Only after the first time a
|
||||
<application>dopackages</application> has been run for the
|
||||
arch: add the arch to
|
||||
arch: add the arch to
|
||||
<filename>/var/portbuild/scripts/dopackagestats</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -2908,7 +2908,7 @@ Use smartctl -X to abort test.</screen>
|
|||
after it finishes:</para>
|
||||
|
||||
<screen># SMART Self-test log structure revision number 1
|
||||
# Num Test_Description Status Remaining
|
||||
# Num Test_Description Status Remaining
|
||||
LifeTime(hours) LBA_of_first_error
|
||||
# 1 Extended offline Completed: read failure 80% 15252 319286</screen>
|
||||
|
||||
|
|
|
@ -123,13 +123,13 @@
|
|||
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.</para>
|
||||
|
||||
|
||||
<para>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.</para>
|
||||
|
||||
|
||||
<para>In either case, following the process described in <ulink
|
||||
url="&url.books.porters-handbook;/port-upgrading.html">Porter's
|
||||
Handbook</ulink> will yield the best results. (You might
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: Practical rc.d scripting in BSD
|
||||
|
|
|
@ -1232,7 +1232,7 @@ run_rc_command "$1"</programlisting>
|
|||
<para>Fortunately, &man.rc.subr.8; allows for passing any number
|
||||
of arguments to script's methods (within the system limits).
|
||||
Due to that, the changes in the script itself can be minimal.</para>
|
||||
|
||||
|
||||
<para>How can &man.rc.subr.8; gain
|
||||
access to the extra command-line arguments. Should it just
|
||||
grab them directly? Not by any means. Firstly, an &man.sh.1;
|
||||
|
|
|
@ -68,7 +68,7 @@
|
|||
set. The current version of <command>perl</command>
|
||||
may need to be removed first; errors will be reported
|
||||
by the install process if this is necessary.</para>
|
||||
|
||||
|
||||
<note>
|
||||
<para>This will require all ports which require
|
||||
<command>perl</command> to be rebuilt and reinstalled;
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
#
|
||||
#
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Article: FreeBSD Release Engineering of Third Party Software Packages
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue