os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix a lot of grammatical/spelling errors. Thanks go to

Browse source 
keramida@, Chris Pepper <pepper@reppep.com>, and
Matthew Seaman <m.seaman@infracaninophile.co.uk> for reviewing.

Translators can ignore this.
This commit is contained in:
Hiroki Sato 2003-04-13 16:31:52 +00:00
parent 993c746a94
commit 1121e12ea1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=16555
24 changed files with 474 additions and 440 deletions
Download patch file Download diff file Expand all files Collapse all files

19
en/news/status/report-2001-06.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>June</month> <month>June</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-june-2001.xml,v 1.4 2001/09/18 12:22:07 chris Exp $ $FreeBSD: www/en/news/status/report-june-2001.xml,v 1.5 2001/09/18 17:48:22 chris Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -424,7 +426,7 @@
</contact> </contact>
<body> <body>
<p>In the last two months, the OLDCARD pccard implemenation was <p>In the last two months, the OLDCARD pccard implementation was
rototilled to within an inch of its life. Many new pci cardbus rototilled to within an inch of its life. Many new pci cardbus
bridges were added. Power handling was improved. PCI Card cardbus bridges were added. Power handling was improved. PCI Card cardbus
bridges are nearly supported and should be committed in early bridges are nearly supported and should be committed in early
@ -454,7 +456,7 @@
in pmap.c after a number of problems encountered where FreeBSD in pmap.c after a number of problems encountered where FreeBSD
passes a vm_page_t to a NetBSD-derived function that expects a passes a vm_page_t to a NetBSD-derived function that expects a
vm_offset_t. Then after debugging the atomic operations code, I'm vm_offset_t. Then after debugging the atomic operations code, I'm
now at the point where VM appears to be initialised and it's now now at the point where VM appears to be initialized and it's now
hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress
continues. =)</p> continues. =)</p>
</body> </body>
@ -549,7 +551,7 @@
from these files (which include, among other things, the release from these files (which include, among other things, the release
notes and the supported hardware list) have been reorganized and notes and the supported hardware list) have been reorganized and
converted to SGML. This helps us produce the documentation in converted to SGML. This helps us produce the documentation in
various formats, as well as facilitating the maintainence of various formats, as well as facilitating the maintenance of
documentation for multiple architectures. This work was recently documentation for multiple architectures. This work was recently
committed to -CURRENT, and I intend to MFC it to 4-STABLE before committed to -CURRENT, and I intend to MFC it to 4-STABLE before
4.4-RELEASE.</p> 4.4-RELEASE.</p>
@ -631,9 +633,9 @@
<body> <body>
<p>mb_alloc is a new specialized allocator for mbufs and mbuf <p>mb_alloc is a new specialized allocator for mbufs and mbuf
clusters. Presently, it offers various important advantages over clusters. Presently, it offers various important advantages over
the old (status quo) mbuf allocator, particularily for MP the old (status quo) mbuf allocator, particularly for MP
machines. Additionally, it is designed with the possibility of machines. Additionally, it is designed with the possibility of
future enchancements in mind.</p> future enhancements in mind.</p>
<p>Presently in initial review &amp; testing stages, most of the <p>Presently in initial review &amp; testing stages, most of the
code is already written.</p> code is already written.</p>
@ -713,11 +715,11 @@
Control (MAC), and other architecture features, including file Control (MAC), and other architecture features, including file
system extended attributes, and improved object labeling.</p> system extended attributes, and improved object labeling.</p>
<p>Individual feature status reports are documented seperately <p>Individual feature status reports are documented separately
below; in general, basic features (such as EAs, ACLs, and kernel below; in general, basic features (such as EAs, ACLs, and kernel
support for Capabilities) will be initially available in support for Capabilities) will be initially available in
5.0-RELEASE, conditional on specific kernel options. A 5.0-RELEASE, conditional on specific kernel options. A
performance-enhanced version of EAs is currently being targetted performance-enhanced version of EAs is currently being targeted
at 6.0-RELEASE, along with an integrated capability-aware at 6.0-RELEASE, along with an integrated capability-aware
userland, and MAC support.</p> userland, and MAC support.</p>
</body> </body>
@ -822,4 +824,3 @@
</body> </body>
</project> </project>
</report> </report>

51
en/news/status/report-2001-07.xml
View file

@ -1,4 +1,7 @@
<?xml version="1.0"?> <?xml version="1.0"?>
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>July</month> <month>July</month>
@ -8,7 +11,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.4 2001/09/18 17:48:22 chris Exp $ $FreeBSD: www/en/news/status/report-july-2001.xml,v 1.5 2002/05/16 01:49:58 trhodes Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -131,7 +134,7 @@
<li>User-level management interfaces.</li> <li>User-level management interfaces.</li>
<li>PCI power manangement.</li> <li>PCI power management.</li>
<li>Bug-hunting.</li> <li>Bug-hunting.</li>
</ul> </ul>
@ -241,9 +244,9 @@
systems. The format will be similar to other conferences, with 2 systems. The format will be similar to other conferences, with 2
days of technical sessions over the Saturday and Sunday.</p> days of technical sessions over the Saturday and Sunday.</p>
<p>We'll be finalising the schedule towards the end of the month <p>We'll be finalizing the schedule towards the end of the month
and anybody who is interested in doing a talk should contact us and anybody who is interested in doing a talk should contact us
asap. There are no restrictions on the use of talks, if it's been ASAP. There are no restrictions on the use of talks; if it's been
done before we may still be interested in having it presented to done before we may still be interested in having it presented to
an European audience, and we make no claims to the talks so an European audience, and we make no claims to the talks so
speakers are free to present the talks again at other speakers are free to present the talks again at other
@ -276,7 +279,7 @@
<body> <body>
<p>The new CAM transport code is starting to get supported in <p>The new CAM transport code is starting to get supported in
more HBAs and to get refined so that it does the intended more HBAs and to get refined so that it does the intended
per-protocol support. No progress on doing any SMPNG work for CAM per-protocol support. No progress on doing any SMPng work for CAM
has been made yet. This is a fairly high priority.</p> has been made yet. This is a fairly high priority.</p>
</body> </body>
</project> </project>
@ -440,7 +443,7 @@
<body> <body>
<p>jailNG is a from-scratch rewrite of the popular jail(8) <p>jailNG is a from-scratch rewrite of the popular jail(8)
service, focussing on improved management functions, as well as service, focusing on improved management functions, as well as
more fine-grained configurability. An initial prototype has been more fine-grained configurability. An initial prototype has been
written, based on explicitly named and configured jails, and work written, based on explicitly named and configured jails, and work
is proceeding on userland integration. Currently, it's not clear is proceeding on userland integration. Currently, it's not clear
@ -467,14 +470,14 @@
<p>The main development in the FreeBSD Java Project over the last <p>The main development in the FreeBSD Java Project over the last
month was the release of an initial "Developers Only" patchset month was the release of an initial "Developers Only" patchset
for the JDK 1.3.1. Since that release progress had been made for the JDK 1.3.1. Since that release progress had been made
towards a much more useable alpha quality patchset which is towards a much more usable alpha quality patchset which is
likely to be turned into a port, as per the current JDK 1.2.2 likely to be turned into a port, as per the current JDK 1.2.2
patchset. This new patchset will feature a number of bugfixes, patchset. This new patchset will feature a number of bugfixes,
which essentially get the JDK to a working state for early which essentially get the JDK to a working state for early
adopters, and an initial implementation of "native threads" based adopters, and an initial implementation of "native threads" based
on FreeBSD's userland pthreads. Unfortunately this implementation on FreeBSD's userland pthreads. Unfortunately this implementation
isn't fully functional, but is included in the hope of more isn't fully functional, but is included in the hope of
getting more eyesballs on the code (particularly experience getting more eyeballs on the code (particularly experienced
pthread programmers). We'd also like to welcome Fuyuhiko pthread programmers). We'd also like to welcome Fuyuhiko
Maruyama-san as a new committer, the usual punishment for too Maruyama-san as a new committer, the usual punishment for too
many good patches.</p> many good patches.</p>
@ -552,7 +555,7 @@
<p>I'm working on multithreading the kernel. So far I have over <p>I'm working on multithreading the kernel. So far I have over
400KB of diffs relative to todays -current (I'm keeping my tree 400KB of diffs relative to todays -current (I'm keeping my tree
updated with changes as they occur rather than get hit with a big updated with changes as they occur rather than get hit with a big
updte at the end).</p> update at the end).</p>
<p>I have split the proc structure and am changing most of the <p>I have split the proc structure and am changing most of the
kernel to pass around a thread identifier instead of a proc kernel to pass around a thread identifier instead of a proc
@ -561,7 +564,7 @@
<p>The following interfaces have been changed so far:</p> <p>The following interfaces have been changed so far:</p>
<ul> <ul>
<li>device devsw entrys</li> <li>device devsw entries</li>
<li>vfs calls</li> <li>vfs calls</li>
@ -571,7 +574,7 @@
<li>system calls</li> <li>system calls</li>
<li>sheduler</li> <li>scheduler</li>
<li>+ a lot of code in between.</li> <li>+ a lot of code in between.</li>
</ul> </ul>
@ -582,9 +585,9 @@
I'd like to check it in on a branch so others can help the I'd like to check it in on a branch so others can help the
editing but haven't worked out the best way to do it yet.</p> editing but haven't worked out the best way to do it yet.</p>
<p>I have implemented changes to the scheduler so that kse's are <p>I have implemented changes to the scheduler so that KSE's are
scheduled instead of processes, and threads sleep, letting the scheduled instead of processes, and threads sleep, letting the
kse pick up a new thread. but it's not anywhere ready yet (heck KSE pick up a new thread. but it's not anywhere ready yet (heck
it doesn't compile yet :-)</p> it doesn't compile yet :-)</p>
<p>Note that I have not yet updated the document listed above.. <p>Note that I have not yet updated the document listed above..
@ -653,7 +656,7 @@
process by porting Luke Mewburn's rc.d work from NetBSD to process by porting Luke Mewburn's rc.d work from NetBSD to
FreeBSD. This will score FreeBSD startup and shutdown FreeBSD. This will score FreeBSD startup and shutdown
dependencies without losing the traditional and much loved dependencies without losing the traditional and much loved
monolothic configuration filesystem.</p> monolithic configuration filesystem.</p>
<p>Luke Mewburn's USENIX paper and slides on the system as <p>Luke Mewburn's USENIX paper and slides on the system as
implemented in NetBSD are available here:</p> implemented in NetBSD are available here:</p>
@ -689,7 +692,7 @@
<body> <body>
<p>The goal of this project is the implementation of ATM <p>The goal of this project is the implementation of ATM
signalling and other ATM protocols by means of the netgraph(4) signalling and other ATM protocols by means of the netgraph(4)
framework. This should provide an easily extendable architecture framework. This should provide an easily extensible architecture
for using ATM on FreeBSD. Currently the full UNI4.0 stack (except for using ATM on FreeBSD. Currently the full UNI4.0 stack (except
for the LIJ capability) has been implemented, including ILMI and for the LIJ capability) has been implemented, including ILMI and
a first version of the ATM Forum API for UNI. An implementation a first version of the ATM Forum API for UNI. An implementation
@ -712,7 +715,7 @@
<body> <body>
<p>Network device cloning support has been imported from NetBSD. <p>Network device cloning support has been imported from NetBSD.
This allows virtual devices to be allocated on demand rather then This allows virtual devices to be allocated on demand rather then
being staticly allocated at compile time. Our implementation being statically allocated at compile time. Our implementation
differs slightly from that of NetBSD's in that we allow both the differs slightly from that of NetBSD's in that we allow both the
creation of specific devices (i.e. gif0) and arbitrary devices creation of specific devices (i.e. gif0) and arbitrary devices
instead of just allowing specific devices. Currently, the only instead of just allowing specific devices. Currently, the only
@ -872,7 +875,7 @@
<p>(First report)</p> <p>(First report)</p>
<p>Large cleanup and extension of FreeBSD PAM modules. All <p>Large cleanup and extension of FreeBSD PAM modules. All
modules are to be documented, consistant in style (style(9) used) modules are to be documented, consistent in style (style(9) used)
and as complete as possible WRT functionality. Mostly done.</p> and as complete as possible WRT functionality. Mostly done.</p>
</body> </body>
</project> </project>
@ -893,7 +896,7 @@
driver for OpenFirmware machines, along with support for the driver for OpenFirmware machines, along with support for the
Apple UniNorth PCI/AGP host bridge. I'm currently trying to get Apple UniNorth PCI/AGP host bridge. I'm currently trying to get
the USB hardware working so that I can get closer to having a the USB hardware working so that I can get closer to having a
console driver independant of OpenFirmware, then I'll be trying console driver independent of OpenFirmware, then I'll be trying
to get the system to get to single-user mode using NFS.</p> to get the system to get to single-user mode using NFS.</p>
</body> </body>
</project> </project>
@ -1032,7 +1035,7 @@
<h4>Management</h4> <h4>Management</h4>
<p>We are using a perforce repository for live development work, <p>We are using a perforce repository for live development work,
which can track multiple seperate long-lived works-in-progress which can track multiple separate long-lived works-in-progress
and collaborate between multiple developers at the same time on and collaborate between multiple developers at the same time on
the same change set.</p> the same change set.</p>
@ -1071,9 +1074,9 @@
<body> <body>
<p>mb_alloc is a specialized allocator for mbufs and mbuf <p>mb_alloc is a specialized allocator for mbufs and mbuf
clusters. It offers various important advantages over the old clusters. It offers various important advantages over the old
mbuf allocator, particularily for MP machines. Additionally, it mbuf allocator, particularly for MP machines. Additionally, it
is designed with the possibility of important future is designed with the possibility of important future
enchancements in mind.</p> enhancements in mind.</p>
<p>The mb_alloc code has been committed to -CURRENT a month ago <p>The mb_alloc code has been committed to -CURRENT a month ago
and appears to be holding up well. Prior to committing it, and appears to be holding up well. Prior to committing it,
@ -1141,7 +1144,7 @@
</project> </project>
<project> <project>
<title>SYN cache implemetation for FreeBSD</title> <title>SYN cache implementation for FreeBSD</title>
<contact> <contact>
<person> <person>
@ -1154,7 +1157,7 @@
<body> <body>
<p>This project brings a SYN cache implementation to FreeBSD, in <p>This project brings a SYN cache implementation to FreeBSD, in
order to make it more robust to DoS attacks. A SYN cookie order to make it more robust to DoS attacks. A SYN cookie
approach was considered, but ultimately rejected becuase it does approach was considered, but ultimately rejected because it does
not conform to the TCP protocol. The SYN cache will work with not conform to the TCP protocol. The SYN cache will work with
T/TCP, IPV6 and IPSEC, and the size of each cache element is T/TCP, IPV6 and IPSEC, and the size of each cache element is
currently is less than 1/5th the size of a normal TCP control currently is less than 1/5th the size of a normal TCP control

