Displaying 14 results from an estimated 14 matches for "currentdirnam".
Did you mean:
currentdirname
2008 Nov 10
2
[PATCH 1/1] COMBOOT API: Add get current working directory call to most
...n API call to obtain the current working directory. EXTLINUX
will not return the correct value yet however SYSLINUX, ISOLINUX, and
PXELINUX will return the correct value. For the moment, EXTLINUX will
ONLY return "/" (null-terminated of course). In SYSLINUX and
ISOLINUX, it presets the CurrentDirName string to "/" for safety.
PXELINUX copies TFTP Prefix to CurrentDirName (minus the trailing
"/").
Based on current head. Conflicts with a previous patch I e-mailed.
diff --git a/core/comboot.inc b/core/comboot.inc
index 810d825..bdc43ba 100644
--- a/core/comboot.inc
+++ b/co...
2008 Nov 10
1
[PATCH 1/1] COMBOOT API: Add get current working directory call to most (revised)
...at gmail.com>
COMBOOT API: Add get current working directory call to most (Revised)
Signed-off-by: Gene Cumm <gene.cumm at gmail.com>
---
Revised based on discussions on this list. Include trailing "/" on
SYSLINUX and ISOLINUX. Copy TFTP Prefix as-is in PXELINUX.
Initialize CurrentDirName to "./" in EXTLINUX (until a better solution
is created).
Based on current head plus the patch from yesterday.
diff --git a/core/extlinux.asm b/core/extlinux.asm
index c9ec166..972a2f6 100644
--- a/core/extlinux.asm
+++ b/core/extlinux.asm
@@ -43,6 +43,7 @@ SYMLINK_SECTORS equ 2 ; Ma...
2008 Dec 04
2
[PATCH 1/1] COMBOOT API: Add calls for directory functions; Implement for FAT
...API call to obtain the current working directory. EXTLINUX
will not return the correct value yet however SYSLINUX, ISOLINUX, and
PXELINUX will return the correct value. For the moment, EXTLINUX will
ONLY return "./" (null-terminated of course). In SYSLINUX and
ISOLINUX, it presets the CurrentDirName string to "/" for safety.
PXELINUX copies TFTP Prefix to CurrentDirName.
Also adds API calls for opening a directory, reading one filename and
some of its info and closing the directory. These API calls are only
implemented in SYSLINUX for now. ISOLINUX will probably be next on my
lis...
2009 Feb 08
1
[PATCH 1/1] COMBOOT API: Add calls for directory functions; Implement for FAT; Try 2
...API call to obtain the current working directory. EXTLINUX
will not return the correct value yet however SYSLINUX, ISOLINUX, and
PXELINUX will return the correct value. For the moment, EXTLINUX will
ONLY return "./" (null-terminated of course). In SYSLINUX and
ISOLINUX, it presets the CurrentDirName string to "/" for safety.
PXELINUX copies TFTP Prefix to CurrentDirName.
Also adds API calls for opening a directory, reading one filename and
some of its info and closing the directory. These API calls are only
implemented in SYSLINUX for now. ISOLINUX will probably be next on my
lis...
2017 Mar 06
3
PATH directive searches in reverse order with wrong separator
...e/path.c
@@ -32,7 +32,7 @@ __export struct path_entry *path_add(const char *str)
if (!entry->str)
goto bail;
- list_add(&entry->list, &PATH);
+ 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
+++...
2009 Jul 27
1
[PATCH] mboot using module path
...-? product etc.
This includes tags that are valuable to us, and that we cannot keep on
shortening.
I have tried changing FILENAME_MAX / FILENAME_MAX_LG2 definitions to accept more
characters, but it wouldn't compile, the linker script complaining
about the 64k limit.
Another way is to use the CurrentDirName and save the precious
characters for the module
names.
thanks,
Damien
---
from: Damien Nozay
[PATCH 01/04] implement chdir as the way to change the path prefix
chdir is unimplemented and returns ENOSYS. we could rely on chdir when
using the pxelinux stack to give a module path. this implementat...
2013 Jun 12
3
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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.
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...flink/load_env32.c b/core/elflink/load_env32.c
index 0483d86..8551831 100644
--- a/core/elflink/load_env32.c
+++ b/core/elflink/load_env32.c
@@ -124,14 +124,11 @@ void load_env32(com32sys_t * regs __unused)
dprintf("Starting 32 bit elf module subsystem...\n");
- PATH = malloc(strlen(CurrentDirName) + 1);
- if (!PATH) {
+ if (strlen(CurrentDirName) && !path_add(CurrentDirName)) {
printf("Couldn't allocate memory for PATH\n");
goto out;
}
- strcpy(PATH, CurrentDirName);
-
init_module_subsystem(&core_module);
start_ldlinux(1, argv);
@@ -159,30 +156,15...
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...flink/load_env32.c b/core/elflink/load_env32.c
index 0483d86..8551831 100644
--- a/core/elflink/load_env32.c
+++ b/core/elflink/load_env32.c
@@ -124,14 +124,11 @@ void load_env32(com32sys_t * regs __unused)
dprintf("Starting 32 bit elf module subsystem...\n");
- PATH = malloc(strlen(CurrentDirName) + 1);
- if (!PATH) {
+ if (strlen(CurrentDirName) && !path_add(CurrentDirName)) {
printf("Couldn't allocate memory for PATH\n");
goto out;
}
- strcpy(PATH, CurrentDirName);
-
init_module_subsystem(&core_module);
start_ldlinux(1, argv);
@@ -159,30 +156,15...
2013 Jun 11
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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)
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...nv32.c
> index 0483d86..8551831 100644
> --- a/core/elflink/load_env32.c
> +++ b/core/elflink/load_env32.c
> @@ -124,14 +124,11 @@ void load_env32(com32sys_t * regs __unused)
>
> dprintf("Starting 32 bit elf module subsystem...\n");
>
> - PATH = malloc(strlen(CurrentDirName) + 1);
> - if (!PATH) {
> + if (strlen(CurrentDirName) && !path_add(CurrentDirName)) {
> printf("Couldn't allocate memory for PATH\n");
> goto out;
> }
>
> - strcpy(PATH, CurrentDirName);
> -
> init_module_subsystem(&core_module);
&g...
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote:
> James Clement
> > Geert Stappers
> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote:
> > > > The screen displays the following:
> > > >
> > > > PXE Network Boot using IPv4
> > > > ....
> > > > Station IP address is 192.168.205.50
2012 Mar 23
19
[PATCH 00/19][elflink] Improve compatibility with 4.x
From: Matt Fleming <matt.fleming at intel.com>
The following patch series is available at,
git://git.zytor.com/users/mfleming/syslinux.git elflink
All patches are against the 'elflink' branch.
This series fixes a few serious bugs and some behavioural
incompatibilities with the 4.x series.
Matt Fleming (19):
ldlinux: Initialise 'p' before using it.
ldlinux: Parse
2012 Aug 20
13
[PATCH 00/12] Multidisk support
Hello,
the following patches should get multidisk access working.
The syntax accepted is the following:
(hdx,y)/path/to/file
where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk.
the other accepted syntax is using MBR's 32 bits disk signature so for example:
(mbr:0x12345678,2)/foo/bar
would address