similar to: Syslinux 4 git repo url?

Hey guys, I can't seem to figure out how to debug a COM32 app with GDB under qemu. I start "qemu -s" and then "gdb hello.elf ; target remote:1234" but can't set any breakpoints that work. I"m using syslinux4 (pathbased from the repo). Can anyone verify that they can use qemu+com32+gdb with something as simple as com32/samples/hello.c32 ? Also, is it

Here is the initial release: git://github.com/donhiatt/Syslinux-EXT2FS-Library-port.git I am very new to git so I hope I managed to get the repo setup properly. The repo is branched from 'disklib' as I plan to use it for all disk read/write access (I'm currently using modified gpllib/disk/* -- see README). Cheers, don ----- README for ext2fs module. * Description -----------

Hello, I tried doing a clone over ssh with git clone ssh://git.kernel.org/pub/scm/boot/syslinux/syslinux.git foo and I'm being prompted for a password: don at git.kernel.org's password: This worked a few weeks back. I've been on vacation so maybe my brain hasn't restarted just yet. :) Thanks! don

>From the current pathbased branch, linux/syslinux.c, line 421, open() yields an error on a FAT floppy image, 2.88M standard size. At first, this was a floppy that did have a previous version of SYSLINUX installed. I saved that floppy image and tried deleting ldlinux.sys with the same results. I'm still trying to drill away and find more about its status and understand what is

Is there a known problem with fopen and/or fwrite in Syslinux? I'm trying to open a file to write data to but fopen( file_name, "w+" ) fails everytime. fopen( file_name, "r" ) works just fine.

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

This patch fixes a crash in disk.c32 owing to the change in get_error()'s signature. Instead of calling get_error() I just dump the error code. don diff --git a/com32/modules/disk.c b/com32/modules/disk.c index e94a36b..2966173 100644 --- a/com32/modules/disk.c +++ b/com32/modules/disk.c @@ -37,11 +37,8 @@ int main(int argc __attribute__ (( unused )), continue;

Hello, Pardon the newbee question but I'd like to be able to log to disk from within syslinux (extlinux actually, as it's a ext2 fs). fopen("w") does not appear to be implemented (returns EINVAL). Has anyone written the filesystem write support, and if not, any suggested routes? Should I just implement the lower level BIOS disk write support, add the FS layer, and go from

Hi, I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below. 1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31 LABEL local MENU DEFAULT MENU LABEL Local Boot ... (skip PXE boot) KERNEL chain.c32 APPEND hd0 0 2) works on all three. LABEL local

Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number of leading multimedia web groups already support Theora.

Theora is a video codec with a small CPU footprint that offers easy portability and requires no patent royalties. While the Theora bitstream format was standardized in 2004 and our beta releases have been used by millions, this 1.0 release is an important milestone reflecting the maturity and stability of the Theora codebase. A number of leading multimedia web groups already support Theora.

Hello, Is there any interest in a port of the EXT2FS lib (from e2fsprogs-1.41.11) to Syslinux? I have EXT2/3/4 read and write working from within C32 applications. Cheers, don

Hi all, I'm new here so bear with me. I am working on a project at work where we are replacing 1000+ Dell servers. When a new Dell server is delivered to one of our remote offices it will PXE boot off of the existing Dell server and install openSuse and then configure itself. We also PXE boot windows PCs in the remote offices so we needed a way to assign a large range of MAC addresses to a

Just a status update on my progress with ROSH: I now have it able to compile as a COM32 and Linux ELF on the pathbased branch. The main reason I am using the Linux ELF is to test and compile a little easier and faster. At this point, it's approaching a stable, usable state. However, it depends on some changes to libutil, the main COM32 library, and the Syslinux core. I think I have the

This will be a git feature in git 2.23 (in Q3 2019). It will allow git blame to ignore revisions with --ignore-rev, which the user can even specify in their git config. Relevant git blame documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125 Relevant git config documentation change:

On Jul 23, 2019, at 9:17 AM, JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> On Jul 23, 2019, at 8:30 AM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> As a very frequent explorer of history, I really don't think this is >> as big an issue as it may seem. Even absent refactorings, you often >> run into the

Hello, Would com32 modules be considered the same as an ordinary Linux executable with respect to LGPL? That is, as long as you released any changes to syslinux/com32 libs would you also have to release the source to the com32 module? Thanks for your time.

I am attempting to bring R-3.0.2 functionality into a project with a very large C++ codebase. The existing codebase already has a LENGTH function defined. R also defines a LENGTH function. I first compiled R as a shared library and linked it into this existing codebase, along with RInside. When I run a parseEvalQ with a linear model command it will stack dump. Looking at the backtrace, what is

On 2/6/19 9:35 AM, Ady Ady via Syslinux wrote: >> however, due to the issues with continuing >> to keep the main archive on kernel.org, I have moved the release archive to: > > Will the archive repo in kernel.org ever be updated again? > > Will the archive repo in kernel.org be updated when some > potential/hypothetical/future final/gold version gets released? >

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our