<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>BSDForen.de</title>
		<link>http://www.bsdforen.de</link>
		<description>BSDForen.de ist eine deutschsprachige Anlaufstelle bei Problem und Fragen zu den BSDs</description>
		<language>de</language>
		<lastBuildDate>Thu, 17 May 2012 13:57:59 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://www.bsdforen.de/images/bsdforen/misc/rss.jpg</url>
			<title>BSDForen.de</title>
			<link>http://www.bsdforen.de</link>
		</image>
		<item>
			<title>Displaymanager gesucht als Alternative zu xdm</title>
			<link>http://www.bsdforen.de/showthread.php?t=27838&amp;goto=newpost</link>
			<pubDate>Thu, 17 May 2012 10:22:44 GMT</pubDate>
			<description>Moin! 
 
Ich teste gerade Displaymanager als Ersatz für xdm bzw. slim. 
 
Bisher habe ich slim benutzt, der hat aber den Nachteil das er relativ alt ist und mit der sessionverwaltung nicht umgehen kann. Im Resultat kann ich - solange ich slim benutze - den Rechner nicht als User herunterfahen. Als...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Moin!<br />
<br />
Ich teste gerade Displaymanager als Ersatz für xdm bzw. slim.<br />
<br />
Bisher habe ich slim benutzt, der hat aber den Nachteil das er relativ alt ist und mit der sessionverwaltung nicht umgehen kann. Im Resultat kann ich - solange ich slim benutze - den Rechner nicht als User herunterfahen. Als Nachfolger wird lxdm empfohlen, aber der ist nicht in den Ports.<br />
<br />
xdm tut was er soll, sieht aber nicht so toll aus ;)<br />
<br />
kdm und gdm scheiden aus, die sind zuviel für den älteren Rechner auf dem das laufen soll, zumal ich da weder gnome noch kde drauf installieren werde, auch keine der dazugehörigen Anwendungen. (Die Kiste wird eigentlich nur zum surfen &amp; Musikabspielen benutzt.)<br />
<br />
Generell scheinen nicht allzuviele displaymanger in den Ports zu sein. Welche kleinen und schlanken Alternativen habe ich noch?<br />
<br />
Grüße,<br />
Errorsmith</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=7">FreeBSD - Anwendungen und Ports</category>
			<dc:creator>Errorsmith</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27838</guid>
		</item>
		<item>
			<title>Backup Lösung für heterogene Umgebung</title>
			<link>http://www.bsdforen.de/showthread.php?t=27837&amp;goto=newpost</link>
			<pubDate>Wed, 16 May 2012 21:45:06 GMT</pubDate>
			<description>Hi 
 
Ich fange wahrscheinlich nächste Woche einen neuen Job an. Meine Aufgabe wird sein den Entwicklern das Spielzeug aus der Hand zu nehmen und eine Abteilung für die reine Administration aufzubauen. Sobald ich da die Hoheit übernommen habe kommt schon gleich das erste Projekt am Zug. Eine...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hi<br />
<br />
Ich fange wahrscheinlich nächste Woche einen neuen Job an. Meine Aufgabe wird sein den Entwicklern das Spielzeug aus der Hand zu nehmen und eine Abteilung für die reine Administration aufzubauen. Sobald ich da die Hoheit übernommen habe kommt schon gleich das erste Projekt am Zug. Eine Backuplösung für alle Server und Desktopclients im Büro.<br />
Die Landschaft ist wirklich Leipziger Allerlei. Von Windows XP bis Windows 8 über Mac OS von Leopard bis Lion. Und was da mit Linux rumsteht muss ich auch noch rausfinden.<br />
<br />
Ich rechne aber bei 40 Clients schon im Terrabyte Bereich für die Angelegenheit. Darum soll das ganze schon mit ZFS an den Start kommen. Zudem will ich da langfristig durch die gute Arbeit mit FreeBSD punkten um auch eine Vereinheitlichung zu erzielen. Und die MS Ad Struktur will ich nicht sofort aber auch langfristig mit Samba 4 und Apache DS über Board werfen.<br />
<br />
Derzeit denke an Backula ich habe bisher davon nur gelesen. Werde mich daher wohl einarbeiten. BackupPC kenne ich sehr gut halte ich aber für ungeeignet. Das ist fehleranfällig und provoziert zu viele Fehler. Aber was wäre sonst noch zu empfehlen? Und vor allem muss ich bei ZFS noch was konfigurieren um die ACL's und andere Dateiatribute von Windows, OSX und Linux in den Backups zu erhalten?<br />
<br />
Danke für eure Beiträge :)</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=25">Geplauder</category>
			<dc:creator>minimike</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27837</guid>
		</item>
		<item>
			<title>BSD-Förderverein</title>
			<link>http://www.bsdforen.de/showthread.php?t=27836&amp;goto=newpost</link>
			<pubDate>Wed, 16 May 2012 12:30:55 GMT</pubDate>
			<description>Moin Moin, 
 
wie geht es eigentlich der Idee des BSD-Fördervereins (http://www.bsdforen.de/showthread.php?t=25228)? 
Wird daran noch gearbeitet? 
Wenn nicht, woran mangelt es? 
 
Gruß 
fussel</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Moin Moin,<br />
<br />
wie geht es eigentlich der Idee des <a href="showthread.php?t=25228" title="BSDForen.de - Thema 25228">BSD-Fördervereins</a>?<br />
Wird daran noch gearbeitet?<br />
Wenn nicht, woran mangelt es?<br />
<br />
Gruß<br />
fussel</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=25">Geplauder</category>
			<dc:creator>fussel</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27836</guid>
		</item>
		<item>
			<title>jgillich</title>
			<link>http://www.bsdforen.de/showthread.php?t=27835&amp;goto=newpost</link>
			<pubDate>Wed, 16 May 2012 06:30:10 GMT</pubDate>
			<description>Bitte um Freischaltung. ;)</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Bitte um Freischaltung. ;)</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=87">Turingtest</category>
			<dc:creator>jgillich</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27835</guid>
		</item>
		<item>
			<title>FreeBSD Server als Domain Controller</title>
			<link>http://www.bsdforen.de/showthread.php?t=27834&amp;goto=newpost</link>
			<pubDate>Wed, 16 May 2012 05:37:13 GMT</pubDate>
			<description>Hallo, 
 
ich habe vor in unser Firmennetzwerk (WinXp Win7 Clients) einen FreeBSD Server als Domain Controller einzusetzten. Könnt ihr mir das empfehlen oder werde ich da im Betrieb auf große Probleme stoßen? 
 
Gibt es für FreeBSD auch eine Groupware like Microsoft Exchange Server? 
 
Grüße Bungle</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hallo,<br />
<br />
ich habe vor in unser Firmennetzwerk (WinXp Win7 Clients) einen FreeBSD Server als Domain Controller einzusetzten. Könnt ihr mir das empfehlen oder werde ich da im Betrieb auf große Probleme stoßen?<br />
<br />
Gibt es für FreeBSD auch eine Groupware like Microsoft Exchange Server?<br />
<br />
Grüße Bungle</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=5">FreeBSD - Allgemein</category>
			<dc:creator>bungle</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27834</guid>
		</item>
		<item>
			<title><![CDATA[[HTML/CSS] Höhe von DIVs automatisch anpassen]]></title>
			<link>http://www.bsdforen.de/showthread.php?t=27833&amp;goto=newpost</link>
			<pubDate>Tue, 15 May 2012 09:33:29 GMT</pubDate>
			<description>Hi 
 
