Technical article 127497

Is there a way to create one CD with the various drivers I need for an ISL?

OpenServer 6.0.0UnixWare 7.1.4

Written

Problem

I want to create a single CD that contains more than one driver that I can use during ISL.

Solution

OpenServer 6 and Unixware 7.1.4 both are using the same format for an HBA floppy.

It is the package format.

So first of all you have to have your drivers in that format.

In the following example we will create one CD with two drivers:

qlc2300 and megasas

1. Create a build directory. Run "mkdir /build".

2. Download the driver as a floppy image.

3. marry -a <floppy image>
4. mount /dev/marry/<floppy image> /mnt

List /mnt and you will see (in this case for the megasas driver)

# l /mnt
total 4
drwxr-xr-x    3 root     sys         96 Dec 21  2006 etc
drwxr-xr-x    4 root     sys         96 Dec 21  2006 megasas
# l /mnt/etc
total 8
drwxr-xr-x    3 root     sys         48 Dec 21  2006 conf
-rw-r--r--    1 root     sys         44 Dec 21  2006 load.name
-rw-r--r--    1 root     sys         20 Dec 21  2006 loadmods
-rw-r--r--    1 root     sys          8 Dec 21  2006 modules
# l /mnt/megasas/
total 8
drwxr-xr-x    2 root     sys         80 Dec 21  2006 install
-rw-r--r--    1 root     sys        206 Dec 21  2006 pkginfo
-rw-r--r--    1 root     sys        858 Dec 21  2006 pkgmap
drwxr-xr-x    3 root     sys         48 Dec 21  2006 root
5. Now copy everything to your /build directory
(cp -r /mnt/* /build)
6. umount /mnt
7. marry -d /dev/marry/<floppy image>

Now you have one driver ready for your ISL HBA CD.

Next step is to add further drivers.

# l /mnt
total 6
drwxr-xr-x    3 root     sys         96 Jul 30  2004 etc
drwxr-xr-x    4 root     sys         96 Jul 30  2004 qlc2300
8. marry -a <floppy image>
9. mount /dev/marry/<floppy image> /mnt

10. Copy the driver directory (qlc2300) to you build directory.

cp -r /mnt/qlc2300/ /build

Now your /build directory looks like this:

# l /build
total 0
drwxr-xr-x    3 root     sys         96 Sep 22 11:31 etc
drwxr-xr-x    4 root     sys         96 Sep 22 11:31 megasas
drwxr-xr-x    4 root     sys         96 Sep 22 11:35 qlc2300

11. Copy the mod.d entry of the driver into the mod.d directory of your build directory.

cp /mnt/etc/conf/mod.d/qlc2300 /build/etc/conf/mod.d/

12. cd to /build/etc. This looks like this:

# cd /build/etc
# l
total 12
drwxr-xr-x    3 root     sys         96 Sep 22 11:31 conf
-rw-r--r--    1 root     sys         44 Sep 22 11:31 load.name
-rw-r--r--    1 root     sys         20 Sep 22 11:31 loadmods
-rw-r--r--    1 root     sys          8 Sep 22 11:31 modules

12. Append the loadmods file of the new driver (qlc2300) to the loadmods file in your build directory:

cat /mnt/etc/loadmods >> /build/etc/loadmods
Your /build/etc/loadmods file should look like:
cat /build/etc/loadmods
6:1:megasas:megasas
6:1:qlc2300:qlc2300

13. Append the modules file of the new driver (qlc2300) to the modules file in your build directory.

cat /mnt/etc/modules >> /build/etc/modules
Your /build/etc/modules file should look like:
megasas
qlc2300
14. umount /mnt
15. marry -d /dev/marry/<floppy image>

Finally you have to create an ISO image of the /build directory and to burn it on a CD.

16. Use mkisofs(8) to create an iso image of the HBA as follows:

# mkisofs -o /hba.iso  -r /build

17. Use cdrecord(1) to burn the iso image to CDROM. e.g.

# cdrecord -v -dev=c,b,t -dao -driveropts=burnfree
  -speed=99 /hba.iso

where c,b,t is taken from the output of the command:

# cdrecord --scanbus

From the Xinuos technical article database, record 127497. Reproduced with permission. The original is at www.sco.com/ta/127497, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.