Novell Home

How to Add or Replace Imaging Files

Novell Cool Solutions: Feature
By Kenn White

Digg This - Slashdot This

Posted: 25 Nov 2002
 

This HOW TO document explains the process you may use to add or replace files on the Imaging CD or diskette boot media.

Please refer to the HOW TO on changing Linux.2 for updating files used by PXE.

Overview

Imaging v3.2 and above has the capability to add or replace network drivers. The imaging script available with Imaging v3.2 sp1 and V4.0 and higher, has the capability to add new or replace any other files without modifying the resource files directly. This is quite important considering the process required to "crack" the resource files to change files.

You can edit the last (3rd) boot diskette directly from any Windows PC as the diskette is formatted as a "fat" file system. Never try to modify or read the second boot diskette as it uses the "minix" file system format and you will get errors.

To modify the Imaging boot CD, you can either use a program like "WinIso.exe" (http://www.winiso.com) to modify the "bootcd.iso" file or create the CD using multi-session capabilities in most CD creating software. The drawback to creating multi-session CDs is that some CD-ROM drives, specifically older models, will not read or boot from them.

Add/replace Linux drivers

Adding Linux drivers involves placing files in a specific directory on the boot CD or last (3rd) boot diskette. To add network drivers to the boot media, create a directory structure as follows:

\drivers\net

To add a new e1000.o driver, place it in this directory structure.

\drivers\net\e1000.o

You may also create a "driver.conf" file to load a specific driver or add command line parameters when the driver is loaded. Refer to the driver manufacturer documentation for available command line switches.

The default "driver.conf" file currently has contents similar to the following.

  • #This file lists the driver modules to be loaded
  • #The syntax of this file is "insmod -f <modulename> <commandline parameters>
  • #for eg, to load driver 3c90x: insmod -f 3c90x.o > /dev/null 2>&1
  • #Command line parameters like half duplex, full duplex mode, 10M, 100M... also can be specified.
  • #for eg, to specify an io port: insmod -f 3c90x.o io=0x300 > /dev/null 2>&1

As you can see, to force your Linux boot to load the 3c90x.o driver and use IO address of 0x300, you could have a command line

insmod -f 3c90x.o io=0x300 > /dev/null 2>&1

in the "driver.conf" file. You can remove the "> /dev/null 2>&1" to be able to view any messages from the driver as it loads.

Once you have the "driver.conf" file working as desired, you place it in the following path on the boot media.

\drivers\driver.conf

Adding or replacing other files

You may add or replace any files in the Linux boot media at run time by using a special directory structure on the boot media. You first add the directory "\addfiles" to the boot media. Below this directory you would add the specific directories and files that you want to replace. For example, to add a file named "myscript.s" to the /bin directory, the structure would look like this.

\addfiles\bin\myscript.s

You could also use this directory structure to add the "driver.conf" and "3c90x.o" files. The files would be in the following directories.

\addfiles\bin\driver.conf
\addfiles\lib\modules\2.4.18\kernel\drivers\net\3c90x.o

More Info

For more help with ZENworks Imaging, don't miss the ZENworks Imaging Resource Library.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell