similar to: Acceptable version mismatch between syslinux 6.0N's MBR/ldlinux.sys and *.c32?

Hi, first, thanks a lot, Ady and Gene, for your prompt and very useful replies! Ady wrote (11 Jun 2014 20:18:43 GMT) : > Although I haven't tested it lately, the Tuxboot tool should be able > to use the version of Syslinux included in your ISO images so to > transfer it to a (USB) drive. Since it works for other Debian-based > distros, it might answer to your needs.

> 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

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:

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, 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:

>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, > > first, thanks a lot, Ady and Gene, for your prompt and very > useful replies! > > Ady wrote (11 Jun 2014 20:18:43 GMT) : > > Although I haven't tested it lately, the Tuxboot tool should be able > > to use the version of Syslinux included in your ISO images so to > > transfer it to a (USB) drive. Since it works for other Debian-based > >

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 $SYSLINUX_SRC/efi64/com32/elflink/ldlinux/ldlinux.e64 work in that context? Best

> 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, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

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

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

Hi, since the Tails ISO grew from ~900MB to ~1.1GB, we see this warning when running isohybrid on it: isohybrid: Warning: more than 1024 cylinders: 1045 isohybrid: Not all BIOSes will be able to boot this device I guess that's fully expected. And, as expected, we get boot failure reports from users. So, my question is: is there a "known optimal" combination of isohybrid

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp

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, > > 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?