This file is now generated using src/tools/tools/pciid/mk_pci_vendors.pl,
which merges the Boemler and Heckenbach lists used for rev 1.2.
For now, mk_pci_vendors.pl is called with the -l option, which uses
the entry with the longer description where the same device or vendor
is found in both lists.
If it turns out that this causes to much "back-and-forth" in future
deltas, we can drop the use of the -l option.
date of the announcement)
couple of URL fixes. From: Petri Koistinen <pkoistin@cs.stadia.fi>
(http://www.byte.com/art/9410/sec8/art3.htm is now a dangling link.
any alternative URL?)
announcement from JKH (back when he was still working for Lotus)
http://minnie.tuhs.org/cgi-bin/newsread?23150
This also means that if, as Microsoft say, Linux is a Cancer, FreeBSD is
a Scorpio.
At least some IBM drives support the Standby Condition Timer (i. e.
they allow for an automatic spindown).
Update copyright for 2001. I don't want to insert my name for just
one mode page definition, do people think that `The FreeBSD Project'
is OK?
current format. The new database also has subvendor/subdevice ID
information, which we aren't using for now. This adds 272 new vendors
and 376 new device identifiers, as well as cleaning out some of the
bad entries in the previous revision.
We now combine data from:
http://www.yourvote.com/pcihttp://members.hyperlink.com.au/~chart/pci.htm
by other tools as well).
Note that omissions and corrections for this file should be resolved
via http://www.yourvote.com/pci, as this is the master source for this
database, rather than by editing this file directly.
code designation, as it's code 275.
Include the URL of the ISO3166 Maintenance Agency.
Remove FX, it's been deprecated.
Update the Palestine entry with the correct code and description.
PR: docs/22570
Submitted by: Laurent Wacrenier <lwa@victor.teaser.fr>
related patches. These include:
* Mode page editting can be scripted. This involves two
things: first, if stdin is not a tty, changes are read from
stdin rather than invoking $EDITOR. Second, and more
importantly, not all modepage entries must be included in the
change set. This means that camcontrol can now gracefully handle
more intrusive editting from the $EDITOR, including removal or
rearrangement of lines. It also means that you can do stuff
like:
# echo "WCE: 1" | camcontrol modepage da3 -m 8 -e
# newfs /dev/da3
# echo "WCE: 0" | camcontrol modepage da3 -m 8 -e
* Range-checking on user-supplied input values. modeedit.c now
uses the field width specifiers to determine the maximum
allowable value for a field. If the user enters a value larger
than the maximum, it clips the value to the max and warns the
user. This also involved patching cam_cmdparse.c to be more
consistent with regards to the "count" parameter to arg_put
(previously is was the length of strings and 1 for all integral
types). The cam_cdbparse(3) man page was also updated to reflect
the revised semantics.
* In the process, I removed the 64 entry limit on mode pages (not
that we were even close to hitting that limit). This was a nice
side-effect of the other changes.
* Technically, the new mode editting functionality allows editting
of character array entries in mode pages (type 'c' or 'z'),
however since buff_encode doesn't grok them it is currently
useless.
* Camcontrol gained two new options related to mode pages: -l and
-b. The former lists all available mode pages for a given
device. The latter forces mode page display in binary format
(the default when no mode page definition was found in
scsi_modes).
* Added support for mode page names to scsi_modes. Allows names to
be displayed alongside mode numbers in the mode page
listing. Updated scsi_modes to use the new functionality. This
also adds the semicolon into the scsi_modes syntax as an
optional mode page definition terminator. This is needed to name
pages without providing a page format definition.
* Updated scsi_all.h to include a structure describing mode page
headers.
* Added $FreeBSD$ line to scsi_modes.
Inspired by: dwhite
Reviewed by: ken
Correct derivation of Eighth Edition Research UNIX. According to dmr,
it was derived from 4.1cBSD; according to the 4.4BSD book, it was
derived from 4.1BSD. Since dmr did the work, he's more likely to be
correct.
Correct typos.
Remove dead URLs.
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 -----