35
en/news/status/report-2001-08.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>August</month> <month>August</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD$ $FreeBSD: www/en/news/status/report-august-2001.xml,v 1.4 2001/09/18 19:39:41 chris Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -135,7 +137,7 @@
<body> <body>
<p>No change since last status. Some discussion amongst all of us <p>No change since last status. Some discussion amongst all of us
occurred, but lack of time and commitment to FreeBSD has meant occurred, but lack of time and commitment to FreeBSD has meant
little has actually been committed to the tree. SMPNG work will little has actually been committed to the tree. SMPng work will
be left to those who seem to have a notion about what needs to be be left to those who seem to have a notion about what needs to be
done.</p> done.</p>
</body> </body>
@ -209,10 +211,10 @@
thread to be created. (nor have new threading syscalls been added thread to be created. (nor have new threading syscalls been added
yet). This is an important milestone as it represents the last yet). This is an important milestone as it represents the last
point where the kernel has only "mechanical" changes. To go point where the kernel has only "mechanical" changes. To go
further we must start adding new algorythms and functions.</p> further we must start adding new algorithms and functions.</p>
<p>The kernel for milestone 2 is reliable and has no noticable <p>The kernel for milestone 2 is reliable and has no noticeable
performance degradations when compared to a matchung -current performance degradations when compared to a matching -current
kernel. (the differences are less than the margin of error, so kernel. (the differences are less than the margin of error, so
that sometimes the new kernel actually fractionally beats the that sometimes the new kernel actually fractionally beats the
unaltered kernel).</p> unaltered kernel).</p>
@ -534,7 +536,7 @@
</project> </project>
<project> <project>
<title>SYN cache implemetation for FreeBSD</title> <title>SYN cache implementation for FreeBSD</title>
<contact> <contact>
<person> <person>
@ -645,7 +647,7 @@
<p>Benefits of approach include the fact that a kqueue filter can <p>Benefits of approach include the fact that a kqueue filter can
be attached to a network device for monitoring purposes. Initial be attached to a network device for monitoring purposes. Initial
code exists to send a kq event whever the network link status code exists to send a kq event whenever the network link status
changes. Other benefits may include better access control by changes. Other benefits may include better access control by
using filesystem ACLs to control access to the device.</p> using filesystem ACLs to control access to the device.</p>
</body> </body>
@ -733,7 +735,7 @@
making some excellent progress. Of note, some problems with the making some excellent progress. Of note, some problems with the
way the pmap module implements copy-on-write mappings have been way the pmap module implements copy-on-write mappings have been
fixed and fork() now works as expected, support for signals has fixed and fork() now works as expected, support for signals has
been added, and the port has been updated for kse in the perforce been added, and the port has been updated for KSE in the perforce
repository. Thomas Moestl has begun work on pci bus support, and repository. Thomas Moestl has begun work on pci bus support, and
a basic nexus bus for sparc64 has been written. The driver for a basic nexus bus for sparc64 has been written. The driver for
the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated
@ -958,7 +960,7 @@
<body> <body>
<p>Support for cloning vlan devices via ifconfig has been <p>Support for cloning vlan devices via ifconfig has been
committed to -current and will be MFC'd after further testing. committed to -current and will be MFC'd after further testing.
Additionaly, Maksim Yevmenkin submitted code to allow cloning of Additionally, Maksim Yevmenkin submitted code to allow cloning of
tap and vmnet devices on devfs systems. Code for faith and stf tap and vmnet devices on devfs systems. Code for faith and stf
should be committed shortly.</p> should be committed shortly.</p>
</body> </body>
@ -1058,7 +1060,7 @@
allowed to make this 97-component meta-package building and allowed to make this 97-component meta-package building and
working properly.</p> working properly.</p>
<p>Next month the project will be focused on organising work of <p>Next month the project will be focused on organizing work of
the FreeBSD GNOME Team as well as on attempts to increase amount the FreeBSD GNOME Team as well as on attempts to increase amount
of people participating in the team (anybody who is willing to of people participating in the team (anybody who is willing to
participate is welcome to drop a note to gnome@FreeBSD with a participate is welcome to drop a note to gnome@FreeBSD with a
@ -1100,7 +1102,7 @@
combination of binary object files and source (under a combination of binary object files and source (under a
constrictive license). The FreeBSD NVIDIA driver project aimed to constrictive license). The FreeBSD NVIDIA driver project aimed to
completely replace the source component of the driver using code completely replace the source component of the driver using code
targetting FreeBSD 4.3 and released under the BSD license. The targeting FreeBSD 4.3 and released under the BSD license. The
binary module provided is supposedly the same module used on binary module provided is supposedly the same module used on
Windows, BeOS, and OS/2, so it should be portable between Windows, BeOS, and OS/2, so it should be portable between
different i80x86 based OS's.</p> different i80x86 based OS's.</p>
@ -1109,16 +1111,16 @@
NVIDIA seemed enthusiastic about the project, and was fairly NVIDIA seemed enthusiastic about the project, and was fairly
quick about returning email, but when we discovered issues that quick about returning email, but when we discovered issues that
prevented porting without changes to the binary component or prevented porting without changes to the binary component or
error codes we needed decyphered, Nick (the contact) said he'd error codes we needed deciphered, Nick (the contact) said he'd
look into it and never got back. The first major problem was the look into it and never got back. The first major problem was the
ioctl interface, the nvidia driver passes a pointer and depends ioctl interface, the NVIDIA driver passes a pointer and depends
on the kernel side to copyout the right amount, where FreeBSD on the kernel side to copyout the right amount, where FreeBSD
expect the parameters to be correct and the copyout is performed expect the parameters to be correct and the copyout is performed
by the subsystem. This was worked around using Dave Rufinos by the subsystem. This was worked around using Dave Rufinos
"ioctl tunnel" idea. After that, we found that X refused to load "ioctl tunnel" idea. After that, we found that X refused to load
and traced it down to an ioctl defined in the binary component and traced it down to an ioctl defined in the binary component
erroring. We cannot tell what that ioctl is, were told that we erroring. We cannot tell what that ioctl is, were told that we
could not sign an nda for source to that component, and have been could not sign an NDA for source to that component, and have been
waiting a month for Nick to "look into it". Therefore progress is waiting a month for Nick to "look into it". Therefore progress is
impossible (without breaking the license) and we believe that the impossible (without breaking the license) and we believe that the
flaws make the driver unportable to any *nix other than flaws make the driver unportable to any *nix other than
@ -1316,7 +1318,7 @@
naturally resulted in a number of bugs being found. Development naturally resulted in a number of bugs being found. Development
work has mostly focused on fixing these problems and the project work has mostly focused on fixing these problems and the project
is now set to release fourth patchset over the weekend, which is now set to release fourth patchset over the weekend, which
should see the JDK in a reasonable useable state. One of the big should see the JDK in a reasonably usable state. One of the big
challenges left is producing a working HotSpot JVM, which looks challenges left is producing a working HotSpot JVM, which looks
like it will require some heavy hacking.</p> like it will require some heavy hacking.</p>
@ -1475,7 +1477,7 @@
</contact> </contact>
<body> <body>
<p>Capabilities support is currently being comitted to the base <p>Capabilities support is currently being committed to the base
FreeBSD tree--userland libraries are now fully committed, and FreeBSD tree--userland libraries are now fully committed, and
kernel infrastructure is being integrated.</p> kernel infrastructure is being integrated.</p>
</body> </body>
@ -1515,4 +1517,3 @@
</body> </body>
</project> </project>
</report> </report>

24
en/news/status/report-2001-09.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>September</month> <month>September</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS"
version="1.0"> version="1.0">
<cvs:keyword name="freebsd">$FreeBSD$</cvs:keyword> <cvs:keyword name="freebsd">$FreeBSD: www/en/news/status/report-september-2001.xml,v 1.1 2001/11/12 22:25:12 chris Exp $</cvs:keyword>
</cvs:keywords> </cvs:keywords>
<section> <section>
@ -132,7 +134,7 @@
updating my snapshot site at the URL above, at least for a little updating my snapshot site at the URL above, at least for a little
while.</p> while.</p>
<p>Call for help: The hardware compatability lists need to be <p>Call for help: The hardware compatibility lists need to be
updated in the areas of the Alpha architecture, USB devices, and updated in the areas of the Alpha architecture, USB devices, and
PCCARD devices. I'm looking for volunteers to help; interested PCCARD devices. I'm looking for volunteers to help; interested
parties should contact me at the email address above. DocBook parties should contact me at the email address above. DocBook
@ -208,7 +210,7 @@
<body> <body>
<p>As you know, in march 2001 the version 2.3 of TIRPC has been <p>As you know, in march 2001 the version 2.3 of TIRPC has been
comitted together with many userland changes. Alfred Perlstein committed together with many userland changes. Alfred Perlstein
and Ian Dowse have helped me a lot with the porting effort and if and Ian Dowse have helped me a lot with the porting effort and if
I had problems with understanding the code.</p> I had problems with understanding the code.</p>
@ -385,7 +387,7 @@
finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro
support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv
changes on Japanese manpages. He also find some issues of these changes on Japanese manpages. He also find some issues of these
macro usage on some original manapges and filed a PR. For macro usage on some original manpages and filed a PR. For
post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is
also in progress.</p> also in progress.</p>
</body> </body>
@ -463,7 +465,7 @@
system can now be successfully mounted from ATA disks on sparc64, system can now be successfully mounted from ATA disks on sparc64,
even in DMA mode. The gem driver, which supports Sun GEM and ERI even in DMA mode. The gem driver, which supports Sun GEM and ERI
and Apple GMAC and GMAC2 ethernet adaptor, has been ported from and Apple GMAC and GMAC2 ethernet adaptor, has been ported from
NetBSD but has not yet had sufficent testing.</p> NetBSD but has not yet had sufficient testing.</p>
</body> </body>
</project> </project>
@ -664,7 +666,7 @@
</links> </links>
<body> <body>
<p>In the last month, not a lot has happenned other than settling <p>In the last month, not a lot has happened other than settling
in of the big August commit. Largely due to me having a sudden in of the big August commit. Largely due to me having a sudden
increased workload at work, and a need for increased time to be increased workload at work, and a need for increased time to be
spent elsewhere. However some design work has proceeded. The API spent elsewhere. However some design work has proceeded. The API
@ -675,12 +677,12 @@
<p>Milestone 3 will be to have the ability to generate and remove <p>Milestone 3 will be to have the ability to generate and remove
multiple threads/KSEs per process. Milestone 3 will NOT require multiple threads/KSEs per process. Milestone 3 will NOT require
that doing so will be safe. (especially in SMP systems), i.e. that doing so will be safe. (especially in SMP systems), i.e.
locking issues will not be fully addressed, so while some testign locking issues will not be fully addressed, so while some testing
will be possible, it will not be possible to actually run in this will be possible, it will not be possible to actually run in this
mode with any load.</p> mode with any load.</p>
<p>This will require allocators and destructors for the new <p>This will require allocators and destructors for the new
structures. Creation of the syscalls. Generation of an acurate structures. Creation of the syscalls. Generation of an accurate
written API for the userland crew. Writing of the upcall launch written API for the userland crew. Writing of the upcall launch
code. Production of a userland test program (not a full thread code. Production of a userland test program (not a full thread
scheduler). Resolution of some of the more glaring scheduler). Resolution of some of the more glaring
@ -689,10 +691,10 @@
system it should behave the same as now (and be as system it should behave the same as now (and be as
reliable)).</p> reliable)).</p>
<p>Criterea for knowing when we have reached Milestione 3 is the <p>Criteria for knowing when we have reached Milestone 3 is the
ability for a simple process on an unloaded system to perform a ability for a simple process on an unloaded system to perform a
series of blocking syscalls reliably. e.g. open 2 sockets, and series of blocking syscalls reliably. e.g. open 2 sockets, and
send data on one, after having done a read on another,and then send data on one, after having done a read on another, and then
'respond' in like manner..</p> 'respond' in like manner..</p>
</body> </body>
</project> </project>
@ -751,7 +753,7 @@
reasonably confident that the latest patchset is a stable release reasonably confident that the latest patchset is a stable release
of the core JDK 1.3.1 tools and classes, when the default "green" of the core JDK 1.3.1 tools and classes, when the default "green"
threads subsystem is used. This is mostly thanks to hard work by threads subsystem is used. This is mostly thanks to hard work by
Fuyuhiko Maruyama to stabilise and fix the code. Bill Huey has Fuyuhiko Maruyama to stabilize and fix the code. Bill Huey has
also been progressing with his work on the "native" threads also been progressing with his work on the "native" threads
subsystem, although this hasn't yet reached the stability of subsystem, although this hasn't yet reached the stability of
"green" threads. Another (arguably the) major highlight of the "green" threads. Another (arguably the) major highlight of the

17
en/news/status/report-2001-11.xml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD$ --> <!-- $FreeBSD: www/en/news/status/report-november-2001.xml,v 1.1 2001/12/22 01:01:27 chris Exp $ -->
<report> <report>
<date> <date>
@ -183,7 +183,7 @@
<tt>pam_self(8)</tt> <tt>pam_self(8)</tt>
, has been written; and preparations have been made for , has been written; and preparations have been made for
transitioning from the transition from
<tt>/etc/pam.conf</tt> <tt>/etc/pam.conf</tt>
to to
@ -404,7 +404,7 @@
<body> <body>
<p>Support for VLAN cloning has been merged from current and will <p>Support for VLAN cloning has been merged from current and will
ship with 4.5-RELEASE. Additionaly, new rc.conf support for ship with 4.5-RELEASE. Additionally, new rc.conf support for
cloning interfaces at boot has been MFD'd. Work is ongoing to MFC cloning interfaces at boot has been MFD'd. Work is ongoing to MFC
stf and faith cloning as well as adding cloning for ppp devices stf and faith cloning as well as adding cloning for ppp devices
and enhancing VLAN modularity.</p> and enhancing VLAN modularity.</p>
@ -732,7 +732,7 @@
<p>Although not strictly ATA, Promise has equipped me with a <p>Although not strictly ATA, Promise has equipped me with a
couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks
and does RAID0-5 in hardware. I have done a driver (its an I2O and does RAID0-5 in hardware. I have done a driver (its an I2O
device) for both -current and -stable and it works butifully with device) for both -current and -stable and it works beautifully with
hotswap the works. It will enter the tree when it is more mature, hotswap the works. It will enter the tree when it is more mature,
and I have an agreement with Promise on how we handle userland and I have an agreement with Promise on how we handle userland
control util etc. BTW it seems it can also be used as a normal 6 control util etc. BTW it seems it can also be used as a normal 6
@ -826,7 +826,7 @@
<name> <name>
<given>Doug Barton</given> <given>Doug Barton</given>
<common>Commiter</common> <common>Committer</common>
</name> </name>
<email>DougB@FreeBSD.org</email> <email>DougB@FreeBSD.org</email>
@ -899,7 +899,7 @@
<p>I have been working behind the scenes on design rather than <p>I have been working behind the scenes on design rather than
programming for this last month. I have been working however in programming for this last month. I have been working however in
the p4 tree to make the system run with the thread structure NOT the p4 tree to make the system run with the thread structure NOT
a part of the proc structure (a prerequisite fo threading)</p> a part of the proc structure (a prerequisite for threading)</p>
</body> </body>
</project> </project>
@ -953,7 +953,7 @@
</links> </links>
<body> <body>
<p>The TrustedBSD Project continued focussing development efforts <p>The TrustedBSD Project continued focusing development efforts
on fine-grained Capabilities and Mandatory Access Control this on fine-grained Capabilities and Mandatory Access Control this
month. Kernel support for capabilities is essentially complete, month. Kernel support for capabilities is essentially complete,
and efforts are underway to adapt userland applications to use and efforts are underway to adapt userland applications to use
@ -964,7 +964,7 @@
integration into the network stack. Both development trees have integration into the network stack. Both development trees have
been updated to work with recent KSE-related developments, as been updated to work with recent KSE-related developments, as
well as exist more happily in a fine-grained SMP kernel. Initial well as exist more happily in a fine-grained SMP kernel. Initial
audit-related work appears in a seperate entry.</p> audit-related work appears in a separate entry.</p>
<p>Development of TrustedBSD source code was moved to the FreeBSD <p>Development of TrustedBSD source code was moved to the FreeBSD
Perforce repository, permitting better source code management. As Perforce repository, permitting better source code management. As
@ -1023,4 +1023,3 @@
</body> </body>
</project> </project>
</report> </report>

