search for: lilos

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

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

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

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

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

> 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

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/

> 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 @@ where <kbd> is the name of the keyboard layout. > Example: > >

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 @@

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

i noticed that the 4.4 upgrade broke LILO on Raid... it gave errors on partitions not on the primary disk along the lines of "/dev/dis: no such device"... even explicitly installing the boot sector on each device in the array, while it allowed the system to boot, gave errors at boot time and did not display the CentOS boot screen anymore... i solved the problem by creating a

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 > perl script) but with an older OS / older version of kbd / loadkeys / > map files. The changed

Since kbd 2.0.3 (commit 6ff47cf2) the format generated by 'loadkeys -m' has changed slightly, using "unsigned short" instead of "u_short" Signed-off-by: Olivier Brunel <jjk at jjacky.com> --- utils/keytab-lilo | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/utils/keytab-lilo b/utils/keytab-lilo index 9e34160..337a869 100755 ---

Hi Updated the firmware on a PERC RAID card as it was out of date and causing a monitoring error - Everything went fine but on the reboot the box now tells me it cant find a valid boot device - I am thinking maybe somehow the boot block on the logical disk is shot. Can anyone advise me on how to rebuild the bootloader on lilo using a rescue CD? thanks

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 mean, let's assume a user using a newer >>>>

Hi, I am trying to use two products that use SysLinux and finally realised the SysLinux is the cause of my woes. I'm trying to use Freesco and IPCop. IPCop version 1.3 used a different boot loader to 1.4 which uses SysLinux. I have been through numerous trials and tribulations in trying to get Freesco to work but eventually gave up and went with IPCop. I kept getting the "Boot

...again, it's not mentioned at all in the 'extlinux' page, so one is hopping back and forth. Vs. LILO: 'SAY' is nice. Longer labels is excellent. I guess not having to reinstall after changing the config is nice, but the reinstall with LILO isn't much of a problem. I miss LILOs 'boot =' and 'map =' and 'image =' features. It is nice to be able to have the first stage bootloader on one device and the map and/or image on another and the root FS on yet another: prompt verbose = 1 install = menu #boot = /dev/fd0 boot = /dev/sdb #boot = /d...

On my Debian box: Package: lilo Version: 1:22.2-5 Severity: normal lilo seems to cause a kernel warning (see subject) when / is a ext3 partition. Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions

We have Xeon IA32 dual-processor servers running Centos 3.5 in an HPC batch-only compute grid configuration . We have yum update operating automatically with default updates being applied weekly. Because of the workload pattern of long-runing jobs, the servers tend to stay up without a reboot for very long periods. Recently, yum installed an updated kernel 2.4.21-32.0.1.ELsmp; when we got

> It is a "generic example" which differs from the "actual example" on Fedora. ;) > Someone may favor wiki style, then again someone graces the source doc style. > What is important, none of them is a redundant, that is, they complement each other. > Patching for Fedora (or for whichever other distro) in upstream Syslinux should only be done when it would affect