similar to: SYSLINUX: Neither prompt nor menu?

> Good day, > > I was expecting this to be a FAQ but haven't been able to find an > answer... how would I arrange to, normally, not be presented with either > prompt or menu when booting, yet be still able to call up prompt/menu > when needed? > > If the right answer is "set PROMPT 0, provide a DEFAULT entry and no UI > entry" then that doesn't

On 31-03-14 02:48, Ady wrote: > First, in the 5+ versions of Syslinux, the shift/alt keys are indeed > not working as expected. This is a bug (among several issues related > to keyboard functionality). Thanks for the reply. I assumed the keys not working would be specific to my straight-booting wish, but playing around with the suggestions that you provided, I see it's indeed more

Hi, I was hoping you could shed some light in usage of the directive MENU HIDDENKEY in syslinux (extlinux 4.04) The docs say: MENU HIDDENKEY key[,key...] command... So, in my conf I have: MENU HIDDENKEY Esc openelec Where openelec is the label of the boot option I want to run only if Esc is pressed. But pressing Esc on boot has no effect. Default is run. So, do I misunderstand the

Hello, Here's a small enhancement feature for menu.c32. Looking for feedback before starting any coding (not sure when I'll have time for implementation) Regards, Dany St-Amant *Problem statement* When MENU HIDDEN is used on an headless server, any noise on the serial console can interrupt the boot; it would be preferable if there only specific keys were allowed to interrupt, reducing

Hi all, new to this list ;) I have a Lenovo Thinkpad T61. lspci|grep VGA says: 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1) I have Slacware64-13.0 and Slackware64-current installed. Nouveau is modularized in all my kernels for -current. A problem arise even if I don't want to use nouveau under X: unless nouveau be blacklisted in

On 01/31/2015 11:28 PM, Ferenc Wagner wrote: > I for one don't expect insults after such a start. Please share your > thoughts, constructive feedback is always useful. Even if there may be > good reasons for some things being as they are. Ok Feri, of course there is no reason for insults, but still, some groups take offense at any criticism. If I sound bitchy it is only as

> The wiki I think should at the very first direct you to the correct > 'variant' for what media you are installing to (extlinux for me). As it > is, on the web all the variants are often referred to generically as > 'syslinux', and it's not till latter that you realize that you must find > the correct variant. It would also be nice (tho probably much work),

On 29.12.2015 22:51, poma wrote: > On 29.12.2015 22:20, Ady via Syslinux wrote: >> >>> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote: >>>> On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote: >>>> >>>>> How this change would affect users with older versions of kbd / >>>>> loadkeys / or in older OSes? I

Hi, I just noticed that the keytab-lilo utility included with SYSLINUX isn't up to date. It *is* a problem since the old version isn't compatible with current distributions like Debian ou Ubuntu (for example). Two options are offered to those who would like to use keytab-lilo in order to generate a file compatible with the KBDMAP directive : - use an up to date version of keytab-lilo

Hello all! I would like to know if is possible to use LILO as the boot loader instead of the default GRUB. My question comes because I tried to run lilo command but the message "command not found" appear. It sounds like my only boot loader option in CentOS is GRUB ??. I found lilo.conf.anaconda, but not the lilo command. From already thanks. Regards, Juan P. Espino

hey folks, Im using pxelinux to boot a Soekris box (which works fine to a default image) Ive added a bunch of LABEL, KERNEL pairs, but I cant read the display; Im buried in escape codes. Ive captured some of it to a typescript file: it starts out kosher, but goes unreadable rather quickly, 0005520 \r T F T P . 0005540 / \b \r 0005560 *

On 07.03.2016 19:24, Ady via Syslinux wrote: >> doc: keytab-lilo example on Fedora >> >> --- >> doc/keytab-lilo.txt | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/doc/keytab-lilo.txt b/doc/keytab-lilo.txt >> index cdbea0f..f35b3e8 100644 >> --- a/doc/keytab-lilo.txt >> +++ b/doc/keytab-lilo.txt >> @@ -83,3 +83,7 @@

> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote: > > On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote: > > > >> How this change would affect users with older versions of kbd / > >> loadkeys / or in older OSes? I mean, let's assume a user using a newer > >> version of Syslinux (containing this proposed change in its keytab-lilo

I can't choose LILO as boot loader anymore in the install process? And what is the advantages in GRUP vs. LILO that are so great that LILO has been deleted all together? One big disadvantages when forced to use GRUB is that it is a hassle to make the disks in a RAID1 bootable. https://www.redhat.com/archives/fedora-list/2005-March/msg05935.html and RAID1 seems pretty useless when it is the

I have a Lilo.conf file, which I have tried for many hours to convert to Syslinux. I looked around on the web for references on translating some of the components. I want to convert it to Syslinux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10

Where can I get lilo for centos 4.2? I did "up2date lilo*" and nothing was retrieved.

Does there exist a version of Lilo built for x86_64 CentOS 5? It does not seem to be on the DVD. *I* really, really, prefer Lilo over Grub. -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller at deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/

Howdy, I use isolinux very successfully to boot a CD on which I have a kernel with an initramfs compiled in that holds the bootsplash as well as an external initrd with a boot script. the CD boots fine and everything works the way it should. My problem is actually when I try to boot the same kernel and initrd from the HD of a machine (easy way to boot the CD without altering the BIOS). For

I figure I'm probably trying to do something stupid, but here goes. I'm trying to boot a hard disk image (with one 420MB partition, lilo in the MBR) containing debian etch (kernel 2.6.18) using memdisk (onto a dell 2950 with 8G of ram). Lilo (22.6.1) fails on memdisk 3.35, 3.36, 3.50, 3.51, and 3.52-pre, with L 99 99 99 99 et al, but works on 2.x, 3.00 and 3.31. However, the kernel

yup runned it. probably something wrong with my initrd filesystem. can you send me a directory listing of your initrd? and probably a sample linuxrc. if worse comes to worse, i'll probably load my usb and scsi modules in the initrd. i'm probably doing it all wrong. i'm trying to imitate the slackware10usb way of booting up. every driver built in the kernel, patch on the mounting root