ich bin gerade etwas am Experimentieren mit DIVs und min-height, max-height usw. Eigentlich wollte ich mit etwas ganz Banalem beginnen, doch ich hänge schon fest und weiß nicht weiter. Was ich machen möchte, ist eine einfache Seite die 2Header hat (Position immer am Kopf der Seite, Größe...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hi<br />
<br />
ich bin gerade etwas am Experimentieren mit DIVs und min-height, max-height usw. Eigentlich wollte ich mit etwas ganz Banalem beginnen, doch ich hänge schon fest und weiß nicht weiter. Was ich machen möchte, ist eine einfache Seite die 2Header hat (Position immer am Kopf der Seite, Größe statisch), 2 &quot;Inhaltsbereiche&quot; die ihre Größe dynamisch je nach Größe des Browserfensters ändern sollen, und eine Fusszeile, die wiederum in ihrer Größe statisch bleibt, sich aber immer am untersten Bildrand befinden soll.<br />
<br />
Hier mal etwas Code von meinem ersten Versuch:<br />
<!-- BEGIN TEMPLATE: bbcode_php_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">PHP-Code:</div>
	<div class="alt2">
		<hr />
		<code style="white-space:nowrap">
		<div dir="ltr" style="text-align:left;">
			<!-- php buffer start --><code><span style="color: #000000">
<span style="color: #0000BB"></span><span style="color: #007700">&lt;</span><span style="color: #0000BB">html</span><span style="color: #007700">&gt;<br />&lt;</span><span style="color: #0000BB">head</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">style</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">html</span><span style="color: #007700">,&nbsp;</span><span style="color: #0000BB">body<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">margin</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">0</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">padding</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">0</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">rahmen&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">border</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">1px&nbsp;solid&nbsp;red</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br /><br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">titel&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">width</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">100</span><span style="color: #007700">%;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">height</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">99px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">white</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">background</span><span style="color: #007700">-</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #FF8000">#0e3852;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #007700">}<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">titel2&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">top</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">100px</span><span style="color: #007700">;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">width</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">100</span><span style="color: #007700">%;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">height</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">60px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">black</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">links&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">width</span><span style="color: #007700">:</span><span style="color: #0000BB">200px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">min</span><span style="color: #007700">-</span><span style="color: #0000BB">height</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">400px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">overflow</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">auto</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">rechts&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">min</span><span style="color: #007700">-</span><span style="color: #0000BB">width</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">500px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">min</span><span style="color: #007700">-</span><span style="color: #0000BB">height</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">400px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">background</span><span style="color: #007700">-</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">white</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.</span><span style="color: #0000BB">fusszeile&nbsp;</span><span style="color: #007700">{<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">width</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">100</span><span style="color: #007700">%;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">height</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">30px</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #0000BB">white</span><span style="color: #007700">;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #0000BB">background</span><span style="color: #007700">-</span><span style="color: #0000BB">color</span><span style="color: #007700">:&nbsp;</span><span style="color: #FF8000">#0e3852;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style="color: #007700">}<br /><br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;/</span><span style="color: #0000BB">style</span><span style="color: #007700">&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&lt;/</span><span style="color: #0000BB">head</span><span style="color: #007700">&gt;<br />&lt;</span><span style="color: #0000BB">body&nbsp;height</span><span style="color: #007700">=</span><span style="color: #DD0000">"100%"</span><span style="color: #007700">&gt;<br /><br />&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen"&nbsp;</span><span style="color: #0000BB">style</span><span style="color: #007700">=</span><span style="color: #DD0000">"min-height:100%;background-color:&nbsp;#edf3fa;"</span><span style="color: #007700">&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen&nbsp;titel"</span><span style="color: #007700">&gt;</span><span style="color: #0000BB">Titel&nbsp;</span><span style="color: #007700">-&nbsp;</span><span style="color: #0000BB">Dunkel&nbsp;mit&nbsp;Bild</span><span style="color: #007700">&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen&nbsp;titel2"</span><span style="color: #007700">&gt;</span><span style="color: #0000BB">Titel2&nbsp;</span><span style="color: #007700">-&nbsp;</span><span style="color: #0000BB">Logo&nbsp;und&nbsp;Menü</span><span style="color: #007700">&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;style</span><span style="color: #007700">=</span><span style="color: #DD0000">"position:static;"</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen&nbsp;links"&nbsp;</span><span style="color: #0000BB">style</span><span style="color: #007700">=</span><span style="color: #DD0000">"position:absolute;left:0px;"</span><span style="color: #007700">&gt;</span><span style="color: #0000BB">Linke&nbsp;Seite&nbsp;</span><span style="color: #007700">-&nbsp;</span><span style="color: #0000BB">Menü2</span><span style="color: #007700">&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen&nbsp;rechts"&nbsp;</span><span style="color: #0000BB">style</span><span style="color: #007700">=</span><span style="color: #DD0000">"position:absolute;left:200px;"</span><span style="color: #007700">&gt;</span><span style="color: #0000BB">Rechte&nbsp;Seite&nbsp;</span><span style="color: #007700">-&nbsp;</span><span style="color: #0000BB">Hauptfenster</span><span style="color: #007700">&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;&lt;</span><span style="color: #0000BB">div&nbsp;</span><span style="color: #007700">class=</span><span style="color: #DD0000">"rahmen&nbsp;fusszeile"</span><span style="color: #007700">&gt;</span><span style="color: #0000BB">Fusszeile</span><span style="color: #007700">&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;<br /><br />&lt;/</span><span style="color: #0000BB">div</span><span style="color: #007700">&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&nbsp;&nbsp;<br />&lt;/</span><span style="color: #0000BB">body</span><span style="color: #007700">&gt;<br />&lt;/</span><span style="color: #0000BB">html</span><span style="color: #007700">&gt;&nbsp;<br /></span><span style="color: #0000BB"></span>
</span>
</code><!-- php buffer end -->
		</div>
		</code>
		<hr />
	</div>
</div>
<!-- END TEMPLATE: bbcode_php_printable -->Irgendwie schaffe ich es nicht die Höhe der beiden InhaltsDIVs an die Höhe des Browserfensters anzupassen und somit auch nicht die Fusszeile an das Ende der Seite zu plazieren. Wenn ich mit min-height: 100% arbeite, wird das DIV immer gleich groß wie das komplette Fenster, ich möchte aber, dass es so groß wird wie die Fensterhöhe minus die Höhen der anderen DIVs. :ugly:<br />
<br />
Ich hoffe ich habe mich halbwegs verständlich ausgedrückt. Geht mein Vorhaben überhaupt ohne javascript?<br />
<br />
thx</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=42">Programmieren</category>
			<dc:creator>martin</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27833</guid>
		</item>
		<item>
			<title>The age of 1337 has begun....</title>
			<link>http://www.bsdforen.de/showthread.php?t=27832&amp;goto=newpost</link>
			<pubDate>Mon, 14 May 2012 21:28:13 GMT</pubDate>
			<description>Gerade auf DuckDuckGo (https://duckduckgo.com/) als Doodle gesehen, dass wir Unixzeitmäßig auf 1337 sind und, da es gerade sonst nichts zu feiern gibt. Happy 1337! :ugly:</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Gerade auf <a href="https://duckduckgo.com/" target="_blank">DuckDuckGo</a> als Doodle gesehen, dass wir Unixzeitmäßig auf 1337 sind und, da es gerade sonst nichts zu feiern gibt. Happy 1337! :ugly:</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=68">Fun</category>
			<dc:creator>Athaba</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27832</guid>
		</item>
		<item>
			<title>ZFS und ECC-Ram</title>
			<link>http://www.bsdforen.de/showthread.php?t=27831&amp;goto=newpost</link>
			<pubDate>Mon, 14 May 2012 11:03:28 GMT</pubDate>
			<description><![CDATA[Hallo, 
 
stimmt es eigentlich, dass ein ZFS-Pool durch Memory-Corruption unbrauchbar werden kann? Es gibt immer wieder Threads in den FreeBSD-Foren, die den Einsatz von ECC-Ram nahe legen. Welche "Gefahren" entstehen denn durch den Einsatz von normalen Speicher? Damit mein ich primär, ob die...]]></description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hallo,<br />
<br />
stimmt es eigentlich, dass ein ZFS-Pool durch Memory-Corruption unbrauchbar werden kann? Es gibt immer wieder Threads in den FreeBSD-Foren, die den Einsatz von ECC-Ram nahe legen. Welche &quot;Gefahren&quot; entstehen denn durch den Einsatz von normalen Speicher? Damit mein ich primär, ob die Auswirkungen schwerer wiegen als z.B bei UFS.<br />
<br />
Danke Schon einmal für alle nützlichen Hinweise.:)</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=5">FreeBSD - Allgemein</category>
			<dc:creator>jmt</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27831</guid>
		</item>
		<item>
			<title>Globales LoadBalancing</title>
			<link>http://www.bsdforen.de/showthread.php?t=27830&amp;goto=newpost</link>
			<pubDate>Mon, 14 May 2012 08:40:35 GMT</pubDate>
			<description><![CDATA[hi 
 
das ich kein "normales" allgemien gefunden habe schreib ich mal hier,  
kann aber gerne verschoben werden. 
 
zz schau ich mit diverse loesungen an wie ich 2 oder mehr rechennzentren 
redundant machen kann. 
 
dier eine weg ist via BGP was aber eingentlich fast nur noch mit ipv6 machbar ist...]]></description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>hi<br />
<br />
das ich kein &quot;normales&quot; allgemien gefunden habe schreib ich mal hier, <br />
kann aber gerne verschoben werden.<br />
<br />
zz schau ich mit diverse loesungen an wie ich 2 oder mehr rechennzentren<br />
redundant machen kann.<br />
<br />
dier eine weg ist via BGP was aber eingentlich fast nur noch mit ipv6 machbar ist<br />
das die huerden mittlerweile sehr hoch sind um eine ipv4 netz samt as zu bekommen.<br />
<br />
alterntiv gibt es globales loadbalancing mit und ohne geoip.<br />
<br />
in dem bereich tummeln sich viele hersteller und cloud dienste.<br />
<br />
im opensource bereich gibt es da nicht viel , oder ich suche falsch , habe mit<br />
<br />
glbdns ein perl dns server gefunden der im prinzip das kann was ich mir <br />
zz vorstelle , anhand von prioritaet und verfuegbarkeit ein entsprechende<br />
dns antwort geben .<br />
<br />
wer kennt loesungen bzw wie kann man alternativ bei dem thema vorgehen ohne gleich die geldboerse massivst zu pluendern.<br />
<br />
holger</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=60">*BSD - Serverdienste</category>
			<dc:creator>mark05</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27830</guid>
		</item>
		<item>
			<title>Soekris wlan box</title>
			<link>http://www.bsdforen.de/showthread.php?t=27829&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 16:41:19 GMT</pubDate>
			<description>Hallo Leute, 
 
ich habe mir eine soekris 5510 gekauft und habe vor die als wlan AP zu konfigurieren. Neben einer sicheren wlan Verschluesselung (WPA/WPA2) soll die kiste auch als DHCP, DNS und HTTP Proxy (squid) konfiguriert werden. 
Ich habe bis jetzt versucht die grundlegenden Dinge selber zu...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hallo Leute,<br />
<br />
ich habe mir eine soekris 5510 gekauft und habe vor die als wlan AP zu konfigurieren. Neben einer sicheren wlan Verschluesselung (WPA/WPA2) soll die kiste auch als DHCP, DNS und HTTP Proxy (squid) konfiguriert werden.<br />
Ich habe bis jetzt versucht die grundlegenden Dinge selber zu machen, dabei habe ich mich darauf konzentriert dass es funktioniert aber nicht darauf geachtet dass es sicher ist. <br />
Meine jetzige Konfiguration ist wie folgt:<br />
<ol style="list-style-type: decimal"><li>Als Wlan habe ich den Hersteller Ralink (RT2561T Chip) gewählt, und besetzt die miniPCI Schnittstelle. Ich habe versucht die Wlankarte mit unter der bridge mit unterzubringen aber ohne einer eigenen IP-Addresse würde ich keine Wlanverbindung mit den Clients aufbauen können, daher habe ich ihr eine eigene IP gegeben und hatte keine Probleme. Neben Notebooks, werden auch 2 bis 3 Repeater über diese Karte verbunden.<br />
Hier ist der Inhalt der hostname.ral0 Datei:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">inet 10.0.0.2<br />
media autoselect mediaopt hostap nwid mynet chan 1 wpa wpapsk test1234<br />
up</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable --></li>
</ol><ol style="list-style-type: decimal"><li>Ueber die NICs vr0,vr1,vr2,vr3 sollen vom dhcpd IP Addressen vom Addressraum 10.0.0.0/24 vergeben werden.Dabei dachte ich mir, ich fasse alle NICs unter einer bridge zusammen und verpasse nur ein NIC eine IP wie 10.0.0.1<br />
Hier ist der Inhalt der hostname.bridge0 Datei:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">add vr0<br />
add vr1<br />
add vr2<br />
add vr3<br />
up</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable -->Hier ist der Inhalt der hostname.vr0 Datei:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">inet 10.0.0.1 255.255.255.0<br />
up</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable --></li>
</ol><ol style="list-style-type: decimal"><li>An der PCI Schnittstelle habe ich eine herkoemmliche 3COM (xl0) Netzwerkkarte. Diese Karte soll zur Fritzbox angeschlossen sein, die (Fritzbox) eine DSL-Verbindung aufbaut.<br />
IP-Addresse dieser Karte ist wie folgt: inet 192.168.1.253 255.255.255.0<br />
Da diese die NIC die Verbindung zum Internet herstellt muss dann in deren hostname.if Datei die default route defeniert werden.<br />
<br />
Hier ist der Inhalt der hostname.xl0Datei:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">inet 192.168.1.200 255.255.255.0 NONE<br />
!route add default 192.168.1.254<br />
!route add -net 10.0.0.0/24 10.0.0.1<br />
!route add -net 192.168.1.0/24 192.168.1.200</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable --></li>
</ol><ol style="list-style-type: decimal"><li>Um NAT zu ermöglichen habe ich diverse Beispiele im Internet gefunden und habe meine Konfiguration (noch nicht ausprobiert) von folgenden <a href="http://wiki.bsdforen.de/howto/firewall-regeln" target="_blank">Link</a> hergeleitet. <br />
Fürs erste ist mir ein Nacktes NAT wichtig, und da ich jedes mal die Soekris abstecken muss und sie an der Fritzbox anschließen muss die sich im Keller befindet habe ich es nicht getestet habe, würde ich in diesen Teil um eine kurze Bestätigung bitten ob es funktionieren würde oder nicht. <br />
<br />
Hier ist der Inhalt der pf.conf Datei:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">IntNet=&quot;10.0.0.0/24&quot; <br />
Ext=&quot;xl0&quot;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  <br />
Int=&quot;vr0&quot; <br />
nat on $Ext from $IntNet to any -&gt; $Ext static-port</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable -->Und ich habe nicht vergessen &quot;net.inet.ip.forwarding&quot; auf 1 zu setzen.</li>
</ol><br />
<br />
Ich vermute dass ich als Anfänger ein paar Sachen entweder umständlich  gemacht habe, oder wie der Lügenbaron &quot;zu Gutenberg&quot; Sachen hier und da Kopiert habe, was ich gleich offen und ehrlich zu gebe. :rolleyes:<br />
Daher wollte ich jeden bitten der sich auskennt, mir zu zeigen wo man es verbessern kann. <br />
Bind und Squid sind jetzt für das erste auch nicht wichtig.<br />
<br />
<br />
Vielen Dank im Voraus an die Community...</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=18">OpenBSD - Allgemein</category>
			<dc:creator>littlebit</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27829</guid>
		</item>
		<item>
			<title>FreeBSD Support für Hyper-V</title>
			<link>http://www.bsdforen.de/showthread.php?t=27828&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 16:36:39 GMT</pubDate>
			<description>Hi 
 
Seit mehr als 10 Jahren nutze ich Produkte von VMware. Leider verläuft die Strategie von VMware nicht so wirklich nach meinen Bedürfnissen. Was mich an VMware bindet ist unter anderem die sehr gute Unterstützung für FreeBSD Gäste. OK es muss Compat6 installiert sein damit der Blob läuft. Aber...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hi<br />
<br />
Seit mehr als 10 Jahren nutze ich Produkte von VMware. Leider verläuft die Strategie von VMware nicht so wirklich nach meinen Bedürfnissen. Was mich an VMware bindet ist unter anderem die sehr gute Unterstützung für FreeBSD Gäste. OK es muss Compat6 installiert sein damit der Blob läuft. Aber es stellt mich zufrieden.<br />
Jedenfalls kommt nun eine weitere Lösung für unternehmenskritische Anwendungen für FreeBSD bald in Betracht. Microsoft arbeitet ja schon seit geraumer Zeit VMware auf dem Markt das Wasser abzugraben. Infolge der Offensive kommt bald vollständige Unterstützung für FreeBSD hinzu :)<br />
<br />
<a href="http://blogs.technet.com/b/openness/archive/2012/05/10/freebsd-support-on-windows-server-hyper-v.aspx" target="_blank">http://blogs.technet.com/b/openness/...r-hyper-v.aspx</a><br />
<br />
Für mich verspricht das ich günstigere Hardware kaufen kann ohne Leistungseinbußen in Kauf nehmen zu müssen, sowie auch etwas mehr an Flexibilität.<br />
<br />
Bhyve währe mir am liebsten. Aber mal ehrlich, das steckt noch alles in den Kinderschuhen.</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=3">News</category>
			<dc:creator>minimike</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27828</guid>
		</item>
		<item>
			<title>pcmanfm aus den Ports - keine Icons?</title>
			<link>http://www.bsdforen.de/showthread.php?t=27827&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 16:29:33 GMT</pubDate>
			<description>Hallo, 
 
