Efsys.file

Embedded filesystem in a file

Syntax:

Efsys.file [-d name][-f basename] 
           [-m mountpoint] ... [-s num]

Options:

-d name

A raw device name (the default is skt).

-f basename

The basename of the file to store data in (the default is socket).

-m mountpoint

The mountpoint for the embedded filesystem (EFS) partitions.

-s num

The number of sockets (the default is 1).

Description:

Efsys.file operates similarly to the other Efsys drivers but stores the filesystem within a file. This lets you create a filesystem using normal tools (e.g. efsinit, mkcis, mkdir, cp, etc.) and then program the resulting image into ROMs for use in a target system.

Don't use the mkcis -2 option if you're using Efsys.file. Efsys.file can't read the level 2 structures.

The driver uses the following default filenames:

/dev/sktX

raw device special file for each EFS socket, where X is the logical socket.

/dev/sktXimgY

raw device special file for each image partition on the EFS, where X is the logical socket, and Y is a unique partition number

/efsXpY

embedded filesystem mountpoint for each EFS partition on the EFS, where X is the logical socket, and Y is a unique partition number

To change the raw device names, use the -d option. To change the mountpoints of the EFS partitions, use the -m option. You can specify multiple -m options.

Efsys.file stores the data for each logical socket within a file named socket.X, where X is the number of the logical socket. You can change this name with the -f option.

Before using the contents of the data files, you should slay Efsys.file.

Examples:

Start Efsys.file, with output to socket.1:

    Efsys.file

Start Efsys.file, with two sockets called rom.1 and rom.2:

    Efsys.file -s 2 -f rom

See also:

romqnx