diff options
| author | Marc Fonvieille <blackend@FreeBSD.org> | 2005-04-23 09:12:04 +0000 |
|---|---|---|
| committer | Marc Fonvieille <blackend@FreeBSD.org> | 2005-04-23 09:12:04 +0000 |
| commit | da54ab658713ed3534e4d602c93322a826c37015 (patch) | |
| tree | 374677237517bb48a1dac4720ca20e785cf6f207 /en/news/status | |
| parent | 4f5bae987056936effb76b17f1d211b53ad4486b (diff) | |
| download | doc-da54ab658713ed3534e4d602c93322a826c37015.tar.gz doc-da54ab658713ed3534e4d602c93322a826c37015.zip | |
- Typos fixes
- some s/linux/Linux and s/openbsd/OpenBSD for document consistency
Notes
Notes:
svn path=/www/; revision=24378
Diffstat (limited to 'en/news/status')
| -rw-r--r-- | en/news/status/report-2005-01-2005-03.xml | 24 | ||||
| -rw-r--r-- | en/news/status/report-jan-2005-mar-2005.xml | 24 |
2 files changed, 24 insertions, 24 deletions
diff --git a/en/news/status/report-2005-01-2005-03.xml b/en/news/status/report-2005-01-2005-03.xml index cb6e568ce8..7421ed53bf 100644 --- a/en/news/status/report-2005-01-2005-03.xml +++ b/en/news/status/report-2005-01-2005-03.xml @@ -237,7 +237,7 @@ fast).</p> <p>As a next step a cleanup/streamlining and the possibility of - overriding the default linux base is in progress. This depends on + overriding the default Linux base is in progress. This depends on changes which need at least one testrun on the ports build cluster, so the final date for those changes depends upon the availability of the cluster resources.</p> @@ -247,7 +247,7 @@ <task>Refactoring the common RPM code into bsd.rpm.mk.</task> <task>Determining which up-to-date Linux distribution to use as the - next default linux base. Important criteria: + next default Linux base. Important criteria: <ul> <li>RPM based (to be able to use the existing infrastructure)</li> @@ -260,7 +260,7 @@ <li>available for several hardware architectures (e.g. i386, amd64, sparc64; Note: not all architectures have a working linuxolator for their native bit with, but as long as there are - no userland bits available, no motivation regarding writting the + no userland bits available, no motivation regarding writing the kernel bits will arise)</li> </ul> </task> @@ -814,7 +814,7 @@ control over which blocks get flushed to disk by the buffer daemon without having to further complicate the UFS/FFS code. One consideration is how Softupdates falls into this and whether it is - multually exclusive of journalling or if it can help provide + mutually exclusive of journalling or if it can help provide transaction ordering functionality to the journal. Research here is on-going.</p> @@ -861,11 +861,11 @@ The rebuild functionality has been changed to rebuild on userland reads, so a simple dd of the entire array will get it rebuild (what atacontrol now does). This means that the resources used for this - can be better tailored to the actualy usage pattern if needed. ATA + can be better tailored to the actually usage pattern if needed. ATA RAID now supports 10+ different RAID metadata formats, so most BIOS defined ATA RAID arrays can be picked up and used. The number of metadata formats that can be created from within FreeBSD is still - limitted though and is not a high priority feature right now.</p> + limited though and is not a high priority feature right now.</p> <p>The lowlevel infrastructure of the ATA driver has been refined even further to support "strange" chipsets much more easily and in @@ -946,7 +946,7 @@ <body> <p>ATAPI/CAM integration with the new ATA (mkIII) framework is now completed. ATAPI/CAM is now available as a loadable module - (atapicam.ko). It is also independant from the native ATAPI drivers + (atapicam.ko). It is also independent from the native ATAPI drivers again, as was the case before mkIII.</p> <p>Thanks to Scott Long and Søren Schmidt for their @@ -1186,7 +1186,7 @@ tested the changes with "make buildworld". I have been testing the new code in a production environment and things appear to be stable. Gleb Smirnoff (glebius@FreeBSD.org) has provided review - comments and I have incorported these feedback into the patch. I + comments and I have incorporated these feedback into the patch. I have discussed the IPv6 changes with two of the core KAME developers during the last IETF meeting in March 2005. They indicated that these changes may result in divergence from the KAME @@ -1287,7 +1287,7 @@ <a href="http://www.vuxml.org/freebsd/">VuXML</a> information. In addition, RESTRICTED and NO_CDROM have been added - to list of things that FreshPorts keeps track of. For unmantained + to list of things that FreshPorts keeps track of. For unmaintained ports, we recently added this message: <p> <em>There is no maintainer for this port. @@ -1546,7 +1546,7 @@ <task>I am working on thread creation performance, currently it needs considerable number of libc functions and syscalls to create a thread, I would like to introduce a syscall to create a thread in - atomicaly. That means one syscall will setup thread entry, tls, and + atomically. That means one syscall will setup thread entry, tls, and signal mask and PTHREAD_SCOPE_PROCESS/SYSTEM; in future maybe even CPU affinity masks, when userland entry code is executed, the thread is already fully setup.</task> @@ -1646,7 +1646,7 @@ preauthentication protocols (these are simple conversions of existing Linux code).</task> - <task>The openbsd dhclient program has been ported but needs a + <task>The OpenBSD dhclient program has been ported but needs a developer that will maintain it once it is brought into cvs.</task> </help> </project> @@ -2047,7 +2047,7 @@ Feature freeze and code freeze for 6.0 are coming up in May and June, and we hope to have 6.0 stable and ready for release in July or August.</p> - <p>The release engineering team has also started doing monthy + <p>The release engineering team has also started doing monthly informal snapshots of the 6-CURRENT and 5-STABLE trees. These are intended to increase the exposure of new features and get more users involved in testing and providing feedback. Snapshots can diff --git a/en/news/status/report-jan-2005-mar-2005.xml b/en/news/status/report-jan-2005-mar-2005.xml index cb6e568ce8..7421ed53bf 100644 --- a/en/news/status/report-jan-2005-mar-2005.xml +++ b/en/news/status/report-jan-2005-mar-2005.xml @@ -237,7 +237,7 @@ fast).</p> <p>As a next step a cleanup/streamlining and the possibility of - overriding the default linux base is in progress. This depends on + overriding the default Linux base is in progress. This depends on changes which need at least one testrun on the ports build cluster, so the final date for those changes depends upon the availability of the cluster resources.</p> @@ -247,7 +247,7 @@ <task>Refactoring the common RPM code into bsd.rpm.mk.</task> <task>Determining which up-to-date Linux distribution to use as the - next default linux base. Important criteria: + next default Linux base. Important criteria: <ul> <li>RPM based (to be able to use the existing infrastructure)</li> @@ -260,7 +260,7 @@ <li>available for several hardware architectures (e.g. i386, amd64, sparc64; Note: not all architectures have a working linuxolator for their native bit with, but as long as there are - no userland bits available, no motivation regarding writting the + no userland bits available, no motivation regarding writing the kernel bits will arise)</li> </ul> </task> @@ -814,7 +814,7 @@ control over which blocks get flushed to disk by the buffer daemon without having to further complicate the UFS/FFS code. One consideration is how Softupdates falls into this and whether it is - multually exclusive of journalling or if it can help provide + mutually exclusive of journalling or if it can help provide transaction ordering functionality to the journal. Research here is on-going.</p> @@ -861,11 +861,11 @@ The rebuild functionality has been changed to rebuild on userland reads, so a simple dd of the entire array will get it rebuild (what atacontrol now does). This means that the resources used for this - can be better tailored to the actualy usage pattern if needed. ATA + can be better tailored to the actually usage pattern if needed. ATA RAID now supports 10+ different RAID metadata formats, so most BIOS defined ATA RAID arrays can be picked up and used. The number of metadata formats that can be created from within FreeBSD is still - limitted though and is not a high priority feature right now.</p> + limited though and is not a high priority feature right now.</p> <p>The lowlevel infrastructure of the ATA driver has been refined even further to support "strange" chipsets much more easily and in @@ -946,7 +946,7 @@ <body> <p>ATAPI/CAM integration with the new ATA (mkIII) framework is now completed. ATAPI/CAM is now available as a loadable module - (atapicam.ko). It is also independant from the native ATAPI drivers + (atapicam.ko). It is also independent from the native ATAPI drivers again, as was the case before mkIII.</p> <p>Thanks to Scott Long and Søren Schmidt for their @@ -1186,7 +1186,7 @@ tested the changes with "make buildworld". I have been testing the new code in a production environment and things appear to be stable. Gleb Smirnoff (glebius@FreeBSD.org) has provided review - comments and I have incorported these feedback into the patch. I + comments and I have incorporated these feedback into the patch. I have discussed the IPv6 changes with two of the core KAME developers during the last IETF meeting in March 2005. They indicated that these changes may result in divergence from the KAME @@ -1287,7 +1287,7 @@ <a href="http://www.vuxml.org/freebsd/">VuXML</a> information. In addition, RESTRICTED and NO_CDROM have been added - to list of things that FreshPorts keeps track of. For unmantained + to list of things that FreshPorts keeps track of. For unmaintained ports, we recently added this message: <p> <em>There is no maintainer for this port. @@ -1546,7 +1546,7 @@ <task>I am working on thread creation performance, currently it needs considerable number of libc functions and syscalls to create a thread, I would like to introduce a syscall to create a thread in - atomicaly. That means one syscall will setup thread entry, tls, and + atomically. That means one syscall will setup thread entry, tls, and signal mask and PTHREAD_SCOPE_PROCESS/SYSTEM; in future maybe even CPU affinity masks, when userland entry code is executed, the thread is already fully setup.</task> @@ -1646,7 +1646,7 @@ preauthentication protocols (these are simple conversions of existing Linux code).</task> - <task>The openbsd dhclient program has been ported but needs a + <task>The OpenBSD dhclient program has been ported but needs a developer that will maintain it once it is brought into cvs.</task> </help> </project> @@ -2047,7 +2047,7 @@ Feature freeze and code freeze for 6.0 are coming up in May and June, and we hope to have 6.0 stable and ready for release in July or August.</p> - <p>The release engineering team has also started doing monthy + <p>The release engineering team has also started doing monthly informal snapshots of the 6-CURRENT and 5-STABLE trees. These are intended to increase the exposure of new features and get more users involved in testing and providing feedback. Snapshots can |