ISC Multi-User Extension

[Steven King]

In article <J5DBy5w163w at aegis.or.jp> davidg%aegis.or.jp at kyoto-u.ac.jp (Dave McLane) writes:
>alexb at cfctech.cfc.com (Alex Beylin) writes:
>
>> That is a bug in the sysadm script.   I don't recall of-hand
>> what has to be changed to fix it.  Warranty Support will give
>> you the fix, if you need it.
>
>From what I can tell, sysadm is a program, not a script; if it was
>a script I would be tearing it apart (if I'm wrong please let me know).

   sysadm IS a script on my copy of 2.2, or rather a set of scripts;
  _/usr/admin/menu/ttymgmt/modtty_ is the actual one that generates that
 message. It checks the file _/usr/options/.license_ ; it should contain
 a single ascii char _3_ for the multi-user license. (not that it appears
 to make a difference for actualy running a multiuser system)
 
>Actually, that's not quite true, I got through to them a couple of
>times and they refused to replace the defective disk I have sitting
>right here on the table in front of me because they said my serial
>number was for single user.  The only way I got the wrong disk (it
>only has the upgrade for the OS, not VP/ix; luckily that part of
>the orignal disk was OK) was to have the place I bought it get it
>for me.

   When I installed my upgrade to 2.2, the multi-user disk developed an
 error in the midst of the installation and bombed out, leaving me with
 a partially upgraded system (2.2 but not multi-user).  Being rather
 irratated that I was going to have to go back to 2.0.2 or wait till they
 replaced my disk, I went ahead and fsck'd it. To my surprise it was able
 to fix the disk and I was able to finish the installation.

-- 
Look Ma! No .sig!
                                        ..!cs.utexas.edu!ut-emx!nowhere!sking