phew!

[Kurt Lidl]

In article <937 at granite.dec.com> rwood at dec.com (Richard Wood) writes:
>
>ULTRIX v4.0 also includes NTP, since time synchronization is necessary
>to keep the timestamp feature of kerberos (as well as other network
>services) from getting messed.

We've had NTP running on the Ultrix 3.1 machines here for quite
some time.  I don't think that this is such a great thing to selling
the system on.  Everybody who is doing lots of networking has
mostly adopted NTP across the board already.  Our Sun3s, Sparcs,
DecStations, Vaxen already do it.  I haven't given it a whack yet on
the RT's, but I don't think there will be any problems...

>ULTRIX v4.0 also includes the BSD kmem and tty groups.

This we have also done.  Mostly an exercise in changing permissions
on devices and files...

>Security can be set at several different levels, and includes features
>such as long passwords, password aging, generated passwords,
>kerberos/hesiod-based networked password database, etc.

Is the password aging a function of using kerberos or from some other
changes to the code.  Also, is there support for the BSD-style
"shadow" password scheme?

So I will ask again:
Did DEC fix the broken behaviour of /bin/sh on its machines?
Try getting the default "rn" compiled and installed and working.
I find that the /bin/sh scripts that it uses a lot (Pnews, Pnews.header,
Rnmail, etc) are a pretty good test of a machine's /bin/sh.
--
/* Kurt J. Lidl (smaug at eng.umd.edu) | Unix is the answer, but only if you */
/* UUCP: uunet!eng.umd.edu!smaug    | phrase the question very carefully. */