similar to: Handling error scenarios in the core

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

Hi, For some time now I have been using pxelinux to add a helpful 'administrator' boot mode to our workstations with the following 'pxelinux.cfg/default' config: ---- DEFAULT local PROMPT 0 TIMEOUT 0 TOTALTIMEOUT 1 ONTIMEOUT menu ALLOWOPTIONS 0 NOESCAPE 0 LABEL local LOCALBOOT 0 LABEL menu CONFIG /pxelinux.cfg/default-menu ---- This is great as by

We modified our copy of syslinux. We're now sharing those modifications. That's so that: 1. We fulfill our requirements under the GPL 2. Our modifications might be picked up and included in the base code. That way we wouldn't have to make the same modifications, again, later. Since we're using CentOS 5.3, and CentOS 5.3 derives from RHEL 5.3, and RHEL 5.3 uses

The following changes since commit 8c576f1fe03e34879921311f46613a35c6530000: Merge remote-tracking branch 'mfleming/for-hpa/elflink/fix-compiler-warnings' into elflink (2011-03-16 12:53:58 -0700) are available in the git repository at: git://git.zytor.com/users/mfleming/syslinux.git for-hpa/elflink/ldlinux Matt Fleming (1): ldlinux: Perform auto-boot if NOESCAPE set in config

Hello, pxelinux does not has any password protection, unfortunately my Assembler skills are not that good to extend pxelinux with a global password option. Nevertheless this feature is important, because not every user should have the right to startup an installation of a machine over network. The following patch is only a dirty hack, but other might find it usefull too.(so I post it here) It

Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G

When Syslinux is running in a VMWare virtual machine and Ctrl-P is typed while editing the boot command line, insert the contents of VMware's clipboard. This allows text to be copied from the host (or wherever the console client is running) into Syslinux. Signed-off-by: Jeffrey Hutzelman <jhutz at cmu.edu> --- core/ui.inc | 72

On 13.07.2015 12:08, Gene Cumm wrote: > systemd Mailing List <systemd-devel at lists.freedesktop.org> would be > the wrong address. > > On Mon, Jul 13, 2015 at 5:33 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 03.07.2015 21:35, Gene Cumm wrote: >>> On Jul 3, 2015 1:34 PM, "poma" <pomidorabelisima at gmail.com> wrote: >>>

This implements the label completion on tab key idea. It does introduce "labelcompl" as new config keyword. The default value is 0 so it does not change current behaviour. If you press tab with an empty command line it will display all labels. If the command line contains any characters it will display the matching labels. This patch is only intended for testing since i didn't check

Hello List, I have below a patch (against Syslinux-1.62), which adds a pseudo-kernel 'swap' which swaps device numbers of the boot device and the first harddisk. It was made for a system equipped with a DiskOnChip (www.msys.com) device which 'steals' the device# of teh first harddisk, This patch is used to enable the syslinux on the DoC to continue booting from the harddisk as if

Peter, Paulo reported some problems with his config files under ISOLINUX and PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches I've pushed to the elflink branch fix this and also fix parsing of the ALLOWOPTIONS config directive. The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389: get_key: Valid key values are positive (2012-04-17 11:25:53

Dear friends, In accordance with RFC 3942 I would like to submit the following DHCP options for official consideration. These options are used by PXELINUX, which is part of the SYSLINUX distribution, and although exact usage count is impossible to determine, is widely held to be the most widely used method for booting Linux from a network. ---------- Option 208: pxelinux.magic (string)

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

When running autotest with AUTOFEATURE=true, all of my specs and features run fine. However, if I have a feature containing a scenario that fails, autotest lists that feature, but then returns "0 scenarios", and then runs all of the features again. Any idea why this might be? Best, Tom -- Posted via http://www.ruby-forum.com/.

Just curious if anything special needs to be done to use the Rails fixture scenarios plugin(http://code.google.com/p/fixture-scenarios/) with rspec? Would I just create the "scenarios" inside the spec/fixtures dir, as opposed to the test/fixtures dir? Thanks, Steve

Clicking on the "For more information, click here" link on the Digium site nice brings back up the same page I was looking at before, without any additional G.729 information that I can see. I'm wondering if some kind asterisker out there could provide us neophytes with some "typical scenarios" where that codec would be useful to us. For instance, I assume that it

Here are three different scenarios in which the browser() exits when I don't want it to. These are all related to the browser accepting either c or (return) to exit. I would like an option to turn off the (return) behavior in order to avoid these problems. # Case 1 - when calling help # Note, I am using ESS in emacs; this is probably an interaction # with ESS handling of ? help. > f