Last week's thought-provoking debate - continued this week; the discussion focused on a a few possible + continued this week; the discussion focused on a few possible workarounds for circumventing the well-known ad driver bug early in the booting process. It seems that an effective solution has not still been implemented. However, a number of diff --git a/en/conspectus/stable/2000/06/12.sgml b/en/conspectus/stable/2000/06/12.sgml index b522f34423..4763b1071e 100644 --- a/en/conspectus/stable/2000/06/12.sgml +++ b/en/conspectus/stable/2000/06/12.sgml @@ -1,6 +1,6 @@ - + %includes;]> @@ -301,8 +301,8 @@ character for a hostname? I think rfc1034 only gives recommendations, but doesn't insist on them. It would make sense for gethostbyname() to return results for such hosts. - In our case, we inetd was receiving connections to the smtp - port, and and we were losing mail from this particular host + In our case, inetd was receiving connections to the smtp + port, and we were losing mail from this particular host (mail_dxb.zu.ac.ae).
diff --git a/en/news/sou1999.sgml b/en/news/sou1999.sgml index 1f9f78ffe9..c1df875ce7 100644 --- a/en/news/sou1999.sgml +++ b/en/news/sou1999.sgml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -309,7 +309,7 @@ of abuse of the various tech support forum volunteers this last year and it frankly sucks. People just need to be more considerate and stop regarding free tech support as a god-given right rather than a - very special privilege. If you want on-demand tech support, to to + very special privilege. If you want on-demand tech support, go to www.freebsdmall.com and order yourself a tech support contract. You get what you pay for! :) diff --git a/en/releases/2.0/notes.sgml b/en/releases/2.0/notes.sgml index 05a9e4ad87..db7536ca04 100644 --- a/en/releases/2.0/notes.sgml +++ b/en/releases/2.0/notes.sgml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -472,7 +472,7 @@ You will need either 10 1.44MB floppies or 12 1.2MB floppies to store just the bindist (binary distribution). These *must* be formatted using MS-DOS, using either the FORMAT command in MS-DOS or the File Manager in Microsoft Windows to prepare the floppies -(though factory preformatted floppies will also well well, provided +(though factory preformatted floppies will also work well, provided that they haven't been previously used for something else). After you've formatted the floppy disks, you'll need to copy the diff --git a/en/releases/2.1.5R/announce.sgml b/en/releases/2.1.5R/announce.sgml index 1d6ec6eb08..aa6b921529 100644 --- a/en/releases/2.1.5R/announce.sgml +++ b/en/releases/2.1.5R/announce.sgml @@ -1,6 +1,6 @@ - + %includes; ]> @@ -11,12 +11,12 @@ 2.1.5-RELEASE is now available on ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from -from Walnut Creek CDROM. +Walnut Creek CDROM.FreeBSD 2.1.5 represents the culmination of over a year's worth of work on the 2.1-STABLE branch of FreeBSD since it began with FreeBSD 2.0.5. In the 7 months since 2.1 -was released, many many bug fixes, updates and careful enhancements +was released, many bug fixes, updates and careful enhancements have been made, the results of which you now see here.
The STABLE branch was conceived out of the need to allow FreeBSD to diff --git a/en/releases/2.2.2R/errata.sgml b/en/releases/2.2.2R/errata.sgml index 03c32742c4..646d7c1d40 100644 --- a/en/releases/2.2.2R/errata.sgml +++ b/en/releases/2.2.2R/errata.sgml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -37,7 +37,7 @@ o Installation floppy does not boot at all - whereas the 2.2.1 floppy worked fine. I get a "panic: double fault" right after it tries to change the root device to fd0c. -Fix: The problem is that you have 48MB of RAM and something very very +Fix: The problem is that you have 48MB of RAM and something very mysterious has happened to FreeBSD twixt 2.2.1 and 2.2.2 which makes it fail with just that exact memory size. Given the popularity of 16MB simms, it also explains why none of us have seen it since we diff --git a/en/security/advisories.xml b/en/security/advisories.xml index 0f4427ac7c..c9851ed7f0 100644 --- a/en/security/advisories.xml +++ b/en/security/advisories.xml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -318,7 +318,7 @@ environment variables, configuration files, incoming TCP/UDP/ICMP packets, hostname lookups, function arguments, etc. If the length of or contents of the date received is at all subject to outside control, then the program or function should watch for this when copying it around. Specific security -issues to watch for in this are are: +issues to watch for in this are: