Problem
Each SCO device driver has a maximum number of devices that
can be configured. It is possible to tune the kernel to a
number exceeding this value. If the maximum number of
drivers allowed is exceeded, the kernel will not relink. Solution
To function, each device used requires a driver in the kernel. Drivers use device nodes (typically entries in the /dev directory) to talk to the devices.
The maximum number of devices that can be accessed, using one
device major number, is 256. In order to exceed this number,
SCO uses a scheme of extended minor numbers. This scheme
requires a separate entry in the file /etc/conf/cf.d/mdevice
for each 256 devices. The maximum number of entries allowed
varies by specific driver.If the kernel is configured to exceed this number of entries for a specific device, any attempt to link the kernel will fail with a message specifying the driver name of the driver which is causing the failure.
To correct the problem, log in as root:
WARNING: If errors are made, this procedure can potentially leave you with a kernel that cannot be rebuilt.
It is recommended that /etc/conf/cf.d/mdevice, and the appropriate file in /etc/conf/sdevice.d be copied to the /tmp directory. This is to ensure, that if errors are made, you have copies of the originals.
1. The file /etc/conf/cf.d/mdevice must be edited to reduce the number of line entries for the specific driver. (NOTE: The socket driver is used as an example.)
a. Using your preferred editor, locate all entries for the specified device in /etc/conf/cf.d/mdevice
If you are using vi, use the command:
/<driver name>For this example, from vi command mode, type:
/socketYou will find an entry such as the one shown below:
socket ocrwis ic sock 0 26 0 256 -1Pay particular attention to the eighth column, which shows the maximum device number for that set of devices.
Find all entries that start with the same name and
identify the entries with the greatest number in the
eighth column. You will also need to know the total
number of lines with the same name.In this example, the following lines were found:
socket ocrwis ic sock 0 26 0 256 -1
socket ocrwis icM sock 0 121 26 256 -1
socket ocrwis icM sock 0 122 26 512 -1
socket ocrwis icM sock 0 123 26 768 -1
socket ocrwis icM sock 0 124 26 1024 -1
socket ocrwis icM sock 0 125 26 1280 -1
socket ocrwis icM sock 0 126 26 1536 -1
socket ocrwis icM sock 0 127 26 1792 -1
socket ocrwis icM sock 0 132 26 2048 -1
socket ocrwis icM sock 0 133 26 2304 -1In this case, there are 10 lines and the highest value in the eighth column is 2304.
Note: There will probably be other information between the lines for a given driver. Do not stop searching until you are sure that you have reached the bottom of the mdevice file.
Remove one or more lines for this driver from the mdevice file, always removing the line with the highest value in the eighth column first.
Keep count of the number of remaining lines.
If you remove one line, it should be the line with
2304 in the eighth column. The total count of lines
would then go to nine.3. Change directories to the directory /etc/conf/sdevice.d.
In that directory, there should be a file with the same name as the driver you are working with (in this example there will be a file named "socket").
This is an example of the file /etc/conf/sdevice.d/socket:
* @(#)System 6.3 8/21/93 - STREAMware TCP/IP source
*
* Copyrighted as an unpublished work.
* (c) Copyright 1987-1993 Lachman Technology, Inc.
* All rights reserved.
*
* SCCS IDENTIFICATION
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0
socket Y 256 0 0 0 0 0 0 0Notice that there are the same number of lines in the driver file as there were in the mdevice file for this driver (in this case, the number is 10).
Remove the same number of lines from this file as you did from the mdevice file (one in this case). The remaining number of lines for this driver should be the same for both files (nine in this case).
4. Change directories to /etc/conf/cf.d and attempt to link a kernel by issuing the command:
./link_unixIf the link succeeds, you are finished.
If it fails, reduce the number of lines on both the mdevice and /etc/conf/sdevice/<device name> files until you succeed.