14
en/news/status/report-2001-12-2002-01.xml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.3 2002/03/02 04:49:31 mike Exp $ --> <!-- $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.4 2002/03/09 07:06:48 dd Exp $ -->
<report> <report>
<date> <date>
@ -9,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.3 2002/03/02 04:49:31 mike Exp $ $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.4 2002/03/09 07:06:48 dd Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -266,14 +266,14 @@
<p>The KSE project (an attempt to support scalable thread in <p>The KSE project (an attempt to support scalable thread in
FreeBSD using kernel support), has reached What I call "milestone FreeBSD using kernel support), has reached What I call "milestone
3". At this milestone it is possible to run a multithreaded 3". At this milestone it is possible to run a multithreaded
program on a single CPU but with full concurrancy of threads on program on a single CPU but with full concurrency of threads on
that CPU. In other words the kernel supports the fact that one that CPU. In other words the kernel supports the fact that one
thread can block by allowing another thread to run in its place. thread can block by allowing another thread to run in its place.
A test program that demonstrates this is available at the above A test program that demonstrates this is available at the above
website.</p> website.</p>
<p>Milestone 4 will be to allow threads from the same program to <p>Milestone 4 will be to allow threads from the same program to
run on multiple CPUS but may require more input from the SMPNG run on multiple CPUs but may require more input from the SMPng
project. I am at the moment (Feb 6) getting ready to commit a project. I am at the moment (Feb 6) getting ready to commit a
first set of changes for milestone 3, that have no real effect first set of changes for milestone 3, that have no real effect
but serve to drastically reduce the complexity of the remaining but serve to drastically reduce the complexity of the remaining
@ -315,7 +315,7 @@
allows one to use ATM PVCs. It should be possible, for example, allows one to use ATM PVCs. It should be possible, for example,
to do PPP over ATM with this package. Both bsnmp and ngatmbase to do PPP over ATM with this package. Both bsnmp and ngatmbase
are available in version 1.0 under the link above. Two other are available in version 1.0 under the link above. Two other
modules will be released in february: ngatmsig containing the modules will be released in February: ngatmsig containing the
UNI-4.0 signalling stack as netgraph nodes and ngatmip containing UNI-4.0 signalling stack as netgraph nodes and ngatmip containing
CLIP and LANE-2.0.</p> CLIP and LANE-2.0.</p>
</body> </body>
@ -699,8 +699,8 @@
</links> </links>
<body> <body>
<p>Alfred Perlstein commited file descriptor locking code <p>Alfred Perlstein committed file descriptor locking code
which was definetly a good push towards trying to lock down which was definitely a good push towards trying to lock down
some important pieces of global data. Peter Wemm has made some important pieces of global data. Peter Wemm has made
progress on pmap cleanups for x86 SMP TLB shootdowns. Matt progress on pmap cleanups for x86 SMP TLB shootdowns. Matt
Dillon and John Baldwin have made progress on getting patches Dillon and John Baldwin have made progress on getting patches

30
en/news/status/report-2002-02-2002-04.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>February - April</month> <month>February - April</month>
@ -75,9 +77,9 @@
</contact> </contact>
<body> <body>
<p>FreeBSD's new kernel memory allocator has been commited to <p>FreeBSD's new kernel memory allocator has been committed to
5.0. UMA is a slabs derived allocator that supports memory 5.0. UMA is a slabs derived allocator that supports memory
reclaiming, object caching, type stable storage, and per cpu reclaiming, object caching, type stable storage, and per CPU
free lists for optimal SMP performance. It has both a free lists for optimal SMP performance. It has both a
malloc(9) interface and a zone style interface for specific malloc(9) interface and a zone style interface for specific
object types. uma(9) will be available shortly.</p> object types. uma(9) will be available shortly.</p>
@ -225,8 +227,8 @@
printf(1) utility was brought up to conformance with the 1992 printf(1) utility was brought up to conformance with the 1992
edition of POSIX.2, with further development planned.</p> edition of POSIX.2, with further development planned.</p>
<p>On the header front, much progress has been made. Specically, <p>On the header front, much progress has been made. Specifically,
infrastructure to control visiblity of components of a header, based infrastructure to control visibility of components of a header, based
on the standard requested by an application, has been added to on the standard requested by an application, has been added to
&lt;sys/cdefs.h&gt;. Some work has been completed on renovating the &lt;sys/cdefs.h&gt;. Some work has been completed on renovating the
way types are defined. This has lead to the creation of way types are defined. This has lead to the creation of
@ -317,7 +319,7 @@
<p>Not to be left out, the existing GNOME 1.4 components have received <p>Not to be left out, the existing GNOME 1.4 components have received
numerous updates to keep them in sync with the stable distfiles numerous updates to keep them in sync with the stable distfiles
on gnome.org. We have seen many "1.0" milsestone releases including on gnome.org. We have seen many "1.0" milestone releases including
the most recent AbiWord 1.0.0. In the next few weeks, we will be the most recent AbiWord 1.0.0. In the next few weeks, we will be
making sure all the GNOME 1.4 components build correct packages making sure all the GNOME 1.4 components build correct packages
on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p> on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p>
@ -347,7 +349,7 @@
<p> FreeBSD/KGI started last year after the port of GGI to VGL. <p> FreeBSD/KGI started last year after the port of GGI to VGL.
KGI (Kernel Graphic Interface) is a kernel infrastructure providing user KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
applications with access to hardware graphic resources (dma, applications with access to hardware graphic resources (dma,
irqs, mmio). KGI is already available under Linux as a seperate irqs, mmio). KGI is already available under Linux as a separate
project. The FreeBSD/KGI project aims at integrating KGI project. The FreeBSD/KGI project aims at integrating KGI
in the FreeBSD kernel. Mostly a port for now, but optimized for in the FreeBSD kernel. Mostly a port for now, but optimized for
FreeBSD in the future. Currently FreeBSD/KGI is under development FreeBSD in the future. Currently FreeBSD/KGI is under development
@ -396,9 +398,9 @@
<body> <body>
<p>We now have a loadable mfsroot floppy. It contains just the <p>We now have a loadable mfsroot floppy. It contains just the
diskeditor (which is really a disk partitioner) which has been diskeditor (which is really a disk partitioner) which has been
enhanced and is probably in his final form. It's been geared enhanced and is probably in its final form. It's been geared
towards making the newfs(1) and mount(1) step seperate dialogs, so towards making the newfs(1) and mount(1) steps separate dialogs, so
it reduced its complexity. A basic fstab class has been it reduceed its complexity. A basic fstab class has been
implemented to manipulate /etc/fstab and mountpoint. This might implemented to manipulate /etc/fstab and mountpoint. This might
find a use outside libh, by the way. Libh package format is still find a use outside libh, by the way. Libh package format is still
incomplete and somehow buggy, so it's my next target.</p> incomplete and somehow buggy, so it's my next target.</p>
@ -438,7 +440,7 @@
separated into kernel part and userland part, yet another snapshots separated into kernel part and userland part, yet another snapshots
from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several
packages including XFree86 4.x to installation CD-ROM, new packages including XFree86 4.x to installation CD-ROM, new
cdboot-only ISO image, fix breackage of duplex.iso, etc. See also cdboot-only ISO image, fix breakage of duplex.iso, etc. See also
the project webpage for more detail. Also, I have a plan to add the project webpage for more detail. Also, I have a plan to add
FreeBSD/alpha distribution to this project -- stay tuned.</p> FreeBSD/alpha distribution to this project -- stay tuned.</p>
</body> </body>
@ -865,7 +867,7 @@ messages.</url>
</links> </links>
<body> <body>
<p>4.5-RELEASE Japanese manapge package, ja-man-doc-4.5.tgz, once <p>4.5-RELEASE Japanese manpage package, ja-man-doc-4.5.tgz, once
published with OpenSSH 2.3 (as reported by previous status published with OpenSSH 2.3 (as reported by previous status
report) on January 31, is replaced with new package with OpenSSH report) on January 31, is replaced with new package with OpenSSH
2.9 based manpages on March 3. Since then, we have been 2.9 based manpages on March 3. Since then, we have been
@ -898,7 +900,7 @@ messages.</url>
<body> <body>
<p>The GEOM code has gotten so far that it beats our current code <p>The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. Work continues on in some areas while still lacking in others. Work continues on
a generalized interface for "magic data" (boot blocks, disklabels a generalized interface for "magic data" (boot blocks, disklabels
MBR's etc) manipulation from userland.</p> MBR's etc) manipulation from userland.</p>
<p>With GEOM enabled in the kernel any FreeBSD platform will now <p>With GEOM enabled in the kernel any FreeBSD platform will now
@ -985,7 +987,7 @@ messages.</url>
In current the API has changed to move unit allocation into the In current the API has changed to move unit allocation into the
generic cloning code reducing the amount of support code required generic cloning code reducing the amount of support code required
in each driver. Code improvements to increase our API in each driver. Code improvements to increase our API
compatability with NetBSD will be commited soon along with cloning compatibility with NetBSD will be committed soon along with cloning
support for discard interfaces and ppp(4) interfaces.</p> support for discard interfaces and ppp(4) interfaces.</p>
<p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support <p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support
and unit allocation cleanups.</p> and unit allocation cleanups.</p>
@ -1282,7 +1284,7 @@ messages.</url>
40 developers attended in person, another five by phone, and many 40 developers attended in person, another five by phone, and many
others by webcast. During a marathon-esque eight hour session, a others by webcast. During a marathon-esque eight hour session, a
variety of development topics were discussed, including adding variety of development topics were discussed, including adding
inheritence to the KOBJ system, ports to new architectures, inheritance to the KOBJ system, ports to new architectures,
adaptations of the toolchain for new architectures, the GEOM adaptations of the toolchain for new architectures, the GEOM
extensible storage device framework, upcoming changes to the network extensible storage device framework, upcoming changes to the network
stack, TrustedBSD features, KSE, SMPng, and the release engineering stack, TrustedBSD features, KSE, SMPng, and the release engineering

195
en/news/status/report-2002-05-2002-06.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>May - June</month> <month>May - June</month>
@ -82,13 +84,13 @@
than 256 bytes) (A full Internet view of 110k routes takes 33 MByte than 256 bytes) (A full Internet view of 110k routes takes 33 MByte
of KVM). Another problem are pointers from and to everywhere of KVM). Another problem are pointers from and to everywhere
in the routing table. This makes replacing the table very hard and in the routing table. This makes replacing the table very hard and
also significantly highers the table maintainance burden (for example also significantly increases the table maintenance burden (for example
for some kinds of updates the entire PCB has be searched lineary). for some kinds of updates the entire PCB has to be searched linearly).
Also this is a heavy burden for SMP locking. The rewrite focuses on Also this is a heavy burden for SMP locking. The rewrite focuses on
untangeling the pointer mess, making the routing table replaceable untangling the pointer mess, making the routing table replaceable
and providing a more IP optimized table (5 MByte for 110k routes). and providing a more IP optimized table (5 MByte for 110k routes).
Other new options include policy routing and some structual alignments Other new options include policy routing and some structural alignments
in the network stack for clarity, cleaness and flexibilty.</p> in the network stack for clarity, simplicity and flexibility.</p>
<p>The rewritten IP routing table will be ready for committing in <p>The rewritten IP routing table will be ready for committing in
October.</p> October.</p>
</body> </body>
@ -123,10 +125,10 @@ Graf</url>
user structure in Switzerland. The nice thing about Switzerland user structure in Switzerland. The nice thing about Switzerland
is that is has a very good mix of Modem/ISDN, leased line, Cable, is that is has a very good mix of Modem/ISDN, leased line, Cable,
ADSL and 3G/GSM/GPRS users. Every Internet access technology is ADSL and 3G/GSM/GPRS users. Every Internet access technology is
represented. The goal is to analyse the behaviour of all TCP represented. The goal is to analyze the behavior of all TCP
sessions to the monitored sites. Parameters to be analysed include sessions to the monitored sites. Parameters to be analyzed include
TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow
control behaviour, packet loss, packet loss, packet retransmit and control behavior, packet loss, packet retransmit and
timing of HTTP traffic to find optimal TCP parameter caching timing of HTTP traffic to find optimal TCP parameter caching
method.</p> method.</p>
<p>If you have any other metrics you think is useful please contact <p>If you have any other metrics you think is useful please contact
@ -194,81 +196,80 @@ September.</p>
as Marcel Moolenaar's prototype EFI GPT tools.</p> as Marcel Moolenaar's prototype EFI GPT tools.</p>
</body> </body>
</project> </project>
<!-- $FreeBSD: www/en/news/status/report-may-2002-june-2002.xml,v 1.3 2002/08/14 18:45:04 rwatson Exp $ -->
<project>
<project> <title>Libh Status Report</title>
<title>Libh Status Report</title>
<contact>
<contact> <person>
<person> <name>
<name> <given>Antoine</given>
<given>Antoine</given>
<common>Beaupre</common>
<common>Beaupre</common> </name>
</name>
<email>antoine@usw4.freebsd.org</email>
<email>antoine@usw4.freebsd.org</email> </person>
</person> </contact>
</contact>
<contact>
<contact> <person>
<person> <name>
<name> <given>Alexander</given>
<given>Alexander</given>
<common>Langer</common>
<common>Langer</common> </name>
</name>
<email>alex@freebsd.org</email>
<email>alex@freebsd.org</email> </person>
</person> </contact>
</contact>
<contact>
<contact> <person>
<person> <name>
<name> <given>Nathan</given>
<given>Nathan</given>
<common>Ahlstrom</common>
<common>Ahlstrom</common> </name>
</name>
<email>nra@freebsd.org</email>
<email>nra@freebsd.org</email> </person>
</person> </contact>
</contact>
<links>
<links> <url href="http://www.freebsd.org/projects/libh.html" />
<url href="http://www.freebsd.org/projects/libh.html" /> <url href="http://usw4.freebsd.org/~libh/">libh
<url href="http://usw4.freebsd.org/~libh/">libh new development web page.</url>
new development web page.</url> <url href="http://usw4.freebsd.org/~libh/screenshots">
<url href="http://usw4.freebsd.org/~libh/screenshots"> First snapshots of the diskeditor in action</url>
First snapshots of the diskeditor in action</url> </links>
</links>
<body>
<body> <p>Max has been busy cleaning up the user interface dark side, and has
<p>Max has been busy cleaning up the user interface dark side, and has come up with a plan to improve the build system (using an automated
come up with a plan to improve the build system (using an automated Makefile dependency generator); the UI design and the TCL glue magic
Makefile dependency generator); the UI design and the TCL glue magic (using Swig). A development page has been created on usw4, publishing
(using Swig). A develepment page has been created on usw4, publishing a lot of information about the current project status, a Changelog,
a lot of information about the current project status, a Changelog, screenshots, documentation, etc. A new listbox widget has been
screenshots, documentation, etc. A new listbox widget has been implemented, making diskeditor look nicer and more usable. The package
implemented, making diskeditor look nicer and more useable. The package system backend is being inspected and redesigned to conform to a standard
system backend is being inspected and redesigned to conform to a standard that is itself being re-thought. Indeed, the old sysinstall2.txt text has
that is itself being re-thought. Indeed, the old sysinstall2.txt text has been SGML-ized and enhanced and now provides a good (although rough) overview
been SGML-ized and enhanced and now provides a good (altough rough) overview of libh package system. This allowed the document to be enhanced with diagrams
of libh package system. This allowed the document to be enhanced with diagrams of how different procedures work. We are therefore getting closer to a
of how different procedures work. We are therefore getting closer to a real pkgAPI specification document. The package management tools have been
real pkgAPI specification document. The package management tools have been slightly enhanced and should be a bit more usable, and we started committing
sligthly enhanced and should be a bit more useable, and we started commiting regression test suites in the tree, mostly to test and maintain pkg API
regression test suites in the tree, mostly to test and maintain pkg API conformance.</p>
conformance.</p>
<p>So work continues on libh. I plan to take a look at the rhtvision port
<p>So work continues on libh. I plan to take a look at the rhtvision port to see if it would be better to use it for the tvision backend. I'll keep
to see if it would be better to use it for the tvision backend. I'll keep on working on the package system to make it really trustworthy, while Max
on working on the package system to make it really trustworthy, while Max is continuing his great work on the UI subsystem. I hope to make a new libh
is continuing his great work on the UI subsystem. I hope to make a new libh alpha release soon. Note that from now on, libh progress will be published
alpha release soon. Note that from now on, libh progress will be published on the development page.</p>
on the development page.</p> </body>
</body> </project>
</project>
<project> <project>
<title>OLDCARD</title> <title>OLDCARD</title>
@ -340,7 +341,7 @@ as it is stable.</p>
probe. The ata driver won't attach. The sio driver hangs on the probe. The ata driver won't attach. The sio driver hangs on the
first character. The wi driver is known to work well. Cardbus cards first character. The wi driver is known to work well. Cardbus cards
are generally known to work well, except for some de based cards, are generally known to work well, except for some de based cards,
which unfortuntely includes the popular Xircom cards. Many systems which unfortunately includes the popular Xircom cards. Many systems
fail to work because acpi fails to route interrupts correctly for fail to work because acpi fails to route interrupts correctly for
non-root pci bridges.</p> non-root pci bridges.</p>
</body> </body>
@ -703,14 +704,14 @@ includes porting this facility to the -current tree.</p>
requirements for full thread-control, suspension etc. that requirements for full thread-control, suspension etc. that
will be required later. </p> will be required later. </p>
<p> <p>
Before M-IV is started some small tweeking is likely Before M-IV is started some small tweaking is likely
in the central sources on M-III as we discover issues in the central sources on M-III as we discover issues
as we try to get the userland jumpstarted. These will have no as we try to get the userland jumpstarted. These will have no
effect on non-KSE processes, (i.e. all of them :-) and effect on non-KSE processes, (i.e. all of them :-) and
should not be an issue for other developers. </p> should not be an issue for other developers. </p>
<p> <p>
A tex/fig->html guru is needed to help maintain the A tex/fig->html guru is needed to help maintain the
KSE web page (not mentionned above as it is broken). KSE web page (not mentioned above as it is broken).
</p> </p>
</body> </body>
</project> </project>
@ -872,7 +873,7 @@ includes porting this facility to the -current tree.</p>
<p>Progression is slow, but the effort is maintained. Most of fb over KGI has been <p>Progression is slow, but the effort is maintained. Most of fb over KGI has been
written in parallel with a KGI display driver based on fb. written in parallel with a KGI display driver based on fb.
DDC/DDC2 is being discussed for Plug &amp; Play monitor support. KGI aims at providing DDC/DDC2 is being discussed for Plug &amp; Play monitor support. KGI aims at providing
a generic OS independant interface which would take advantage of FreeBSD I2C (iic(4)) a generic OS independent interface which would take advantage of FreeBSD I2C (iic(4))
infrastructure. infrastructure.
</p> </p>
@ -940,7 +941,7 @@ includes porting this facility to the -current tree.</p>
<body> <body>
<p> <p>
The GEOM code has gotten so far that it beats our current code The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. The goal is for in some areas while still lacking in others. The goal is for
GEOM to be the default in 5.0-RELEASE. GEOM to be the default in 5.0-RELEASE.
</p> </p>
<p> <p>
@ -975,8 +976,8 @@ includes porting this facility to the -current tree.</p>
with rtld, libc and our toolchain have been fixed. There is one remaining with rtld, libc and our toolchain have been fixed. There is one remaining
deadlock in the web-browser code of OO.org. If anybody like to help deadlock in the web-browser code of OO.org. If anybody like to help
us with fixing this bug (may be another libc_r bug as it looks like) us with fixing this bug (may be another libc_r bug as it looks like)
just mail me ! Unfortunalty gcc2 support got broken again with the import just mail me! Unfortunately gcc2 support got broken again with the import
of gcc2.95.4 in STABLE. Exceptions support seems to be broken again, we get of gcc2.95.4 in STABLE. Exceptions support seems to be broken again; we get
internal compiler errors with c++ exceptions code. You'll have to use gcc31 internal compiler errors with c++ exceptions code. You'll have to use gcc31
again.</p> again.</p>
@ -1050,7 +1051,7 @@ includes porting this facility to the -current tree.</p>
<body> <body>
<p> <p>
A lot of remaining PR's and Bugs have been closed. All relevant rpc A lot of remaining PR's and Bugs have been closed. All relevant rpc
concerning patches have been comitted. Thank goes to Alfred and Ian Dowese. concerning patches have been committed. Thanks go to Alfred and Ian Dowese.
</p> </p>
<p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch <p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch
available which adds IPv6 support to all remaining rpc servers. available which adds IPv6 support to all remaining rpc servers.
@ -1086,7 +1087,7 @@ includes porting this facility to the -current tree.</p>
</links> </links>
<body> <body>
<p>mb_alloc is getting some updates and a couple of optimisations. <p>mb_alloc is getting some updates and a couple of optimizations.
A new allocator interface routine should already be committed by A new allocator interface routine should already be committed by
the time this report is "published:" m_getcl() allocates an mbuf the time this report is "published:" m_getcl() allocates an mbuf
and a cluster in one shot. This is the result of months and a cluster in one shot. This is the result of months
@ -1096,7 +1097,7 @@ includes porting this facility to the -current tree.</p>
<p>Other than that, mb_alloc is being shown how to perform <p>Other than that, mb_alloc is being shown how to perform
multi-mbuf or cluster allocations without dropping the cache lock in multi-mbuf or cluster allocations without dropping the cache lock in
between (m_getcl() and m_getm() will use this). Finally, work is between (m_getcl() and m_getm() will use this). Finally, work is
being done to optimise ext_buf ref. count allocations and to provide being done to optimize ext_buf ref. count allocations and to provide
support for jumbo (> 9K) clusters.</p> support for jumbo (> 9K) clusters.</p>
</body> </body>
</project> </project>
@ -1214,10 +1215,10 @@ includes porting this facility to the -current tree.</p>
<p> <p>
I'm seriously considering to solve the lack of CPU and network I'm seriously considering to solve the lack of CPU and network
resources for the project's future evolution. Maybe the bandwidth resources for the project's future evolution. Maybe the bandwidth
problem can be resolved (several bandwidth offering are received!), problem can be resolved (several bandwidth offers have been received!),
but there is no answer about CPU problem (I have a plan to upgrade but there is no answer about CPU problems (I have a plan to upgrade
our PCs from P3-500Mhz to P4 or something better than previous). our PCs from P3-500MHz to P4 or better).
If you have interested to donate PCs to the project, please email me If you have interested in donating PCs to the project, please email me
for more detail. for more detail.
</p> </p>
</body> </body>

