[42044] in Hotline Meeting
Re: [Fwd: New Printer for Athena at WHOI]
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Mon Feb 23 18:37:11 1998
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Eric Cunningham <ecunningham@whoi.edu>
Cc: Jonathon Weiss <jweiss@MIT.EDU>, op@MIT.EDU, hotline@MIT.EDU
In-Reply-To: Your message of "Tue, 10 Feb 1998 08:51:33 EST."
<34E05B65.3DCE36C@whoi.edu>
Date: Mon, 23 Feb 1998 18:37:05 EST
Hi, I'm sorry it's taken us so long to get back to you.
> WRT updating "quahog" to 8.1 - where do we stand with this?
The problem here is that the athena 8.1 release isn't very graceful
about machines that are not on net 18. I believe this is fixed in
8.2, but that isn't scheduled for release until this summer. To
complicate matters, the machine will update in the middle of the
update process, and it may be tricky to make sure that it is
configured correctly for the second half of the update.
Here are my notes on updating you machines (put together from several
pieces of mail from when tautog was updated to 8.1), but they have not
been tested.
Make sure SYNCCONFIG=false in /etc/athena/rc.conf. If your machine is
running 8.0, you will have to add this variable.
make sure that /etc/inet/netmasks has the following line:
128.128 255.255.252.0
(this is one of the things that is the most likely to get broken
halfway through the update.)
/etc/hosts needs to contain a line for the local machine. However,
there is a lot of inconsistancy among your 4 machines right now.
I believe the correct thing would be somethign like:
128.128.16.221 squeteague.whoi.edu squeteague
but tautog has the following, and you haven't noticed any problems:
128.128.16.220 tautog.MIT.EDU tautog
quahog and menhaden don't have a fully qualified domain name, or have it
second. This is definately wrong.
/etc/defaultrouter should have the router for the relevant subnet.
It's possible, but not too likely that this will get corrupted by the
update. Currently, this is:
menhaden 128.128.108.1
quahog 128.128.92.1
squeteague 128.128.16.7
tautog 128.128.16.7
There is also a slight chance that there will be a problem with any of
the following:
/etc/hostname.le0 (should have name of machine)
/etc/nodename (should have name of machine)
/etc/athena/rc.conf (should have the host name and the address)
Given all of this information, do you feel comfortable trying to
update the quahog yourself (possibly at a time when I can arrange to
be contactable by phone)? If so, you should confirm that both PUBLIC
and AUTOUPDATE are set to false in /etc/athena/rc.conf, and let me
know. I will then update the hesiod information for the machine, and
you can do the update anything after that change has taken effect (it
takes overnight). Once we get quahog updated to 8.1, we can
coordinate updating the rest of the machines. If you don't feel
comfortable trying this, let me know, and someone (probably me) will
schedule a trip down there to help you out. (The obivious advantage
of you doing this yourself is that it's likely to happen sooner.)
> Is there anything special required in terms of cabling this new printer
> the our LAN? It doesn't require an IP address, does it? Our current
> Athena printer, "scallop", doesn't (I believe).
A standard UTP cable to the JetDirect card will suffice in the cabling
department. Yes the printer will require an IP address. Scallop has
one, it's just under the name scallop-p (yes, we have two conventions,
some printers have the -p in the IP name, others don't.) Although on
further inspection, scallop is a little confused in this area:
starbasezero:~: hi scallop-p.mit.edu
Desired host: scallop-p.mit.edu
Official name: scallop-p.mit.edu
Host address: 128.128.16.223
Host info: HP/LASERJET-4.SI/MX
starbasezero:~: hi scallop-p.whoi.edu
No such host 'scallop-p.whoi.edu'.
starbasezero:~: hi 128.128.16.223
Desired host: 128.128.16.223
Official name: scup.whoi.edu
Host address: 128.128.16.223
I believe that our software is currently using the scallop-p.mit.edu
name, although we could change that.
> - "quahog" should be a second print and bootp server for this new
> printer (can we call the printer "mussel"?)
I've grabbed the printer name mussel for you. It should show up in
hesiod tomorrow. The IP name mussel is taken, but mussel-p is not. I
haven't reserved that, since I don't knwo what IP address it will
have, or if there is anythign funny we have to do when adding machines
at WHOI. Matt, do you knwo?
> - "mussel" should be the default system printer for "quahog" and
> "menhaden"
I'm not going to make these changes until the printer is up and
working.
> - "scallop" should be the default system printer for "tautog" and
> "squeteague"
This is already the case.
> - both printers should be accessible from all WHOI Athena workstations
This we'll deal with when we set up quahog as a printserver. If you
tell me you are comfortable trying the update, I'll also write up some
instructions on making quahog a printserver. (Actually, configuring
it as a printserver is something I can proabbly do from here once it
is running 8.1, if you'd prefer, but you'll still need to do the
testing.
> - all WHOI Athena workstations should probably be upgraded to 8.1 if
> they aren't already, if possible.
Either we can coordinate this once you've updated quahog, or I'll deal
while I'm there if we go with that option.
Jonathon
