[186] in DeathTongue Changes

home help back first fref pref prev next nref lref last post

dt is mostly set up

daemon@ATHENA.MIT.EDU (Danilo Almeida)
Sun Dec 19 19:34:19 1999

From: "Danilo Almeida" <dalmeida@MIT.EDU>
To: <licks@MIT.EDU>
Cc: <sipb-office@MIT.EDU>, <pismere-team@MIT.EDU>
Date: Sun, 19 Dec 1999 19:33:49 -0500

I reinstalled dt from scratch.  It is not quite done, but it is mostly done.
It is in a state where users can log in and not screw up anything.  People
should not log in as admin unless absolutely necessary.  Also, you can use
runas if you need to run something as admin insteadd of logging in as such
(it's like su).

The machine has Win2k RC3.  I'll upgrade it to RTM later.  It has lots of
dev tools.  It has Office 2k.  Oh, and it has AFS.  People's homedirs will
be under "Documents and Settings".  As a regular users, you should not be
able to screw up the machine too much.  Please don't damage the install
because it took a lot of work.  This is not a pismere workstation (whatever
hat is).  It is a machine so that people can do dev work.

I'm including 3 text files in this message which explain a bunch of the
stuff I did.  Tese files are DONE.txt, TODO.txt, and BUGS.txt.  They can be
found under c:\athena on dt.  Please read this stuff before if you want to
help out.

- Danilo

P.S.: A note on AFS...  Once logged in, map a drive letter to
\\deathtongue-afs\\afs  Then all you have to do is kinit, aklog, and party.

P.P.S.: There's a sipb0 account like before.

----------------------------------------------------------------------
[DONE.txt]

Preamble:
--------

These notes should help someone know how deathtongue is set up and it should
help Pismere folks prepare an installation that automatically does some of
the stuff listed here.

Some of the notes below are so that I can later create an install that
automatically sets up some of this stuff rather than going through the
laborious manual process I went through.

If people have feedback, please send e-mail to licks@mit.edu.  Please
qualify bugs as suggestions, comments, or actual bugs.  There is a
TODO.txt file that keeps track of what needs to be done.  All of these
files live in c:\athena.

Please don't screw over the machine.  Don't log in as admin unless
absolutely necessary.  I still need to automate a lot of the
installation.  I'd like to get to the point where I can simply choose
to install the machine such that it gets all this stuff automatically
(which is theoretically possible).  If people want to help in this
effort, please contact me.  This would immediately benefit developers
doing Pismere-related work (in e40 and SIPB) who want to get a machine
up and running from scratch and who need a standard environment.

I should point out that I installed dt as part of a domain but then
pulled it off since this domain is unsupported at this time.  So dt is
a standalong workstation.  In the Athenanized Windows 2000
environment, we will have a domain, but for now, dt will just use
local user accounts.

                                      - Danilo (dalmeida@mit.edu)


Installed:
---------
Windows 2000 RC3
Netscape 4.7
Office 2000
MSDN Oct '99
Visual Studio 6.0 (VC++/VB/VJ++) with SP3
Visual Studio Installer
Secure CRT 3.0
Active Perl build 517
WinZip
Virus Scan 4.0.3a (with 4.0.4052 definitions)
GNU Emacs 20.3.1
Windows 2000 Support Tools
Kerberos
Moira
AFS
GNU Utilities (cygwin b19)


athena dir:
----------

The athena dir is simply a convenient place where I threw in a bunch
of stuff.  We haven't given enough though as to what things should be
local and where they should be located.

The bin subdir has Pismere/Athena-type binaries.  All of them are
binaries that we build at MIT.  They were built on my machine today
(12/18/99), so they are newer than any officially released software.
(In fact, I need to check in my moira changes later today or
tomorrow.)

The cfg.copy subdir contains copies of the config files that got put
into the winnt directory.  (Note: The kerberos files do not neet to be
in the winnt directory, but I thought the principle of least surprise
might be useful -- it seemed /etc-like in that regard.)

The extra subdir contains an assortment to utilities.  One worth
noting is linkd, which lets you do directory-level symlinks (as long
as they do not reference remote file systems).  There's also zip, unzip,
cvs, and others.

The gnu subdir contains the cygwin stuff.  The g subdir under that has
some the utilities renamed in case there might be a conflict...  (The
g subdir is not in the PATH.)


Lockdown:
--------

Currently, the filesystem got locked down so that Everyone can read
but only admins can modify stuff outside outside of the user-specific
"Documents and Settings" dirs.

The winnt and "Program Files" dirs had some form of lockdown, so I
left that alone.


SendTo:
------

The default SendTo has been enhanced to contain Notepad and Emacs (via
gnuclientw).


Emacs:
-----

I stole the config from the stuff we use in our Windows environment in
e40 and enhanced site-start.el it so that gnuserv get loaded.


Environment Variables:
---------------------

I had to manually make the Visual Studio variables be system-wide.  I
also put some stuff under c:\athena in the PATH.


User Settings:
-------------

I made a "Useful Setttings" folder in the start menu that sets up some
things that individual users may find useful.


Configure Meadow:
----------------

Configured meadow as a klpr printer.  Here is how I did it.  First, I
added a new HP Laserjet 4Si MX PS printer (printing to FILE:).  Then,
I ran fix-ppd.pl to fix the PostSrcript Printer Description file (just
ran it -- it automatically fixes all PPD files on the system -- yay!).
Next, I changed meadow's port, adding a new port type from
c:\athena\bin (KLPR Port).

The current build of klpr (12/18/99) does not store the port name
happily, but that should be fixed by the middle of next week.  For
now, you also need to kinit before you print.  Hopefully that will be
fixed on the next build.

Ok, I tried printing as administrator, but that did not work.  There may
be some username vs Kerberos credentials issue.  Sigh.

In the end, I set up meadow-legacy as the default printer using plain
LPR so that people can print while this is resolved.


Kerberized Login:
----------------

We can't do this until the Athena KDC gets fixed in terms of salting
(ask dalmeida if you want more info).

----------------------------------------------------------------------
[TODO.txt]

TODO:
----

- Upgrade Windows 2000 to RTM
- Upgrade cygwin to B20.1
- Upgrade emacs to 20.4
- Kerberized login (after KDC database is reordered)
- Configure meadow with new klpr build when it is available.

----------------------------------------------------------------------
[BUGS.txt]

BUGS
----

Let's try this as a format (suggestion on the format welcome):

[BUG|SUGGEST|COMMENT]
Date: mm/dd/yy
User: athena username
Desc:
description

----------------------------------------------------------------------------
---

[BUG]
Date: 12/18/99
User: dalmeida
Desc:
hes crashes in some cases.  (hes meadow)

[BUG]
Date: 12/18/99
User: dalmeida
Desc:
Cannot print as administrator even though I have tix as myself.  Also,
lpq complains about missing PrintQueueIsLPRng in klprhelp.dll.

----

That's all folks.
- Danilo


home help back first fref pref prev next nref lref last post