search for: findpath

...ple, but for any reason, when instructions are called by puppet they are not working instead you call directly, same instructions, using DOS, where works sweet.* * * *Here is part of the code:* $cmd = "C:\\Windows\\System32\\cmd.exe" $scPath = "C:\\Windows\\System32\\sc.exe" $findPath = "C:\\Windows\\System32\\find.exe" # Create Service exec{''Create Service nsc-devops'': command => "${cmd} /c \"${scPath} create nsc-devops binPath= \"C:\\NSClient++\\nsclient++.exe\" DisplayName= \"NSClient Devops\" Start= \&quo...

...list_add_tail(&entry->list, &PATH); return entry; But that will cause the code that attempts to put the CurrentDirName at the beginning of the list to break because it will end up at the end. Probably better to move the check for current working directory location for a file to findpath() like this: diff --git a/com32/lib/sys/module/common.c b/com32/lib/sys/module/common.c --- a/com32/lib/sys/module/common.c +++ b/com32/lib/sys/module/common.c @@ -67,6 +67,14 @@ FILE *findpath(char *name) if (f) return f; + /* Look in CurrentDirName */ + /* Cu...

...COM32 module com32/lib/sys/module/common.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/com32/lib/sys/module/common.c b/com32/lib/sys/module/common.c index eeb2607..9d29075 100644 --- a/com32/lib/sys/module/common.c +++ b/com32/lib/sys/module/common.c @@ -64,6 +64,10 @@ static FILE *findpath(char *name) char *p, *n; int i; + f = fopen(name, "rb"); /* for full path */ + if (f) + return f; + p = PATH; again: i = 0;

...tries in the PATH directive and they're also used in TFTP-style paths. While I see that you don't use the PATH directive in your config files, a list is built internally nevertheless. Based on my testing your's will look something like, "::/arch/boot/syslinux/" The code in findpath() sees the first ':' and goes nutso. I'm not quite sure what the proper solution is. Clearly using ':' to separate entries was a terrible idea, but presumably some people are using that syntax now and it would cause issues if we changed it - the PATH directive has been supporte...

Hi all, The help message in debufs.ocfs2 is not consist among ``extent'', ``findpath'', ``locate'', ``ncheck'' and ``help''. ``help'' show that extent accept a block number as its argument. ---8<--- extent <block#> Show extent block ---8<--- But ``extent'' says its argument is an inode number. ---...

...y're also used in > TFTP-style paths. While I see that you don't use the PATH directive in > your config files, a list is built internally nevertheless. Based on my > testing your's will look something like, > > "::/arch/boot/syslinux/" > > The code in findpath() sees the first ':' and goes nutso. > > I'm not quite sure what the proper solution is. Clearly using ':' to > separate entries was a terrible idea, but presumably some people are > using that syntax now and it would cause issues if we changed it - the > PATH di...

