DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

dosfloppy(CDMT)


dosfloppy -- place a custom-installable distribution image on an existing DOS floppy filesystem

Description

The custom(ADM) utility supports installation of SCO OpenServer System-compatible products from a DOS floppy filesystem (version 5.0 or earlier). Use this feature to distribute both DOS and UNIX versions of a single-floppy product, such as a device driver, on one floppy disk, thus reducing media costs.

To install a product from a single DOS floppy, first generate the distribution image using either the Software Mastering Toolkit (SMT) or the Custom Distribution Mastering Toolkit (CDMT), then copy the custom-installable image to an existing DOS floppy filesystem and use custom to install it.


NOTE: The target SCO OpenServer system does not require DOS filesystem support linked into the kernel; custom uses the SCO OpenServer UNIX doscmd(C) utilities to manage the DOS floppy.

The custom utility supports all standard installation features for a product distributed on a DOS filesystem floppy, with the restriction that the distribution size be smaller than a single floppy. Only one image per product is supported and the image must fit on a single floppy volume.

You should be familiar with the concepts and tools required to cut custom-installable distributions on media other than DOS floppies.

To cut, create, and install a custom-installable product on a DOS floppy:

  1. Use the distribution mastering tools to cut the custom-installable distribution image:

    Software Mastering Toolkit
    For a perms(F) list-based product, use the SMT to cut the distribution image. See the Software Mastering Toolkit Guide for details.

    Given the desired floppy device and media size, the mkcuts(SMT) utility generates enough media-sized tar(C) images to contain the entire distribution. Because the SMT-generated images are padded to the specified media size (for example, 1.44MB), you must use tar to extract the files from the generated image into a directory. You can then use tar to re-archive the directory into a new nonpadded product image to copy to the DOS floppy.


    Custom Distribution Mastering Toolkit
    For a Software Storage Object (SSO)-based distribution, use the CDMT. See UNRESOLVED XREF-0. CDMT generates a cpio(C) archive image.


    NOTE: If more than one image is generated, the product is too large to use the DOS floppy distribution feature.

  2. Format the DOS floppy using either the format command from DOS or the dosformat(C) command from your SCO OpenServer system:

    dosformat /dev/fd0

  3. Create a directory called /SCO in the DOS filesystem. To create the directory on the DOS floppy, use either the mkdir command from DOS or the dosmkdir(C) command from your SCO OpenServer system:

    dosmkdir /dev/fd0:/SCO

  4. Copy the single-volume media image that you generated using the mastering tools onto the DOS floppy as /SCO/CUSTOM.DST. Use the doscp(C) command from your SCO OpenServer system to copy the image:

    doscp /SCO/CUSTOM.DST /dev/fd0:/SCO/CUSTOM.DST

Once you place the custom-installable distribution on a DOS floppy, it can be installed using custom on an SCO OpenServer system.

Use one of the following methods to install the product:


Install from the command line:

  1. Insert the floppy into the floppy drive.

  2. Enter:

    custom -p product_name -i -m floppy_device


Install using the Software manager:

  1. In the Software manager, select Run Installation from the Software menu.

  2. Insert the floppy disk into a drive and select that device from the menu.

  3. Click on Full.

Limitations

The following limitations apply to custom-installable DOS floppy filesystem distributions:

Files

/etc/custom

See also

custom(ADM)

``Installing and managing software components'' in Installing and removing software and
UNRESOLVED XREF-0

Standards conformance

dosfloppy is not part of any currently supported standard; it is an extension of AT&T System V provided by The SCO Group.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 26 May 2005