idmkunix error trying to compile after installing oss711a

[Rick_Hoyle]

I'm unable to complete the installation of oss711a on a SCO OpenServer
6.0.0 system (mp4 already installed). The error is:

UX:idmkunix: ERROR: Identical character device major number range,
14-14, for 'agp' and 'tun'
UX:idmkunix: ERROR: Errors encountered. Configuration terminated.

I can see that the error is indeed valid, and probably has nothing to
do with the installation of oss711a.:

# cd /dev
# l tun0 agp*
crw-rw-rw- 1 root sys 14, 0 May 20 15:05 agpgart
crw-rw-rw- 1 root root 14, 0 Jun 28 08:43 tun0

There are hundreds of ther "tunXX" entries, all having the same MAJOR
# of 14 with a modification/date of Jun 28. On that day,
coincidentally, I was testing Rescue Ranger and did a complete
recovery. My other SCO-6 servers don't have either of those devices
listed in the /dev directory.

We're not running the X-windows system (relates to agpgart?) nor
Morning Star PPP (relates to tunXXX). Is there a way to remove those
from the configuration? Did these come along with MP4?

Any information is appreciated. I've tried to research this issue on
SCO's Knowledge Base and general google searching.

[Jean-Pierre Radley]

Rick_Hoyle typed (on Thu, Oct 01, 2009 at 03:41:27PM -0700):

I've got MP4 installed, and here I see that the /dev/tun?? entries have
the major number 13, while dev/agppart has the major number 12.

Can you link a kernel?

--
JP

[Rick_Hoyle]

When the error occurs, I'm given the option to "Ignore" or "Cancel". I
assume I could ignore the error and the kernel would link. For the
time being, I opted to "Cancel".

I don't see any devices in my /dev directory with a major number of 12
or 13. Does that mean I can change one of those drivers to use 12
instead of 14? If so, which file contains that information? I'm
reluctant to change much without guidance in this area. I'm also
somewhat familiar with the concept that I can change the "installed"
flag from "Y" to "N" in the devices file, but again, my comfort level
here is thin.

Thanks for the reply.
-Rick

[Rick_Hoyle]

> -Rick- Hide quoted text -
>
> - Show quoted text -

Sorry to bump this one: I have hopes of getting some time on that
system again tomorrow. What is the recommended method to resolve my
major-number conflict? Is it as easy as modifying the /etc/conf/
mdevice.d/tun (or agp) text file and change the specified major-
number? How does the system keep track of which majors are in use when
you add a new driver? I believe older SCO systems had a "majorsinuse"
file.
Upon reflection, it makes sense that I induced the problem when I did
the test restore. The restore CD might have been created before one of
those drivers was added to the kernel.

Thanks much for guidance.

-Rick