NAME

fsgen − Filesystem image generator - Pass 2

SYNOPSIS

fsgen [-Vcvwa] [-f outfile] fileprefix

SUMMARY

fsgen reads a .lst file as produced by fscoll(1) and prepares one or more filesystem images from the information contained in the file.  The images are written sequentially to any specified file or device.  The fsgen program also writes a .log file, that contains all warning and error messages, as well as final image sizing information. 

Fsgen is capable of creating both UNIX and ISO9660 format filesystems, as well as simple image slices and Motorola style VID blocks. 

DESCRIPTION

fsgen expects to be given a file name prefix as an argument.  The prefix is used to construct an input file name by adding the string .lst to the prefix supplied.  If the constructed file name cannot be opened, fsgen aborts with an error. 

The user may supply any of the following command-line options:

-V causes fsgen to print its version number and exit. 

-v causes fsgen to generate brief messages about the slices currently being processed and some sizing information, including the total size of the final image.  The total image size is also always written to the .log file. 

-w causes fsgen to treat the output image as if it is intended for a writable device (not a CD-ROM).  Currently the only effect of this flag is to turn off the V_RONLY flag in the SVR4 VTOC. It thus has no effect unless the image is mounted under SVR4. 

-a causes fsgen to run only the first allocation pass on the input .lst file.  The output device is not opened, and no image is created.  The allocation and sizing information for the image is recorded in the .log file in the usual way.  Because the allocation pass is fast, it is a good idea to use the -a option for the initial run because it identifies many problems that cause a full image write to fail.  Also use the -a option to check that an image is not too big to fit on the final device. For example the CD-ROM size limit is usually around 600MB, but varies between different manufacturers. 

-f device
allows the user to supply an output device or file to which the image will be written.  If no -f option is supplied, the default device /dev/rmt/ctape is always used. 

-c option (continue), causes fsgen to try and ignore all file open and read errors during the image creation process.  Any failed attempts to open a file or read a file that made up part of a UNIXS5 or ISOFS slice causes that file to be written either partially or completely empty (all zeros).  A suitable warning message is generated in all cases. 

If the output file is a tape device, and fsgen finds that it cannot fit the entire image on one tape, fsgen prompts the user to insert a new tape at the correct time.  The correct operation of multi-tape images relies on using the correct, BCS compliant, tape device node. 

DIAGNOSTICS

Since fsgen expects that the fscoll utility has already checked the information in the input .lst file, its error checking is not as thorough as in fscoll.  However, all error messages detail the problem encountered, the input file line number (where relevant), and the UNIX errno (if applicable). 

All error and warning messages printed by fsgen during its execution are also copied to a file named xxx.log (where ´xxx´ is replaced by fileprefix).  This .log file should always be carefully examined after fsgen has been run.  Any fatal errors mean that the image is unusable.  Any warnings usually mean that the image is complete, but not correct in data content. 

fsgen always has a zero exit value unless an error was encountered.  The exit value on encountering an error is picked from the following table based on the class of error. This same set of exit values is used by all the CD-ROM generation tools. 
 

LIMITATIONS

For ISO9660 filesystems (ISOFS) fscoll and fsgen currently only support interchange level 1 as described in the ISO9660 document.  This means that all filenames recorded in an ISOFS slice will have a maximum of 8 characters, with a maximum extension of 3 characters. 

CD-ROM Volume Sets, or the recording of a file tree over several physical CD-ROM volumes are not supported.  Each ISO9660 Volume recorded by fsgen will be logically complete. 

SEE ALSO

fscoll(1), loadimg(1). 
 

  —  Motorola, Inc