22
en/news/status/report-2002-07-2002-08.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>July - August</month> <month>July - August</month>
@ -175,7 +177,7 @@
<body> <body>
<p>The GEOM code has gotten so far that it beats our current code <p>The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. The goal is for in some areas while still lacking in others. The goal is for
GEOM to be the default in 5.0-RELEASE.</p> GEOM to be the default in 5.0-RELEASE.</p>
<p>Currently work on a cryptographic module which should be able <p>Currently work on a cryptographic module which should be able
to protect a diskpartition from practically any sort of attack to protect a diskpartition from practically any sort of attack
@ -337,7 +339,7 @@
an any recent FreeBSD-current. Support to manipulate SUNI registers an any recent FreeBSD-current. Support to manipulate SUNI registers
has been added to the ATM drivers (to switch between SONET and SDH has been added to the ATM drivers (to switch between SONET and SDH
modes, for example). The ngatmsig package now includes a small and modes, for example). The ngatmsig package now includes a small and
simple call control module that mayh be used to build a simple ATM simple call control module that may be used to build a simple ATM
switch. The netgraph stuff has been patched to use the official switch. The netgraph stuff has been patched to use the official
netgraph locking.</p> netgraph locking.</p>
</body> </body>
@ -386,7 +388,7 @@
created.</p> created.</p>
<p>The sh(1) built-in, command(1), was reimplemented to conform with <p>The sh(1) built-in, command(1), was reimplemented to conform with
POSIX. Additionally, several utilities which were previously brought POSIX. Additionally, several utilities which were previously brought
up to conformance were merged into the 4-STABLE banch.</p> up to conformance were merged into the 4-STABLE branch.</p>
</body> </body>
</project> </project>
@ -431,7 +433,7 @@
smoothing out some of the rough edges, then, once all the work is done, smoothing out some of the rough edges, then, once all the work is done,
make GNOMENG the default.</p> make GNOMENG the default.</p>
<p>A long-standing annoyance in Nautilus has also been recently <p>A long-standing annoyance in Nautilus has also been recently
corrected. The desktop is no longer clutered with volume icons, and corrected. The desktop is no longer cluttered with volume icons, and
removable media (such as CDs) should now be handled correctly.</p> removable media (such as CDs) should now be handled correctly.</p>
</body> </body>
@ -487,7 +489,7 @@
OpenSSL (through the /dev/crypto device).</p> OpenSSL (through the /dev/crypto device).</p>
<p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's <p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's
source tree. This permits any user-level application that use -lcrypto to source tree. This permits any user-level application that use -lcrypto to
automatically get hardware crypto acceleration. Otherwse the core crypto automatically get hardware crypto acceleration. Otherwise the core crypto
support is stable and has been in production use on -stable machines for support is stable and has been in production use on -stable machines for
several months.</p> several months.</p>
<p>Import of this work into the -current tree has started. A publicly <p>Import of this work into the -current tree has started. A publicly
@ -543,7 +545,7 @@
<p>Work is in progress to MFC a number of bug fixes related <p>Work is in progress to MFC a number of bug fixes related
to vm_map corruption into -stable. This work is probably to vm_map corruption into -stable. This work is probably
too involved to make it into the 4.7 release but is expected to too involved to make it into the 4.7 release but is expected to
be comitted just after the freeze is lifted. The corruption be committed just after the freeze is lifted. The corruption
in question typically occurs in large-memory systems under heavy in question typically occurs in large-memory systems under heavy
loads and typically panics or KPFs (kernel-page-fault's) the machine loads and typically panics or KPFs (kernel-page-fault's) the machine
in a vm_map related function.</p> in a vm_map related function.</p>
@ -750,7 +752,7 @@
<body> <body>
<p> David Xu and I have been working on cleaning up some of the work done <p> David Xu and I have been working on cleaning up some of the work done
in KSE-III and Jonathon and Dan have been working on the userland in KSE-III and Jonathon and Dan have been working on the userland
interface. The userland libray will be committed soon in a interface. The userland library will be committed soon in a
prototypical state and a working test program using that interface will prototypical state and a working test program using that interface will
hopefully accompany it. I have just committed a rework of the run hopefully accompany it. I have just committed a rework of the run
states for kernel threads that simplifies or solves some problems that states for kernel threads that simplifies or solves some problems that
@ -1012,7 +1014,7 @@
matured substantially, and large parts of it were merged to the matured substantially, and large parts of it were merged to the
main FreeBSD tree over July and August.</p> main FreeBSD tree over July and August.</p>
<p>A variety of entry point changes were made, including: component <p>A variety of entry point changes were made, including: component
names are now passed to VFS namespace VOPs; agressive caching names are now passed to VFS namespace VOPs; aggressive caching
of MAC labels in vnodes; mmap memory access downgrades on subject of MAC labels in vnodes; mmap memory access downgrades on subject
relabel; check for access()/eaccess(); checks for vnode read, relabel; check for access()/eaccess(); checks for vnode read,
write, ioctl, pool, permitting revocation post-open() by aware write, ioctl, pool, permitting revocation post-open() by aware
@ -1041,12 +1043,12 @@
main FreeBSD tree. KDE interfaces to common management main FreeBSD tree. KDE interfaces to common management
activities.</p> activities.</p>
<p>Wrote and taught full-day MAC framework tutorial at STOS <p>Wrote and taught full-day MAC framework tutorial at STOS
BSD and Darwin Security Symposium; first draft of MAC fraemwork BSD and Darwin Security Symposium; first draft of MAC framework
architecture and API guide. This is now in the Developer's architecture and API guide. This is now in the Developer's
Handbook.</p> Handbook.</p>
<p>Next couple of months will bring continued maturity improvements, <p>Next couple of months will bring continued maturity improvements,
labeling and protection of more objects; VFS performance labeling and protection of more objects; VFS performance
improvements; better support for UFS2 EAs and seperate EA improvements; better support for UFS2 EAs and separate EA
entries for each policy; improved support for LOMAC; MLS entries for each policy; improved support for LOMAC; MLS
compartments; IPsec security association labeling; improved compartments; IPsec security association labeling; improved
SEBSD FLASK/TE port; and much more.</p> SEBSD FLASK/TE port; and much more.</p>

18
en/news/status/report-2002-09-2002-10.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>September-October</month> <month>September-October</month>
@ -23,7 +25,7 @@
continue to be the production supported platform as 5.X is brought continue to be the production supported platform as 5.X is brought
in for landing.</p> in for landing.</p>
<p>Over the next two months, the FreeBSD Project will be focussed <p>Over the next two months, the FreeBSD Project will be focused
almost entirely on making 5.0 a success: improving system almost entirely on making 5.0 a success: improving system
stability and performance, as well as increasing the pool of stability and performance, as well as increasing the pool of
applications that build and run on 5.0. The Release Engineering applications that build and run on 5.0. The Release Engineering
@ -267,8 +269,8 @@
very strong encryption of a GEOM "disk". The algorithm has passed very strong encryption of a GEOM "disk". The algorithm has passed
informal review by a couple of seasoned crypto heavy-weights. informal review by a couple of seasoned crypto heavy-weights.
Any GEOM device can be protected with GBDE, entire physical disks, Any GEOM device can be protected with GBDE, entire physical disks,
MBR slices, BSD paritions etc etc. Booting from an encrypted MBR slices, BSD partitions etc etc. Booting from an encrypted
partition is not possible however.</p> partition is not possible, however.</p>
<p>The focus of GBDE is to protect a "cold" disk media. (FreeBSD is <p>The focus of GBDE is to protect a "cold" disk media. (FreeBSD is
not equipped well for protecting key material on a running system not equipped well for protecting key material on a running system
@ -416,7 +418,7 @@
/dev/crypto device).</p> /dev/crypto device).</p>
<p>This work was committed to the -current tree. To configure it for use <p>This work was committed to the -current tree. To configure it for use
specifiy device crypto in your system configuration file or you can load the specify device crypto in your system configuration file or you can load the
crypto module. The /dev/crypto device support is brought in with device crypto module. The /dev/crypto device support is brought in with device
cryptodev or by loading the cryptodev module. Two crypto device drivers cryptodev or by loading the cryptodev module. Two crypto device drivers
exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI
@ -579,7 +581,7 @@
<body> <body>
<p>The KSE code has now all the basic kernel functionality <p>The KSE code has now all the basic kernel functionality
to start being used by the userland. There are still things to start being used by the userland. There are still things
to be done for testing and familiarisation.</p> to be done for testing and familiarization.</p>
<p>General system utilities have not yet been changed. <p>General system utilities have not yet been changed.
e.g. ps and top etc. need to know about threads.</p> e.g. ps and top etc. need to know about threads.</p>
@ -597,7 +599,7 @@
time that this report is published.</p> time that this report is published.</p>
<p>I still need someone to take over the "official" web page <p>I still need someone to take over the "official" web page
since jason left. LaTex sure isn't my thing. </p> since jason left. LaTeX sure isn't my thing. </p>
</body> </body>
</project> </project>
@ -972,12 +974,12 @@
<body> <body>
<p>Universally Unique Identifiers (UUIDs) are 128 bit values that may <p>Universally Unique Identifiers (UUIDs) are 128 bit values that may
be generated independently on seperate nodes (hosts), which, result in be generated independently on separate nodes (hosts), which result in
globally unique strings. UUIDs are also known as Globally Unique globally unique strings. UUIDs are also known as Globally Unique
Identifiers (GUIDs). The UUID support for FreeBSD (libc) conforms to the Identifiers (GUIDs). The UUID support for FreeBSD (libc) conforms to the
DCE 1.1 RPC specification.</p> DCE 1.1 RPC specification.</p>
<p>UUID suport has been added to FreeBSD -CURRENT, and will be available <p>UUID support has been added to FreeBSD -CURRENT, and will be available
in version 5.0. It is being extensively used in GPT partition handling in version 5.0. It is being extensively used in GPT partition handling
for IA-64 platform. For now, a simple manual page has been provided, for IA-64 platform. For now, a simple manual page has been provided,
which outlines information about the provided uuid routines. Many which outlines information about the provided uuid routines. Many

20
en/news/status/report-2002-11-2002-12.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>November-December</month> <month>November-December</month>
@ -325,7 +327,7 @@
config files are fully parsed now and their actions are config files are fully parsed now and their actions are
performed.</p> performed.</p>
<p>Future work in this area are likely to be limited to imporving <p>Future work in this area is likely to be limited to improving
the devctl interface. /dev/devctl likely will be a cloneable the devctl interface. /dev/devctl likely will be a cloneable
device in future versions. Individual device control via devctl device in future versions. Individual device control via devctl
is also planned.</p> is also planned.</p>
@ -482,10 +484,10 @@
S&#233;bastien is still maintaining the Release Notes.</p> S&#233;bastien is still maintaining the Release Notes.</p>
<p>We launched a new site, www.FreeBSD-fr.info, consisting in a French <p>We launched a new site, www.FreeBSD-fr.info, consisting in a French
Dameon News like site. Netasq have donated our new server; we will Daemon News like site. Netasq have donated our new server; we will
install it in a new hosting provider in the few next weeks. One of the install it in a new hosting provider in the few next weeks. One of the
big job now, project now, is the translation of the FAQ, and the big big job now is the translation of the FAQ, and the big
project will be the manual pages</p> project will be the manual pages.</p>
</body> </body>
</project> </project>
@ -588,7 +590,7 @@
the changes necessary to run these are sitting in the perforce the changes necessary to run these are sitting in the perforce
tree and are not in the -current or RELENG_5 cvs tree. As a tree and are not in the -current or RELENG_5 cvs tree. As a
result, the cvs derived builds (-current and the 5.0-RC series result, the cvs derived builds (-current and the 5.0-RC series
and presumably 5.0-RELEASE) are only useable on obsolete Itanium1 and presumably 5.0-RELEASE) are only usable on obsolete Itanium1
systems.</p> systems.</p>
<p>Lots of other stability and functionality fixes have been made <p>Lots of other stability and functionality fixes have been made
@ -647,7 +649,7 @@
<body> <body>
<p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user <p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
applications with means to access hardware graphic resources (dma, applications with means to access hardware graphic resources (dma,
irqs, mmio). KGI is already available under Linux as a seperate irqs, mmio). KGI is already available under Linux as a separate
standalone project. The KGI/FreeBSD project aims at integrating KGI standalone project. The KGI/FreeBSD project aims at integrating KGI
in the FreeBSD kernel.</p> in the FreeBSD kernel.</p>
@ -693,7 +695,7 @@
<p>In addition to TCP and UDP, the other networking protocols <p>In addition to TCP and UDP, the other networking protocols
such as raw IP, IPv6, AppleTalk, and XNS need to be locked up. such as raw IP, IPv6, AppleTalk, and XNS need to be locked up.
Around 1/4 these remaining protocols have been locked and Around 1/4 these remaining protocols have been locked and
will be commited after the IP stack is locked.</p> will be committed after the IP stack is locked.</p>
<p>The protocol independent socket layer needs to be locked and <p>The protocol independent socket layer needs to be locked and
operating correctly with the protocol dependent locks. This operating correctly with the protocol dependent locks. This
@ -814,12 +816,12 @@
</contact> </contact>
<links> <links>
<url href="http://www.freebsd.org/releng/index.html">Release Enginerring <url href="http://www.freebsd.org/releng/index.html">Release Engineering
Homepage</url> Homepage</url>
</links> </links>
<body> <body>
<p>November and December were especially busy for the release egineering <p>November and December were especially busy for the release engineering
team. Scott Long joined the team to help with secretary and team. Scott Long joined the team to help with secretary and
communications tasks while Brian Somers bowed out to focus on other communications tasks while Brian Somers bowed out to focus on other
projects.</p> projects.</p>

12
en/news/status/report-2003-01-2003-02.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>January-February</month> <month>January-February</month>
@ -321,7 +323,7 @@
<body> <body>
<p>We have the first disk device driver (aac) out from under Giant <p>We have the first disk device driver (aac) out from under Giant
now, and in certain scenarios it gives improvements up to 20%. now, and in certain scenarios it gives improvements up to 20%.
The device drive API was pruned to reflect that NO_GEOM The device driver API was pruned to reflect that NO_GEOM
compatibility is unnecessary, this resulted in approx 1000 compatibility is unnecessary, this resulted in approx 1000
lines less source code, the majority of which were removed lines less source code, the majority of which were removed
from the device drivers. The new API for cdevsw is a lot simpler from the device drivers. The new API for cdevsw is a lot simpler
@ -547,7 +549,7 @@
<body> <body>
<p>Most of the file system buffer cache has been reviewed and protected. <p>Most of the file system buffer cache has been reviewed and protected.
The vnode interlock was extended to cover some buffer flag fields so The vnode interlock was extended to cover some buffer flag fields so
that a seperate interlock was not required. The global buffer queue that a separate interlock was not required. The global buffer queue
data structures were locked and counters were converted to atomic ops. data structures were locked and counters were converted to atomic ops.
The BUF_*LOCK functions grew an interlock argument so that buffers The BUF_*LOCK functions grew an interlock argument so that buffers
could be safely removed from the vnode clean and dirty lists. The could be safely removed from the vnode clean and dirty lists. The
@ -580,7 +582,7 @@
<body> <body>
<p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early <p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early
adopters and experimenters are welcome to try it and submit bug adopters and experimenters are welcome to try it and submit bug
reports. It has shown noticable performance improvements over the old reports. It has shown noticeable performance improvements over the old
scheduler under some workloads. There are currently problems with scheduler under some workloads. There are currently problems with
nice fairness but otherwise the interactive performance is very good. nice fairness but otherwise the interactive performance is very good.
More work to improve the load balancing algorithm is required as well. More work to improve the load balancing algorithm is required as well.
@ -632,7 +634,7 @@
some lock order issues remain. After this some lock order issues remain. After this
work, it will no longer be necessary to hold Giant to call work, it will no longer be necessary to hold Giant to call
device_* routines safely. kobj work is being done by others and device_* routines safely. kobj work is being done by others and
will likely require more extensive design work to make smp will likely require more extensive design work to make SMP
friendly.</p> friendly.</p>
</body> </body>
</project> </project>
@ -660,7 +662,7 @@
with existing specifications. The upcoming 4.8 and 5.1 releases will with existing specifications. The upcoming 4.8 and 5.1 releases will
be the first ones using the new NewReno logic. Recently, we be the first ones using the new NewReno logic. Recently, we
implemented the Limited Transmit algorithm (RFC 3042) which benefits implemented the Limited Transmit algorithm (RFC 3042) which benefits
connections with small congestions windows, as happens, for example, connections with small congestion windows, as happens, for example,
on many short web connections. We also recently added support for larger on many short web connections. We also recently added support for larger
sized starting congestion windows as described in RFC 3390. This helps sized starting congestion windows as described in RFC 3390. This helps
short TCP connections as well as those with large round-trip delays, short TCP connections as well as those with large round-trip delays,

