- fix typos

- some minor rewording
- fix a few whitespaces
- make the links click-able
This commit is contained in:
Daniel Gerzo 2008-09-18 14:44:56 +00:00
parent c58b507b38
commit d4c03eac07
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=32924

View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/projects/summerofcode-2008.sgml,v 1.2 2008/04/24 21:22:35 murray Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/summerofcode-2008.sgml,v 1.3 2008/09/18 08:53:11 murray Exp $">
<!ENTITY title "FreeBSD Summer of Code 2008">
<!ENTITY % navinclude.developers "INCLUDE">
<!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
@ -47,7 +47,7 @@
operating systems. Basic functionality of sending and receiving
packets was the main goal of the project, but unfortunately this
was not acheived. It is very close to having this functionality,
but there are a ffew minor bugs preventing the code from
but there are a few minor bugs preventing the code from
integrating fully with the FreeBSD networking stack.</p>
<p>This project will continue to be worked on until sending,
@ -68,10 +68,10 @@
aid to protocol developers and both testing and debugging of
firewalls/routers.</p>
<p>It's built on top of PCS(Packet Construction Set) "PCS is a set
<p>It is built on top of PCS(Packet Construction Set) "PCS is a set
of Python modules and objects that make building network
protocol code easier for the protocol developer. PCS enables
testing at OSI layers 3, 4, and 5. "</p>
testing at OSI layers 3, 4, and 5."</p>
<p>Tcptest mainly is a python module and one script for each test
covered (more then one per script often) The module count with
@ -92,13 +92,11 @@
previously registered way.</p>
Links:
http://wiki.freebsd.org/VictorBilouro/TCP-IP_regression_test_suite
(project wiki)
http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/bilouro_tcptest/src
(freebsd repository)
http://code.google.com/p/tcptest/ (source code download)
http://bilouro.com/tcptest (source code documentation)
http://pcs.sf.net - Packet Construction Set
<a href="http://wiki.freebsd.org/VictorBilouro/TCP-IP_regression_test_suite">project wiki</a>
<a href="http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/bilouro_tcptest/src">&os; Perforce project repository</a>
<a href="http://code.google.com/p/tcptest/">source code download</a>
<a href="http://bilouro.com/tcptest">source code documentation</a>
<a href="http://pcs.sf.net">Packet Construction Set</a>
</li>
<li>
@ -108,20 +106,20 @@
<strong>Summary:</strong>
<p>Sun Open Solaris Dtrace is pretty useful feature.Users can find
<p>Sun Open Solaris Dtrace is pretty useful feature. Users can find
performance bottlenecks with Dtrace in real production
environment. Since many probes implemented in Open Solaris are
not supported in FreeBSD. so when we port Dtrace Toolkit to
FreeBSD, main job is to find whether this probe is supported by
not supported in FreeBSD, the Open Solaris Dtrace Toolkit should be
ported to &os;. Its main job is to find whether a given probe is supported by
FreeBSD, if so, find it; if not, develop one to support this
function. This summer, at first, I went throught all DTK script
commands, found some of them work directly. But most do
not. Under my mentor John Birrell careful help, I retrieved the
respective system variables FreeBSD kernel, and ended up making
respective FreeBSD kernel variables, and ended up making
system/uname.d work. In addition, I tried to make sar-c.d work
under FreeBSD. Since we need to investigate into Son Open
Solaris Kernel to find how Open Solaris defines the probe and
what probes it needs, this work is realy time consuming, not
under FreeBSD. Since we need to investigate in Sun Open
Solaris Kernel how Open Solaris defines the probe and
what probes it needs, this work is realy time consuming, and not
done yet. From this project, I got to know much about FreeBSD
kernel and Dtrace probes. I found kernel hacking/coding pretty
interesting.</p>
@ -148,10 +146,10 @@
<p>A new tool pkg_convert(1), caches some parts of the existing
/var/db/pkg/ flat database into a Berkeley DB file, and the
tools check for this file and uses it for speed improvements if
it's available and updates it according to
it is available and updates it according to
pkg_{add|delete}'s. You can also use pkg_convert(1) to view the
entries in the cache. The tools will give you an indication if
the database is corrupt, and it's fully recoverable by using
the database is corrupt, and it is fully recoverable by using
pkg_convert(1).</p>
<p>Two bugs in the existing pkg_tools have also been discovered
@ -214,9 +212,9 @@
doesn't full Unicode Collation Algorithm - the part which deals
with expansions. It is needed for half of languages to pass the
more advanced regression tests.</li>
<li>for last few days I'm working on implementing expansions, I'll
<li>for last few days I am working on implementing expansions, I will
not rest until they work</li>
<li>I wasn't able to start writing manpages and create a megapatch
<li>I was not able to start writing manpages and create a megapatch
agains HEAD, I'll do that when the algorithm is 100% correct
for all the languages.</li>
</ul>
@ -259,10 +257,10 @@
<strong>Summary:</strong>
<p>The TCP Anomaly Detector (tcpad, for short) project went
reasonably well. I'm currently tracking some bugs and lowering
reasonably well. I am currently tracking some bugs and lowering
the number of false positives.</p>
<p>tcpad tries to monitor your TCP connections and detect
<p>tcpad tries to monitor TCP connections and detect
non-conformant hosts. It does this by sniffing packets on the
wire and creating, what I would like to call, a virtual TCP
stack on each end. When an error is detected, tcpad creates a
@ -279,8 +277,9 @@
knowledge has increased a few points. :-)</p>
<p>Andre Oppermann is my mentor. I blogged a bit about this
project at http://blogs.freebsdish.org/rpaulo/. The wiki page
is at http://wiki.freebsd.org/RuiPaulo/TCPAnomaly.</p>
project at <a href="http://blogs.freebsdish.org/rpaulo/">my blog</a>.
The wiki page is located <a
href="http://wiki.freebsd.org/RuiPaulo/TCPAnomaly">here</a>.</p>
<strong>Ready to enter CVS/SVN:</strong> No.
</li>
@ -296,7 +295,7 @@
part of the project consisted of writing a patch for
/dev/auditpipe in order to preselect events by process' pid. The
second half was focused on creating a testing framework for
audit. Some auxiliary functions and modules were written. what's
audit. Some auxiliary functions and modules were written. What is
missing: - More abstraction in the framework - More tests for
events</p>
</li>
@ -331,8 +330,8 @@
testing from more users to shake out any bugs or potential
workloads where the new code may hurt overall performance.</p>
<p>Current details about status are on the wiki here:
http://wiki.freebsd.org/DirhashDynamicMemory</p>
<p>Current details about status are on the <a
href="http://wiki.freebsd.org/DirhashDynamicMemory">wiki</a>.</p>
</li>
<li>
@ -443,14 +442,14 @@ Collection
<p>The license database (a list of them and their properties) was
going to be mirrored from FOSSology: a tool to analyze software
licenses. We're working on getting FOSSology to automatically
licenses. We are working on getting FOSSology to automatically
classify ports (I've sent suggestions and patches to the
developers, who accepted them and provided very good
support). So for the moment it's not usable (at least
support). So for the moment it is not usable (at least
licenses/properties are defined manually, and each port is
marked manually to indicate its license).</p>
<p>I'll continue working on the FOSSology's port, and on the
<p>I will continue working on the FOSSology's port, and on the
missing features such as multiple licenses support (AND, OR,
etc). For more information see the wiki page: Ports license
auditing infrastructure</p>
@ -477,8 +476,8 @@ Collection
<p>ipfw was extended to perform arp packet filtering: arp-op,
src-arp and dst-arp options added.</p>
<p>Details and usage examples are on my blog:
http://blogs.freebsdish.org/gleb/</p>
<p>Details and usage examples are on my
<a href="http://blogs.freebsdish.org/gleb/">blog</a>.</p>
<strong>Ready to enter CVS/SVN:</strong> Not yet, diff is submitted to freebsd-net@
for public review.