diff options
authorGene Cumm <gene.cumm@gmail.com>2013-06-12 22:53:30 -0400
committerGene Cumm <gene.cumm@gmail.com>2013-06-12 22:53:30 -0400
commit985d269eaece49c4ef66208568cc8bfafdc45052 (patch)
parenta73ac7b6a6b1c3c975c32672cb2a74f11b8bdee4 (diff)
txt/syslinux-cli.txt: Path rules
Signed-off-by: Gene Cumm <gene.cumm@gmail.com>
1 files changed, 28 insertions, 0 deletions
diff --git a/txt/syslinux-cli.txt b/txt/syslinux-cli.txt
index fa6a4dc5..a338d9b6 100644
--- a/txt/syslinux-cli.txt
+++ b/txt/syslinux-cli.txt
@@ -59,6 +59,34 @@ the file is not found in the following order: .0[*PXELINUX* only],
// Is this true of file names specified in a config? As of when?
+=== PATH RULES ===
+The current working directory is *always* searched first, before PATH,
+when attempting to open a filename. The current working directory is
+not affected when specifying a file with an absolute path. For
+example, given the following file system layout,
+ /bin/
+ ls.c32
+ libls.c32
+ /foo/
+ libls.c32
+assuming that the current working directory is /boot/foo, and assuming
+that libls.c32 is a dependency of ls.c32, executing /boot/bin/ls.c32
+will cause /boot/foo/libls.c32 to be loaded, not /boot/bin/libls.c32,
+even if /boot/bin is specified in the PATH directive of a config file.
+The reason that things work this way is that typically a user will
+install all library files in the Syslinux installation directory, as
+specified with the --directory installer option. This method allows
+the user to omit the PATH directive from their config file and still
+have things work correctly.
== AUTHOR ==
This AsciiDoc derived document is a modified version of the original
*SYSLINUX* documentation by {author} <{author-email}>. The conversion