Hi All, I have the following adjacency matrix for a directed graph: [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [1,] 0 0 0 0 0 0 0 0 [2,] 0 0 0 0 0 0 0 0 [3,] 1 0 0 0 0 0 0 0 [4,] 0 0 1 0 0 0 0 0 [5,] 0 0 1 0 0 0 0 0 [6,] 1 1 0 0 0 0 0 0 [7,] 0 0

...of git://zytor.com/users/pcacjr/syslinux into merge/elflink/xfs hdt-cli: Correct malloc() size argument screensize: Dereference pointers when checking cols/rows pxe: Don't leak inode on timeout module: Fix memory leak in spawn_load() module: Fix off-by-one error in findpath() core/elflink: Fix off-by-one error Merge branch 'coverity' into elflink Paulo Alcantara (46): EXTLINUX: Initial XFS filesystem support mbr: Add support for loading VBRs from XFS filesystems xfs: Initial skeleton for XFS filesystem support xfs: Implemen...

...t for weak symbols elflink: Replace __intcall() with direct function calls Use pxe_call() instead of COMBOOT API com32: Use --as-needed for LDFLAGS ldlinux: Return to command prompt after loading COM32 rawcon_read: Fix reading high part of input keys ldlinux: Use findpath() to lookup filenames com32/chain/utility.c | 30 ++------- com32/cmenu/Makefile | 8 +- com32/cmenu/libmenu/syslnx.c | 22 +++---- com32/elflink/ldlinux/chainboot.c | 5 +- com32/elflink/ldlinux/config.h | 2 + com32/elflink/ldlin...

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

...st union syslinux_derivative_info *sdi; diff --git a/com32/lib/sys/module/common.c b/com32/lib/sys/module/common.c index 8547036..b763704 100644 --- a/com32/lib/sys/module/common.c +++ b/com32/lib/sys/module/common.c @@ -59,40 +59,28 @@ void print_elf_symbols(struct elf_module *module) { FILE *findpath(char *name) { + struct path_entry *entry; char path[FILENAME_MAX]; FILE *f; - char *p, *n; - int i; f = fopen(name, "rb"); /* for full path */ if (f) return f; - p = PATH; -again: - i = 0; - while (*p && *p != ':' && i < FILENAME_MAX - 1) { - pa...

...st union syslinux_derivative_info *sdi; diff --git a/com32/lib/sys/module/common.c b/com32/lib/sys/module/common.c index 8547036..b763704 100644 --- a/com32/lib/sys/module/common.c +++ b/com32/lib/sys/module/common.c @@ -59,40 +59,28 @@ void print_elf_symbols(struct elf_module *module) { FILE *findpath(char *name) { + struct path_entry *entry; char path[FILENAME_MAX]; FILE *f; - char *p, *n; - int i; f = fopen(name, "rb"); /* for full path */ if (f) return f; - p = PATH; -again: - i = 0; - while (*p && *p != ':' && i < FILENAME_MAX - 1) { - pa...

...ers its own new search, according to > all these rules. Correct. > 3_ When the c32 file is explicitly referenced by an absolute path, the > explicitly-referenced c32 file is search-for in such location first. Correct. This question forced me to go stare at the code ;-) Specifically findpath() and open_file(). Every time we attempt to open a .c32 module we call fopen() and the call stack ultimately looks like this, fopen() open() open_file() searchdir() So this is where the "search for absolute path first" semantics come from. This part is the same for...

On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > Either that or make the path a list rather than a string, using the > normal word separators when entered on the command line, a bit like the > (t)csh does. That is a bigger change but is probably a better solution. How would this solution handle filenames containing spaces? Would we need to escape (presumably with a backslash)

...> > diff --git a/com32/lib/sys/module/common.c b/com32/lib/sys/module/common.c > index 8547036..b763704 100644 > --- a/com32/lib/sys/module/common.c > +++ b/com32/lib/sys/module/common.c > @@ -59,40 +59,28 @@ void print_elf_symbols(struct elf_module *module) { > > FILE *findpath(char *name) > { > + struct path_entry *entry; > char path[FILENAME_MAX]; > FILE *f; > - char *p, *n; > - int i; > > f = fopen(name, "rb"); /* for full path */ > if (f) > return f; > > - p = PATH; > -again: > - i = 0; > - while (...

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at

.... I.e. we'll keep the list of files for lib/System and anything else that needs to be tested on multiple machines but use a wildcard in the places that are pure/vanilla C++ and a check-in on one platform is pretty much guaranteed to work everywhere. (3) Another thing you'll run into is the FINDPATH macro function in the Makefile.rules.am. This is a hack currently implemented for simplicity in the tools/*/Makefile.am files. What we eventually want to do is put all the libraries into one directory and use a -L option to find them. (4) We've recently discovered that executable size is abou...

> On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > > I have a question about the PATH directive. In fact, the question is > > not about how it is currently working, but about its intention or goal, > > or how it was supposed to work (or how it was thought about for the > > 5.00 release). > > > > Previous discussions about the PATH directive in the Syslinux

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

...se rules. > > Correct. > > > 3_ When the c32 file is explicitly referenced by an absolute path, the > > explicitly-referenced c32 file is search-for in such location first. > > Correct. > > This question forced me to go stare at the code ;-) Specifically > findpath() and open_file(). > > Every time we attempt to open a .c32 module we call fopen() and the call > stack ultimately looks like this, > > fopen() > open() > open_file() > searchdir() > > So this is where the "search for absolute path first&quo...