similar to: git repo: primary/secondary/unofficial

On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: > > > I'm starting this thread to discuss what git repository should be > > designated as primary and which repositories should be designated as > > secondary. > > > > For years, git.kernel.org has been the primary repo, updated at least > > with every full and pre- release.

> I'm starting this thread to discuss what git repository should be > designated as primary and which repositories should be designated as > secondary. > > For years, git.kernel.org has been the primary repo, updated at least > with every full and pre- release. git.zytor.com has been the > secondary and development repo. > > Additionally, I've maintained my

On Sun, Jun 14, 2015 at 4:33 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: >> >> > I'm starting this thread to discuss what git repository should be >> > designated as primary and which repositories should be designated as >> > secondary. >> > >> >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 18/01/15 a las 13:18, Gene Cumm escribi?: > On Sun, Jan 18, 2015 at 6:44 AM, Angel <angelv64 at gmail.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hello. >> >> I'm trying to setup an multiboot USB, mainly to install Debian >> using netinst images. >> >>

> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative

This got me closer, but it got to "Encapsulating winpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. Here is relative portion of pxelinux: LABEL SCCM OSD Boot MENU LABEL ^2. SCCM OSD Boot com32 linux.c32 append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim TEXT HELP

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

I have some questions about "ALLOWOPTIONS 0". [quote] ALLOWOPTIONS flag_val If flag_val is 0, the user is not allowed to specify any arguments on the kernel command line. The only options recognized are those specified in an APPEND) statement. The default is 1. [/quote] My understanding of the behavior of "ALLOWOPTIONS 0" is that unless I type-in a command that is exactly

>Several points (please read the whole email before doing anything else): > >1_ It is not clear whether you still need/want to "avoid displaying" the menu border (i.e. make it transparent). You mentioned that you >eventually managed to do so, but then you also ask (again) about vesamenu.c regarding the menu border. Or, perhaps... Do you >actually, really, want to

In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Recent (testing) Clonezilla versions include changes related to >booting problems, so there are valid reasons to try the very latest >version available. At the time I am writing this email, Clonezilla >Live 2.2.1-22 is the latest available (at this moment, under

Hi, I've just pushed out a last -pre release before 4.06 final. The purpose of this prerelease was to make sure that all the build infrastructure is configured correctly and to ensure that the win installer problem is now gone (I've done the build on an F16 machine which should have a working mingw toolchain). Barring any major problems I'll do the final release this week. -- Matt

The config.c32 module (and the CONFIG directive) is not behaving as expected when using syslinux.exe 5.00pre11 as installer. To replicate: 1_ The content of the device: /dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL

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

My summary: reviewing ALLOWOPTIONS found reasons for further reviewing 'ALLOWOPTIONS' Op 2014-07-12 om 04:35 schreef Ady: > > > I have some questions about "ALLOWOPTIONS 0". > > > > [quote] > > ALLOWOPTIONS flag_val > > If flag_val is 0, the user is not allowed to specify any arguments on > > the kernel command line. The only

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote: > Am 27.06.2013 22:08, schrieb Matt Fleming: > > I'm planning on releasing 6.01 next week. The list of changes (so far) > > are appended below. This is going to be a quick bug fix release, mainly > > because of the rather embarrassing bug in the 6.00 that prevents booting > > a Linux kernel on BIOS. The idea is to

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

Hi I have tried to install syslinux 4.06 on the SD card again, it works like a charm. I am being very carefull with c32 files from the same version bootloader. No success. I am also unmounting /dev/sdb1 before installing syslinux, as mentioned in the given documentations. In the pasted syslinux.cfg content--- I have also tried using only one DEFAULT directive. No success. syslinux boots

Thanks. I've looked through all the links, and it seems everything is fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, but it didn't help). I'd be glad to provide more details, but the error message is the only info I've got by now. It seems nothing else can be got from syslinux shell without modifiying the code. I've tried to make it load the kernel