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

- Rewording of some parts and another language improvements

Browse source
This commit is contained in:
Gabor Kovesdan 2010-01-14 15:19:07 +00:00
parent aa8483cdeb
commit 9c473e861f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=35191
1 changed files with 129 additions and 139 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

268
en/news/status/report-2009-10-2009-12.xml
View file

@ -2,7 +2,7 @@
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status
Report//EN"
"http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
<!-- $FreeBSD: www/en/news/status/report-2009-10-2009-12.xml,v 1.5 2010/01/14 14:14:56 gabor Exp $ -->
<!-- $FreeBSD: www/en/news/status/report-2009-10-2009-12.xml,v 1.6 2010/01/14 14:17:14 gabor Exp $ -->
<report>
<date>
<month>October-December</month>
@ -14,14 +14,14 @@ Report//EN"
<title>Introduction</title>
<p>This report covers &os; related projects between October and
December 2009. Obviously, this is the last report in the year 2009,
which has shown to be very important for the &os; Project. Besides
other remarkable things, a new major version of &os;, 8.0, has been
released, while the release process for 7.3 is soon to begin.</p>
December 2009. Obviously, this is the last report in 2009,
which has shown to be very important for the &os; Project. Beside
other remarkable things, a new major version of &os;, 8.0-RELEASE, has been
released, while the release process for 7.3-RELEASE is soon to begin.</p>
<p>Thanks to all the reporters for the excellent work! We hope you
enjoy the reading. Let us also use this opportunity to wish you all
happy and successful new year 2010.</p>
enjoy reading. Let us also use this opportunity to wish you all a
happy and successful new year for 2010.</p>
<p>Please note that the next deadline for submissions covering the
period between January and March 2010 is April 15th, 2010.</p>
@ -175,9 +175,9 @@ Report//EN"
<p>More HW drivers need to be ported.</p>
<p>Please let me know if you can provide remote access with
serial console to the box with ISDN/T1/E1 HW not currently
serial console to any box with ISDN/T1/E1 HW not currently
supported by DAHDI for &os; but supported by DAHDI for Linux. I
am also interested in porting drivers for FXO/FXS cards: please
am also interested in porting drivers for FXO/FXS cards. Please
let me know if you can provide a remote access or donate a
card.</p>
</task>
@ -210,28 +210,28 @@ Report//EN"
</contact>
<body>
<p>Existing ata(4) infrastructure which has been around many years
has number of problems and limitations, in respect to modern
<p>Existing ata(4) infrastructure, which has been around many years
has various problems and limitations, with respect to modern
controllers/devices support. A CAM subsystem (used for SCSI), which
is around for almost the same time, implements many of required
algorithms solving many problems in a better way. To reduce code
has been around for almost the same time, implements many of the
algorithms required to solve many problems in a better way. To reduce code
duplication and better support border cases such as ATAPI and SAS,
new CAM based ATA implementation has been started in order to use
its benefits.</p>
<p>As such, CAM infrastructure was extended to support different
transports. New transport was implemented to support PATA/SATA
buses. To support ATA disks, new CAM driver ada was written. ATAPI
<p>As such, CAM infrastructure has been extended to support different
transports. New transport has been implemented to support PATA/SATA
buses. To support ATA disks, new CAM driver ada has been written. ATAPI
devices are supported by existing SCSI drivers cd, da, sa, etc. To
support SATA port-multipliers new CAM driver pmp was written. To
support SATA port-multipliers new CAM driver pmp has been written. To
support most featured and widespread SATA controllers, new drivers
ahci(4) and siis(4) were developed.</p>
ahci(4) and siis(4) have been developed.</p>
<p>To support legacy ATA controllers, kernel option ATA_CAM was
<p>To support legacy ATA controllers, kernel option ATA_CAM has been
added. When used, it makes all ata(4) controllers directly
available to CAM, deprecating ata(4) peripheral drivers and external
APIs. To make it possible, ata(4) code was heavily refactored,
making controller driver API more strict.</p>
APIs. To make this possible, ata(4) code has been heavily refactored,
making controller driver API stricter.</p>
<p>Command queuing support gives new ATA implementation up to
double performance benefit on some workloads, whereas 20-30% is
@ -241,7 +241,7 @@ Report//EN"
cheap storages with huge capacities, by using dozens of SATA drives
in one system or external enclosures,</p>
<p>Some of that code was presented in &os; 8.0-RELEASE, but
<p>Some of that code has been presented in the recently released &os; 8.0-RELEASE but
8-STABLE includes much improved version now.</p>
</body>
@ -261,12 +261,12 @@ Report//EN"
<task>
<p>Write new, more featured driver for Marvell SATA controllers
(specs wanted).</p>
(specifications desired).</p>
</task>
<task>
<p>Write SAS-specific transport and drivers for SAS HBAs (specs
wanted). SAS controllers can support SATA devices and
<p>Write SAS-specific transport and drivers for SAS HBAs (specifications
desired). SAS controllers can support SATA devices and
multipliers, so it should fit nicely into the new
infrastructure.</p>
</task>
@ -298,25 +298,25 @@ Report//EN"
<body>
<p>Chromium is a Webkit-based web browser that is largely BSD
licensed. We ported it from linux to &os; in October and have been
posting patches and test builds periodically ever since. Chromium
licensed. We have ported it from Linux to &os; in October and have been
posting patches and test builds periodically since then. Chromium
works well on &os; &mdash; it is very fast and stable, but there
are a handful of rough edges that need to be polished up. Two
remaining bugs should probably be fixed before releasing a
chromium-devel port. We are looking for volunteers to test and
maintain this port, to make this BSD browser a viable option on the
&os; desktop.</p>
maintain this port, to make this BSD browser a viable option on
&os; desktop systems.</p>
</body>
<help>
<task>Fix sporadic rendering freezes</task>
<task>Fix javascript interpreter, v8, on i386 architecture</task>
<task>Fix JavaScript interpreter, v8, on i386 architecture</task>
</help>
</project>
<project cat='proj'>
<title>SUJ: Journaled Softupdates</title>
<title>SUJ: Journaled SoftUpdates</title>
<contact>
<person>
@ -335,24 +335,24 @@ Report//EN"
</links>
<body>
<p>I have been adding a small intent log to softupdates to
<p>I have been adding a small intent log to SoftUpdates to
eliminate the requirement for fsck after an unclean shutdown. This
work has been funded by Yahoo!, iXsystems, and Juniper. Kirk
McKusick has been aiding me with design critiques and helping me
better understand softupdates.</p>
better understand SoftUpdates.</p>
<p>Extensive testing by myself and Peter Holm has yielded a stable
patch. Current users are encouraged to follow the instructions
posted to current@ to verify stability in your own workloads.
posted to the current@FreeBSD.org mailing list to verify stability in your own workloads.
Updates are forthcoming and it is expected to be merged with
current before the end of January. Ports to older versions of &os;
will be available in SVN under alternate branches. Official
backports will be decided by re@ when current is stable.</p>
backports will be decided by re@ when 9.0-CURRENT is stable.</p>
<p>The changes are fully backwards and forwards compatible as there
are very few metadata changes to the filesystem. The journal may be
enabled or disabled on existing ffs filesystems using tunefs(8).
The log consumes 64 megabytes of space at maximum and fsck time is
enabled or disabled on existing FFS filesystems using tunefs(8).
The log consumes 64 MB of space at maximum and fsck time is
bounded by the size of the log rather than the size of the
filesystem. Other details are available in my technical
journal.</p>
@ -393,12 +393,12 @@ Report//EN"
</links>
<body>
<p>Most of the recent activity was dealing with the 8.0 release
process. As an experiment, we tried to decouple the ports QA
<p>Most of the recent activity has been dealing with the 8.0-RELEASE
process. As an experiment, we have tried to decouple the ports QA
timeline as much as possible from the src QA timeline. Although
this meant that the impact on people actively maintaining and using
ports was much less than in previous releases, it still has not
solved the problem of the release going out with an stale set of
ports has been much less than in previous releases, it still has not
solved the problem of the release going out with a stale set of
packages. We are still trying to come up with a better solution for
the problem.</p>
@ -411,8 +411,8 @@ Report//EN"
the last report.</p>
<p>There has been some discussion of when to drop regular package
builds for 6.x, but no decision has been made yet. The cluster, and
the portmgrs, are struggling to keep up with so many branches being
builds for 6.X but no decision has been made yet. The cluster and
the port managers are struggling to keep up with so many branches being
active all at the same time.</p>
<p>Mark Linimon continues to make progress on the cluster nodes.
@ -430,14 +430,14 @@ Report//EN"
machine itself are much harder. Complicating the matter is that
there are several periodic processes (ZFS backup, ZFS expiration,
and errorlog compression, among others) that can combine to slow
that machine significantly. The interaction of all these
simultaneously is proving difficult to quantify.</p>
that machine significantly. The simultaneous interaction of all these
is proving difficult to quantify.</p>
<p>Between pav and miwi, many more experimental ports runs have
<p>Between Pav Lucistnik and Martin Wilke, many more experimental ports runs have
been completed and committed.</p>
<p>We have added 3 new committers since the last report, and 1
older one has rejoined.</p>
older one has rejoined us.</p>
</body>
<help>
@ -450,8 +450,8 @@ Report//EN"
to get the ports in the shape they really need to be in.</task>
<task>Although we have added many maintainers, we still have more
than 4,700 unmaintained ports (see, for instance, the list on
portsmon). (The percentage remains steady at just over 22%.) We are
than 4,700 unmaintained ports. (See, for instance, the list on
portsmon. The percentage remains steady at just over 22%.) We are
always looking for dedicated volunteers to adopt at least a few
unmaintained ports. As well, the packages on amd64 and especially
sparc64 lag behind i386, and we need more testers for those.</task>
@ -477,25 +477,25 @@ Report//EN"
<p>The main thing that has taken place since the last Status Report
is that I have gotten to the bottom of the remaining PCI problems
with Sun Fire V215/V245 and support for these has been completed
and since r202023 now is part of HEAD. With some luck it will also
and since r202023 now is part of 9.0-CURRENT. With some luck it will also
be part of the upcoming 7.3-RELEASE.</p>
<p>In other news:</p>
<ul>
<li>Two bugs in the NFS server causing unaligned accesses and
<li>Two bugs in the NFS server causing unaligned access and
thus panics on sparc64 and all other architectures with strict
alignment requirements (basically all Tier 2 ones) have been
alignment requirements (basically all Tier-2 ones) have been
fixed. There likely will be a 8.0-RELEASE Erratum Notice released
for these.</li>
<li>&os; has been adopted to the changed firmware of newer Sun
Fire V480 (those equipped with version 7 Schizo bridges) and was
Fire V480 (those equipped with version 7 Schizo bridges) and has been
reported to now run fine on these. The necessary change will be
part of 7.3-RELEASE. Unfortunately, using the on-board NICs in
older models of Sun Fire V480 (at least those equipped with
version 4 Schizo bridges) under &os; still leads to the firmware
issuing a FATAL RESET due to what appears to be a CPU bug which
issuing a FATAL RESET due to what appears to be a CPU bug, which
needs to be worked around.</li>
<li>Work on supporting Sun Fire V1280 has been started but still
@ -524,17 +524,17 @@ Report//EN"
</contact>
<body>
<p>Recently a bunch of new device IDs have been added for the
u3g(4) cellular wireless driver, the list should be comparable with
<p>Recently, a bunch of new device IDs have been added for the
u3g(4) cellular wireless driver, the list should be comparable now with
other operating systems around. A lot of these devices have a
feature where the unit first attaches as a disk or cdrom that
contains the Win/Mac drivers, this state should be detected by the
feature where the unit first attaches as a disk or CD-ROM that
contains the Win/Mac drivers. This state should be detected by the
u3g driver and the usb device is sent a command to switch to modem
mode. This has been working for quite some time but as its
mode. This has been working for quite some time but as it is
implemented differently for each vendor I am looking for feedback
on any units where the auto switchover is not working (or the init
is not recognized at all). Please ensure you are running an up to
date kernel from head r201681 or later, or stable/8 if r201681 has
date kernel from 9.0-CURRENT r201681 or later, or 8-STABLE if r201681 has
been merged by the time of publication.</p>
</body>
</project>
@ -581,17 +581,17 @@ Report//EN"
<body>
<p>We are happy to announce that Benedict Reuschling is now free
from mentorship and can commit to the doc-tree on his own.</p>
from mentorship and can commit to the documentation tree on his own.</p>
<p>Since the last status report, the German Documentation Team has
chased updates to various sections of the &os; handbook, FAQ and
the german website. Many handbook pages were updated to the latest
chased updates to various sections of the &os; Handbook, FAQ and
the German website. Many handbook pages have been updated to the latest
version, including chapters about configuration, disks, kernel
configuration, printing, multimedia and virtualization.</p>
<p>We require help from volunteers who are willing to contribute
<p>We require help from volunteers that are willing to contribute
bug fixes or translations. The following documents need active
maintainership and are a good training-ground for those willing to
maintainership and are a good training ground for those willing to
join the translation team:</p>
<ul>
@ -640,10 +640,10 @@ Report//EN"
<body>
<p>There is one article translation pending review. Apart from this,
neither translation nor maintainance work has been done. We need
neither translations nor maintainance work have been done. We need
more volunteers, mostly translators but we are glad to have
more reviewers, as well. One can join by simply subscribing to
the translators' mailing list, where all the work is done.</p>
the translators' mailing list where all the work is done.</p>
</body>
<help>
@ -691,8 +691,8 @@ Report//EN"
<body>
<p>In the last months, no new translation has been added.
Lacking human resources, we can only manage the existing
documentation and web page translations. If you are interested
Lacking human resources, we can only manage to keep the existing
documentation and web page translations up to date. If you are interested
in helping us, please contact us via the the email addresses
noted above.</p>
</body>
@ -734,10 +734,10 @@ Report//EN"
</links>
<body>
<p>Since the last report we have seen a growth of 2000 users on our
Forums resulting in ca. 10.000 registered users at this time. The
posts count is about to reach 60.000 soon, which are contained in
almost 9000 threads.</p>
<p>Since the last report we have seen a growth of 2,000 users on our
forums resulting in approximately 10,000 registered users at this time. The
posts count is about to reach 60,000 soon, which are contained in
almost 9,000 threads.</p>
<p>The sign-up rate still hovers between 50-100 each week. The
total number of visitors (including 'guests') is currently hard to
@ -745,13 +745,13 @@ Report//EN"
userbase.</p>
<p>New topics and posts are actively 'pushed out' to search
engines. This in turn makes the Forums show up in search results
engines. This in turn makes the forums show up in search results
more and more often, making it a valuable and very accessible
source of information for the &os; community.</p>
<p>One of the contributing factors to the Forums' success is their
<p>One of the contributing factors to the forums' success is their
'BSD-style' approach when it comes to administration and
moderation. The Forums have a strong and unified identity and are
moderation. The forums have a strong and unified identity and are
very actively moderated, spam-free, and with a core group of very
active and helpful members, dispensing many combined decades' worth
of knowledge to starting, intermediate and professional users of
@ -784,14 +784,14 @@ Report//EN"
<p>This work allows Linux applications using V4L video calls to
work with existing &os; video drivers that provide V4L interfaces.
It is tested and working with the net/skype port and also with
browser-based Flash apps that access webcams. It is tested on
browser-based Flash applications that access webcams. It is tested on
&os;-8.0/amd64 and &os;-7.2/i386. An early version has been
committed to head and work is in progress to commit the latest
committed to 9.0-CURRENT and work is in progress to commit the latest
version and then MFC.</p>
<p>Note: to be clear, this does not add V4L support to all webcams.
The &os; camera driver must already offer V4L support itself in
order for a Linux app to be able to use that camera. The
order for a Linux application to be able to use that camera. The
multimedia/pwcbsd port provides the pwc(4) driver that already has
V4L support. If your camera is supported by a different driver, you
will need to enhance that driver to add V4L support.</p>
@ -820,7 +820,7 @@ Report//EN"
<body>
<p>The webcamd daemon enables hundreds of different USB based
webcam devices to be used under the &os;-8/9 operating system. The
webcam daemon is basically an application which is a port of
webcam daemon is basically an application, which is a port of
Video4Linux USB webcam drivers into userspace on &os;. The daemon
currently depends on libc, pthreads, libusb and the VIDEO4BSD
kernel module.</p>
@ -850,15 +850,15 @@ Report//EN"
<links/>
<body>
<p>Historically, FreeBSD has limited the number of supplemental
<p>Historically, &os; has limited the number of supplemental
groups per process to 15 (NGROUPS_MAX was incorrectly declared to be
16). In FreeBSD 8.0 we raised the limit to 1023, which should be
16). In FreeBSD 8.0-RELEASE we raised the limit to 1023, which should be
sufficient for most users and will be acceptably efficient for
incorrectly written applications that statically allocate
NGROUPS_MAX + 1 entries.</p>
<p>Because some systems such as Linux 2.6 support a larger
group limit, we have further relaxed this restriction in -CURRENT and
group limit, we have further relaxed this restriction in 9.0-CURRENT and
made kern.ngroups a tunable value, which supports values between 1023
and INT_MAX - 1. We plan to merge this to 8-STABLE before
8.1-RELEASE.</p>
@ -895,10 +895,10 @@ Report//EN"
<p>This import is based on OpenBSD 4.5 state of pf(4). It includes
many improvements over the code currently present in &os;. The
actual new feature present in pf45 repository is support for
divert(4) which should allow tools like snort_inline to work with
divert(4), which should allow tools like snort_inline to work with
pf(4) too.</p>
<p>Currently the pf(4) import is considered stable with normal
<p>Currently, the pf(4) import is considered stable with normal
kernel, as well as VIMAGE enabled kernels.</p>
</body>
@ -930,8 +930,8 @@ Report//EN"
</links>
<body>
<p>Native NFSv4 ACL support in ZFS and UFS was merged into HEAD. It
is expected to be MFCed in order to make it into FreeBSD 8.1.</p>
<p>Native NFSv4 ACL support in ZFS and UFS has been committed into 9.0-CURRENT. It
is expected to be MFCed in order to make it into FreeBSD 8.1-RELEASE.</p>
</body>
<help>
@ -1011,7 +1011,7 @@ Report//EN"
</links>
<body>
<p>The base/projects/mips branch has been merged into base/head.
<p>The base/projects/mips branch has been merged into 9.0-CURRENT.
The merge is complete and the sanity tests have passed. The code
has booted on both a Ubiquiti RouterStation (big endian) as well as
in gxemul (little endian).</p>
@ -1041,7 +1041,7 @@ Report//EN"
code into the tree.</li>
<li>A port, donated by RMI, to their XLR series of SoCs. This
port is single core only as well. The code reaches multi-user but
port is single core only, as well. The code reaches multi-user but
should be considered beta quality for the moment. Randal Stewart
(rrs@FreeBSD.org) has been driving the efforts to integrate this
into the tree.</li>
@ -1072,12 +1072,9 @@ Report//EN"
the sibyte, Octeon and XLR processors.</li>
</ul>
<p>I am sure there are minor items I have forgotten. If so, please
forgive any omission on my part...</p>
<p>he branch had been updated incorrectly several times over the
<p>The development branch had been updated incorrectly several times over the
past year, and the damage was too much to repair. We've retired the
branch and will do further mips development in "head" for the time
branch and will do further mips development in 9.0-CURRENT for the time
being. If you have a checked out tree, the suggested way to update
the projects/mips tree you have is to do a "svn switch
svn://svn.freebsd.org/base/head" in that tree.</p>
@ -1092,7 +1089,7 @@ Report//EN"
<help>
<task>We are still investigating how feasible merging all this work
into stable/8 will be, as it represents a huge leap forward in code
into 8-STABLE will be, as it represents a huge leap forward in code
stability and quality.</task>
</help>
</project>
@ -1117,45 +1114,45 @@ Report//EN"
</links>
<body>
<p>The purpose of this project is to provide FreeBSD with support for the
<p>The purpose of this project is to provide &os; with support for the
Flattened Device Tree (FDT) technology, the mechanism for describing
computer hardware resources, which cannot be probed or self enumerated, in
a uniform and portable way. The primary consumer of this technology are
embedded FreeBSD platforms (ARM, AVR32, MIPS, PowerPC), where a lot of
designs are based on similar chips, but have different assignment of pins,
designs are based on similar chips but have different assignment of pins,
memory layout, addresses bindings, interrupts routing and other resources.</p>
<p>Current state highlights:</p>
<ul>
<li>Environment, support tools</li>
<li>Environment, supported tools</li>
<ul>
<li>integrated device tree compiler (dtc) and libfdt into FreeBSD
<li>Integrated device tree compiler (dtc) and libfdt into &os;
userspace, kernel and loader build</li>
</ul>
<li>loader(8)</li>
<ul>
<li>full support for device tree blob handling</li>
<li>Full support for device tree blob handling</li>
<li>load, traverse, modify (including add/remove) device tree
<li>Load, traverse, modify (including add/remove) device tree
nodes and properties</li>
<li>pass the device tree blob to the kernel</li>
<li>Pass the device tree blob to the kernel</li>
<li>both ARM and PowerPC loader(8) supported</li>
<li>Both ARM and PowerPC loader(8) supported</li>
</ul>
<li>kernel side FDT support (common)</li>
<li>Kernel side FDT support (common)</li>
<ul>
<li>developed OF interface for FDT-backed platforms</li>
<li>Developed OF interface for FDT-backed platforms</li>
<li>ofw_bus I/F (and /dev/openfirm) available with FDT</li>
<li>integrated FDT resources representation with newbus (fdtbus
<li>Integrated FDT resources representation with newbus (fdtbus
and simplebus drivers)</li>
</ul>
@ -1169,12 +1166,12 @@ Report//EN"
<li>ARM kernel (Marvell Orion, Kirkwood and Discovery SOC)</li>
<ul>
<li>work in progress on integrating FDT infrastructure with ARM
<li>Work in progress on integrating FDT infrastructure with ARM
platform code</li>
</ul>
</ul>
<p>Work on this project is sponsored by the FreeBSD Foundation.</p>
<p>Work on this project has been sponsored by the FreeBSD Foundation.</p>
</body>
<help>
@ -1212,34 +1209,27 @@ Report//EN"
<body>
<p>HAST software will provide synchronous replication of any GEOM
provider (eg. disk, partition, mirror, etc.) or file from one &os;
machine (primary node) to another one (secondary node).
<br />
machine (primary node) to another one (secondary node).</p>
Because data is replicated on block level neither application, no
<p>Because data is replicated on block level neither application, no
file systems have to be modified to take advantage of this
functionality.
<br />
functionality.</p>
The functionality that HAST software will provide is very similar
to the functionality provided by the DRBD project for Linux.
<br />
<p>The functionality that HAST software will provide is very similar
to the functionality provided by the DRBD project for Linux.</p>
The HAST project is sponsored by the &os; Foundation.
<br />
<p>The HAST project is sponsored by the &os; Foundation.</p>
Work is progressing well, first milestone was reached in December
2009 and the project completion date is January 31st 2010.
<br />
<p>Work is progressing well, first milestone was reached in December
2009 and the project completion date is January 31, 2010.</p>
Check out &os; mailing lists for patches to test in February and
wish me good luck!
<br />
<p>Check out &os; mailing lists for patches to test in February and
wish me good luck!</p>
And BTW, don't forget to donate to the &os; Foundation, as your
donations make projects like this possible.
<br />
<p>And by the way, don't forget to donate to the &os; Foundation, as your
donations make projects like this possible.</p>
Thank you!</p>
<p>Thank you!</p>
</body>
</project>
@ -1295,7 +1285,7 @@ Report//EN"
</contact>
<body>
<p>Important changes regarding FreeBSD TDM Framework since last Status
<p>Important changes regarding &os; TDM Framework since last Status
Report:</p>
<ul>
@ -1307,7 +1297,7 @@ Report//EN"
<li>Working Si3215, Si3050 codec drivers on corresponding FXS, FXO
ports.</li>
<li>Demo application which is capable of manipulating voiceband
<li>Demo application, which is capable of manipulating voiceband
channel and codec state, starting/stopping channel transfers and
echoing on single channel.</li>
@ -1328,7 +1318,7 @@ Report//EN"
</project>
<project cat='proj'>
<title>utmpx for FreeBSD</title>
<title>POSIX utmpx for FreeBSD</title>
<contact>
<person>
@ -1349,8 +1339,8 @@ Report//EN"
</links>
<body>
<p>On January 13 I removed the utmp user accounting database and
replaced it by POSIX utmpx. Unfortunately the upgrade path is a bit
<p>On January 13, I removed the utmp user accounting database and
replaced it by POSIX utmpx. Unfortunately, the upgrade path is a bit
bumpy, because the utmp interface provided almost no library
interface to interact with the database files.</p>
@ -1360,11 +1350,11 @@ Report//EN"
</body>
<help>
<task>Get a list of broken ports.</task>
<task>Get a list of broken ports</task>
<task>Fix them to comply to standards.</task>
<task>Fix them to comply to standards</task>
<task>Send patches upstream.</task>
<task>Send patches upstream</task>
</help>
</project>
@ -1419,9 +1409,9 @@ Report//EN"
</links>
<body>
<p>As 8.0-RELEASE is out, BSD bc/dc can be now committed, we are
only waiting for the portbuild exp-run to make sure there are no
regressions after this change. BSD grep is stalled because of
<p>As 8.0-RELEASE is out, BSD bc/dc can be now committed to 9.0-CURRENT. We are
only waiting for an experimental package building to make sure there are no
regressions after this change. BSD grep is complete but it cannot be integrated yet because of
some regex library issues. We need first a fast and modern regex
library so that we can change to BSD grep. BSD sort has few
incomplete features and needs some performance review.</p>