35
en/news/status/report-august-2001.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>August</month> <month>August</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD$ $FreeBSD: www/en/news/status/report-august-2001.xml,v 1.4 2001/09/18 19:39:41 chris Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -135,7 +137,7 @@
<body> <body>
<p>No change since last status. Some discussion amongst all of us <p>No change since last status. Some discussion amongst all of us
occurred, but lack of time and commitment to FreeBSD has meant occurred, but lack of time and commitment to FreeBSD has meant
little has actually been committed to the tree. SMPNG work will little has actually been committed to the tree. SMPng work will
be left to those who seem to have a notion about what needs to be be left to those who seem to have a notion about what needs to be
done.</p> done.</p>
</body> </body>
@ -209,10 +211,10 @@
thread to be created. (nor have new threading syscalls been added thread to be created. (nor have new threading syscalls been added
yet). This is an important milestone as it represents the last yet). This is an important milestone as it represents the last
point where the kernel has only "mechanical" changes. To go point where the kernel has only "mechanical" changes. To go
further we must start adding new algorythms and functions.</p> further we must start adding new algorithms and functions.</p>
<p>The kernel for milestone 2 is reliable and has no noticable <p>The kernel for milestone 2 is reliable and has no noticeable
performance degradations when compared to a matchung -current performance degradations when compared to a matching -current
kernel. (the differences are less than the margin of error, so kernel. (the differences are less than the margin of error, so
that sometimes the new kernel actually fractionally beats the that sometimes the new kernel actually fractionally beats the
unaltered kernel).</p> unaltered kernel).</p>
@ -534,7 +536,7 @@
</project> </project>
<project> <project>
<title>SYN cache implemetation for FreeBSD</title> <title>SYN cache implementation for FreeBSD</title>
<contact> <contact>
<person> <person>
@ -645,7 +647,7 @@
<p>Benefits of approach include the fact that a kqueue filter can <p>Benefits of approach include the fact that a kqueue filter can
be attached to a network device for monitoring purposes. Initial be attached to a network device for monitoring purposes. Initial
code exists to send a kq event whever the network link status code exists to send a kq event whenever the network link status
changes. Other benefits may include better access control by changes. Other benefits may include better access control by
using filesystem ACLs to control access to the device.</p> using filesystem ACLs to control access to the device.</p>
</body> </body>
@ -733,7 +735,7 @@
making some excellent progress. Of note, some problems with the making some excellent progress. Of note, some problems with the
way the pmap module implements copy-on-write mappings have been way the pmap module implements copy-on-write mappings have been
fixed and fork() now works as expected, support for signals has fixed and fork() now works as expected, support for signals has
been added, and the port has been updated for kse in the perforce been added, and the port has been updated for KSE in the perforce
repository. Thomas Moestl has begun work on pci bus support, and repository. Thomas Moestl has begun work on pci bus support, and
a basic nexus bus for sparc64 has been written. The driver for a basic nexus bus for sparc64 has been written. The driver for
the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated
@ -958,7 +960,7 @@
<body> <body>
<p>Support for cloning vlan devices via ifconfig has been <p>Support for cloning vlan devices via ifconfig has been
committed to -current and will be MFC'd after further testing. committed to -current and will be MFC'd after further testing.
Additionaly, Maksim Yevmenkin submitted code to allow cloning of Additionally, Maksim Yevmenkin submitted code to allow cloning of
tap and vmnet devices on devfs systems. Code for faith and stf tap and vmnet devices on devfs systems. Code for faith and stf
should be committed shortly.</p> should be committed shortly.</p>
</body> </body>
@ -1058,7 +1060,7 @@
allowed to make this 97-component meta-package building and allowed to make this 97-component meta-package building and
working properly.</p> working properly.</p>
<p>Next month the project will be focused on organising work of <p>Next month the project will be focused on organizing work of
the FreeBSD GNOME Team as well as on attempts to increase amount the FreeBSD GNOME Team as well as on attempts to increase amount
of people participating in the team (anybody who is willing to of people participating in the team (anybody who is willing to
participate is welcome to drop a note to gnome@FreeBSD with a participate is welcome to drop a note to gnome@FreeBSD with a
@ -1100,7 +1102,7 @@
combination of binary object files and source (under a combination of binary object files and source (under a
constrictive license). The FreeBSD NVIDIA driver project aimed to constrictive license). The FreeBSD NVIDIA driver project aimed to
completely replace the source component of the driver using code completely replace the source component of the driver using code
targetting FreeBSD 4.3 and released under the BSD license. The targeting FreeBSD 4.3 and released under the BSD license. The
binary module provided is supposedly the same module used on binary module provided is supposedly the same module used on
Windows, BeOS, and OS/2, so it should be portable between Windows, BeOS, and OS/2, so it should be portable between
different i80x86 based OS's.</p> different i80x86 based OS's.</p>
@ -1109,16 +1111,16 @@
NVIDIA seemed enthusiastic about the project, and was fairly NVIDIA seemed enthusiastic about the project, and was fairly
quick about returning email, but when we discovered issues that quick about returning email, but when we discovered issues that
prevented porting without changes to the binary component or prevented porting without changes to the binary component or
error codes we needed decyphered, Nick (the contact) said he'd error codes we needed deciphered, Nick (the contact) said he'd
look into it and never got back. The first major problem was the look into it and never got back. The first major problem was the
ioctl interface, the nvidia driver passes a pointer and depends ioctl interface, the NVIDIA driver passes a pointer and depends
on the kernel side to copyout the right amount, where FreeBSD on the kernel side to copyout the right amount, where FreeBSD
expect the parameters to be correct and the copyout is performed expect the parameters to be correct and the copyout is performed
by the subsystem. This was worked around using Dave Rufinos by the subsystem. This was worked around using Dave Rufinos
"ioctl tunnel" idea. After that, we found that X refused to load "ioctl tunnel" idea. After that, we found that X refused to load
and traced it down to an ioctl defined in the binary component and traced it down to an ioctl defined in the binary component
erroring. We cannot tell what that ioctl is, were told that we erroring. We cannot tell what that ioctl is, were told that we
could not sign an nda for source to that component, and have been could not sign an NDA for source to that component, and have been
waiting a month for Nick to "look into it". Therefore progress is waiting a month for Nick to "look into it". Therefore progress is
impossible (without breaking the license) and we believe that the impossible (without breaking the license) and we believe that the
flaws make the driver unportable to any *nix other than flaws make the driver unportable to any *nix other than
@ -1316,7 +1318,7 @@
naturally resulted in a number of bugs being found. Development naturally resulted in a number of bugs being found. Development
work has mostly focused on fixing these problems and the project work has mostly focused on fixing these problems and the project
is now set to release fourth patchset over the weekend, which is now set to release fourth patchset over the weekend, which
should see the JDK in a reasonable useable state. One of the big should see the JDK in a reasonably usable state. One of the big
challenges left is producing a working HotSpot JVM, which looks challenges left is producing a working HotSpot JVM, which looks
like it will require some heavy hacking.</p> like it will require some heavy hacking.</p>
@ -1475,7 +1477,7 @@
</contact> </contact>
<body> <body>
<p>Capabilities support is currently being comitted to the base <p>Capabilities support is currently being committed to the base
FreeBSD tree--userland libraries are now fully committed, and FreeBSD tree--userland libraries are now fully committed, and
kernel infrastructure is being integrated.</p> kernel infrastructure is being integrated.</p>
</body> </body>
@ -1515,4 +1517,3 @@
</body> </body>
</project> </project>
</report> </report>

14
en/news/status/report-dec-2001-jan-2002.xml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.3 2002/03/02 04:49:31 mike Exp $ --> <!-- $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.4 2002/03/09 07:06:48 dd Exp $ -->
<report> <report>
<date> <date>
@ -9,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.3 2002/03/02 04:49:31 mike Exp $ $FreeBSD: www/en/news/status/report-dec-2001-jan-2002.xml,v 1.4 2002/03/09 07:06:48 dd Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -266,14 +266,14 @@
<p>The KSE project (an attempt to support scalable thread in <p>The KSE project (an attempt to support scalable thread in
FreeBSD using kernel support), has reached What I call "milestone FreeBSD using kernel support), has reached What I call "milestone
3". At this milestone it is possible to run a multithreaded 3". At this milestone it is possible to run a multithreaded
program on a single CPU but with full concurrancy of threads on program on a single CPU but with full concurrency of threads on
that CPU. In other words the kernel supports the fact that one that CPU. In other words the kernel supports the fact that one
thread can block by allowing another thread to run in its place. thread can block by allowing another thread to run in its place.
A test program that demonstrates this is available at the above A test program that demonstrates this is available at the above
website.</p> website.</p>
<p>Milestone 4 will be to allow threads from the same program to <p>Milestone 4 will be to allow threads from the same program to
run on multiple CPUS but may require more input from the SMPNG run on multiple CPUs but may require more input from the SMPng
project. I am at the moment (Feb 6) getting ready to commit a project. I am at the moment (Feb 6) getting ready to commit a
first set of changes for milestone 3, that have no real effect first set of changes for milestone 3, that have no real effect
but serve to drastically reduce the complexity of the remaining but serve to drastically reduce the complexity of the remaining
@ -315,7 +315,7 @@
allows one to use ATM PVCs. It should be possible, for example, allows one to use ATM PVCs. It should be possible, for example,
to do PPP over ATM with this package. Both bsnmp and ngatmbase to do PPP over ATM with this package. Both bsnmp and ngatmbase
are available in version 1.0 under the link above. Two other are available in version 1.0 under the link above. Two other
modules will be released in february: ngatmsig containing the modules will be released in February: ngatmsig containing the
UNI-4.0 signalling stack as netgraph nodes and ngatmip containing UNI-4.0 signalling stack as netgraph nodes and ngatmip containing
CLIP and LANE-2.0.</p> CLIP and LANE-2.0.</p>
</body> </body>
@ -699,8 +699,8 @@
</links> </links>
<body> <body>
<p>Alfred Perlstein commited file descriptor locking code <p>Alfred Perlstein committed file descriptor locking code
which was definetly a good push towards trying to lock down which was definitely a good push towards trying to lock down
some important pieces of global data. Peter Wemm has made some important pieces of global data. Peter Wemm has made
progress on pmap cleanups for x86 SMP TLB shootdowns. Matt progress on pmap cleanups for x86 SMP TLB shootdowns. Matt
Dillon and John Baldwin have made progress on getting patches Dillon and John Baldwin have made progress on getting patches

30
en/news/status/report-feb-2002-apr-2002.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>February - April</month> <month>February - April</month>
@ -75,9 +77,9 @@
</contact> </contact>
<body> <body>
<p>FreeBSD's new kernel memory allocator has been commited to <p>FreeBSD's new kernel memory allocator has been committed to
5.0. UMA is a slabs derived allocator that supports memory 5.0. UMA is a slabs derived allocator that supports memory
reclaiming, object caching, type stable storage, and per cpu reclaiming, object caching, type stable storage, and per CPU
free lists for optimal SMP performance. It has both a free lists for optimal SMP performance. It has both a
malloc(9) interface and a zone style interface for specific malloc(9) interface and a zone style interface for specific
object types. uma(9) will be available shortly.</p> object types. uma(9) will be available shortly.</p>
@ -225,8 +227,8 @@
printf(1) utility was brought up to conformance with the 1992 printf(1) utility was brought up to conformance with the 1992
edition of POSIX.2, with further development planned.</p> edition of POSIX.2, with further development planned.</p>
<p>On the header front, much progress has been made. Specically, <p>On the header front, much progress has been made. Specifically,
infrastructure to control visiblity of components of a header, based infrastructure to control visibility of components of a header, based
on the standard requested by an application, has been added to on the standard requested by an application, has been added to
&lt;sys/cdefs.h&gt;. Some work has been completed on renovating the &lt;sys/cdefs.h&gt;. Some work has been completed on renovating the
way types are defined. This has lead to the creation of way types are defined. This has lead to the creation of
@ -317,7 +319,7 @@
<p>Not to be left out, the existing GNOME 1.4 components have received <p>Not to be left out, the existing GNOME 1.4 components have received
numerous updates to keep them in sync with the stable distfiles numerous updates to keep them in sync with the stable distfiles
on gnome.org. We have seen many "1.0" milsestone releases including on gnome.org. We have seen many "1.0" milestone releases including
the most recent AbiWord 1.0.0. In the next few weeks, we will be the most recent AbiWord 1.0.0. In the next few weeks, we will be
making sure all the GNOME 1.4 components build correct packages making sure all the GNOME 1.4 components build correct packages
on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p> on bento so that GNOME 1.4 will be on the 4.6-RELEASE CD.</p>
@ -347,7 +349,7 @@
<p> FreeBSD/KGI started last year after the port of GGI to VGL. <p> FreeBSD/KGI started last year after the port of GGI to VGL.
KGI (Kernel Graphic Interface) is a kernel infrastructure providing user KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
applications with access to hardware graphic resources (dma, applications with access to hardware graphic resources (dma,
irqs, mmio). KGI is already available under Linux as a seperate irqs, mmio). KGI is already available under Linux as a separate
project. The FreeBSD/KGI project aims at integrating KGI project. The FreeBSD/KGI project aims at integrating KGI
in the FreeBSD kernel. Mostly a port for now, but optimized for in the FreeBSD kernel. Mostly a port for now, but optimized for
FreeBSD in the future. Currently FreeBSD/KGI is under development FreeBSD in the future. Currently FreeBSD/KGI is under development
@ -396,9 +398,9 @@
<body> <body>
<p>We now have a loadable mfsroot floppy. It contains just the <p>We now have a loadable mfsroot floppy. It contains just the
diskeditor (which is really a disk partitioner) which has been diskeditor (which is really a disk partitioner) which has been
enhanced and is probably in his final form. It's been geared enhanced and is probably in its final form. It's been geared
towards making the newfs(1) and mount(1) step seperate dialogs, so towards making the newfs(1) and mount(1) steps separate dialogs, so
it reduced its complexity. A basic fstab class has been it reduceed its complexity. A basic fstab class has been
implemented to manipulate /etc/fstab and mountpoint. This might implemented to manipulate /etc/fstab and mountpoint. This might
find a use outside libh, by the way. Libh package format is still find a use outside libh, by the way. Libh package format is still
incomplete and somehow buggy, so it's my next target.</p> incomplete and somehow buggy, so it's my next target.</p>
@ -438,7 +440,7 @@
separated into kernel part and userland part, yet another snapshots separated into kernel part and userland part, yet another snapshots
from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several from RELENG_4_x branch (currently 4.5-RELEASE-p4), add several
packages including XFree86 4.x to installation CD-ROM, new packages including XFree86 4.x to installation CD-ROM, new
cdboot-only ISO image, fix breackage of duplex.iso, etc. See also cdboot-only ISO image, fix breakage of duplex.iso, etc. See also
the project webpage for more detail. Also, I have a plan to add the project webpage for more detail. Also, I have a plan to add
FreeBSD/alpha distribution to this project -- stay tuned.</p> FreeBSD/alpha distribution to this project -- stay tuned.</p>
</body> </body>
@ -865,7 +867,7 @@ messages.</url>
</links> </links>
<body> <body>
<p>4.5-RELEASE Japanese manapge package, ja-man-doc-4.5.tgz, once <p>4.5-RELEASE Japanese manpage package, ja-man-doc-4.5.tgz, once
published with OpenSSH 2.3 (as reported by previous status published with OpenSSH 2.3 (as reported by previous status
report) on January 31, is replaced with new package with OpenSSH report) on January 31, is replaced with new package with OpenSSH
2.9 based manpages on March 3. Since then, we have been 2.9 based manpages on March 3. Since then, we have been
@ -898,7 +900,7 @@ messages.</url>
<body> <body>
<p>The GEOM code has gotten so far that it beats our current code <p>The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. Work continues on in some areas while still lacking in others. Work continues on
a generalized interface for "magic data" (boot blocks, disklabels a generalized interface for "magic data" (boot blocks, disklabels
MBR's etc) manipulation from userland.</p> MBR's etc) manipulation from userland.</p>
<p>With GEOM enabled in the kernel any FreeBSD platform will now <p>With GEOM enabled in the kernel any FreeBSD platform will now
@ -985,7 +987,7 @@ messages.</url>
In current the API has changed to move unit allocation into the In current the API has changed to move unit allocation into the
generic cloning code reducing the amount of support code required generic cloning code reducing the amount of support code required
in each driver. Code improvements to increase our API in each driver. Code improvements to increase our API
compatability with NetBSD will be commited soon along with cloning compatibility with NetBSD will be committed soon along with cloning
support for discard interfaces and ppp(4) interfaces.</p> support for discard interfaces and ppp(4) interfaces.</p>
<p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support <p>Thanks to <email>mux@FreeBSD.org</email> for the loopback support
and unit allocation cleanups.</p> and unit allocation cleanups.</p>
@ -1282,7 +1284,7 @@ messages.</url>
40 developers attended in person, another five by phone, and many 40 developers attended in person, another five by phone, and many
others by webcast. During a marathon-esque eight hour session, a others by webcast. During a marathon-esque eight hour session, a
variety of development topics were discussed, including adding variety of development topics were discussed, including adding
inheritence to the KOBJ system, ports to new architectures, inheritance to the KOBJ system, ports to new architectures,
adaptations of the toolchain for new architectures, the GEOM adaptations of the toolchain for new architectures, the GEOM
extensible storage device framework, upcoming changes to the network extensible storage device framework, upcoming changes to the network
stack, TrustedBSD features, KSE, SMPng, and the release engineering stack, TrustedBSD features, KSE, SMPng, and the release engineering

12
en/news/status/report-jan-2003-feb-2003.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>January-February</month> <month>January-February</month>
@ -321,7 +323,7 @@
<body> <body>
<p>We have the first disk device driver (aac) out from under Giant <p>We have the first disk device driver (aac) out from under Giant
now, and in certain scenarios it gives improvements up to 20%. now, and in certain scenarios it gives improvements up to 20%.
The device drive API was pruned to reflect that NO_GEOM The device driver API was pruned to reflect that NO_GEOM
compatibility is unnecessary, this resulted in approx 1000 compatibility is unnecessary, this resulted in approx 1000
lines less source code, the majority of which were removed lines less source code, the majority of which were removed
from the device drivers. The new API for cdevsw is a lot simpler from the device drivers. The new API for cdevsw is a lot simpler
@ -547,7 +549,7 @@
<body> <body>
<p>Most of the file system buffer cache has been reviewed and protected. <p>Most of the file system buffer cache has been reviewed and protected.
The vnode interlock was extended to cover some buffer flag fields so The vnode interlock was extended to cover some buffer flag fields so
that a seperate interlock was not required. The global buffer queue that a separate interlock was not required. The global buffer queue
data structures were locked and counters were converted to atomic ops. data structures were locked and counters were converted to atomic ops.
The BUF_*LOCK functions grew an interlock argument so that buffers The BUF_*LOCK functions grew an interlock argument so that buffers
could be safely removed from the vnode clean and dirty lists. The could be safely removed from the vnode clean and dirty lists. The
@ -580,7 +582,7 @@
<body> <body>
<p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early <p>The ULE scheduler has been committed to the 5.0-CURRENT branch. Early
adopters and experimenters are welcome to try it and submit bug adopters and experimenters are welcome to try it and submit bug
reports. It has shown noticable performance improvements over the old reports. It has shown noticeable performance improvements over the old
scheduler under some workloads. There are currently problems with scheduler under some workloads. There are currently problems with
nice fairness but otherwise the interactive performance is very good. nice fairness but otherwise the interactive performance is very good.
More work to improve the load balancing algorithm is required as well. More work to improve the load balancing algorithm is required as well.
@ -632,7 +634,7 @@
some lock order issues remain. After this some lock order issues remain. After this
work, it will no longer be necessary to hold Giant to call work, it will no longer be necessary to hold Giant to call
device_* routines safely. kobj work is being done by others and device_* routines safely. kobj work is being done by others and
will likely require more extensive design work to make smp will likely require more extensive design work to make SMP
friendly.</p> friendly.</p>
</body> </body>
</project> </project>
@ -660,7 +662,7 @@
with existing specifications. The upcoming 4.8 and 5.1 releases will with existing specifications. The upcoming 4.8 and 5.1 releases will
be the first ones using the new NewReno logic. Recently, we be the first ones using the new NewReno logic. Recently, we
implemented the Limited Transmit algorithm (RFC 3042) which benefits implemented the Limited Transmit algorithm (RFC 3042) which benefits
connections with small congestions windows, as happens, for example, connections with small congestion windows, as happens, for example,
on many short web connections. We also recently added support for larger on many short web connections. We also recently added support for larger
sized starting congestion windows as described in RFC 3390. This helps sized starting congestion windows as described in RFC 3390. This helps
short TCP connections as well as those with large round-trip delays, short TCP connections as well as those with large round-trip delays,

51
en/news/status/report-july-2001.xml
View file

@ -1,4 +1,7 @@
<?xml version="1.0"?> <?xml version="1.0"?>
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>July</month> <month>July</month>
@ -8,7 +11,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.4 2001/09/18 17:48:22 chris Exp $ $FreeBSD: www/en/news/status/report-july-2001.xml,v 1.5 2002/05/16 01:49:58 trhodes Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -131,7 +134,7 @@
<li>User-level management interfaces.</li> <li>User-level management interfaces.</li>
<li>PCI power manangement.</li> <li>PCI power management.</li>
<li>Bug-hunting.</li> <li>Bug-hunting.</li>
</ul> </ul>
@ -241,9 +244,9 @@
systems. The format will be similar to other conferences, with 2 systems. The format will be similar to other conferences, with 2
days of technical sessions over the Saturday and Sunday.</p> days of technical sessions over the Saturday and Sunday.</p>
<p>We'll be finalising the schedule towards the end of the month <p>We'll be finalizing the schedule towards the end of the month
and anybody who is interested in doing a talk should contact us and anybody who is interested in doing a talk should contact us
asap. There are no restrictions on the use of talks, if it's been ASAP. There are no restrictions on the use of talks; if it's been
done before we may still be interested in having it presented to done before we may still be interested in having it presented to
an European audience, and we make no claims to the talks so an European audience, and we make no claims to the talks so
speakers are free to present the talks again at other speakers are free to present the talks again at other
@ -276,7 +279,7 @@
<body> <body>
<p>The new CAM transport code is starting to get supported in <p>The new CAM transport code is starting to get supported in
more HBAs and to get refined so that it does the intended more HBAs and to get refined so that it does the intended
per-protocol support. No progress on doing any SMPNG work for CAM per-protocol support. No progress on doing any SMPng work for CAM
has been made yet. This is a fairly high priority.</p> has been made yet. This is a fairly high priority.</p>
</body> </body>
</project> </project>
@ -440,7 +443,7 @@
<body> <body>
<p>jailNG is a from-scratch rewrite of the popular jail(8) <p>jailNG is a from-scratch rewrite of the popular jail(8)
service, focussing on improved management functions, as well as service, focusing on improved management functions, as well as
more fine-grained configurability. An initial prototype has been more fine-grained configurability. An initial prototype has been
written, based on explicitly named and configured jails, and work written, based on explicitly named and configured jails, and work
is proceeding on userland integration. Currently, it's not clear is proceeding on userland integration. Currently, it's not clear
@ -467,14 +470,14 @@
<p>The main development in the FreeBSD Java Project over the last <p>The main development in the FreeBSD Java Project over the last
month was the release of an initial "Developers Only" patchset month was the release of an initial "Developers Only" patchset
for the JDK 1.3.1. Since that release progress had been made for the JDK 1.3.1. Since that release progress had been made
towards a much more useable alpha quality patchset which is towards a much more usable alpha quality patchset which is
likely to be turned into a port, as per the current JDK 1.2.2 likely to be turned into a port, as per the current JDK 1.2.2
patchset. This new patchset will feature a number of bugfixes, patchset. This new patchset will feature a number of bugfixes,
which essentially get the JDK to a working state for early which essentially get the JDK to a working state for early
adopters, and an initial implementation of "native threads" based adopters, and an initial implementation of "native threads" based
on FreeBSD's userland pthreads. Unfortunately this implementation on FreeBSD's userland pthreads. Unfortunately this implementation
isn't fully functional, but is included in the hope of more isn't fully functional, but is included in the hope of
getting more eyesballs on the code (particularly experience getting more eyeballs on the code (particularly experienced
pthread programmers). We'd also like to welcome Fuyuhiko pthread programmers). We'd also like to welcome Fuyuhiko
Maruyama-san as a new committer, the usual punishment for too Maruyama-san as a new committer, the usual punishment for too
many good patches.</p> many good patches.</p>
@ -552,7 +555,7 @@
<p>I'm working on multithreading the kernel. So far I have over <p>I'm working on multithreading the kernel. So far I have over
400KB of diffs relative to todays -current (I'm keeping my tree 400KB of diffs relative to todays -current (I'm keeping my tree
updated with changes as they occur rather than get hit with a big updated with changes as they occur rather than get hit with a big
updte at the end).</p> update at the end).</p>
<p>I have split the proc structure and am changing most of the <p>I have split the proc structure and am changing most of the
kernel to pass around a thread identifier instead of a proc kernel to pass around a thread identifier instead of a proc
@ -561,7 +564,7 @@
<p>The following interfaces have been changed so far:</p> <p>The following interfaces have been changed so far:</p>
<ul> <ul>
<li>device devsw entrys</li> <li>device devsw entries</li>
<li>vfs calls</li> <li>vfs calls</li>
@ -571,7 +574,7 @@
<li>system calls</li> <li>system calls</li>
<li>sheduler</li> <li>scheduler</li>
<li>+ a lot of code in between.</li> <li>+ a lot of code in between.</li>
</ul> </ul>
@ -582,9 +585,9 @@
I'd like to check it in on a branch so others can help the I'd like to check it in on a branch so others can help the
editing but haven't worked out the best way to do it yet.</p> editing but haven't worked out the best way to do it yet.</p>
<p>I have implemented changes to the scheduler so that kse's are <p>I have implemented changes to the scheduler so that KSE's are
scheduled instead of processes, and threads sleep, letting the scheduled instead of processes, and threads sleep, letting the
kse pick up a new thread. but it's not anywhere ready yet (heck KSE pick up a new thread. but it's not anywhere ready yet (heck
it doesn't compile yet :-)</p> it doesn't compile yet :-)</p>
<p>Note that I have not yet updated the document listed above.. <p>Note that I have not yet updated the document listed above..
@ -653,7 +656,7 @@
process by porting Luke Mewburn's rc.d work from NetBSD to process by porting Luke Mewburn's rc.d work from NetBSD to
FreeBSD. This will score FreeBSD startup and shutdown FreeBSD. This will score FreeBSD startup and shutdown
dependencies without losing the traditional and much loved dependencies without losing the traditional and much loved
monolothic configuration filesystem.</p> monolithic configuration filesystem.</p>
<p>Luke Mewburn's USENIX paper and slides on the system as <p>Luke Mewburn's USENIX paper and slides on the system as
implemented in NetBSD are available here:</p> implemented in NetBSD are available here:</p>
@ -689,7 +692,7 @@
<body> <body>
<p>The goal of this project is the implementation of ATM <p>The goal of this project is the implementation of ATM
signalling and other ATM protocols by means of the netgraph(4) signalling and other ATM protocols by means of the netgraph(4)
framework. This should provide an easily extendable architecture framework. This should provide an easily extensible architecture
for using ATM on FreeBSD. Currently the full UNI4.0 stack (except for using ATM on FreeBSD. Currently the full UNI4.0 stack (except
for the LIJ capability) has been implemented, including ILMI and for the LIJ capability) has been implemented, including ILMI and
a first version of the ATM Forum API for UNI. An implementation a first version of the ATM Forum API for UNI. An implementation
@ -712,7 +715,7 @@
<body> <body>
<p>Network device cloning support has been imported from NetBSD. <p>Network device cloning support has been imported from NetBSD.
This allows virtual devices to be allocated on demand rather then This allows virtual devices to be allocated on demand rather then
being staticly allocated at compile time. Our implementation being statically allocated at compile time. Our implementation
differs slightly from that of NetBSD's in that we allow both the differs slightly from that of NetBSD's in that we allow both the
creation of specific devices (i.e. gif0) and arbitrary devices creation of specific devices (i.e. gif0) and arbitrary devices
instead of just allowing specific devices. Currently, the only instead of just allowing specific devices. Currently, the only
@ -872,7 +875,7 @@
<p>(First report)</p> <p>(First report)</p>
<p>Large cleanup and extension of FreeBSD PAM modules. All <p>Large cleanup and extension of FreeBSD PAM modules. All
modules are to be documented, consistant in style (style(9) used) modules are to be documented, consistent in style (style(9) used)
and as complete as possible WRT functionality. Mostly done.</p> and as complete as possible WRT functionality. Mostly done.</p>
</body> </body>
</project> </project>
@ -893,7 +896,7 @@
driver for OpenFirmware machines, along with support for the driver for OpenFirmware machines, along with support for the
Apple UniNorth PCI/AGP host bridge. I'm currently trying to get Apple UniNorth PCI/AGP host bridge. I'm currently trying to get
the USB hardware working so that I can get closer to having a the USB hardware working so that I can get closer to having a
console driver independant of OpenFirmware, then I'll be trying console driver independent of OpenFirmware, then I'll be trying
to get the system to get to single-user mode using NFS.</p> to get the system to get to single-user mode using NFS.</p>
</body> </body>
</project> </project>
@ -1032,7 +1035,7 @@
<h4>Management</h4> <h4>Management</h4>
<p>We are using a perforce repository for live development work, <p>We are using a perforce repository for live development work,
which can track multiple seperate long-lived works-in-progress which can track multiple separate long-lived works-in-progress
and collaborate between multiple developers at the same time on and collaborate between multiple developers at the same time on
the same change set.</p> the same change set.</p>
@ -1071,9 +1074,9 @@
<body> <body>
<p>mb_alloc is a specialized allocator for mbufs and mbuf <p>mb_alloc is a specialized allocator for mbufs and mbuf
clusters. It offers various important advantages over the old clusters. It offers various important advantages over the old
mbuf allocator, particularily for MP machines. Additionally, it mbuf allocator, particularly for MP machines. Additionally, it
is designed with the possibility of important future is designed with the possibility of important future
enchancements in mind.</p> enhancements in mind.</p>
<p>The mb_alloc code has been committed to -CURRENT a month ago <p>The mb_alloc code has been committed to -CURRENT a month ago
and appears to be holding up well. Prior to committing it, and appears to be holding up well. Prior to committing it,
@ -1141,7 +1144,7 @@
</project> </project>
<project> <project>
<title>SYN cache implemetation for FreeBSD</title> <title>SYN cache implementation for FreeBSD</title>
<contact> <contact>
<person> <person>
@ -1154,7 +1157,7 @@
<body> <body>
<p>This project brings a SYN cache implementation to FreeBSD, in <p>This project brings a SYN cache implementation to FreeBSD, in
order to make it more robust to DoS attacks. A SYN cookie order to make it more robust to DoS attacks. A SYN cookie
approach was considered, but ultimately rejected becuase it does approach was considered, but ultimately rejected because it does
not conform to the TCP protocol. The SYN cache will work with not conform to the TCP protocol. The SYN cache will work with
T/TCP, IPV6 and IPSEC, and the size of each cache element is T/TCP, IPV6 and IPSEC, and the size of each cache element is
currently is less than 1/5th the size of a normal TCP control currently is less than 1/5th the size of a normal TCP control

22
en/news/status/report-july-2002-aug-2002.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>July - August</month> <month>July - August</month>
@ -175,7 +177,7 @@
<body> <body>
<p>The GEOM code has gotten so far that it beats our current code <p>The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. The goal is for in some areas while still lacking in others. The goal is for
GEOM to be the default in 5.0-RELEASE.</p> GEOM to be the default in 5.0-RELEASE.</p>
<p>Currently work on a cryptographic module which should be able <p>Currently work on a cryptographic module which should be able
to protect a diskpartition from practically any sort of attack to protect a diskpartition from practically any sort of attack
@ -337,7 +339,7 @@
an any recent FreeBSD-current. Support to manipulate SUNI registers an any recent FreeBSD-current. Support to manipulate SUNI registers
has been added to the ATM drivers (to switch between SONET and SDH has been added to the ATM drivers (to switch between SONET and SDH
modes, for example). The ngatmsig package now includes a small and modes, for example). The ngatmsig package now includes a small and
simple call control module that mayh be used to build a simple ATM simple call control module that may be used to build a simple ATM
switch. The netgraph stuff has been patched to use the official switch. The netgraph stuff has been patched to use the official
netgraph locking.</p> netgraph locking.</p>
</body> </body>
@ -386,7 +388,7 @@
created.</p> created.</p>
<p>The sh(1) built-in, command(1), was reimplemented to conform with <p>The sh(1) built-in, command(1), was reimplemented to conform with
POSIX. Additionally, several utilities which were previously brought POSIX. Additionally, several utilities which were previously brought
up to conformance were merged into the 4-STABLE banch.</p> up to conformance were merged into the 4-STABLE branch.</p>
</body> </body>
</project> </project>
@ -431,7 +433,7 @@
smoothing out some of the rough edges, then, once all the work is done, smoothing out some of the rough edges, then, once all the work is done,
make GNOMENG the default.</p> make GNOMENG the default.</p>
<p>A long-standing annoyance in Nautilus has also been recently <p>A long-standing annoyance in Nautilus has also been recently
corrected. The desktop is no longer clutered with volume icons, and corrected. The desktop is no longer cluttered with volume icons, and
removable media (such as CDs) should now be handled correctly.</p> removable media (such as CDs) should now be handled correctly.</p>
</body> </body>
@ -487,7 +489,7 @@
OpenSSL (through the /dev/crypto device).</p> OpenSSL (through the /dev/crypto device).</p>
<p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's <p>OpenSSL 0.9.7 beta 3 was imported and patched with fixes from OpenBSD's
source tree. This permits any user-level application that use -lcrypto to source tree. This permits any user-level application that use -lcrypto to
automatically get hardware crypto acceleration. Otherwse the core crypto automatically get hardware crypto acceleration. Otherwise the core crypto
support is stable and has been in production use on -stable machines for support is stable and has been in production use on -stable machines for
several months.</p> several months.</p>
<p>Import of this work into the -current tree has started. A publicly <p>Import of this work into the -current tree has started. A publicly
@ -543,7 +545,7 @@
<p>Work is in progress to MFC a number of bug fixes related <p>Work is in progress to MFC a number of bug fixes related
to vm_map corruption into -stable. This work is probably to vm_map corruption into -stable. This work is probably
too involved to make it into the 4.7 release but is expected to too involved to make it into the 4.7 release but is expected to
be comitted just after the freeze is lifted. The corruption be committed just after the freeze is lifted. The corruption
in question typically occurs in large-memory systems under heavy in question typically occurs in large-memory systems under heavy
loads and typically panics or KPFs (kernel-page-fault's) the machine loads and typically panics or KPFs (kernel-page-fault's) the machine
in a vm_map related function.</p> in a vm_map related function.</p>
@ -750,7 +752,7 @@
<body> <body>
<p> David Xu and I have been working on cleaning up some of the work done <p> David Xu and I have been working on cleaning up some of the work done
in KSE-III and Jonathon and Dan have been working on the userland in KSE-III and Jonathon and Dan have been working on the userland
interface. The userland libray will be committed soon in a interface. The userland library will be committed soon in a
prototypical state and a working test program using that interface will prototypical state and a working test program using that interface will
hopefully accompany it. I have just committed a rework of the run hopefully accompany it. I have just committed a rework of the run
states for kernel threads that simplifies or solves some problems that states for kernel threads that simplifies or solves some problems that
@ -1012,7 +1014,7 @@
matured substantially, and large parts of it were merged to the matured substantially, and large parts of it were merged to the
main FreeBSD tree over July and August.</p> main FreeBSD tree over July and August.</p>
<p>A variety of entry point changes were made, including: component <p>A variety of entry point changes were made, including: component
names are now passed to VFS namespace VOPs; agressive caching names are now passed to VFS namespace VOPs; aggressive caching
of MAC labels in vnodes; mmap memory access downgrades on subject of MAC labels in vnodes; mmap memory access downgrades on subject
relabel; check for access()/eaccess(); checks for vnode read, relabel; check for access()/eaccess(); checks for vnode read,
write, ioctl, pool, permitting revocation post-open() by aware write, ioctl, pool, permitting revocation post-open() by aware
@ -1041,12 +1043,12 @@
main FreeBSD tree. KDE interfaces to common management main FreeBSD tree. KDE interfaces to common management
activities.</p> activities.</p>
<p>Wrote and taught full-day MAC framework tutorial at STOS <p>Wrote and taught full-day MAC framework tutorial at STOS
BSD and Darwin Security Symposium; first draft of MAC fraemwork BSD and Darwin Security Symposium; first draft of MAC framework
architecture and API guide. This is now in the Developer's architecture and API guide. This is now in the Developer's
Handbook.</p> Handbook.</p>
<p>Next couple of months will bring continued maturity improvements, <p>Next couple of months will bring continued maturity improvements,
labeling and protection of more objects; VFS performance labeling and protection of more objects; VFS performance
improvements; better support for UFS2 EAs and seperate EA improvements; better support for UFS2 EAs and separate EA
entries for each policy; improved support for LOMAC; MLS entries for each policy; improved support for LOMAC; MLS
compartments; IPsec security association labeling; improved compartments; IPsec security association labeling; improved
SEBSD FLASK/TE port; and much more.</p> SEBSD FLASK/TE port; and much more.</p>

19
en/news/status/report-june-2001.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>June</month> <month>June</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-june-2001.xml,v 1.4 2001/09/18 12:22:07 chris Exp $ $FreeBSD: www/en/news/status/report-june-2001.xml,v 1.5 2001/09/18 17:48:22 chris Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -424,7 +426,7 @@
</contact> </contact>
<body> <body>
<p>In the last two months, the OLDCARD pccard implemenation was <p>In the last two months, the OLDCARD pccard implementation was
rototilled to within an inch of its life. Many new pci cardbus rototilled to within an inch of its life. Many new pci cardbus
bridges were added. Power handling was improved. PCI Card cardbus bridges were added. Power handling was improved. PCI Card cardbus
bridges are nearly supported and should be committed in early bridges are nearly supported and should be committed in early
@ -454,7 +456,7 @@
in pmap.c after a number of problems encountered where FreeBSD in pmap.c after a number of problems encountered where FreeBSD
passes a vm_page_t to a NetBSD-derived function that expects a passes a vm_page_t to a NetBSD-derived function that expects a
vm_offset_t. Then after debugging the atomic operations code, I'm vm_offset_t. Then after debugging the atomic operations code, I'm
now at the point where VM appears to be initialised and it's now now at the point where VM appears to be initialized and it's now
hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress hanging while in sys/kern/kern_malloc.c:kmeminit(). Progress
continues. =)</p> continues. =)</p>
</body> </body>
@ -549,7 +551,7 @@
from these files (which include, among other things, the release from these files (which include, among other things, the release
notes and the supported hardware list) have been reorganized and notes and the supported hardware list) have been reorganized and
converted to SGML. This helps us produce the documentation in converted to SGML. This helps us produce the documentation in
various formats, as well as facilitating the maintainence of various formats, as well as facilitating the maintenance of
documentation for multiple architectures. This work was recently documentation for multiple architectures. This work was recently
committed to -CURRENT, and I intend to MFC it to 4-STABLE before committed to -CURRENT, and I intend to MFC it to 4-STABLE before
4.4-RELEASE.</p> 4.4-RELEASE.</p>
@ -631,9 +633,9 @@
<body> <body>
<p>mb_alloc is a new specialized allocator for mbufs and mbuf <p>mb_alloc is a new specialized allocator for mbufs and mbuf
clusters. Presently, it offers various important advantages over clusters. Presently, it offers various important advantages over
the old (status quo) mbuf allocator, particularily for MP the old (status quo) mbuf allocator, particularly for MP
machines. Additionally, it is designed with the possibility of machines. Additionally, it is designed with the possibility of
future enchancements in mind.</p> future enhancements in mind.</p>
<p>Presently in initial review &amp; testing stages, most of the <p>Presently in initial review &amp; testing stages, most of the
code is already written.</p> code is already written.</p>
@ -713,11 +715,11 @@
Control (MAC), and other architecture features, including file Control (MAC), and other architecture features, including file
system extended attributes, and improved object labeling.</p> system extended attributes, and improved object labeling.</p>
<p>Individual feature status reports are documented seperately <p>Individual feature status reports are documented separately
below; in general, basic features (such as EAs, ACLs, and kernel below; in general, basic features (such as EAs, ACLs, and kernel
support for Capabilities) will be initially available in support for Capabilities) will be initially available in
5.0-RELEASE, conditional on specific kernel options. A 5.0-RELEASE, conditional on specific kernel options. A
performance-enhanced version of EAs is currently being targetted performance-enhanced version of EAs is currently being targeted
at 6.0-RELEASE, along with an integrated capability-aware at 6.0-RELEASE, along with an integrated capability-aware
userland, and MAC support.</p> userland, and MAC support.</p>
</body> </body>
@ -822,4 +824,3 @@
</body> </body>
</project> </project>
</report> </report>

195
en/news/status/report-may-2002-june-2002.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>May - June</month> <month>May - June</month>
@ -82,13 +84,13 @@
than 256 bytes) (A full Internet view of 110k routes takes 33 MByte than 256 bytes) (A full Internet view of 110k routes takes 33 MByte
of KVM). Another problem are pointers from and to everywhere of KVM). Another problem are pointers from and to everywhere
in the routing table. This makes replacing the table very hard and in the routing table. This makes replacing the table very hard and
also significantly highers the table maintainance burden (for example also significantly increases the table maintenance burden (for example
for some kinds of updates the entire PCB has be searched lineary). for some kinds of updates the entire PCB has to be searched linearly).
Also this is a heavy burden for SMP locking. The rewrite focuses on Also this is a heavy burden for SMP locking. The rewrite focuses on
untangeling the pointer mess, making the routing table replaceable untangling the pointer mess, making the routing table replaceable
and providing a more IP optimized table (5 MByte for 110k routes). and providing a more IP optimized table (5 MByte for 110k routes).
Other new options include policy routing and some structual alignments Other new options include policy routing and some structural alignments
in the network stack for clarity, cleaness and flexibilty.</p> in the network stack for clarity, simplicity and flexibility.</p>
<p>The rewritten IP routing table will be ready for committing in <p>The rewritten IP routing table will be ready for committing in
October.</p> October.</p>
</body> </body>
@ -123,10 +125,10 @@ Graf</url>
user structure in Switzerland. The nice thing about Switzerland user structure in Switzerland. The nice thing about Switzerland
is that is has a very good mix of Modem/ISDN, leased line, Cable, is that is has a very good mix of Modem/ISDN, leased line, Cable,
ADSL and 3G/GSM/GPRS users. Every Internet access technology is ADSL and 3G/GSM/GPRS users. Every Internet access technology is
represented. The goal is to analyse the behaviour of all TCP represented. The goal is to analyze the behavior of all TCP
sessions to the monitored sites. Parameters to be analysed include sessions to the monitored sites. Parameters to be analyzed include
TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow
control behaviour, packet loss, packet loss, packet retransmit and control behavior, packet loss, packet retransmit and
timing of HTTP traffic to find optimal TCP parameter caching timing of HTTP traffic to find optimal TCP parameter caching
method.</p> method.</p>
<p>If you have any other metrics you think is useful please contact <p>If you have any other metrics you think is useful please contact
@ -194,81 +196,80 @@ September.</p>
as Marcel Moolenaar's prototype EFI GPT tools.</p> as Marcel Moolenaar's prototype EFI GPT tools.</p>
</body> </body>
</project> </project>
<!-- $FreeBSD: www/en/news/status/report-may-2002-june-2002.xml,v 1.3 2002/08/14 18:45:04 rwatson Exp $ -->
<project>
<project> <title>Libh Status Report</title>
<title>Libh Status Report</title>
<contact>
<contact> <person>
<person> <name>
<name> <given>Antoine</given>
<given>Antoine</given>
<common>Beaupre</common>
<common>Beaupre</common> </name>
</name>
<email>antoine@usw4.freebsd.org</email>
<email>antoine@usw4.freebsd.org</email> </person>
</person> </contact>
</contact>
<contact>
<contact> <person>
<person> <name>
<name> <given>Alexander</given>
<given>Alexander</given>
<common>Langer</common>
<common>Langer</common> </name>
</name>
<email>alex@freebsd.org</email>
<email>alex@freebsd.org</email> </person>
</person> </contact>
</contact>
<contact>
<contact> <person>
<person> <name>
<name> <given>Nathan</given>
<given>Nathan</given>
<common>Ahlstrom</common>
<common>Ahlstrom</common> </name>
</name>
<email>nra@freebsd.org</email>
<email>nra@freebsd.org</email> </person>
</person> </contact>
</contact>
<links>
<links> <url href="http://www.freebsd.org/projects/libh.html" />
<url href="http://www.freebsd.org/projects/libh.html" /> <url href="http://usw4.freebsd.org/~libh/">libh
<url href="http://usw4.freebsd.org/~libh/">libh new development web page.</url>
new development web page.</url> <url href="http://usw4.freebsd.org/~libh/screenshots">
<url href="http://usw4.freebsd.org/~libh/screenshots"> First snapshots of the diskeditor in action</url>
First snapshots of the diskeditor in action</url> </links>
</links>
<body>
<body> <p>Max has been busy cleaning up the user interface dark side, and has
<p>Max has been busy cleaning up the user interface dark side, and has come up with a plan to improve the build system (using an automated
come up with a plan to improve the build system (using an automated Makefile dependency generator); the UI design and the TCL glue magic
Makefile dependency generator); the UI design and the TCL glue magic (using Swig). A development page has been created on usw4, publishing
(using Swig). A develepment page has been created on usw4, publishing a lot of information about the current project status, a Changelog,
a lot of information about the current project status, a Changelog, screenshots, documentation, etc. A new listbox widget has been
screenshots, documentation, etc. A new listbox widget has been implemented, making diskeditor look nicer and more usable. The package
implemented, making diskeditor look nicer and more useable. The package system backend is being inspected and redesigned to conform to a standard
system backend is being inspected and redesigned to conform to a standard that is itself being re-thought. Indeed, the old sysinstall2.txt text has
that is itself being re-thought. Indeed, the old sysinstall2.txt text has been SGML-ized and enhanced and now provides a good (although rough) overview
been SGML-ized and enhanced and now provides a good (altough rough) overview of libh package system. This allowed the document to be enhanced with diagrams
of libh package system. This allowed the document to be enhanced with diagrams of how different procedures work. We are therefore getting closer to a
of how different procedures work. We are therefore getting closer to a real pkgAPI specification document. The package management tools have been
real pkgAPI specification document. The package management tools have been slightly enhanced and should be a bit more usable, and we started committing
sligthly enhanced and should be a bit more useable, and we started commiting regression test suites in the tree, mostly to test and maintain pkg API
regression test suites in the tree, mostly to test and maintain pkg API conformance.</p>
conformance.</p>
<p>So work continues on libh. I plan to take a look at the rhtvision port
<p>So work continues on libh. I plan to take a look at the rhtvision port to see if it would be better to use it for the tvision backend. I'll keep
to see if it would be better to use it for the tvision backend. I'll keep on working on the package system to make it really trustworthy, while Max
on working on the package system to make it really trustworthy, while Max is continuing his great work on the UI subsystem. I hope to make a new libh
is continuing his great work on the UI subsystem. I hope to make a new libh alpha release soon. Note that from now on, libh progress will be published
alpha release soon. Note that from now on, libh progress will be published on the development page.</p>
on the development page.</p> </body>
</body> </project>
</project>
<project> <project>
<title>OLDCARD</title> <title>OLDCARD</title>
@ -340,7 +341,7 @@ as it is stable.</p>
probe. The ata driver won't attach. The sio driver hangs on the probe. The ata driver won't attach. The sio driver hangs on the
first character. The wi driver is known to work well. Cardbus cards first character. The wi driver is known to work well. Cardbus cards
are generally known to work well, except for some de based cards, are generally known to work well, except for some de based cards,
which unfortuntely includes the popular Xircom cards. Many systems which unfortunately includes the popular Xircom cards. Many systems
fail to work because acpi fails to route interrupts correctly for fail to work because acpi fails to route interrupts correctly for
non-root pci bridges.</p> non-root pci bridges.</p>
</body> </body>
@ -703,14 +704,14 @@ includes porting this facility to the -current tree.</p>
requirements for full thread-control, suspension etc. that requirements for full thread-control, suspension etc. that
will be required later. </p> will be required later. </p>
<p> <p>
Before M-IV is started some small tweeking is likely Before M-IV is started some small tweaking is likely
in the central sources on M-III as we discover issues in the central sources on M-III as we discover issues
as we try to get the userland jumpstarted. These will have no as we try to get the userland jumpstarted. These will have no
effect on non-KSE processes, (i.e. all of them :-) and effect on non-KSE processes, (i.e. all of them :-) and
should not be an issue for other developers. </p> should not be an issue for other developers. </p>
<p> <p>
A tex/fig->html guru is needed to help maintain the A tex/fig->html guru is needed to help maintain the
KSE web page (not mentionned above as it is broken). KSE web page (not mentioned above as it is broken).
</p> </p>
</body> </body>
</project> </project>
@ -872,7 +873,7 @@ includes porting this facility to the -current tree.</p>
<p>Progression is slow, but the effort is maintained. Most of fb over KGI has been <p>Progression is slow, but the effort is maintained. Most of fb over KGI has been
written in parallel with a KGI display driver based on fb. written in parallel with a KGI display driver based on fb.
DDC/DDC2 is being discussed for Plug &amp; Play monitor support. KGI aims at providing DDC/DDC2 is being discussed for Plug &amp; Play monitor support. KGI aims at providing
a generic OS independant interface which would take advantage of FreeBSD I2C (iic(4)) a generic OS independent interface which would take advantage of FreeBSD I2C (iic(4))
infrastructure. infrastructure.
</p> </p>
@ -940,7 +941,7 @@ includes porting this facility to the -current tree.</p>
<body> <body>
<p> <p>
The GEOM code has gotten so far that it beats our current code The GEOM code has gotten so far that it beats our current code
in some areas while stil lacking in others. The goal is for in some areas while still lacking in others. The goal is for
GEOM to be the default in 5.0-RELEASE. GEOM to be the default in 5.0-RELEASE.
</p> </p>
<p> <p>
@ -975,8 +976,8 @@ includes porting this facility to the -current tree.</p>
with rtld, libc and our toolchain have been fixed. There is one remaining with rtld, libc and our toolchain have been fixed. There is one remaining
deadlock in the web-browser code of OO.org. If anybody like to help deadlock in the web-browser code of OO.org. If anybody like to help
us with fixing this bug (may be another libc_r bug as it looks like) us with fixing this bug (may be another libc_r bug as it looks like)
just mail me ! Unfortunalty gcc2 support got broken again with the import just mail me! Unfortunately gcc2 support got broken again with the import
of gcc2.95.4 in STABLE. Exceptions support seems to be broken again, we get of gcc2.95.4 in STABLE. Exceptions support seems to be broken again; we get
internal compiler errors with c++ exceptions code. You'll have to use gcc31 internal compiler errors with c++ exceptions code. You'll have to use gcc31
again.</p> again.</p>
@ -1050,7 +1051,7 @@ includes porting this facility to the -current tree.</p>
<body> <body>
<p> <p>
A lot of remaining PR's and Bugs have been closed. All relevant rpc A lot of remaining PR's and Bugs have been closed. All relevant rpc
concerning patches have been comitted. Thank goes to Alfred and Ian Dowese. concerning patches have been committed. Thanks go to Alfred and Ian Dowese.
</p> </p>
<p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch <p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch
available which adds IPv6 support to all remaining rpc servers. available which adds IPv6 support to all remaining rpc servers.
@ -1086,7 +1087,7 @@ includes porting this facility to the -current tree.</p>
</links> </links>
<body> <body>
<p>mb_alloc is getting some updates and a couple of optimisations. <p>mb_alloc is getting some updates and a couple of optimizations.
A new allocator interface routine should already be committed by A new allocator interface routine should already be committed by
the time this report is "published:" m_getcl() allocates an mbuf the time this report is "published:" m_getcl() allocates an mbuf
and a cluster in one shot. This is the result of months and a cluster in one shot. This is the result of months
@ -1096,7 +1097,7 @@ includes porting this facility to the -current tree.</p>
<p>Other than that, mb_alloc is being shown how to perform <p>Other than that, mb_alloc is being shown how to perform
multi-mbuf or cluster allocations without dropping the cache lock in multi-mbuf or cluster allocations without dropping the cache lock in
between (m_getcl() and m_getm() will use this). Finally, work is between (m_getcl() and m_getm() will use this). Finally, work is
being done to optimise ext_buf ref. count allocations and to provide being done to optimize ext_buf ref. count allocations and to provide
support for jumbo (> 9K) clusters.</p> support for jumbo (> 9K) clusters.</p>
</body> </body>
</project> </project>
@ -1214,10 +1215,10 @@ includes porting this facility to the -current tree.</p>
<p> <p>
I'm seriously considering to solve the lack of CPU and network I'm seriously considering to solve the lack of CPU and network
resources for the project's future evolution. Maybe the bandwidth resources for the project's future evolution. Maybe the bandwidth
problem can be resolved (several bandwidth offering are received!), problem can be resolved (several bandwidth offers have been received!),
but there is no answer about CPU problem (I have a plan to upgrade but there is no answer about CPU problems (I have a plan to upgrade
our PCs from P3-500Mhz to P4 or something better than previous). our PCs from P3-500MHz to P4 or better).
If you have interested to donate PCs to the project, please email me If you have interested in donating PCs to the project, please email me
for more detail. for more detail.
</p> </p>
</body> </body>

