are from 3.x-stable which was branched quite some time after 3.0-release
(about Jan 15 if I recall correctly).
----> FreeBSD-3.0-----\----- FreeBSD-4.x-current -----....
\
3.x-stable ----> 3.1 ---> 3.2 ....
Submitted by: peter
Added upcoming releases FreeBSD 3.2, NetBSD 1.3, OpenBSD 2.5
NetBSD 1.2.1 is a patch release of NetBSD 1.2 (a branch of 1.2)
NetBSD 1.3.1, 1.3.2, 1.3.3 are a patch release of NetBSD 1.3 (a branch of 1.3).
FreeBSD 3.0, FreeBSD 3.1 and FreeBSD 3.2 are a releases
from the 3.0-stable branch.
Added FreeBSD 4.0-current.
Added FreeBSD 3.1 release date.
languages (en = English, de = German, zn = Chinese, and so on). This
complements the existing iso3166 file, which maps codes to countries.
Country code != language code.
I ran this past -core. No one voiced any objections, jkh said "fine".
The Eighth Edition is *not* descended from the Seventh Edition.
Submitted by: Greg Lehey <grog@lemis.com>
and Dennis Ritchie
Here's a quote from Dennis Ritchie, posted to Warren Toomey:
[January 1999]
----- Forwarded message from dmr -----
I also got mail from Norman Wilson today about the discussion.
This is mainly to confirm and fill out details of Wilson's account.
The Eighth Edition system started with (I believe) BSD 4.1c and
the work was done on VAX 11/750s -- our group did not get
a 780 until a while later.
Most of the operating system superstructure of BSD was retained
(in particular no one (even the indefatigable Norman)
wanted to get much into the paging code. Norman is also
right that the competitor was John Reiser's (and Tom London's)
32V descendant from another group at the Labs. In structure
this system had a lot to offer (in particular the buffer cache and the page
pool were unified, but it was clear that their work was not being
supported by their own management. It was used for a while on
our first 750 and also our first 11/780 ("alice", a name that lives
in netnews fame preceding the reach of Dejanews).
The big change leading to V8 was the scooping-out and replacement of
the character-device and networking part by the streams mechanism. Later,
Peter Weinberger added the file-system switch that enabled
remote file systems and prescient things ideas like /proc). Weinberger,
as Norman said, also did a simple-minded FFS.
The TCP/IP stack wasn't very important to us then and it has a mixed and
murky history. Much of it came from early CSRG work, but it was converted
to a streams approach by Robert Morris and subsequently fiddled over a lot.
Likewise, as Norman said, the applications (/bin and whatnot) were somewhat
of a mixture. Many were the locally-done versions, some were taken
from BSD in some incarnation, some from System V.
Dennis
----- End of forwarded message from dmr -----
uk.phone (in line with na.phone). This is a more detailed
list than the one in inter.phone.
Add uk.postcodes. I've prefixed it with `uk' to leave room
for (maybe) au.postcodes etc. (if someone feels so inclined).
Obtained from: http://www.brainstorm.co.uk/public/utils
Ok'd to use by: steve@brainstorm.co.uk (Steve Crook)
Some firmware versions becomes unreliable when these bits are not preserved,
e.g. ST15150N-0017 breaks if the DISC bit is cleared in the caching page.
This happened by default when editing the page.
configure ee to use emacs key-bindings
do not expand tabs into spaces
dont truncate lines at the right margin
Submitted by: Aled Morris <aledm@routers.co.uk>
Reviewed by: jkh
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
partial sync with iso3166
2-letter country codes added to na.phone for Caribbean islands
(except Cayman Islands and Monserrat since the 2-letter codes clash with
Kentucky and Mississippi)
changed city codes in Finland (from Ville.Eerola@vlsi.fi)
changed city codes in Australia (from danny@hilink.com.au)
books that I have laying around my house. Please check to see if your
state is now correct :-). I know that the one area code states are correct,
as well as CO and KS, but although I've tried to be careful about the
rest, I may have goofed.
