Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!rochester!pt.cs.cmu.edu!sei!sei.cmu.edu!pdb
From: pdb@sei.cmu.edu.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Ultrix32m 1.1 on MicroVaxII
Message-ID: <1427@aw.sei.cmu.edu>
Date: Wed, 27-May-87 08:53:06 EDT
Article-I.D.: aw.1427
Posted: Wed May 27 08:53:06 1987
Date-Received: Thu, 4-Jun-87 06:47:09 EDT
References: <7539@brl-adm.ARPA>
Sender: netnews@sei.cmu.edu
Reply-To: pdb@sei.cmu.edu (Pat Barron)
Organization: Carnegie-Mellon University, SEI, Pgh, Pa
Lines: 27

In article <7539@brl-adm.ARPA> cew@venera.isi.EDU (Craig E. Ward) writes:
>First problem: the kernel keeps writing "Login limit reached" to
>/usr/adm/messages.  I have a hard time believing this because it usually
>just has one user (me) on it.  This problem is interfering with the
>operator backups.  The kernel is configured for 32 users (was 16).  Any
>ideas what this really means?

The setting of MAXUSERS in your config file has no relation to the maximum
number of users that you're licensed for.  This is hardwired into the kernel,
and with Ultrix-32m 1.1, I believe this limit is 2.

>I don't intend to stay with Ultrix 1.1.  Does anyone have any experience
>with 4.3bsd or Ultrix 2.0 on mVaxII's?  I have tried building a 4.3
>kernel from our Mt. Xinu 4.3 distribution but these kernels will not
>come up single-user.  (Mt. Xinu seems to be missing one driver (device
>qv -- isn't that the console monitor?).  Are there substitutes?)

The qv device is for the display, which becomes your console if you have
one.  If you're willing to lose the display, you could put a terminal
on the console serial port, and that would become your console, and things
*should* work.  But you'd probably rather keep the display, right?  Maybe
you should call Mt. Xinu; they might have a driver for that device.

We have Ultrix 2.0 running on a couple of MicroVAXen, with NFS talking to
some Suns, and it seems to be working out pretty well.

--Pat.