search for: loadconfig

...ttp://www.syslinux.org/commit/7d9c9eca562857fed25b4c8ef902e3de968d7631 > Author: Ady <ady-sf at hotmail.com> > AuthorDate: Sun, 20 Sep 2015 15:35:52 -0400 > Committer: Gene Cumm <gene.cumm at gmail.com> > CommitDate: Sun, 20 Sep 2015 15:35:54 -0400 > > core/fs/lib/loadconfig.c: Add architecture-specific config name to search > > When multiple architectures are on a single media, all will try to use the > same config, preventing PATH from pointing to an architecture-specific > directory. > > Signed-off-by: Gene Cumm <gene.cumm at gmail.com> >...

...for > all variants, just for the case that the "rename" was forgotten when copying > over the files from an iso9660 CD/DVD to FAT32 flash disk. > > Regards > -Klaus A simpler patch for just the config filenames (whitespace changed for email): diff --git a/core/fs/lib/loadconfig.c b/core/fs/lib/loadconfig.c index 95e6f3f..47101f9 100644 --- a/core/fs/lib/loadconfig.c +++ b/core/fs/lib/loadconfig.c @@ -22,6 +22,11 @@ int generic_open_config(struct com32_filedata *filedata) }; static const char *filenames[] = { "extlinux.conf", +#if defined(__FIRM...

> Their isolinux/isolinux.cfg has > DEFAULT loadconfig > LABEL loadconfig > CONFIG /arch/boot/syslinux/archiso.cfg > The file arch/boot/syslinux/archiso.cfg is readable too. > IIRC, Arch isolinux/isolinux.cfg should say: DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg APPEND /arch/ Or it might b...

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

...n file. The administrator should be able to delegate the task of maintainung the configuration file to the departments: The master configuration file created by the administrator only provides a basic set of boot images and each department should be able to add new ones. Therefore I think that a LOADCONFIG command would be useful for pxelinux. Here is an expample: pxelinux.cfg/default LABEL load_new_config LOADCONFIG 192.168.0.1::my_new_config when load_new_config is selected pxelinux downloads the file "my_new_config" from the TFTP server with the IP 192.168.0.1 and uses it as its con...

This one is the most critical for my app, but also possibly the most controversial to integrate. A few applications that convert isolinux ISOs to bootable USB, including mine, copy the ISO content to a VFAT formatted partition and then add syslinux to make it bootable. This would work great... if isolinux and syslinux shared the same defaults when it comes to configuration files.

...it variant > - prepend syslnx32.cfg to the config file search path for the 32bit variant For the BIOS cpu architectures, there is already ifcpu[64].c32. In my proposal, I am focusing on EFIIA32 and EFIX64 only. If I understand correctly, your patch seems to be based on "core/fs/lib/loadconfig.c": +#if defined(__amd64__) || defined(__x86_64__) || defined(_M_AMD64) which means (again, if I understand correctly) that it affects BIOS-based systems too. As potential reference, in "gpxe/src/include/gpxe/efi/Uefi/UefiSpec.h" we have: "// EFI File location to boot fr...

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

...ot;/otherdir/" are copied/moved to "/boot/syslinux/" too. So, if the installation directory is one of the standard directories, all works as expected. But if the installation directory is other than the standard ones, the behavior is slightly inconsistent. BTW, "core/fs/lib/loadconfig.c" includes: * This searches for extlinux.conf and syslinux.cfg in the install * directory, followed by a set of fallback directories. If found, * set the current working directory to match. which means that we are failing to do what that paragraph says we are supposed to be doing (i.e....

Hello, I wish to recompile only isolinux.bin and nothing else. I made some changes to core/fs/lib/loadconfig.c and now I wish to make (compile) isolinux.bin only. The only way how to do it seems to be "make" in the directory of syslinux sources. But this takes very long and compiles everything. Is there a better way to make only isolinux.bin? Something like "make isolinux" (which obv...

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

...g. The ISO filesystem ? The missing thing is not in the System Area. Overwriting the first 32 KB of the original ISO does not hamper its bootability from DVD. But repacking its content and writing new El Torito does. The repacked ISO images are mountable. Their isolinux/isolinux.cfg has DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg The file arch/boot/syslinux/archiso.cfg is readable too. The boot image isolinux.bin gets to quite a high address by the repacking runs (263858 * 2KB in case of xorriso-1.3.2). But it did not help to apply option --sort-weight 2 /is...

...adequate efi binary for each > EFI architecture (x86 / ia32), overcoming a (prior) limitation in > Syslinux. Syslinux 6.04-pre1 already includes a solution for this > situation. We'll see whether intrigeri bites ;). Assuming you're referring to commit 7d9c9ec ("core/fs/lib/loadconfig.c: Add architecture-specific config name to search"): right, I do intend to look into it, and indeed this will most likely allow us to drop GRUB for ia32 EFI. Thanks! But quite frankly I'd rather wait for 6.04 to be actually released. Now tracked on Tails' side: https://labs.riseup.ne...

...} ;; debian) CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-samba} CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; *) # Use redhat style as default: CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb} CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; esac service_name="samba" loadconfig ctdb_setup_service_state_dir service_start () { # make sure samba is not already started service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVICE_NMB" stop > /dev/null 2>&1 fi...

