similar to: SAY command (mis)behaviour?

> > I boot my system with the attached extlinux.conf, which has some > entries to boot old kernels. When i'm booting the old versions i'd > like to have a reminder message recalling me that the most recent > kernel is not being used, so that i don't forget to switch back to it, > for example after many days of uptime. > > Now, is it normal that _every_ SAY

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

Hello, I just setup a Xen server and wanted to use bond0 for my network connection. I ended up downloading and addeding the attatched file and making the following change in /etc/xen/xend-config.sxp. I added this line: (network-script 'network-bond netdev=bond0') Would this line be a good one to add to the commented lines and include the network-bond file in the scripts? Just thought

On Thu, Nov 01, 2018 at 04:51:46PM +0000, Ady Ady via Syslinux wrote: > > ... > > Now, is it normal that _every_ SAY command is executed no matter which > > LABEL block is being booted? > > > Indeed, "SAY" is a "global" directive, not a "per-label" directive. Oh thanks, this is what i was suspecting... that was the missing piece indeed.

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

On 8/5/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Since you are using only 2 menu entries, would you consider the > possibility of using the msg file(s) and the boot prompt, while > avoiding the use of (vesa)menu.c32 for this particular project? If you > do, there is room for improvements. > > Thanks for the info. Yes, I previously did not have a menu, for

I?ve been trying to get the dd of an iso to a usb flash drive to work for CentOS 6.7. It is working with the CentOS 7 DVD1 iso (x64), but if I use the same process with 6.7 bin dvd1 iso or the 6.7 live dvd, the flash drive will not boot. I thought 6.x and forward could be done like this. -wes

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

The followings WORKS OK in Syslinux-4.06 LABEL ** ^TEST IMG/ISO File. kernel /test/memdisk initrd test/filename.iso append iso # [if not use iso raw] TEXT HELP [Tab] >Use (i) iso initrd=test/filename.iso OR (ii) initrd=test/filename.extn ENDTEXT However sorry to say FAILS in Syslinux-5.01 Thanks in advance. Prof S W Damle

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

> Thank you for your fast and in-depth reply, and for the practical > example. I think i will dig deeper into the modules part of the wiki, > which i skipped when i first configured the bootloader some time > ago... One of the "over-complicated" ways to circumvent the limitation (i.e. SAY being a global directive, not a per-label directive) without using modules would be

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

On Tue, 25 Jun, at 01:09:47PM, H. Peter Anvin wrote: > Not really... let's just document "make bios". There's preliminary documentation in doc/building.txt. -- Matt Fleming, Intel Open Source Technology Center

I've been using linux:TC from a USBstik in order to not break the M$ capability, as previously always happened. Since TC runs in RAM, it has many extra problems; like reinstalling all the apps and your private settings at each boot. The sample isolinux.cfg which I've been emailed by the oficianado is very unfamiliar and worrying. Where is the official syntax ? -- Without knowing if/how

Un texte encapsul? et encod? dans un jeu de caract?res inconnu a ?t? nettoy?... Nom : non disponible URL : <https://stat.ethz.ch/pipermail/r-help/attachments/20100818/5f203714/attachment.pl>

I just encountered my only bug w/ the ISOLINUX+VESAMENU combination from 3.52-pre5. Updated a *working* CD project w/ the new ISOLINUX+VESAMENU combo just last week. Booting my preferred Linux distro (Slax-6) from my custom CDs work perfectly, however when I updated a CD project that includes BartPE/WinPE, BartPE fails to boot w/ 'CDBoot can not boot CD: error 4" msg. For the

All, Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying & failing to do this. I haven't UEFI-booted RHEL7.0 kernel via syslinux before. (But I have UEFI pxelinux booted Fedora 20, which is approximately RHEL7.0.) I remember HPA mentioned that older Linux kernels required "UEFI boot assist", something that GRUB2 offers but syslinux does not. And

I have just created an ISO containing Fedora and ISOLinux as the bootloader. This is the ISO creation command: genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e