<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
- <link rel="stylesheet" href="../../mrtg-td/slides.css" type="text/css">
+ <link rel="stylesheet" href="../mrtg-td/slides.css" type="text/css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Language" content="en">
<meta name="Author" content="Petter Reinholdtsen">
<h2>We are in trouble</h2>
+<li>Some thinks 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?
+
+<h2>Trouble moving</h2>
+
<p>With 60000 users and about 150 home directory file servers
available from 12000 machines, users move from file server to file
server. This break several applications when the path to the users
openoffice configuration. - not using relative paths
-->
-<h2>More trouble</h2>
+<h2>Downgrade trouble</h2>
<p>With 900 linux machines with common user database and home
directories while running different versions of programs, users will
<p>Do users always read their ~/.xsession-error file?
-Providing hooks to the local admins
-
-backdoor - alternative way in. fixing 800 machines by hand is not
-possible. - ssh config fuckup
-
-reduce flexibility. trying to support people over the phone when the
-gui is different for every person is a pain.
-
-
<h2>Clues for the clueless</h2>
<ul>
<li>reuse configuration. ktouch have its own x layout setting.
better to fetch the current one from X like xkeycaps.
+<li>providing hooks to the local admins
+
+<li>reduce flexibility. trying to support people over the phone when
+ the gui is different for every person is a pain.
+
</ul>
<h2>Solving the upgrade problem using multilevel
projects / homepage.git / commitdiff