Use &unix; macro for conistent capitalization of Unix throughout this

book.
This commit is contained in:
Murray Stokely 2005-05-04 15:44:19 +00:00
parent b4194b3507
commit 59c15dde22
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=24448
2 changed files with 5 additions and 5 deletions

View file

@ -25,7 +25,7 @@
system statically or loaded on demand through the dynamic kernel
linker facility `kld'.</para>
<para>Most devices in a Unix-like operating system are accessed
<para>Most devices in a &unix;-like operating system are accessed
through device-nodes, sometimes also called special files.
These files are usually located under the directory
<filename>/dev</filename> in the filesystem hierarchy.
@ -133,7 +133,7 @@ KMOD=skeleton
<sect1 id="driverbasics-access">
<title>Accessing a device driver</title>
<para>Unix provides a common set of system calls for user
<para>&unix; provides a common set of system calls for user
applications to use. The upper layers of the kernel dispatch
these calls to the corresponding device driver when a user
accesses a device node. The <command>/dev/MAKEDEV</command>

View file

@ -24,7 +24,7 @@
<indexterm><primary>Jail</primary></indexterm>
<indexterm><primary>root</primary></indexterm>
<para>On most UNIX systems, root has omnipotent power. This promotes
<para>On most &unix; systems, root has omnipotent power. This promotes
insecurity. If an attacker were to gain root on a system, he would
have every function at his fingertips. In FreeBSD there are
sysctls which dilute the power of root, in order to minimize the
@ -177,7 +177,7 @@ SYSCTL_INT(_jail, OID_AUTO, set_hostname_allowed, CTLFLAG_RW,
int jail_socket_unixiproute_only = 1;
SYSCTL_INT(_jail, OID_AUTO, socket_unixiproute_only, CTLFLAG_RW,
<![CDATA[&jail]]>_socket_unixiproute_only, 0,
"Processes in jail are limited to creating UNIX/IPv4/route sockets only
"Processes in jail are limited to creating &unix;/IPv4/route sockets only
");
int jail_sysvipc_allowed = 0;
@ -271,7 +271,7 @@ error = chroot(p, <![CDATA[&ca]]>);</programlisting>
<para>These next three lines in the source are very important,
as they specify how the kernel recognizes a process as
jailed. Each process on a Unix system is described by its
jailed. Each process on a &unix; system is described by its
own proc structure. You can see the whole proc structure in
<filename>/usr/include/sys/proc.h</filename>. For example,
the p argument in any system call is actually a pointer to