20
en/news/status/report-nov-2002-dec-2002.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>November-December</month> <month>November-December</month>
@ -325,7 +327,7 @@
config files are fully parsed now and their actions are config files are fully parsed now and their actions are
performed.</p> performed.</p>
<p>Future work in this area are likely to be limited to imporving <p>Future work in this area is likely to be limited to improving
the devctl interface. /dev/devctl likely will be a cloneable the devctl interface. /dev/devctl likely will be a cloneable
device in future versions. Individual device control via devctl device in future versions. Individual device control via devctl
is also planned.</p> is also planned.</p>
@ -482,10 +484,10 @@
S&#233;bastien is still maintaining the Release Notes.</p> S&#233;bastien is still maintaining the Release Notes.</p>
<p>We launched a new site, www.FreeBSD-fr.info, consisting in a French <p>We launched a new site, www.FreeBSD-fr.info, consisting in a French
Dameon News like site. Netasq have donated our new server; we will Daemon News like site. Netasq have donated our new server; we will
install it in a new hosting provider in the few next weeks. One of the install it in a new hosting provider in the few next weeks. One of the
big job now, project now, is the translation of the FAQ, and the big big job now is the translation of the FAQ, and the big
project will be the manual pages</p> project will be the manual pages.</p>
</body> </body>
</project> </project>
@ -588,7 +590,7 @@
the changes necessary to run these are sitting in the perforce the changes necessary to run these are sitting in the perforce
tree and are not in the -current or RELENG_5 cvs tree. As a tree and are not in the -current or RELENG_5 cvs tree. As a
result, the cvs derived builds (-current and the 5.0-RC series result, the cvs derived builds (-current and the 5.0-RC series
and presumably 5.0-RELEASE) are only useable on obsolete Itanium1 and presumably 5.0-RELEASE) are only usable on obsolete Itanium1
systems.</p> systems.</p>
<p>Lots of other stability and functionality fixes have been made <p>Lots of other stability and functionality fixes have been made
@ -647,7 +649,7 @@
<body> <body>
<p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user <p>KGI (Kernel Graphic Interface) is a kernel infrastructure providing user
applications with means to access hardware graphic resources (dma, applications with means to access hardware graphic resources (dma,
irqs, mmio). KGI is already available under Linux as a seperate irqs, mmio). KGI is already available under Linux as a separate
standalone project. The KGI/FreeBSD project aims at integrating KGI standalone project. The KGI/FreeBSD project aims at integrating KGI
in the FreeBSD kernel.</p> in the FreeBSD kernel.</p>
@ -693,7 +695,7 @@
<p>In addition to TCP and UDP, the other networking protocols <p>In addition to TCP and UDP, the other networking protocols
such as raw IP, IPv6, AppleTalk, and XNS need to be locked up. such as raw IP, IPv6, AppleTalk, and XNS need to be locked up.
Around 1/4 these remaining protocols have been locked and Around 1/4 these remaining protocols have been locked and
will be commited after the IP stack is locked.</p> will be committed after the IP stack is locked.</p>
<p>The protocol independent socket layer needs to be locked and <p>The protocol independent socket layer needs to be locked and
operating correctly with the protocol dependent locks. This operating correctly with the protocol dependent locks. This
@ -814,12 +816,12 @@
</contact> </contact>
<links> <links>
<url href="http://www.freebsd.org/releng/index.html">Release Enginerring <url href="http://www.freebsd.org/releng/index.html">Release Engineering
Homepage</url> Homepage</url>
</links> </links>
<body> <body>
<p>November and December were especially busy for the release egineering <p>November and December were especially busy for the release engineering
team. Scott Long joined the team to help with secretary and team. Scott Long joined the team to help with secretary and
communications tasks while Brian Somers bowed out to focus on other communications tasks while Brian Somers bowed out to focus on other
projects.</p> projects.</p>

