[6266] in Release_7.7_team
Installation results
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Mar 4 13:31:36 2009
Message-Id: <1B0C1B88-404B-42EC-B911-2F7A9D85A105@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: release-team@mit.edu
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 4 Mar 2009 13:30:53 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00
The installation of the beta machines has been completed. Lessons
learned:
- Our PXE environment is tempermental
- Installation is reasonably fast. In 66, I had 4 GX620s going at the
same time, and it didn't seem any slower that on a single machine in
N42.
- texlive, specifically the 5 billion fonts we install, totally
sucks. It runs mktexlsr and updmap-sys after every single font
package, which takes a LONG time. (This is after installation, not
the "Setting up..." stage). I wonder if there's any way we can (for
summer, not now) do something clever to work around this.
- Short login sessions (ie: login, make sure things work, log out)
seem to trigger a reboot-on-logout more often than longer sessions.
I'm attempting to figure out why, but if I had to guess, I'd say
probably one of the hundreds of GNOME processes is still starting up
or figuring itself out by the time it gets the SIGTERM and it doesn't
like it. It seems to be either the update notifier or avahi.
- workstations initially boot up with sound enabled. After the first
login, sound is disabled. However, on the 745s and 755s, they did not
make any sounds, even though it was enabled, whereas the 620s made the
happy jungle noises at boot-up and login. Are we setting mixer values
too?
- The GX620s and 745s pop up a panel applet in the "system tray" with
a libnotify popup encouraging users to activate the fglrx driver for
their display. Attempting to activate it brings up the system policy
authentication dialog. Typing the user's password results in nothing
happening. Attempting to click the "Activate" button again results in
"You are not authorized to perform this action." I suspect it's a
group issue or something weird. Screenshots are in /mit/joeuser/
Public/drivers.png and drivers2.png
- The following scrolls by, it may be harmless, but it says "FATAL" so
I'l mention it:
Setting up bind9 (1:9.5.0.dfsg.P2-1ubuntu3.1)...
Adding group 'bind' (GID 128) ...
Done.
Adding system user 'bind' (UID 113)
Adding new user 'bind' (UID 113) with group 'bind'...
Not creating home directory '/var/cache/bind'
wrote key file "/etc/bind/rndc.key"
#
mount: mount point /sys/kernel/security does not exist
$Mounting securityfs on /sys/kernel/security: Failed.
mount: mount point /sys/kernel/security does not exist
$Mounting securityfs on /sys/kernel/security: Failed.
FATAL: Could not load /lib/modules/2.6.27-7-generic/modules.dep: No
such file or directory
$Loading AppArmor module: Failed.
invoke-rc.d: initscript apparmor, action "force-reload" failed.
*Starting domain name service... bind9
resolvconf: Error: /etc/resolv.conf mut be a symlink
... done
