similar to: mbr problem with pxelinux

Are there any tools for working with and moving or copying the MBR? My machine has 2 PATA drives (hda & hdb) and 2 SATA drives (sda & sdb). The MBR is on hda, but I would like (eventually or sooner) to boot from sda because it is two years newer, faster and, hopefully, more reliable. Even if I don't change that, I'd like a backup MBR on sda in case hda fails (hdb has gone sour a

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

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 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),

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

Hello guys, Sorry to make noise in the group, but I had really hard time finding how to configure PXELinux to my requirements, despite reading everything available on syslinux.zytor.com and combing google for config examples for your beast. Also, did browse the source code, but good luck to understand what is there in half a day... The boot loader is really nice, but may please someone

On 02/01/2015 10:27 AM, Ady via Syslinux wrote: > FWIW (this info can be found elsewhere too): _ "SYSLINUX" refers the > install the bootloader files on the adequate boot area (see ... Ok thanks, this also would be good information 'up front'. I can only comment on how it could be better for a beginner, not in what is actually available if you know where to look.

a bit unrelated, still I wonder: does syslinux contain an mbr? or does anyone know any app that contains an mbr and can install it, without overwriting the partition table? my experience is, that is wise to have an mbr and use the active flag to select the active partition (which might have a bootmanager installed). however every linux distribution I know installed the bootloader such as

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

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

Add detection code for "MS-DOS 3.30 through Windows 95 (A)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 77e4180..37309e1 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@

Add detection code for "FreeDOS (eXtended FDisk)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 37309e1..6150fcf 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@ -27,7 +27,6

hi, we've got many mandrake 8,9 and 10 system remotely. we'd like to remotely replace these systems to centos 5. we've 4 disk in them. one is the system drive (no need for raid) and there is free space on the remaining 3 disk. so what we think about: - download the new system to the data disks - install grub (mandrake has lilo) to boot the old system and reboot - create the old system

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

With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with

I am trying to boot a ramdisk on a usb stick in read-only mode using extlinux. When the system boots all I am getting is a blinking cursor. The stick booted with lilo, but I had some issues with lilo so I am trying extlinux. 1) I partitioned the stick as a linux partition, formated it ext2, and mounted /dev/sda1 on /mnt/flash. 2) I am running extlinux 3.86. 3) excuted "extlinux -i

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