similar to: Syslinux 6.03 for booting Mac Intels?

> Hi, > > So far I use the official binaries to boot an USB installer > in UEFI and BIOS mode. > > I want to add a (recent) MacBooks target. > > I know that needs to set up on the device an HFS+ partition with a > specific layout, but my question is: do you know if the official > binaries: > $SYSLINUX_SRC/efi64/efi/syslinux.efi >

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

Hi, dovecot's imap process segfaults when I search a virtual mailbox using the fts_squat plugin. Is this supposed to work, or a known bug? I've seen some changes commited to fts_solr a couple of months ago that where supposed to fix search issues on virtual mailboxes, maybe fts_squat needs to be fixed to? log === rawlog ------ 3551 SELECT "INBOX.virtual.unseen" 3552 UID

Hi, [ouch, it take me a year? thank you all for this very interesting thread that I'm going to finish reading now.] Pete Batard via Syslinux: > I'll skip the EFI part of tails (that uses grub/EFI) to talk only > about the BIOS/Syslinux part. JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS and 64-bit UEFI. > So, one thing Rufus will need to do is find a

Hi, I have just installed dovecot and offlineimap on my laptop for syncing with my gmail, and reading in gnus, as outlined in this article: http://sachachua.com/wp/2008/05/08/geek-how-to-use-offlineimap-and-the-dovecot-mail-server-to-read-your-gmail-in-emacs-efficiently/ I am using Debian Etch, and I am the only user. The only change I made to the default dovecot.conf file was to set:

Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux leaves long mode in kernel_jump assembly routine does not follow AMD64 specifications. More precisely: 1. After setting a new GADT, `cs` has to be refresh by doing a long jump, but it is not 2. Other segments have to be updated, but they are not 3. Disabling paging has to be done before disabling long mode, but the

>What I reminder from it: > > The first "isohybrid" was in perl. > But that made perl a run-time dependency. > > A compiled version of "isohybrid" removed that > run-time dependency on perl. > > >What I think of it: > > The Perl variant of isohybrid should be removed > from the source tree. One advantage of the Perl one for me

Hi, we're trying to solve CVE-2008-4870 = rhbz#436287 = dovecot.conf is world readable - possible password exposure. This problem seems to be little more complicated than we thought. dovecot.conf can contain passphrase for ssl key, which is available for everyone since dovecot.conf has world readable permissions. (In CVE's description is note that it RHEL's/Fedora's problem,

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

Hi, at [Tails] we're in the process of shipping hybrid ISO images by default again. We're using `isohybrid -h 255 -s 63' to do that (thanks to the advice we got on this mailing-list a few months ago!). And then, we've discovered that sometimes, isohybrid produces ISO images whose size is not a multiple of 2048 bytes. Who cares? ... may you ask. Well, apparently, VirtualBox does:

Hello All, This is my first time requesting help, so please bear with me. I don't upgrade Syslinux very often (only when the need arises), until now I have been using version 4.05. However, I have recently acquired several UEFI servers that are in need of being able to do OS installations via pxelinux. I have upgraded to Syslinux version 6.03, however I am not able to compile my custom

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,

> Le 13 ao?t 2019 ? 14:16, Sami Ketola via dovecot <dovecot at dovecot.org> a ?crit : > > > >> On 13 Aug 2019, at 14.58, James Brown via dovecot <dovecot at dovecot.org> wrote: >> >> I?m thinking of getting Solr working with my Dovecot server. Server is new 6-core Mac Mini, mail store of over 1/2 TB. Mailboxes with 100s of thousands of messages.

Actually, as you may have questions with some elements you'll see in the log, and especially: Detected Syslinux version: 6.03/20150819 (from '/EFI/BOOT/isolinux.bin') So I should point out that EFI/grub is actually used by the tails people to chain load EFI/Syslinux (hence the ldlinux.e64, ldlinux.c32 as well as isolinux.bin one also sees in /efi/boot/). As a result, in the

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).