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

Include FreeBSD entity definitions, and use &unix instead of 'UNIX' to

Browse source 
render a (R) after the first occurrence of that word.
This commit is contained in:
Murray Stokely 2003-06-17 21:10:45 +00:00
parent 00b824feeb
commit a4085987a0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17358
4 changed files with 14 additions and 4 deletions
en_US.ISO8859-1
articles
smp
article.sgml
vm-design
article.sgml
zip-drive
article.sgml
books/arch-handbook/smp
chapter.sgml

4
en_US.ISO8859-1/articles/smp/article.sgml
View file

@ -6,6 +6,8 @@
%authors;
<!ENTITY % misc PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%misc;
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
<!--ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"-->
<!--
@ -180,7 +182,7 @@
<sect2>
<title>Interrupt Handling</title>
<para>Following the pattern of several other multi-threaded Unix
<para>Following the pattern of several other multi-threaded &unix;
kernels, FreeBSD deals with interrupt handlers by giving them
their own thread context. Providing a context for interrupt
handlers allows them to block on locks. To help avoid

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

@ -4,6 +4,9 @@
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
]>
<article>
@ -75,7 +78,7 @@
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
other hand, repeatedly make the same mistakes solved by Unix decades ago
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
right because our marketing department says so</quote>. I have little

5
en_US.ISO8859-1/articles/zip-drive/article.sgml
View file

@ -3,6 +3,9 @@
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
]>
<article>
@ -267,7 +270,7 @@
<para>You can also create a FreeBSD file-system on the ZIP disk using
&man.newfs.8;. However, the disk will only be usable on a FreeBSD
system, or perhaps a few other Unix clones that recognize FreeBSD
system, or perhaps a few other &unix; clones that recognize FreeBSD
file-systems. (Definitely not DOS or Windows.)</para>
</sect1>
</article>

4
en_US.ISO8859-1/books/arch-handbook/smp/chapter.sgml
View file

@ -6,6 +6,8 @@
%authors;
<!ENTITY % misc PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%misc;
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
<!--ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"-->
<!--
@ -180,7 +182,7 @@
<sect2>
<title>Interrupt Handling</title>
<para>Following the pattern of several other multi-threaded Unix
<para>Following the pattern of several other multi-threaded &unix;
kernels, FreeBSD deals with interrupt handlers by giving them
their own thread context. Providing a context for interrupt
handlers allows them to block on locks. To help avoid