Changes between Version 7 and Version 8 of Configured Workstations

Timestamp:

08/16/06 15:09:16 (20 years ago)

Author:

dkg@…

Comment:

--

Configured Workstations

@@ -1 @@
-the [wiki:"Configured Workstations"] will be running [wiki:"Ubuntu GNU/Linux"], initially release 5.10 (breezy badger).
+the [wiki:"Configured Workstations"] are Intel-compatible 32-bit i386 hardware running [wiki:"Ubuntu GNU/Linux"], release 6.06 LTS (Dapper Drake).
 
-They should be capable of having the [wiki:"Required Astronomical Software"] installed on them, but not every workstation needs all the different tools.
+They have the [wiki:"Required Astronomical Software"] installed on them.
 
 == Authentication Model ==
 
-The workstations should use PAM to authenticate against the [wiki:"CAL Kerberos Domain"]
-
-== Prototyping ==
-
-A prototypical configured workstation will be set up and given over to try to install the [wiki:"Required Astronomical Software"].  We're calling this the [wiki:Proto-CW] 
+The workstations use PAM to authenticate against the [wiki:"CAL Kerberos Domain"]
 
 == Partitioning Scheme ==
 
-We'll use [wiki:LVM].  here's the proposed partitioning scheme: 
+CWs use [wiki:LVM].  here's the basic partitioning scheme: 
 
 Base disk is broken into two partitions:
@@ -30 +26 @@
 == temporary space ==
 
-i'm inclined to mount `/tmp` as a RAM-backed filesystem.  Since all RAM is actually backed by swap, this is reasonable, and it means that `/tmp` will be nicely auto-flushed on a reboot.  An example line in `/etc/fstab` for such a method would look like this:
+`/tmp` is mounted as a `tmpfs` (a RAM-backed filesystem).  Since all RAM is actually backed by swap, this is reasonable from an efficiency viewpoint, and it means that `/tmp` will be nicely auto-flushed on a reboot.  An example line in `/etc/fstab` for such a method looks like this:
 {{{
 tmpfs /tmp tmpfs size=300m,mode=1777,nosuid,nodev 0   0
 }}}
 
-== weird issues ==
-
-[wiki:gdm] is behaving oddly under libnss-ldap.
-
 == installation process ==