<h2>We are in trouble</h2>
-<li>Some thinks are possible for 1 to 10 machines, and impossible with
+<p>Some things are possible for 1 to 10 machines, and impossible with
500 machines. What do you do when you break the ssh configuration
file on 700 machines?
<li>make the source available to make it possible to fix problems on
site, and to use it on different platforms (os/hw) in the future
+</ul>
+
+<h2>More tips</h2>
+
+<ul>
+
<li>Make paths into users home directories relative to ~user/, as users
will move from disk to disk, or copy their home directory from site
to site. Always convert paths when saving config files.
<li>use a well known license. it is a pain to evaluate every new
license
+</ul>
+
+<h2>Make it easier for everyone</h2>
+
+<ul>
+
<li>when distributing source, do not use vendor specific compiler
features. It will not work with the other vendors compilers used to
compile on site.
<li>system services should send messages to syslog. always log why when
crashing. always log problems and errors.
-<li>reuse configuration. ktouch have its own x layout setting.
+</ul>
+
+<h2>Final clues</h2>
+
+<ul>
+
+<li>reuse configuration when possible. ktouch have its own x layout setting.
better to fetch the current one from X like xkeycaps.
<li>providing hooks to the local admins