...nmb} ;; debian) CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-samba} CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; *) # Use redhat style as default: CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb} CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; esac service_name="samba" loadconfig ctdb_setup_service_state_dir service_start () { # make sure samba is not already started service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVICE_NMB" stop > /dev/null 2>&1 fi...

...ile, do you see something like > `.safeseh _elements_exception_handler` somewhere in there? If > not, that's a problem. I think it would also be a problem if > _elements_exception_handler is imported. If so, try making a > thunk for it.> > You can also try running `dumpbin /loadconfig` (or equivalently llvm- > readobj -coff-load-config) on your binary to confirm that the RVA of > _elements_exception_handler appears in the safe seh table.> > On Mon, Aug 20, 2018 at 7:00 AM Carlo Kok via llvm-dev <llvm- > dev at lists.llvm.org> wrote:>> Hi, >> &g...

...r the EFI binaries. For BIOS mode, I stay with the official "stable" branch that is included in Debian. But, the patches don't actually change much of the documented default behavior in BIOS mode. > If I understand correctly, your patch seems to be based on > "core/fs/lib/loadconfig.c": > > +#if defined(__amd64__) || defined(__x86_64__) || defined(_M_AMD64) > > which means (again, if I understand correctly) that it affects > BIOS-based systems too. Right. It's a compile time peprocessor directive, which means that a 64bit version (which is probabl...

...ICE_SMB:-smbd} # CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} CTDB_SERVICE_SMB=smbd ;; *) # Use redhat style as default: # CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb} # CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} CTDB_SERVICE_SMB=smbd ;; esac service_name="smbd" loadconfig ctdb_setup_service_state_dir CTDB_SERVICE_SMB=smbd service_start () { # make sure samba is not already started echo $CTDB_SERVICE_SMB exit 1 service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVIC...

Hi, I'm getting: Unhandled exception at 0x00C211F0 in ConsoleApplication830.exe: 0xC00001A5: An invalid exception handler routine has been detected (parameters: 0x00000001). With some fairly simple SEH enabled routine: define i32 @__elements_entry_point_main(%._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s*) #0 personality i8* bitcast (i32 ()* @_elements_exception_handler to i8*) !dbg

...DB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smbd} ##changed to smbd here #CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; *) # Use redhat style as default: CTDB_SERVICE_SMB=${CTDB_SERVICE_SMB:-smb} CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-""} ;; esac service_name="samba" loadconfig ctdb_setup_service_state_dir service_start () { # make sure samba is not already started service "$CTDB_SERVICE_SMB" stop > /dev/null 2>&1 if [ -n "$CTDB_SERVICE_NMB" ] ; then service "$CTDB_SERVICE_NMB" stop > /dev/null 2>&1 fi...