similar to: When is PATH directive used?

>> There's nothing in Directives/path that says it applies only to c32. > You probably mean something like "Config#PATH" [...] No, I really did mean Directives/path, which is the first link in the "See Also" under PXELINUX-Multi-Arch. At any rate, it appears that page has been edited within the last couple days, and the new contents are well-written and

With 6.03, I'm trying the "common directory distinct config" approach from http://www.syslinux.org/wiki/index.php?title=PXELINUX-Multi-Arch which essentially sets a different PATH (for BIOS vs EFI64). It seems PATH is correctly used to load .c32 modules, but not to load 'memdisk': PATH syslinux/bios UI vesamenu.c32 <-- WORKS (tries /vesamenu.c32, 404 error,

My architecture has an FPU, but uses integer registers to store floating-point values. So each register can store either an int or an IEEE float. I define a register class like this: def GR32 : RegisterClass<"MyArch", [i32, f32], 32, (sequence "R%u", 0, 32)>; So far so good. However, when I write a rule to store a register: def STORE32r : S32< (outs), (ins

Hi, I'm trying to compile llvm/clang so that: it is compiled on osx 10.6, it runs on osx, but it outputs win32 objects. More exactly, I'm building an app which generates a .c file that doesn't include or link with anything, and I'd like to be able to make a win32 .dll of it on osx. Below is what I'm getting. Full log is here: http://pastebin.com/KsPGvAfW It fails while

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 Mailing > List, and its

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 Mailing List, and its documentation (e.g. "PATH rules") left on me the impression that it was

> 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

Suppose...: - For non-releases: "git" + We take the first 6 chars of git commit - For releases: "ver" + major + "." + minor - For tar-balls: Something clever, maybe involving the date ...that we embed such a version in Syslinux core and in all OS programs and modules. Maybe even with some nearby magic so that a "whichver" command can examine and answer.

On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > So, my first (still incomplete and still inaccurate) attempt to write > some rules about the PATH directive, and ask about remaining doubts!... > > > The search (for c32 files) is supposed to respect the following rules: > > 1_ The search for c32 files is performed according to the following > rules. The search for

On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > Hmm, I thought it was decided to consider the colon (":") character as > deprecated, and instead we should be using a space character as > separator for the PATH directive (or multiple lines). Well, at least as > for the current MASTER HEAD, Syslinux 6.03. Are you referring to commit 1945579 ("PATH: use a linked

Thank you for your reply. > On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > > > Hmm, I thought it was decided to consider the colon (":") character as > > deprecated, and instead we should be using a space character as > > separator for the PATH directive (or multiple lines). Well, at least as > > for the current MASTER HEAD, Syslinux 6.03. >

Is there an alternative to using link(2) to rename files in sftp-server? Some users use sftp to upload files to a vfat partition on an sftp-server, and then renaming doesn't work. This breaks konqueror, for example (from KDE, which u), which upload files first with a ".part" extension and then renames them removing this extension.

> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to

I'm working on setting up a semi-trusted sftp service, and to get it working, I need chroot capability. I've taken the /./ wuftpd magic token code from contrib/chroot.diff and put it into the sftp server. The main problem is that privileges have been dropped by the time the subsystem is exec'ed, so my patch requires that sftp-server be setuid root. Not ideal, I know, but I drop all

Hello Syslinux Team, If I understand correctly (and I should emphasize that condition), the lib*.c32 library modules, when required, are initially searched-for according to the following (fallback) rules: 1_ Search for the relevant lib*.c32 file(s) in the Current Working Directory. 2_ Search for the relevant lib*.c32 file(s) in the directory where ldlinux.c32 is located. Then the lib*.c32

And while we are at it, can you please comment on these patches as well, originally submitted around one year ago. Oh, and I think we can agree, that the secsh-filexfer standardization is dead, so there's not much point in trying to support newer protocol versions, which don't have statfs anyway. Thanks, Miklos ----- This is needed to be able to support statfs operation on an SSH

Martin Maechler <maechler@stat.math.ethz.ch> writes: > (from R-help) > PD> Stephen Eglen <stephen@cogsci.ed.ac.uk> writes: > > > > > generated by R into a latex document. Specifically, the latex package > > > > graphicsx allow you to specify the bounding box of the postscript > > > > file, so that you can just show

> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > Would someone please be so kind to explain / describe the PXERETRY > > directive? > > $ git grep -ni pxeretry > com32/elflink/ldlinux/readconfig.c:1305: else if (looking_at(p, "pxeretry")) > com32/elflink/ldlinux/readconfig.c:1306: PXERetry = >

Hi, After a successful upgrade CentOS 3.8 i386 to CentOS 4.4 x86_64 and, after cleaning old 3.8 packages, yum does not update the x86_64 packages but just the i386's. The rhn-applet see the x86_64 updates but neither yum nor up2date see them. When I run: # yum -d 3 check-update Yum Version: 2.4.3 COMMAND: yum -d 3 Installroot: / Setting up repositories Baseurl(s) for repo:

> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> > there is no convenient way in new_linux_kernel() to control the boot > >> > flags value. > >> > >> This is the part that has me questioning things and trying