similar to: Development Question for version 2.11 of isolinux

Displaying 20 results from an estimated 100 matches similar to: "Development Question for version 2.11 of isolinux"

2007 Aug 22
5
Slow concurrent actions on the same LVM logical volume
Hi 2 all ! I have problems with concurrent filesystem actions on a ocfs2 filesystem which is mounted by 2 nodes. OS=RH5ES and OCFS2=1.2.6 F.e.: If I have a LV called testlv which is mounted on /mnt on both servers and I do a "dd if=/dev/zero of=/mnt/test.a bs=1024 count=1000000" on server 1 and do at the same time a du -hs /mnt/test.a it takes about 5 seconds for du -hs to execute: 270M
2005 Dec 12
2
Configuration question for syslinux 3.11 menu and ontimeout option
I just started to play with syslinux 3.11 and have some problems with the configuration. I want to implement following: wait 5 seconds till the users chooses the right label. if nothing is done for 5 seconds it should boot from next boot device specified by the BIOS. I configured syslinux like that: default menu.c32 prompt 0 timeout 50 ONTIMEOUT localboot totaltimeout 200 display boot.msg MENU
2008 Jul 30
1
Filesystem usage after mkfs.ocfs2
Hi ! I recognized today that if I create a new filesystem that already 2% of the filesystem are used: /dev/mapper/raid3VG-sts007 79G 1.1G 78G 2% /srv/xyz/sts/007 even if the filesystem is completly empty. What are this 2% of (hidden) data or is it some kind of reserved blocks ? yours Arnold -- Arnold Maderthaner J4Care Inc.
2008 Sep 09
1
[PATCH] parsecmd: show keyword in err_noparm message
Show which keyword is missing the parameter. - Sebastian Index: syslinux-3.72-pre5/core/parsecmd.inc =================================================================== --- syslinux-3.72-pre5.orig/core/parsecmd.inc 2008-06-23 17:11:47.000000000 +0200 +++ syslinux-3.72-pre5/core/parsecmd.inc 2008-09-09 22:11:35.000000000 +0200 @@ -82,9 +82,11 @@ ; No parameter .noparm: mov si,err_noparm -
2015 Jan 15
0
PXE Error Reporting
Hello Andreas, Andreas Gruenbacher wrote: > Sebastian, > > On 01/15/2015 12:49 AM, Sebastian Herbszt wrote: > > which version of pxelinux were you trying? Looks like < 5.x. > > the one from Fedora 20, syslinux-4.05. > > It turns out that pxelinux.0 from Fedora 21, syslinux-6.03, reports > "Failed to load ldlinux.c32" when ldlinux.c32 can't be
2002 Mar 08
0
PXELINUX: suggestion for improvement
Hi, We're planning to deploy PXELINUX as a primary kernel loader in cluster environment. Problem is that we plan to have IP numbers assigned dynamically while there is no guarantee that all machines has same CPU architecture. This makes IP-based config search algorithm inappropriate for our purposes because we [naturally] expect loaded kernel to match hardware. For this reason I've
2004 Oct 07
1
x86 vs. x86_64 detection proof of concept patch (try two)
Greetings all, Sorry, resending this with the attachment inline. First of all, a disclaimer: Please forgive my horrible assembly code. This is just a quick munging of code to achieve x86 versus x86_64 detection within pxelinux. So please look at it as a proof of concept and not a real piece of code. :) For example it only works on pxelinux and has no thought for extending it beyond simple x86
2013 Jul 12
0
[PATCH 001/001] core/serial: Add support for serial output functions.
[PATCH 001/001 v2] core/serial: Add support for serial output functions. Second version fixes an initialization issue. ----- This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts
2012 Apr 17
2
[GIT PULL] elflink warning fixes and auto extension support
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
2013 Jul 12
2
[PATCH 001/001] core/serial: Add support for serial output functions.
This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts respectivelly. For QEMU, you only need to specify the option -serial stdio. If you use another VM, find how you can redirect the serial
2013 Jul 11
2
make efi64 install in syslinux-6.02-pre3 fail
Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***
2010 Mar 21
0
[PATCH] core: use MY_NAME for syslinux_banner
Use MY_NAME for syslinux_banner in isolinux and pxelinux. This is already done in ldlinux and extlinux. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/isolinux.asm b/core/isolinux.asm index ef7d92d..23429bd 100644 --- a/core/isolinux.asm +++ b/core/isolinux.asm @@ -1034,7 +1034,7 @@ writestr_early equ writestr ; Data that needs to be in the first sector ;
2013 Jul 12
0
make efi64 install in syslinux-6.02-pre3 fail
On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote: > Hello, > > I tried to make my own binary with 'make efi64 install' but it fail with > > make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' > make[2]: ***
2015 Apr 14
0
debugging pxelinux
On Tue, Apr 14, 2015 at 11:25 AM, Patrick Welche via Syslinux <syslinux at zytor.com> wrote: 0) What version(s)? Have you tried the precompiled ones at kernel.org? > I have reason to believe that an odd box that is having boot trouble has > three instances of "!PXE" in the chunk of memory that "Method D" should > look at. 1) You can't have 3 instances in
2009 Feb 08
2
Graphic boot ...
Hi Peter and Group, First, thanks for great boot system. My goal is to create a boot process that is clean from any text message and shows simple graphics at startup. That graphic image will last until the X server is starting (with the same background, might be with different resolution). My reason is, that many end users prefer graphics on simple cryptic text messages. Messages will be
2014 Jun 09
1
syslinux (pxelinux.0) debug prints
On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >
2008 Aug 31
1
[RFC][PATCH] ui: label completion on tab key
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
2003 Dec 27
0
2 disks boot patch
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 ==
2010 Jul 15
1
Accessing command_line from core C code
I tried to replace display_labels asm code (ui.inc) with new C code (pm_display_labels), but the data i access in command_line doesn't seem to be always up to date. The patch i am working on is only for PXELINUX because of different vkernel structure: diff --git a/core/com32.inc b/core/com32.inc index 111590c..f19df7c 100644 --- a/core/com32.inc +++ b/core/com32.inc @@ -135,6 +135,7 @@
2003 Dec 27
0
FW: 2 disks boot patch
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 ==