For convenience, the format rules for entries in
Bootdisk_Contents
is given in comments at the beginning of
that file. Here is a list of the allowable forms:
filename1 -> filename2
will create symbolic (soft) links on the root filesystem. For example, if
you want sh
linked to bash
in the root filesystem, you specify:
/bin/sh -> /bin/bash
(There is no way to specify hard links, though hard linked files
that exist on the hard disk will be hard linked on the floppy.)
filename1 <= filename2
will cause filename2 to be
copied to filename1 on the boot disk. This is useful for specifying
trimmed-down replacements for /etc/passwd, /etc/inittab, etc. filename2 will
be found first by searching PATH, then by searching relative to the current
directory.
A useful variant of this is:
filename1 <= /dev/null
/dev/hd[ab]*
. Wildcards are not allowed in link specs or
replacement specs because no one knows what they mean.
$kernel
).
In most cases you don't need to specify shared libraries or loaders. The
script will detect dependencies (via ldd
) and include them
automatically. The exception for this is PAM.
You don't need to explicitly specify intermediate directories unless you just want to make sure they exist. For example, if you mention /foo/bar/slog, Yard will make sure /foo and /foo/bar exist.