Date: Mon, 25 Aug 2003 19:16:54 -0700 (PDT) From: Robert Watson <rwatson@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 36925 for review Message-ID: <200308260216.h7Q2GsOL020559@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=36925 Change 36925 by rwatson@rwatson_paprika on 2003/08/25 19:16:34 Use <filename> instead of <literal> for filenames. Pointed out by: simon@FreeBSD.org Affected files ... .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/arch-handbook/secarch/chapter.sgml#5 edit Differences ... ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/arch-handbook/secarch/chapter.sgml#5 (text+ko) ==== @@ -1733,7 +1733,7 @@ broadly, what types of mounts are permitted (read-only or otherwise). Enforcement of these protections is split between the user mountd - process, which reads the <literal>/etc/exports</literal> file + process, which reads the <filename>/etc/exports</filename> file and services mount requests, and the kernel NFS implementation, which is informed of the export rules by the mount daemon. Once a mount has taken place, each file system RPC is accompanied
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200308260216.h7Q2GsOL020559>