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

- Use trademark entities.

Browse source 
- Add trademark attributions.
This commit is contained in:
Simon L. B. Nielsen 2003-10-18 10:39:16 +00:00
parent 6e1fe5cacb
commit 09f3c92252
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=18478
5 changed files with 72 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

16
en_US.ISO8859-1/articles/vm-design/article.sgml
View file

@ -7,6 +7,8 @@
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN">
%trademarks;
]>
<article>
@ -27,6 +29,14 @@
</author>
</authorgroup>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.linux;
&tm-attrib.microsoft;
&tm-attrib.opengroup;
&tm-attrib.general;
</legalnotice>
<abstract>
<para>The title is really just a fancy way of saying that I am going to
attempt to describe the whole VM enchilada, hopefully in a way that
@ -70,14 +80,14 @@
be. This is an important distinction to make and one that is
unfortunately lost to many people. The biggest error a programmer can
make is to not learn from history, and this is precisely the error that
many other modern operating systems have made. NT is the best example
many other modern operating systems have made. &windowsnt; is the best example
of this, and the consequences have been dire. Linux also makes this
mistake to some degree&mdash;enough that we BSD folk can make small
jokes about it every once in a while, anyway. Linux's problem is simply
one of a lack of experience and history to compare ideas against, a
problem that is easily and rapidly being addressed by the Linux
community in the same way it has been addressed in the BSD
community&mdash;by continuous code development. The NT folk, on the
community&mdash;by continuous code development. The &windowsnt; folk, on the
other hand, repeatedly make the same mistakes solved by &unix; decades ago
and then spend years fixing them. Over and over again. They have a
severe case of <quote>not designed here</quote> and <quote>we are always
@ -796,7 +806,7 @@
This allows the cache to be left alone across a process context
switch, which is very important.</para>
<para>But in the Unix world you are dealing with virtual address
<para>But in the &unix; world you are dealing with virtual address
spaces, not physical address spaces. Any program you write will
see the virtual address space given to it. The actual
<emphasis>physical</emphasis> pages underlying that virtual