Files
oldlinux-files/docs/Install-Guide/install-guide-2.2.2/node160.html
2024-02-19 00:23:35 -05:00

49 lines
3.1 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3O//DTD W3 HTML 2.0//EN">
<!Converted with LaTeX2HTML 95.1 (Fri Jan 20 1995) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds >
<HEAD>
<TITLE>4.1.4 Setting the rules</TITLE>
</HEAD>
<BODY>
<meta name="description" value="4.1.4 Setting the rules">
<meta name="keywords" value="gs">
<meta name="resource-type" value="document">
<meta name="distribution" value="global">
<P>
<BR> <HR><A NAME=tex2html3814 HREF="node161.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html3812 HREF="node156.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html3806 HREF="node159.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html3816 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html3817 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html3815 HREF="node161.html">4.1.5 What it all </A>
<B>Up:</B> <A NAME=tex2html3813 HREF="node156.html">4.1 About RootHats, </A>
<B> Previous:</B> <A NAME=tex2html3807 HREF="node159.html">4.1.3 Dealing with users</A>
<BR> <HR> <P>
<H2><A NAME=SECTION00614000000000000000>4.1.4 Setting the rules</A></H2>
<P>
<A NAME=4228>&#160;</A>
The best way to run a system is not with an iron fist. That may be how
you run the military, but UNIX was not designed for such discipline.
It makes sense to lay down a simple and flexible set of guidelines for
users---but remember, the fewer rules you have, the less chance there is
of breaking them. Even if your rules for using the system are perfectly
reasonable and clear, users will always at times break these rules without
intending to. This is especially true in the case of new UNIX users, who
are just learning the ropes of the system. It's not patently obvious,
for example, that you shouldn't download a gigabyte of files and mail them
to everyone on the system. Users need help understanding the rules, and
why they are there.
<P>
If you do specify usage guidelines for your
system, make sure that the reason behind a particular guideline is
made clear. If you don't, then users will find all sorts of creative
ways to get around the rule, and not know that they are in fact
breaking it.
<P>
<BR> <HR><A NAME=tex2html3814 HREF="node161.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html3812 HREF="node156.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html3806 HREF="node159.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html3816 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html3817 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html3815 HREF="node161.html">4.1.5 What it all </A>
<B>Up:</B> <A NAME=tex2html3813 HREF="node156.html">4.1 About RootHats, </A>
<B> Previous:</B> <A NAME=tex2html3807 HREF="node159.html">4.1.3 Dealing with users</A>
<BR> <HR> <P>
<BR> <HR>
<P><ADDRESS>
<I>Matt Welsh <BR>
mdw@sunsite.unc.edu</I>
</ADDRESS>
</BODY>