17
en/news/status/report-november-2001.xml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD$ --> <!-- $FreeBSD: www/en/news/status/report-november-2001.xml,v 1.1 2001/12/22 01:01:27 chris Exp $ -->
<report> <report>
<date> <date>
@ -183,7 +183,7 @@
<tt>pam_self(8)</tt> <tt>pam_self(8)</tt>
, has been written; and preparations have been made for , has been written; and preparations have been made for
transitioning from the transition from
<tt>/etc/pam.conf</tt> <tt>/etc/pam.conf</tt>
to to
@ -404,7 +404,7 @@
<body> <body>
<p>Support for VLAN cloning has been merged from current and will <p>Support for VLAN cloning has been merged from current and will
ship with 4.5-RELEASE. Additionaly, new rc.conf support for ship with 4.5-RELEASE. Additionally, new rc.conf support for
cloning interfaces at boot has been MFD'd. Work is ongoing to MFC cloning interfaces at boot has been MFD'd. Work is ongoing to MFC
stf and faith cloning as well as adding cloning for ppp devices stf and faith cloning as well as adding cloning for ppp devices
and enhancing VLAN modularity.</p> and enhancing VLAN modularity.</p>
@ -732,7 +732,7 @@
<p>Although not strictly ATA, Promise has equipped me with a <p>Although not strictly ATA, Promise has equipped me with a
couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks
and does RAID0-5 in hardware. I have done a driver (its an I2O and does RAID0-5 in hardware. I have done a driver (its an I2O
device) for both -current and -stable and it works butifully with device) for both -current and -stable and it works beautifully with
hotswap the works. It will enter the tree when it is more mature, hotswap the works. It will enter the tree when it is more mature,
and I have an agreement with Promise on how we handle userland and I have an agreement with Promise on how we handle userland
control util etc. BTW it seems it can also be used as a normal 6 control util etc. BTW it seems it can also be used as a normal 6
@ -826,7 +826,7 @@
<name> <name>
<given>Doug Barton</given> <given>Doug Barton</given>
<common>Commiter</common> <common>Committer</common>
</name> </name>
<email>DougB@FreeBSD.org</email> <email>DougB@FreeBSD.org</email>
@ -899,7 +899,7 @@
<p>I have been working behind the scenes on design rather than <p>I have been working behind the scenes on design rather than
programming for this last month. I have been working however in programming for this last month. I have been working however in
the p4 tree to make the system run with the thread structure NOT the p4 tree to make the system run with the thread structure NOT
a part of the proc structure (a prerequisite fo threading)</p> a part of the proc structure (a prerequisite for threading)</p>
</body> </body>
</project> </project>
@ -953,7 +953,7 @@
</links> </links>
<body> <body>
<p>The TrustedBSD Project continued focussing development efforts <p>The TrustedBSD Project continued focusing development efforts
on fine-grained Capabilities and Mandatory Access Control this on fine-grained Capabilities and Mandatory Access Control this
month. Kernel support for capabilities is essentially complete, month. Kernel support for capabilities is essentially complete,
and efforts are underway to adapt userland applications to use and efforts are underway to adapt userland applications to use
@ -964,7 +964,7 @@
integration into the network stack. Both development trees have integration into the network stack. Both development trees have
been updated to work with recent KSE-related developments, as been updated to work with recent KSE-related developments, as
well as exist more happily in a fine-grained SMP kernel. Initial well as exist more happily in a fine-grained SMP kernel. Initial
audit-related work appears in a seperate entry.</p> audit-related work appears in a separate entry.</p>
<p>Development of TrustedBSD source code was moved to the FreeBSD <p>Development of TrustedBSD source code was moved to the FreeBSD
Perforce repository, permitting better source code management. As Perforce repository, permitting better source code management. As
@ -1023,4 +1023,3 @@
</body> </body>
</project> </project>
</report> </report>

