[258] in athena10
Re: Athena 10 on ashdown04 cluster machine: installation report and
daemon@ATHENA.MIT.EDU (Timothy G Abbott)
Sat Jun 21 17:51:47 2008
Date: Sat, 21 Jun 2008 17:51:02 -0400 (EDT)
From: Timothy G Abbott <tabbott@MIT.EDU>
To: Kenneth Arnold <kcarnold@mit.edu>
cc: ashdown-webmaster@mit.edu, athena10@mit.edu
In-Reply-To: <485D73A1.6050602@mit.edu>
Message-ID: <alpine.DEB.1.10.0806211737110.14493@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
On Sat, 21 Jun 2008, Kenneth Arnold wrote:
> - aptitude complains about a missing debathena-evolution-data-server
> dependency => cancel debathena-evolution-wrapper installation for now
> - aptitude also wants to downgrade bash. ok.
> - manually installed all the debathena base packages, and all
> debathena-workstation deps except the evolution-data-server dep
The fact that Debathena doesn't install at the moment seems like a rather
serious problem.
> * PRINTING DOESN'T WORK to the ashdown printer. I can get around that by
> using mit-lpq etc., but that shouldn't be necessary. And it doesn't seem to
Yeah, I think we should by default divert (using a Recommended package) so
that the mit-lp* versions are what you get when you run lp*, since that's
what most people want.
> be using the cluster info to get the printer.
Regarding cluster info, the relevant code in /usr/lib/get_hesiod_pcap is:
if [ -z "$PRINTER" ]; then
host=`hostname`
PRINTER=`hesinfo "$host" cluster 2>/dev/null | \
awk '/^lpr / {print $2; exit;}'`
if [ -z "$PRINTER" ]; then
# We have no default. Let LPRng come up with its own default.
exit 0
fi
fi
Perhaps `hostname` is not returning ashdown04? Unless you mean that CUPS
doesn't know the default printer, which I would not find surprising.
> * group ownership in my home directory is weird. (libuuid?) Though it's
> weird on linerva too.
> * I'm not listed as being in the 'mit' group (though on linerva I am).
These are because the 'mit' group has gid 101, which conflicts with local
groups (I guess libuuid got 101 on your system). On Linerva we manually
renumber the local group with gid 101 to some other number.
The right long-term solution to this problem is probably for the 'mit'
group to find a new number in the ranges that aren't used by local
systems, but I don't see how to get there from here.
-Tim Abbott