ich habe mir heute unter FreeBSD 9 aus den Ports den pcmanfm gebaut. Der Buildvorgang ist auch ohne Fehlermeldungen durchgelaufen. Aber wenn ich jetzt den Filemanager starte, werden mir für die Dateien und Ordner keine Icons angezeigt. Starte ich den Filemanager aus einer Konsole, erhalte...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hallo,<br />
<br />
ich habe mir heute unter FreeBSD 9 aus den Ports den pcmanfm gebaut. Der Buildvorgang ist auch ohne Fehlermeldungen durchgelaufen. Aber wenn ich jetzt den Filemanager starte, werden mir für die Dateien und Ordner keine Icons angezeigt. Starte ich den Filemanager aus einer Konsole, erhalte ich jede Menge Fehlermeldungen: <br />
<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">galileo# pcmanfm<br />
** (pcmanfm:44255): DEBUG: unable to load icon media-eject<br />
** (pcmanfm:44255): DEBUG: unable to load icon user-home<br />
<br />
(pcmanfm:44255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed<br />
** (pcmanfm:44255): DEBUG: unable to load icon user-trash<br />
<br />
(pcmanfm:44255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed<br />
** (pcmanfm:44255): DEBUG: unable to load icon system-software-install<br />
<br />
(pcmanfm:44255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed<br />
** (pcmanfm:44255): DEBUG: unable to load icon folder<br />
<br />
(pcmanfm:44255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed<br />
** (pcmanfm:44255): DEBUG: unable to load icon folder<br />
<br />
(pcmanfm:44255): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed<br />
** (pcmanfm:44255): DEBUG: unable to load icon . GThemedIcon folder inode-directory gnome-mime-inode-directory inode-x-generic<br />
** (pcmanfm:44255): DEBUG: unable to load icon . GThemedIcon application-mbox gnome-mime-application-mbox text-x-generic application-x-generic application-x-executable<br />
** (pcmanfm:44255): DEBUG: unable to load icon . GThemedIcon text-plain gnome-mime-text-plain text-x-generic application-x-executable<br />
** (pcmanfm:44255): DEBUG: unable to load icon . GThemedIcon application-octet-stream gnome-mime-application-octet-stream application-x-generic</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable -->Ich vermute, dass da irgendwelche Icons fehlen, allerdings sollte der Port doch alle Abhängigkeiten mit installieren. Hat jemand eine Idee, wie ich das Problem beheben kann?<br />
<br />
Gruß, Morph</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=7">FreeBSD - Anwendungen und Ports</category>
			<dc:creator>morpheus</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27827</guid>
		</item>
		<item>
			<title>turingtest - littlebit</title>
			<link>http://www.bsdforen.de/showthread.php?t=27826&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 10:37:22 GMT</pubDate>
			<description>Hllo, 
 
bräuchte Hilfe mit der Konfiguration eines access points mit wpa2 Verschlüsselung. 
Habe einiges Probiert und komme nicht voran. :grumble: 
 
Ich hoffe auf eine baldige Freischaltung. 
 
Vielen Dank Hades.</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hllo,<br />
<br />
bräuchte Hilfe mit der Konfiguration eines access points mit wpa2 Verschlüsselung.<br />
Habe einiges Probiert und komme nicht voran. :grumble:<br />
<br />
Ich hoffe auf eine baldige Freischaltung.<br />
<br />
Vielen Dank Hades.</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=87">Turingtest</category>
			<dc:creator>littlebit</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27826</guid>
		</item>
		<item>
			<title>brauche openbsd hilfe</title>
			<link>http://www.bsdforen.de/showthread.php?t=27825&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 10:25:30 GMT</pubDate>
			<description>Hi, 
 
ich hoffe eine Lösung zu meinem Problem bei openBSD zu finden, und hoffe auf eine Registrierung. 
 
Danke</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Hi,<br />
<br />
ich hoffe eine Lösung zu meinem Problem bei openBSD zu finden, und hoffe auf eine Registrierung.<br />
<br />
Danke</div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=87">Turingtest</category>
			<dc:creator>Unregistriert</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27825</guid>
		</item>
		<item>
			<title>FreeBSD Statusreport Januar bis März 2012</title>
			<link>http://www.bsdforen.de/showthread.php?t=27824&amp;goto=newpost</link>
			<pubDate>Sun, 13 May 2012 09:15:56 GMT</pubDate>
			<description>Mit der obligatorischen Verspätung ist der Statusreport der ersten drei Monate des Jahres nun erschienen. Wie immer listet er interessante Entwicklungen im FreeBSD Projekt auf, gibt Einblicke in die Arbeit und Fortschritte an neuen Funktionen. Eine HTML-Version findet sich auf der Homepage unter:...</description>
			<content:encoded><![CDATA[<!-- BEGIN TEMPLATE: postbit_external -->
<div>Mit der obligatorischen Verspätung ist der Statusreport der ersten drei Monate des Jahres nun erschienen. Wie immer listet er interessante Entwicklungen im FreeBSD Projekt auf, gibt Einblicke in die Arbeit und Fortschritte an neuen Funktionen. Eine HTML-Version findet sich auf der Homepage unter: <a href="http://www.freebsd.org/news/status/report-2012-01-2012-03.html" target="_blank">http://www.freebsd.org/news/status/r...1-2012-03.html</a><br />
<br />
Die Text-Version:<br />
<!-- BEGIN TEMPLATE: bbcode_code_printable -->
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<hr /><code style="margin:0px" dir="ltr" style="text-align:left">FreeBSD Quarterly Status Report January-March, 2012<br />
<br />
Introduction<br />
<br />
&nbsp;  This report covers FreeBSD-related projects between January and March<br />
&nbsp;  2012. It is the first of the four reports planned for 2012. This<br />
&nbsp;  quarter was highlighted by releasing the next major version of FreeBSD,<br />
&nbsp;  9.0, which was finally released in the beginning of January 2012. The<br />
&nbsp;  FreeBSD Project dedicates the FreeBSD 9.0-RELEASE to the memory of<br />
&nbsp;  Dennis M. Ritchie, one of the founding fathers of the UNIX&#381; operating<br />
&nbsp;  system. Our release engineering team has been also busy with<br />
&nbsp;  preparation of the 8.3-RELEASE, which was publicly announced in April.<br />
<br />
&nbsp;  Thanks to all the reporters for the excellent work! This report<br />
&nbsp;  contains 27 entries and we hope you enjoy reading it.<br />
<br />
&nbsp;  Please note that the deadline for submissions covering the period<br />
&nbsp;  between April and June 2012 is July 15th, 2012.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Projects<br />
<br />
&nbsp; &nbsp;  * FreeBSD Services Control<br />
&nbsp; &nbsp;  * GNU-Free C++11 Stack<br />
&nbsp; &nbsp;  * Growing filesystems online<br />
&nbsp; &nbsp;  * The FreeNAS Project<br />
<br />
User-land Programs<br />
<br />
&nbsp; &nbsp;  * Clang Replacing GCC in the Base System<br />
&nbsp; &nbsp;  * Replacing the Regular Expression Code<br />
&nbsp; &nbsp;  * The bsdconfig(8) utility<br />
<br />
FreeBSD Team Reports<br />
<br />
&nbsp; &nbsp;  * Release Engineering Team Status Report<br />
&nbsp; &nbsp;  * The FreeBSD Foundation Team Report<br />
<br />
Kernel<br />
<br />
&nbsp; &nbsp;  * DTrace Probes for the linuxulator<br />
&nbsp; &nbsp;  * HDMI/DisplayPort Audio Support in HDA Sound Driver (snd_hda)<br />
&nbsp; &nbsp;  * Improved hwpmc(9) Support for MIPS<br />
&nbsp; &nbsp;  * isci(4) SAS Driver<br />
<br />
Network Infrastructure<br />
<br />
&nbsp; &nbsp;  * Atheros 802.11n Support<br />
&nbsp; &nbsp;  * IPv6 Performance Analysis<br />
&nbsp; &nbsp;  * Multi-FIB: IPv6 Support and Other Enhancements<br />
<br />
Documentation<br />
<br />
&nbsp; &nbsp;  * The FreeBSD Japanese Documentation Project<br />
<br />
Architectures<br />
<br />
&nbsp; &nbsp;  * FreeBSD/arm on Various TI Boards<br />
&nbsp; &nbsp;  * FreeBSD/powerpc on Freescale QorIQ DPAA<br />
&nbsp; &nbsp;  * NAND File System, NAND Flash Framework, NAND Simulator<br />
&nbsp; &nbsp;  * Porting DTrace to MIPS and ARM<br />
<br />
Ports<br />
<br />
&nbsp; &nbsp;  * A New linux_base Port Based Upon CentOS<br />
&nbsp; &nbsp;  * BSD-licensed sort Utility (GNU sort Replacement)<br />
&nbsp; &nbsp;  * KDE/FreeBSD<br />
&nbsp; &nbsp;  * Perl Ports Testing<br />
&nbsp; &nbsp;  * The FreeBSD Haskell Ports<br />
&nbsp; &nbsp;  * The FreeBSD Ports Collection<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
A New linux_base Port Based Upon CentOS<br />
<br />
&nbsp;  Contact: Alexander Leidinger &lt;netchild@FreeBSD.org&gt;<br />
<br />
&nbsp;  We got a PR with a linux_based port which is based upon CentOS 6.<br />
&nbsp;  Currently this can only be used as a test environment, as it depends<br />
&nbsp;  upon a more recent linux kernel version, than the linuxulator provides.<br />
<br />
&nbsp;  As of this writing, I'm in the process of preparing a commit of this<br />
&nbsp;  port.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Repocopy by portmgr.<br />
&nbsp; &nbsp; 2. Add conflicts in other linux_base ports.<br />
&nbsp; &nbsp; 3. Commit the CentOS based one.<br />
&nbsp; &nbsp; 4. Some cleanup.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Atheros 802.11n Support<br />
<br />
&nbsp;  URL: http://wiki.FreeBSD.org/AdrianChadd/AtherosTxAgg<br />
&nbsp;  URL: http://wiki.FreeBSD.org/dev/ath(4)<br />
<br />
&nbsp;  Contact: Adrian Chadd &lt;adrian@FreeBSD.org&gt;<br />
<br />
&nbsp;  802.11n station and hostap support is now fully functional, sans<br />
&nbsp;  correct hostap side power saving. TX aggregation and TX BAR handling is<br />
&nbsp;  implemented.<br />
<br />
&nbsp;  Station chip power saving is not implemented at all yet, it's not in<br />
&nbsp;  the scope of this work.<br />
<br />
&nbsp;  Testers should disable bgscan (-bgscan) as scan/bgscan will simply drop<br />
&nbsp;  any traffic in the TX/RX queues, causing potential traffic stalls.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Fix up hostap side power save handling.<br />
&nbsp; &nbsp; 2. Implement filtered frames support in the driver.<br />
&nbsp; &nbsp; 3. Fix scan/bgscan to correctly buffer and retransmit frames when<br />
&nbsp; &nbsp; &nbsp;  going off channel, so frames are not just &quot;dropped&quot; - this causes<br />
&nbsp; &nbsp; &nbsp;  issues in the aggregation sessions and may cause traffic stalls.<br />
&nbsp; &nbsp; 4. Test/fix any issues with adhoc 802.11n support.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
BSD-licensed sort Utility (GNU sort Replacement)<br />
<br />
&nbsp;  URL: http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/<br />
&nbsp;  URL:<br />
&nbsp;  http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html<br />
<br />
&nbsp;  Contact: Oleg Moskalenko &lt;oleg.moskalenko@citrix.com&gt;<br />
&nbsp;  Contact: Gábor Kövesdán &lt;gabor@FreeBSD.org&gt;<br />
<br />
&nbsp;  Currently the BSD sort reached usable stable stage. It is stable, it is<br />
&nbsp;  as fast as the GNU sort, and it supports multi-byte locales (this is<br />
&nbsp;  something that GNU sort does not do correctly). BSD sort has all<br />
&nbsp;  features of GNU sort 5.3.0 (version included into FreeBSD) with some<br />
&nbsp;  extra features and bug fixes.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Add BSD sort into HEAD as an alternative, installed as bsdsort. If<br />
&nbsp; &nbsp; &nbsp;  proven to work as expected, change it to the default sort version<br />
&nbsp; &nbsp; &nbsp;  and remove GNU sort.<br />
&nbsp; &nbsp; 2. Investigate the possibility of a multi-threaded sort implementation<br />
&nbsp; &nbsp; &nbsp;  and implement it, if it proves more efficient.<br />
&nbsp; &nbsp; 3. Upgrade BSD sort features to include some obscure new features in<br />
&nbsp; &nbsp; &nbsp;  the latest GNU sort version 8.15.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Clang Replacing GCC in the Base System<br />
<br />
&nbsp;  URL: http://wiki.FreeBSD.org/BuildingFreeBSDWithClang<br />
<br />
&nbsp;  Contact: Brooks Davis &lt;brooks@FreeBSD.org&gt;<br />
&nbsp;  Contact: David Chisnall &lt;theraven@FreeBSD.org&gt;<br />
&nbsp;  Contact: Dimitry Andric &lt;dim@FreeBSD.org&gt;<br />
&nbsp;  Contact: Ed Schouten &lt;ed@FreeBSD.org&gt;<br />
&nbsp;  Contact: Pawel Worach &lt;pawel.worach@gmail.com&gt;<br />
&nbsp;  Contact: Roman Divacky &lt;rdivacky@FreeBSD.org&gt;<br />
<br />
&nbsp;  Both FreeBSD 10.0-CURRENT and 9.0-STABLE now have Clang 3.0 release<br />
&nbsp;  installed by default. At least on 10.0-CURRENT, both world and the<br />
&nbsp;  GENERIC kernel can be completely built without any -Werror warnings.<br />
&nbsp;  This may not be the case for all custom kernel configurations yet.<br />
<br />
&nbsp;  As of r231057, there is a WITH_CLANG_EXTRAS option for src.conf(5),<br />
&nbsp;  which will enable a number of additional LLVM and Clang tools, such as<br />
&nbsp;  'llc' and 'opt'. These tools are mainly useful for people that want to<br />
&nbsp;  manipulate LLVM bitcode (.bc) and LLVM assembly language (.ll) files,<br />
&nbsp;  or want to tinker with LLVM and Clang themselves.<br />
<br />
&nbsp;  Also, as of r232322, there is a WITH_CLANG_IS_CC option for<br />
&nbsp;  src.conf(5), which will install Clang as /usr/bin/cc, /usr/bin/c++ and<br />
&nbsp;  /usr/bin/cpp, making it the default system compiler. Unless you also<br />
&nbsp;  use the WITHOUT_GCC option, gcc will still be available as<br />
&nbsp;  /usr/bin/gcc, /usr/bin/g++ and /usr/bin/gcpp.<br />
<br />
&nbsp;  The intent is to switch on this option by default rather sooner than<br />
&nbsp;  later, so we can start preparing for shipping 10.0-RELEASE with Clang<br />
&nbsp;  as as the default system compiler, and deprecating gcc.<br />
<br />
&nbsp;  In other news, we will import a newer snapshot of Clang soon, since<br />
&nbsp;  upstream LLVM/Clang has already announced their 3.1 release will be<br />
&nbsp;  branched April 16, 2012. Most likely, the actual 3.1 release will be<br />
&nbsp;  follow a few weeks later, after which we will do another import.<br />
<br />
&nbsp;  Last but not least, there are many ports people working on making our<br />
&nbsp;  ports compile properly with Clang. Fixes are checked in on a very<br />
&nbsp;  regular basis now, and full exp-runs with Clang are also done fairly<br />
&nbsp;  regularly. Of course, there are always a few difficult cases,<br />
&nbsp;  especially with very old software that will not even compile with newer<br />
&nbsp;  versions of gcc, let alone clang.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. One of the most important tasks at the moment is to actually build<br />
&nbsp; &nbsp; &nbsp;  and run your entire FreeBSD system with Clang, as much as possible.<br />
&nbsp; &nbsp; &nbsp;  Any compile-time or run-time problems should be reported to the<br />
&nbsp; &nbsp; &nbsp;  appropriate mailing list, or filed as a PR. If you have patches<br />
&nbsp; &nbsp; &nbsp;  and/or workarounds, that would be even better.<br />
&nbsp; &nbsp; 2. Clang should have gotten better support for cross-compiling after<br />
&nbsp; &nbsp; &nbsp;  3.0, so as soon as a 3.1 version is imported, we will need to look<br />
&nbsp; &nbsp; &nbsp;  at ways to get the FreeBSD world and kernels to cross-compile. This<br />
&nbsp; &nbsp; &nbsp;  is mainly of use for ARM and MIPS, which are architectures you<br />
&nbsp; &nbsp; &nbsp;  usually do not want to build natively on.<br />
&nbsp; &nbsp; 3. Help to make unwilling ports build with Clang is always needed, and<br />
&nbsp; &nbsp; &nbsp;  greatly appreciated. Please mail the maintainer of your favorite<br />
&nbsp; &nbsp; &nbsp;  port with patches, or file PRs.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
DTrace Probes for the linuxulator<br />
<br />
&nbsp;  Contact: Alexander Leidinger &lt;netchild@FreeBSD.org&gt;<br />
<br />
&nbsp;  Recently DTrace in the kernel was improved to be able to load kernel<br />
&nbsp;  modules with static dtrace providers after the dtrace modules. This<br />
&nbsp;  allows me to commit my linuxulator specific static provider work to<br />
&nbsp;  -CURRENT.<br />
<br />
&nbsp;  Together with the linuxulator DTrace probes I developed some D scripts<br />
&nbsp;  to check various code paths in the linuxulator. Those scripts check<br />
&nbsp;  various error cases which may be interesting to verify userland code,<br />
&nbsp;  but also linuxulator internals like locks.<br />
<br />
&nbsp;  As of this writing I'm in the process of updating a test machine to a<br />
&nbsp;  more recent -current to prepare the commit.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
FreeBSD Services Control<br />
<br />
&nbsp;  URL: http://people.FreeBSD.org/~trhodes/fsc/<br />
<br />
&nbsp;  Contact: Tom Rhodes &lt;trhodes@FreeBSD.org&gt;<br />
<br />
&nbsp;  After a while of moving and getting a new job, I finally got back to<br />
&nbsp;  this project (also thanks to several submissions by Julian Fagir), a<br />
&nbsp;  new version has been uploaded along with a short description page. The<br />
&nbsp;  current version supports more options, a configuration file, and<br />
&nbsp;  updated rc.d script. It also includes manual page updates and an<br />
&nbsp;  optional debugging mode.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
FreeBSD/arm on Various TI Boards<br />
<br />
&nbsp;  URL: http://svnweb.FreeBSD.org/base/projects/armv6/sys/arm/ti/<br />
<br />
&nbsp;  Contact: Ben Gray &lt;bgray@FreeBSD.org&gt;<br />
&nbsp;  Contact: Olivier Houchard &lt;cognet@FreeBSD.org&gt;<br />
&nbsp;  Contact: Damjan Marion &lt;dmarion@FreeBSD.org&gt;<br />
&nbsp;  Contact: Oleksandr Tymoshenko &lt;gonzo@FreeBSD.org&gt;<br />
<br />
&nbsp;  The goal of this project is to get FreeBSD running on various popular<br />
&nbsp;  boards that use TI-based SoCs like OMAP3, OMAP4, AM335x. Project covers<br />
&nbsp;  some ARM generic Cortex-A components: GIC (Generic Interrupt<br />
&nbsp;  Controller), PL310 L2 Cache Controller and SCU.<br />
<br />
&nbsp;  PandaBoard (TI OMAP4430) and PandaBoard ES (OMAP4460) Dual core ARM<br />
&nbsp;  Cortex-A9 board support includes: USB, onboard Ethernet over USB, GPIO,<br />
&nbsp;  I2C and MMC/SD card drivers. Board works in multiuser mode over NFS<br />
&nbsp;  root.<br />
<br />
&nbsp;  BeagleBone (TI AM3358/AM3359) single core ARM Cortex-A8 based board<br />
&nbsp;  support currently includes: Ethernet, L2 cache, GPIO, I2C. Board works<br />
&nbsp;  in multiuser mode over NFS root.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Completing missing peripherals: DMA, SPI, MMC/SD, Video, Audio.<br />
&nbsp; &nbsp; 2. Completing SMP support and testing.<br />
&nbsp; &nbsp; 3. Importing BeagleBoard (OMAP3) code to SVN.<br />
&nbsp; &nbsp; 4. Improving overall stability and performance.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
FreeBSD/powerpc on Freescale QorIQ DPAA<br />
<br />
&nbsp;  URL:<br />
&nbsp;  http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2040<br />
&nbsp;  URL:<br />
&nbsp;  http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P3041<br />
&nbsp;  URL:<br />
&nbsp;  http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P5020<br />
&nbsp;  URL:<br />
&nbsp;  http://www.freescale.com/webapp/sps/site/homepage.jsp?code=64BIT&amp;fsrch=<br />
&nbsp;  1&amp;sr=1<br />
<br />
&nbsp;  Contact: Michal Dubiel &lt;md@semihalf.com&gt;<br />
&nbsp;  Contact: Rafal Jaworowski &lt;raj@semihalf.com&gt;<br />
&nbsp;  Contact: Piotr Ziecik &lt;kosmo@semihalf.com&gt;<br />
<br />
&nbsp;  This work is bringing up the FreeBSD on Freescale QorIQ Data Path<br />
&nbsp;  Acceleration Architecture (DPAA) system-on-chips along with device<br />
&nbsp;  drivers for integrated peripherals. Since the last status report, the<br />
&nbsp;  following support has been added:<br />
&nbsp; &nbsp;  * Ethernet (full network functionality using Regular Mode of DPAA<br />
&nbsp; &nbsp; &nbsp;  infrastructure)<br />
&nbsp; &nbsp;  * QorIQ P5020 SoC (e5500 core in legacy 32-bit mode)<br />
&nbsp; &nbsp;  * P5020 QorIQ Development System support<br />
&nbsp; &nbsp;  * Initial support for Enhanced SDHC<br />
<br />
&nbsp;  The next step is:<br />
&nbsp; &nbsp;  * e5500 core in native 64-bit mode<br />
<br />
&nbsp;  Related publications:<br />
&nbsp; &nbsp;  * Michal Dubiel, Piotr Ziecik, &quot;FreeBSD on Freescale QorIQ Data Path<br />
&nbsp; &nbsp; &nbsp;  Acceleration Architecture Devices&quot;, AsiaBSDCon, March 2012, Tokyo,<br />
&nbsp; &nbsp; &nbsp;  Japan.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
GNU-Free C++11 Stack<br />
<br />
&nbsp;  Contact: David Chisnall &lt;theraven@FreeBSD.org&gt;<br />
<br />
&nbsp;  Since the last status report, the combination of libc++ and libcxxrt<br />
&nbsp;  has received some additional testing and gained some new features<br />
&nbsp;  including support for ARM EABI. With clang 3.1, we now pass all of the<br />
&nbsp;  C++11 atomics tests.<br />
<br />
&nbsp;  The xlocale implementation (required for libc++) has been tested with a<br />
&nbsp;  variety of ports that were originally written for the Darwin<br />
&nbsp;  implementation, and bugs that this testing uncovered have been fixed.<br />
&nbsp;  This should be released in 9.1.<br />
<br />
&nbsp;  In -CURRENT, we are now building libsupc++ as a shared library. This<br />
&nbsp;  provides the ABI layer and building it as a shared library means that<br />
&nbsp;  we can replace it with libcxxrt easily. If you are running -CURRENT,<br />
&nbsp;  please try using libmap.conf to enable libcxxrt instead of libsupc++.<br />
<br />
&nbsp;  If libstdc++ is using libcxxrt, you can now link against both libraries<br />
&nbsp;  that are using libstdc++ and libc++, making the migration slightly<br />
&nbsp;  easier, although you cannot pass STL objects between libraries using<br />
&nbsp;  different STL versions.<br />
<br />
&nbsp;  We still need a replacement for some parts of libgcc_s and for the<br />
&nbsp;  linker, but we're on track for a BSD licensed C++ stack in 10.0.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Test ports with libc++. Hopefully most will Just Work, but others<br />
&nbsp; &nbsp; &nbsp;  may need patches or have a hard dependency on libstdc++.<br />
&nbsp; &nbsp; 2. Enable building libc++ by default. This is dependent upon building<br />
&nbsp; &nbsp; &nbsp;  with clang, because the version of gcc in the base system does not<br />
&nbsp; &nbsp; &nbsp;  support C++11 and so can not be used to build libc++.<br />
&nbsp; &nbsp; 3. Removing libstdc++ from the base system and making it available<br />
&nbsp; &nbsp; &nbsp;  through ports for backwards compatibility.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Growing filesystems online<br />
<br />
&nbsp;  Contact: Edward Tomasz Napierala &lt;trasz@FreeBSD.org&gt;<br />
<br />
&nbsp;  The goal of this project is to make it possible to grow a filesystem,<br />
&nbsp;  both UFS and ZFS, while it's mounted read-write. This includes changes<br />
&nbsp;  to both filesystems, GEOM infrastructure, and the da(4) driver. For<br />
&nbsp;  testing purposes, I've also added resizing to mdconfig(8) and<br />
&nbsp;  implemented LUN resizing in CAM Target Layer.<br />
<br />
&nbsp;  From the system administrator point of view, this makes it possible to<br />
&nbsp;  resize mounted partition using gpart(8) and then resize the filesystem<br />
&nbsp;  on it using growfs(8) - all without unmounting it first; especially<br />
&nbsp;  useful if it's a root filesystem.<br />
<br />
&nbsp;  All the functionality works and is in the process of being refined,<br />
&nbsp;  reviewed and merged to HEAD.<br />
<br />
&nbsp;  This project is sponsored by The FreeBSD Foundation.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. The write suspension infrastructure (/dev/ufssuspend) implemented<br />
&nbsp; &nbsp; &nbsp;  to make resizing possible makes it also possible to implement<br />
&nbsp; &nbsp; &nbsp;  online tunefs(8) and fsck(8).<br />
&nbsp; &nbsp; 2. Right now, there is no way for a GEOM class to veto resizing --<br />
&nbsp; &nbsp; &nbsp;  classes are notified about resize and they can either adapt, or<br />
&nbsp; &nbsp; &nbsp;  wither. Many classes store their metadata in the last sector,<br />
&nbsp; &nbsp; &nbsp;  though, so resizing a partition containing e.g. gmirror will make<br />
&nbsp; &nbsp; &nbsp;  it inoperable. It would be nice if geom_mirror(4) could veto<br />
&nbsp; &nbsp; &nbsp;  resizing, so the administrator attempting to shoot himself in the<br />
&nbsp; &nbsp; &nbsp;  foot would get a warning.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
HDMI/DisplayPort Audio Support in HDA Sound Driver (snd_hda)<br />
<br />
&nbsp;  Contact: Alexander Motin &lt;mav@FreeBSD.org&gt;<br />
<br />
&nbsp;  snd_hda(4) driver got number of improvements to better support<br />
&nbsp;  HDMI/DisplayPort audio, such as:<br />
&nbsp; &nbsp;  * Added fetching EDID-Like Data from the CODEC and video driver,<br />
&nbsp; &nbsp; &nbsp;  describing audio capabilities of the display device.<br />
&nbsp; &nbsp;  * Added setting HDMI/DP-specific CODEC options, such as number of<br />
&nbsp; &nbsp; &nbsp;  channels, speakers configuration and channels mapping.<br />
&nbsp; &nbsp;  * Added support for more multichannel formats. For HDMI and<br />
&nbsp; &nbsp; &nbsp;  DisplayPort device now supported: 2.0, 2.1, 3.0, 3.1, 4.0, 4.1,<br />
&nbsp; &nbsp; &nbsp;  5.0, 5.1, 6.0, 6.1, 7.0 and 7.1 channels.<br />
&nbsp; &nbsp;  * Added support for compressed streams passthrough with data rate<br />
&nbsp; &nbsp; &nbsp;  6.144 - 24Mbps, such as DTS-HD Master Audio or Dolby TrueHD.<br />
&nbsp; &nbsp;  * Added support for HDA bus multiplexing to handle higher data rates<br />
&nbsp; &nbsp; &nbsp;  (up to 92, 184 or more Mbps, depending on hardware capabilities).<br />
&nbsp; &nbsp; &nbsp;  It allows to handle several 192/24/8 LPCM playback streams<br />
&nbsp; &nbsp; &nbsp;  simultaneously.<br />
<br />
&nbsp;  Above functionality was successfully tested on NVIDIA GT210 and GT520<br />
&nbsp;  video cards with nvidia-driver-290.10 driver. HDMI audio on older<br />
&nbsp;  NVIDIA ION and Geforce 8300 boards still does not work for unknown<br />
&nbsp;  reason. There are also successful reports about Intel video with latest<br />
&nbsp;  KMS-based drivers. Support for ATI cards is limited to older cards,<br />
&nbsp;  because video driver supporting newer cards does not support HDMI<br />
&nbsp;  audio.<br />
<br />
&nbsp;  The code was committed to HEAD and merged to 9-STABLE branch.<br />
<br />
&nbsp;  Project sponsored by iXsystems, Inc.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Make better use of received EDID-Like Data.<br />
&nbsp; &nbsp; 2. Identify and fix problem with older NVIDIA cards.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Improved hwpmc(9) Support for MIPS<br />
<br />
&nbsp;  Contact: Oleksandr Tymoshenko &lt;gonzo@FreeBSD.org&gt;<br />
<br />
&nbsp;  hwpmc(9) for MIPS has been reworked. The changes include:<br />
&nbsp; &nbsp;  * msip24k code was split to CPU-specific and arch-specific parts to<br />
&nbsp; &nbsp; &nbsp;  make adding support for new CPUs easier<br />
&nbsp; &nbsp;  * Added support for Octeon PMC<br />
&nbsp; &nbsp;  * Added sampling support for MIPS in general<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
IPv6 Performance Analysis<br />
<br />
&nbsp;  URL: http://people.FreeBSD.org/~bz/bench/<br />
<br />
&nbsp;  Contact: Bjoern A. Zeeb &lt;bz@FreeBSD.org&gt;<br />
<br />
&nbsp;  IPv6 performance numbers were often seen (significantly) lower on<br />
&nbsp;  FreeBSD when compared to IPv4. Continuing last years IPv6-only kernel<br />
&nbsp;  efforts this project looked at various reasons for this and started<br />
&nbsp;  fixing some.<br />
<br />
&nbsp;  As part of the project a benchmark framework was created that could<br />
&nbsp;  carry out various tests including reboots in between runs and gather<br />
&nbsp;  results reproducibly without user intervention. It allows regular<br />
&nbsp;  benchmarking with minimal configuration and easy future extension for<br />
&nbsp;  more benchmarks.<br />
<br />
&nbsp;  As a result of the initial analysis, UDP locking and route lookups were<br />
&nbsp;  improved, and delayed checksumming, TSO6 and LRO support for IPv6 were<br />
&nbsp;  implemented. Following this checksum &quot;offload&quot; for IPv6 on loopback was<br />
&nbsp;  enabled and various further individual improvements, both locking and<br />
&nbsp;  general code changes, as well as a reduction of the cache size<br />
&nbsp;  footprint were carried out. Some of the changes were equally applied to<br />
&nbsp;  IPv4.<br />
<br />
&nbsp;  Performance numbers on physical and loopback interfaces are on par with<br />
&nbsp;  IPv4 when using offload support with TCP/IPv6, which is a huge<br />
&nbsp;  improvement. UDP and non-offload numbers on IPv6 have generally<br />
&nbsp;  improved but are still lower than on IPv4 and will need future work to<br />
&nbsp;  catch up with a decade of IPv4 benchmarking and code path<br />
&nbsp;  optimizations. UDP IPv6 minimal size send path packets per second (pps)<br />
&nbsp;  numbers however have increased beating IPv4 when sending to a local<br />
&nbsp;  discard device.<br />
<br />
&nbsp;  This gets us really close to being able to prefer IPv6 by default<br />
&nbsp;  without causing loopback performance regressions. For physical<br />
&nbsp;  interfaces, cxgb(4) in HEAD already supports IPv6 TCP offload and<br />
&nbsp;  LRO/v6 support was added. To be able to get more test results on<br />
&nbsp;  different hardware, both ixgbe(4) and cxgbe(4) were also updated to<br />
&nbsp;  support TSO6 and LRO with IPv6.<br />
<br />
&nbsp;  Some of the insights gained from this work will help upcoming<br />
&nbsp;  discussions on both the lower/link-layer overhaul as well as for the<br />
&nbsp;  mbuf changes to prepare our stack for more, future improvements (ahead<br />
&nbsp;  of time).<br />
<br />
&nbsp;  I once again want to thank the FreeBSD Foundation and iXsystems for<br />
&nbsp;  their support of the project, as well as George Neville-Neil for<br />
&nbsp;  providing review.<br />
<br />
&nbsp;  Having set the start to close one of the biggest feature parity gaps<br />
&nbsp;  left I will continue to improve IPv6 code paths and hope that we will<br />
&nbsp;  see more contributions and independent results from the community as<br />
&nbsp;  well soon.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Carefully merge code changes to SVN.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
isci(4) SAS Driver<br />
<br />
&nbsp;  Contact: Jim Harris &lt;jimharris@FreeBSD.org&gt;<br />
<br />
&nbsp;  An Intel-supported isci(4) driver, for the integrated SAS controller in<br />
&nbsp;  Intel's C600 chipsets, is now available in head, stable/9, stable/8 and<br />
&nbsp;  stable/7.<br />
<br />
&nbsp;  The isci(4) driver will also be part of the FreeBSD 8.3 release.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
KDE/FreeBSD<br />
<br />
&nbsp;  URL: http://FreeBSD.kde.org<br />
&nbsp;  URL: http://FreeBSD.kde.org/area51.php<br />
<br />
&nbsp;  Contact: KDE FreeBSD &lt;kde@FreeBSD.org&gt;<br />
<br />
&nbsp;  The team has made many releases and upstreamed many fixes and patches.<br />
&nbsp;  The latest round of releases include:<br />
&nbsp; &nbsp;  * KDE SC: 4.7.4 (in ports) and 4.8.0, 4.8.1, 4.8.2 (in area51)<br />
&nbsp; &nbsp;  * Qt: 4.8.0, 4.8.1 (in area51)<br />
&nbsp; &nbsp;  * PyQt: 4.9.1; SIP: 4.13.2 (in area51)<br />
&nbsp; &nbsp;  * KDevelop: 2.3.0; KDevPlatform: 1.3.0 (in area51)<br />
&nbsp; &nbsp;  * Calligra: 2.3.87 (in area51)<br />
&nbsp; &nbsp;  * Amarok: 2.5.0<br />
&nbsp; &nbsp;  * CMake: 2.8.7<br />
<br />
&nbsp;  Due to the prolonged port freeze the KDE team has not been able to<br />
&nbsp;  update KDE in Ports as it is considered a intrusive change.<br />
<br />
&nbsp;  The team is always looking for more testers and porters so please<br />
&nbsp;  contact us at kde@FreeBSD.org and visit our home page at<br />
&nbsp;  http://FreeBSD.kde.org.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Testing KDE SC 4.8.2.<br />
&nbsp; &nbsp; 2. Testing KDE PIM 4.8.2.<br />
&nbsp; &nbsp; 3. Testing phonon-gstreamer and phonon-vlc as the phonon-xine backend<br />
&nbsp; &nbsp; &nbsp;  was deprecated (but will remain in the ports for now).<br />
&nbsp; &nbsp; 4. Testing the Calligra beta releases (in the area51 repository).<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Multi-FIB: IPv6 Support and Other Enhancements<br />
<br />
&nbsp;  URL: http://svnweb.FreeBSD.org/base/projects/multi-fibv6/<br />
<br />
&nbsp;  Contact: Bjoern A. Zeeb &lt;bz@FreeBSD.org&gt;<br />
&nbsp;  Contact: Alexander V. Chernikov &lt;melifaro@FreeBSD.org&gt;<br />
<br />
&nbsp;  In 2008 the multiple forwarding information base (FIB) feature was<br />
&nbsp;  introduced for IPv4 allowing up to 16 distinct forwarding (&quot;routing&quot;)<br />
&nbsp;  tables in the kernel. Thanks to the sponsorship from Cisco Systems,<br />
&nbsp;  Inc. this feature is now also available for IPv6 and one of the bigger<br />
&nbsp;  IPv6 feature-parity gaps is closed. The changes have been integrated to<br />
&nbsp;  HEAD, were merged back to stable/9 and stable/8 and will be part of<br />
&nbsp;  future releases for these branches. A backport to stable/7 is also<br />
&nbsp;  available in the project branch. If more than one FIB is requested,<br />
&nbsp;  IPv6 FIBs will be added along the extra IPv4 FIBs without any special<br />
&nbsp;  configuration needed and programs like netstat and setfib, as well as<br />
&nbsp;  ipfw, etc. were extended to seamlessly support the multi-FIB feature on<br />
&nbsp;  both address families.<br />
<br />
&nbsp;  Thanks to the help of Alexander V. Chernikov all usage of the multi-FIB<br />
&nbsp;  feature is now using the boot-time variable rather than depending on<br />
&nbsp;  the compile time option. In HEAD this now allows us you to use the<br />
&nbsp;  multi-FIB feature with GENERIC kernels not needing to recompile your<br />
&nbsp;  own anymore. The former kernel option can still be used to set a<br />
&nbsp;  default value if desired. Otherwise the net.fibs loader tunable can be<br />
&nbsp;  used to request more than one IPv6 and IPv4 FIB at boot time.<br />
<br />
&nbsp;  Last, routing sockets are now aware of FIBs and will only show the<br />
&nbsp;  routing messages targeted at the FIB attached to. This allows route<br />
&nbsp;  monitor or routing daemons to get selective updates for just a specific<br />
&nbsp;  FIB.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
NAND File System, NAND Flash Framework, NAND Simulator<br />
<br />
&nbsp;  URL: http://svnweb.FreeBSD.org/base/projects/nand/<br />
<br />
&nbsp;  Contact: Grzegorz Bernacki &lt;gjb@semihalf.com&gt;<br />
&nbsp;  Contact: Mateusz Guzik &lt;mjg@semihalf.com&gt;<br />
<br />
&nbsp;  The NAND Flash stack consists of a driver framework for NAND<br />
&nbsp;  controllers and memory chips, a NAND device simulator and a fault<br />
&nbsp;  tolerant, log-structured file system, accompanied by tools, utilities<br />
&nbsp;  and documentation.<br />
&nbsp; &nbsp;  <br />
&nbsp;  NAND FS support merged into &quot;nand&quot; project branch:<br />
&nbsp; &nbsp;  * NAND FS filesystem<br />
&nbsp; &nbsp;  * NAND FS userland tools<br />
<br />
&nbsp;  NAND Framework and NAND simulator merged into &quot;nand&quot; project<br />
&nbsp;  branch:<br />
&nbsp; &nbsp;  * NAND framework: nandbus, generic nand chips drivers<br />
&nbsp; &nbsp;  * NAND Flash controllers (NFC) drivers for NAND Simulator and Marvell<br />
&nbsp; &nbsp; &nbsp;  MV-78100 (ARM)<br />
&nbsp; &nbsp;  * NAND tool (which allows to erase, write/read pages/oob, etc.<br />
<br />
&nbsp;  The next steps include:<br />
&nbsp; &nbsp;  * Fix bugs<br />
&nbsp; &nbsp;  * Merge into HEAD<br />
<br />
&nbsp;  Work on this project is supported by the FreeBSD Foundation and Juniper<br />
&nbsp;  Networks.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Perl Ports Testing<br />
<br />
&nbsp;  URL: http://wiki.FreeBSD.org/Perl#Test_Dependencies<br />
<br />
&nbsp;  Contact: Steve Wills &lt;swills@FreeBSD.org&gt;<br />
<br />
&nbsp;  Many Perl modules in ports come with test cases included with their<br />
&nbsp;  source. This project's goal is to ensure that all these tests pass.<br />
&nbsp;  Significant progress has been made on this project. The change to build<br />
&nbsp;  perl with -pthread was committed and no issues have been reported. Many<br />
&nbsp;  ports have had missing dependencies added and/or other changes and<br />
&nbsp;  approximately 90% of p5- ports pass tests. Work is being done on<br />
&nbsp;  bringing testing support out of ports tinderbox.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Finish work on patch to bring testing support to ports.<br />
&nbsp; &nbsp; 2. Add additional support for testing other types of ports such as<br />
&nbsp; &nbsp; &nbsp;  python and ruby.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Porting DTrace to MIPS and ARM<br />
<br />
&nbsp;  Contact: Oleksandr Tymoshenko &lt;gonzo@FreeBSD.org&gt;<br />
<br />
&nbsp;  The major part of DTrace has been ported to MIPS platform. Supported<br />
&nbsp;  ABIs: o32 and n64. n32 has not been tested yet. MIPS implementation<br />
&nbsp;  passes 853 of 927 tests from DTrace test suite.<br />
<br />
&nbsp;  The fbt provider and userland DTrace are not supported yet.<br />
<br />
&nbsp;  The port to ARM is in progress.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Userland DTrace support for MIPS.<br />
&nbsp; &nbsp; 2. Investigate amount of effort required for getting fbt provider work<br />
&nbsp; &nbsp; &nbsp;  at least partially.<br />
&nbsp; &nbsp; 3. Find proper solution for cross-platform CTF data generation<br />
&nbsp; &nbsp; &nbsp;  (required for ARM).<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Release Engineering Team Status Report<br />
<br />
&nbsp;  URL: http://www.FreeBSD.org/releng/<br />
<br />
&nbsp;  Contact: Release Engineering Team &lt;re@FreeBSD.org&gt;<br />
<br />
&nbsp;  On behalf of the FreeBSD Project the Release Engineering Team was are<br />
&nbsp;  pleased to announce the release of the FreeBSD 8.3-RELEASE on April<br />
&nbsp;  18th, 2012.<br />
<br />
&nbsp;  With the FreeBSD 8.3 release cycle completed our focus shifts to<br />
&nbsp;  preparing for the FreeBSD 9.1-RELEASE. A schedule will be posted<br />
&nbsp;  shortly, with the release target date set for mid-July 2012.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
Replacing the Regular Expression Code<br />
<br />
&nbsp;  URL: http://svnweb.FreeBSD.org/base/user/gabor/tre-integration/<br />
&nbsp;  URL: http://laurikari.net/tre/<br />
&nbsp;  URL:<br />
&nbsp;  http://www.tdk.aut.bme.hu/Files/TDK2011/POSIX-regularis-kifejezesek1.pd<br />
&nbsp;  f<br />
<br />
&nbsp;  Contact: Gábor Kövesdán &lt;gabor@FreeBSD.org&gt;<br />
<br />
&nbsp;  Since the last status report, there has been a significant progress in<br />
&nbsp;  optimizing TRE. The multiple pattern heuristic code is mostly finished<br />
&nbsp;  and it distinguishes several different cases to speed up pattern<br />
&nbsp;  matching. It extracts literal fragments from the original patterns and<br />
&nbsp;  uses a multiple pattern matching algorithm to find any occurrence. GNU<br />
&nbsp;  grep uses the Commentz-Walter algorithm, which is an automaton-based<br />
&nbsp;  algorithm, while in this project, it has been decided to use a<br />
&nbsp;  Wu-Manber algorithm, which is more efficient and also easier to<br />
&nbsp;  implement. In the current state, it does not work entirely yet and some<br />
&nbsp;  cases, like the REG_ICASE flag are not yet covered. This is the next<br />
&nbsp;  major step to complete this multiple pattern interface. In the<br />
&nbsp;  development branch, BSD grep is already modified to use this new<br />
&nbsp;  interface so it can be used for testing and debugging purposes.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Finish multiple pattern heuristic regex matching.<br />
&nbsp; &nbsp; 2. Implement GNU-specific regex extensions.<br />
&nbsp; &nbsp; 3. Test standard-compliance and correct behavior.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The bsdconfig(8) utility<br />
<br />
&nbsp;  URL: http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdconfig/<br />
&nbsp;  URL: http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1.svg<br />
&nbsp;  URL:<br />
&nbsp;  http://druidbsd.sf.net/download/bsdconfig/bsdconfig-20120512-1i.svg<br />
<br />
&nbsp;  Contact: Devin Teske &lt;dteske@FreeBSD.org&gt;<br />
&nbsp;  Contact: Ron McDowell &lt;rcm@fuzzwad.org&gt;<br />
<br />
&nbsp;  Approaching 20,000 lines of sh(1) code, the bsdconfig(8) tool is<br />
&nbsp;  approximately 70% complete. Upon completion of this project,<br />
&nbsp;  bsdconfig(8) will represent (in conjunction with already-existing<br />
&nbsp;  bsdinstall(8)) a complete set of utilities capable of purposefully<br />
&nbsp;  deprecating sysinstall(8) in FreeBSD 9 and higher. This project has<br />
&nbsp;  been a labor of love for Ron McDowell and I for over 90 days now and we<br />
&nbsp;  are approaching the completion of this wonderful tool.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. The &quot;installer suite&quot; modules for acquiring/installing binary<br />
&nbsp; &nbsp; &nbsp;  packages and additional distribution sets. Startup services module.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The FreeBSD Foundation Team Report<br />
<br />
&nbsp;  URL: www.FreeBSDFoundation.org<br />
<br />
&nbsp;  Contact: Deb Goodkin &lt;deb@FreeBSDFoundation.org&gt;<br />
<br />
&nbsp;  The Foundation sponsored AsiaBSDCon 2012 which was held in Tokyo,<br />
&nbsp;  Japan, March 22-25. We were represented at SCALE on Jan 21 and NELF on<br />
&nbsp;  March 17. This quarter we plan on being at ILF (Indiana LinuxFest)<br />
&nbsp;  April 14th, BSDCan May 11-12, and SELF (Southeast LinuxFest) June 9.<br />
<br />
&nbsp;  We are proud to be a gold sponsor of BSDCan 2012, which will be held in<br />
&nbsp;  Ottawa, Canada, May 11-12. We are sponsoring 14 developers to attend<br />
&nbsp;  the conference.<br />
<br />
&nbsp;  We kicked off three foundation funded projects -- Growing Filesystems<br />
&nbsp;  Online by Edward Tomasz Napierala, Implementing auditdistd daemon by<br />
&nbsp;  Pawel Jakub Dawidek, and NAND Flash Support by Semihalf.<br />
<br />
&nbsp;  We are pleased to announce the addition of George Neville-Neil to our<br />
&nbsp;  board of directors. Deb Goodkin, our Director of Operations, was<br />
&nbsp;  interviewed by bsdtalk.<br />
<br />
&nbsp;  We announced a call for project proposals. We will accept proposals<br />
&nbsp;  until April 30th. Please read Project Proposal Procedures to find out<br />
&nbsp;  more.<br />
<br />
&nbsp;  FreeBSD 9.0 was released and we are proud to say we funded 7 of the new<br />
&nbsp;  features!<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The FreeBSD Haskell Ports<br />
<br />
&nbsp;  URL: http://wiki.FreeBSD.org/Haskell<br />
&nbsp;  URL: https://github.com/freebsd-haskell/freebsd-haskell/<br />
&nbsp;  URL: https://github.com/freebsd-haskell/hsporter/<br />
&nbsp;  URL: https://github.com/freebsd-haskell/hsmtk/<br />
<br />
&nbsp;  Contact: Gábor PÁLI &lt;pgj@FreeBSD.org&gt;<br />
&nbsp;  Contact: Ashish SHUKLA &lt;ashish@FreeBSD.org&gt;<br />
<br />
&nbsp;  We are proud announce that the FreeBSD Haskell Team has committed the<br />
&nbsp;  Haskell Platform 2011.4.0.0 update, GHC 7.0.4 update, existing port<br />
&nbsp;  updates, as well new port additions to FreeBSD ports repository, which<br />
&nbsp;  were pending due to freeze for 9.0-RELEASE. Some of the new ports which<br />
&nbsp;  were committed include Yesod, Happstack, wxHaskell, gitit, Threadscope,<br />
&nbsp;  etc. and the count of Haskell ports in FreeBSD Ports tree is now almost<br />
&nbsp;  300. All of these updates will be available as part of upcoming<br />
&nbsp;  8.3-RELEASE.<br />
<br />
&nbsp;  We started project hsporter to automate creation of new FreeBSD Haskell<br />
&nbsp;  ports from .cabal file, as well as update existing ports. We also<br />
&nbsp;  published scripts which we were using in the FreeBSD Haskell project<br />
&nbsp;  under the project hsmtk.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Test GHC to work with clang/LLVM.<br />
&nbsp; &nbsp; 2. Add an option to the lang/ghc port to be able to build it with<br />
&nbsp; &nbsp; &nbsp;  already installed GHC instead of requiring a separate GHC boostrap<br />
&nbsp; &nbsp; &nbsp;  tarball.<br />
&nbsp; &nbsp; 3. Add more ports to the Ports Collection.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The FreeBSD Japanese Documentation Project<br />
<br />
&nbsp;  URL: http://www.FreeBSD.org/ja/<br />
&nbsp;  URL: http://www.jp.FreeBSD.org/doc-jp/<br />
<br />
&nbsp;  Contact: Hiroki Sato &lt;hrs@FreeBSD.org&gt;<br />
&nbsp;  Contact: Ryusuke Suzuki &lt;ryusuke@FreeBSD.org&gt;<br />
<br />
&nbsp;  The same as before, the outdated contents in the www/ja subtree were<br />
&nbsp;  updated to the latest versions in the English counterpart. The updating<br />
&nbsp;  work of the outdated translations in the www/ja subtree is almost<br />
&nbsp;  complete. Only the translations of the release documents for old<br />
&nbsp;  releases may be outdated.<br />
<br />
&nbsp;  During this period, we translated the 9.0-RELEASE announcement and<br />
&nbsp;  published it in a timely manner. It seems that the Japanese version of<br />
&nbsp;  the release announcement is important for Japanese people as this page<br />
&nbsp;  has frequently been referenced.<br />
<br />
&nbsp;  For FreeBSD Handbook, translation work of the &quot;cutting-edge&quot; section is<br />
&nbsp;  still on-going. Some updates in the &quot;printing&quot; and the &quot;linuxemu&quot;<br />
&nbsp;  section were done.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Further translation work of outdated documents in both<br />
&nbsp; &nbsp; &nbsp;  doc/ja_JP.eucJP and www/ja.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The FreeBSD Ports Collection<br />
<br />
&nbsp;  URL: http://www.FreeBSD.org/ports/<br />
&nbsp;  URL:<br />
&nbsp;  http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/<br />
&nbsp;  URL: http://portsmon.FreeBSD.org/index.html<br />
&nbsp;  URL: http://www.FreeBSD.org/portmgr/index.html<br />
&nbsp;  URL: http://blogs.FreeBSDish.org/portmgr/<br />
&nbsp;  URL: http://www.twitter.com/freebsd_portmgr/<br />
&nbsp;  URL: http://www.facebook.com/portmgr<br />
<br />
&nbsp;  Contact: Thomas Abthorpe &lt;portmgr-secretary@FreeBSD.org&gt;<br />
&nbsp;  Contact: Port Management Team &lt;portmgr@FreeBSD.org&gt;<br />
<br />
&nbsp;  The ports tree slowly climbs above 23,000 ports. The PR count still<br />
&nbsp;  remains at about 1100.<br />
<br />
&nbsp;  In Q1 we added 2 new committers, took in 2 commit bits for safe<br />
&nbsp;  keeping, and had one committer return to ports work.<br />
<br />
&nbsp;  The Ports Management team have been running -exp runs on an ongoing<br />
&nbsp;  basis, verifying how base system updates may affect the ports tree, as<br />
&nbsp;  well as providing QA runs for major ports updates. Of note, -exp runs<br />
&nbsp;  were done for:<br />
&nbsp; &nbsp;  * Ports validation in the FreeBSD 10 environment<br />
&nbsp; &nbsp;  * Updates to bison, libtool and libiconv<br />
&nbsp; &nbsp;  * Set java/opendjdk6 as default java<br />
&nbsp; &nbsp;  * Tests with clang set as default<br />
&nbsp; &nbsp;  * Update to devel/boost and friends<br />
&nbsp; &nbsp;  * Update of audio/sdl and friends<br />
&nbsp; &nbsp;  * Tests for changes in the ports licensing infrastructure<br />
&nbsp; &nbsp;  * Update to devel/ruby1[8|9]<br />
&nbsp; &nbsp;  * Update to postresql<br />
&nbsp; &nbsp;  * Update to apr<br />
&nbsp; &nbsp;  * Checks for new x11/xorg<br />
&nbsp; &nbsp;  * Security update to security/gnutls<br />
&nbsp; &nbsp;  * Ongoing validation of infrastructure with pkgng<br />
<br />
&nbsp;  A lot of focus during this period was put into getting the ports tree<br />
&nbsp;  into a ready state for FreeBSD 8.3, including preparing packages for<br />
&nbsp;  the release.<br />
<br />
&nbsp;  Beat Gaetzi has been doing ongoing tests with the ports tree to ensure<br />
&nbsp;  a smooth transition from CVS to Subversion.<br />
<br />
Open tasks:<br />
<br />
&nbsp; &nbsp; 1. Looking for help getting ports to build with clang.<br />
&nbsp; &nbsp; 2. Looking for help with Tier-2 architectures.<br />
&nbsp; &nbsp; 3. ports broken by src changes.<br />
&nbsp; &nbsp; 4. ports failing on pointyhat.<br />
&nbsp; &nbsp; 5. ports failing on pointyhat-west.<br />
&nbsp; &nbsp; 6. ports that are marked as BROKEN.<br />
&nbsp; &nbsp; 7. When did that port break?<br />
&nbsp; &nbsp; 8. Most ports PRs are assigned, we now need to focus on testing,<br />
&nbsp; &nbsp; &nbsp;  committing and closing.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
The FreeNAS Project<br />
<br />
&nbsp;  URL: http://www.FreeNAS.org<br />
<br />
&nbsp;  Contact: Josh Paetzel &lt;jpaetzel@FreeBSD.org&gt;<br />
&nbsp;  Contact: Xin Li &lt;delphij@FreeBSD.org&gt;<br />
<br />
&nbsp;  FreeNAS 8.0.4 was released last month, which marks the end of the 8.0.x<br />
&nbsp;  branch in FreeNAS.<br />
<br />
&nbsp;  FreeNAS 8.2.0 is in BETA currently, and will hopefully be released by<br />
&nbsp;  the end of April.<br />
<br />
&nbsp;  It features a number of improvements over the 8.0.x line, including<br />
&nbsp;  plugin support, (the ability to run arbitrary software in jails), as<br />
&nbsp;  well as better integration between command line ZFS and the GUI.<br />
<br />
&nbsp;  Once 8.2.0 is out it will be quickly followed up with 8.3.0, which will<br />
&nbsp;  include a number of driver updates as well as the long awaited ZFS v28.<br />
&nbsp; &nbsp;  __________________________________________________________________<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp;  (c) 1995-2012 The FreeBSD Project. All rights reserved.</code><hr />
</div>
<!-- END TEMPLATE: bbcode_code_printable --></div>


<!-- END TEMPLATE: postbit_external -->]]></content:encoded>
			<category domain="http://www.bsdforen.de/forumdisplay.php?f=3">News</category>
			<dc:creator>Yamagi</dc:creator>
			<guid isPermaLink="true">http://www.bsdforen.de/showthread.php?t=27824</guid>
		</item>
	</channel>
</rss>