18
en/news/status/report-sept-2002-oct-2002.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>September-October</month> <month>September-October</month>
@ -23,7 +25,7 @@
continue to be the production supported platform as 5.X is brought continue to be the production supported platform as 5.X is brought
in for landing.</p> in for landing.</p>
<p>Over the next two months, the FreeBSD Project will be focussed <p>Over the next two months, the FreeBSD Project will be focused
almost entirely on making 5.0 a success: improving system almost entirely on making 5.0 a success: improving system
stability and performance, as well as increasing the pool of stability and performance, as well as increasing the pool of
applications that build and run on 5.0. The Release Engineering applications that build and run on 5.0. The Release Engineering
@ -267,8 +269,8 @@
very strong encryption of a GEOM "disk". The algorithm has passed very strong encryption of a GEOM "disk". The algorithm has passed
informal review by a couple of seasoned crypto heavy-weights. informal review by a couple of seasoned crypto heavy-weights.
Any GEOM device can be protected with GBDE, entire physical disks, Any GEOM device can be protected with GBDE, entire physical disks,
MBR slices, BSD paritions etc etc. Booting from an encrypted MBR slices, BSD partitions etc etc. Booting from an encrypted
partition is not possible however.</p> partition is not possible, however.</p>
<p>The focus of GBDE is to protect a "cold" disk media. (FreeBSD is <p>The focus of GBDE is to protect a "cold" disk media. (FreeBSD is
not equipped well for protecting key material on a running system not equipped well for protecting key material on a running system
@ -416,7 +418,7 @@
/dev/crypto device).</p> /dev/crypto device).</p>
<p>This work was committed to the -current tree. To configure it for use <p>This work was committed to the -current tree. To configure it for use
specifiy device crypto in your system configuration file or you can load the specify device crypto in your system configuration file or you can load the
crypto module. The /dev/crypto device support is brought in with device crypto module. The /dev/crypto device support is brought in with device
cryptodev or by loading the cryptodev module. Two crypto device drivers cryptodev or by loading the cryptodev module. Two crypto device drivers
exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI exist: ubsec for Broadcom-based PCI hardware and hifn for Hifn-based PCI
@ -579,7 +581,7 @@
<body> <body>
<p>The KSE code has now all the basic kernel functionality <p>The KSE code has now all the basic kernel functionality
to start being used by the userland. There are still things to start being used by the userland. There are still things
to be done for testing and familiarisation.</p> to be done for testing and familiarization.</p>
<p>General system utilities have not yet been changed. <p>General system utilities have not yet been changed.
e.g. ps and top etc. need to know about threads.</p> e.g. ps and top etc. need to know about threads.</p>
@ -597,7 +599,7 @@
time that this report is published.</p> time that this report is published.</p>
<p>I still need someone to take over the "official" web page <p>I still need someone to take over the "official" web page
since jason left. LaTex sure isn't my thing. </p> since jason left. LaTeX sure isn't my thing. </p>
</body> </body>
</project> </project>
@ -972,12 +974,12 @@
<body> <body>
<p>Universally Unique Identifiers (UUIDs) are 128 bit values that may <p>Universally Unique Identifiers (UUIDs) are 128 bit values that may
be generated independently on seperate nodes (hosts), which, result in be generated independently on separate nodes (hosts), which result in
globally unique strings. UUIDs are also known as Globally Unique globally unique strings. UUIDs are also known as Globally Unique
Identifiers (GUIDs). The UUID support for FreeBSD (libc) conforms to the Identifiers (GUIDs). The UUID support for FreeBSD (libc) conforms to the
DCE 1.1 RPC specification.</p> DCE 1.1 RPC specification.</p>
<p>UUID suport has been added to FreeBSD -CURRENT, and will be available <p>UUID support has been added to FreeBSD -CURRENT, and will be available
in version 5.0. It is being extensively used in GPT partition handling in version 5.0. It is being extensively used in GPT partition handling
for IA-64 platform. For now, a simple manual page has been provided, for IA-64 platform. For now, a simple manual page has been provided,
which outlines information about the provided uuid routines. Many which outlines information about the provided uuid routines. Many

24
en/news/status/report-september-2001.xml
View file

@ -1,3 +1,5 @@
<!-- $FreeBSD$ -->
<report> <report>
<date> <date>
<month>September</month> <month>September</month>
@ -7,7 +9,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS"
version="1.0"> version="1.0">
<cvs:keyword name="freebsd">$FreeBSD$</cvs:keyword> <cvs:keyword name="freebsd">$FreeBSD: www/en/news/status/report-september-2001.xml,v 1.1 2001/11/12 22:25:12 chris Exp $</cvs:keyword>
</cvs:keywords> </cvs:keywords>
<section> <section>
@ -132,7 +134,7 @@
updating my snapshot site at the URL above, at least for a little updating my snapshot site at the URL above, at least for a little
while.</p> while.</p>
<p>Call for help: The hardware compatability lists need to be <p>Call for help: The hardware compatibility lists need to be
updated in the areas of the Alpha architecture, USB devices, and updated in the areas of the Alpha architecture, USB devices, and
PCCARD devices. I'm looking for volunteers to help; interested PCCARD devices. I'm looking for volunteers to help; interested
parties should contact me at the email address above. DocBook parties should contact me at the email address above. DocBook
@ -208,7 +210,7 @@
<body> <body>
<p>As you know, in march 2001 the version 2.3 of TIRPC has been <p>As you know, in march 2001 the version 2.3 of TIRPC has been
comitted together with many userland changes. Alfred Perlstein committed together with many userland changes. Alfred Perlstein
and Ian Dowse have helped me a lot with the porting effort and if and Ian Dowse have helped me a lot with the porting effort and if
I had problems with understanding the code.</p> I had problems with understanding the code.</p>
@ -385,7 +387,7 @@
finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro finish this update, OKAZAKI Tetsurou has imported Ex/Rv macro
support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv support on ja-groff-1.17.2_1. SUZUKI Koichi did most Ex/Rv
changes on Japanese manpages. He also find some issues of these changes on Japanese manpages. He also find some issues of these
macro usage on some original manapges and filed a PR. For macro usage on some original manpages and filed a PR. For
post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is post-4.4-RELEASE, now we target 4.5-RELEASE. Section 3 update is
also in progress.</p> also in progress.</p>
</body> </body>
@ -463,7 +465,7 @@
system can now be successfully mounted from ATA disks on sparc64, system can now be successfully mounted from ATA disks on sparc64,
even in DMA mode. The gem driver, which supports Sun GEM and ERI even in DMA mode. The gem driver, which supports Sun GEM and ERI
and Apple GMAC and GMAC2 ethernet adaptor, has been ported from and Apple GMAC and GMAC2 ethernet adaptor, has been ported from
NetBSD but has not yet had sufficent testing.</p> NetBSD but has not yet had sufficient testing.</p>
</body> </body>
</project> </project>
@ -664,7 +666,7 @@
</links> </links>
<body> <body>
<p>In the last month, not a lot has happenned other than settling <p>In the last month, not a lot has happened other than settling
in of the big August commit. Largely due to me having a sudden in of the big August commit. Largely due to me having a sudden
increased workload at work, and a need for increased time to be increased workload at work, and a need for increased time to be
spent elsewhere. However some design work has proceeded. The API spent elsewhere. However some design work has proceeded. The API
@ -675,12 +677,12 @@
<p>Milestone 3 will be to have the ability to generate and remove <p>Milestone 3 will be to have the ability to generate and remove
multiple threads/KSEs per process. Milestone 3 will NOT require multiple threads/KSEs per process. Milestone 3 will NOT require
that doing so will be safe. (especially in SMP systems), i.e. that doing so will be safe. (especially in SMP systems), i.e.
locking issues will not be fully addressed, so while some testign locking issues will not be fully addressed, so while some testing
will be possible, it will not be possible to actually run in this will be possible, it will not be possible to actually run in this
mode with any load.</p> mode with any load.</p>
<p>This will require allocators and destructors for the new <p>This will require allocators and destructors for the new
structures. Creation of the syscalls. Generation of an acurate structures. Creation of the syscalls. Generation of an accurate
written API for the userland crew. Writing of the upcall launch written API for the userland crew. Writing of the upcall launch
code. Production of a userland test program (not a full thread code. Production of a userland test program (not a full thread
scheduler). Resolution of some of the more glaring scheduler). Resolution of some of the more glaring
@ -689,10 +691,10 @@
system it should behave the same as now (and be as system it should behave the same as now (and be as
reliable)).</p> reliable)).</p>
<p>Criterea for knowing when we have reached Milestione 3 is the <p>Criteria for knowing when we have reached Milestone 3 is the
ability for a simple process on an unloaded system to perform a ability for a simple process on an unloaded system to perform a
series of blocking syscalls reliably. e.g. open 2 sockets, and series of blocking syscalls reliably. e.g. open 2 sockets, and
send data on one, after having done a read on another,and then send data on one, after having done a read on another, and then
'respond' in like manner..</p> 'respond' in like manner..</p>
</body> </body>
</project> </project>
@ -751,7 +753,7 @@
reasonably confident that the latest patchset is a stable release reasonably confident that the latest patchset is a stable release
of the core JDK 1.3.1 tools and classes, when the default "green" of the core JDK 1.3.1 tools and classes, when the default "green"
threads subsystem is used. This is mostly thanks to hard work by threads subsystem is used. This is mostly thanks to hard work by
Fuyuhiko Maruyama to stabilise and fix the code. Bill Huey has Fuyuhiko Maruyama to stabilize and fix the code. Bill Huey has
also been progressing with his work on the "native" threads also been progressing with his work on the "native" threads
subsystem, although this hasn't yet reached the stability of subsystem, although this hasn't yet reached the stability of
"green" threads. Another (arguably the) major highlight of the "green" threads. Another (arguably the) major highlight of the