If you mean the Android Grub, I don't know what it does. Based on my experience with it, I expect it tries to install to the partition because it definitely didn't overwrite the MBR. When I installed Android and selected to install Grub there was no option as to where to install. When trying to chainload it from another system with Grub, it failed so I had to install Grub from another system which then worked to chainload it from both Grub Legacy and Lilo. I have an Ubuntu install and ran update-grub from it and it detected the other operating systems on the same drive but not Android.

Almost all Linux systems I have used will give you the option of where to install during the operating system installation. You can install to the MBR or to the root or boot partition where the system boot files are. Not sure why that happened as it is obviously possible to boot it from Grub2.

you would have a much easier task with syslinux than lilo.

heere my easy howto http://www.linuxquestions.org/questi...ks-4175581486/
even with menus syslinux

@yancek:
When I installed Android 4.4.2 it let me choose the partition for the OS but wrote the MBR. I know it because when I booted I was led to a grub menu. I had to run lilo to restore the MBR. But then of course I lost the capacity to boot Android. There is a way to do dual boot Android and Slackware Linux: using grub, say grub2. Another one, as I am told, is using syslinux but, here, I'm afraid I would have to learn a lot of things first. I don't think using grub to do the job can be that difficult, though I don't know how to do it. I can boot android with a grub.cfg written by myself but I couldn't make it to boot linux too (dual boot) which is odd.

If your install of Android had Grub on it's partition then the Lilo entry I posted above (post number 8) should have worked. If it doesn't I really don't know why not as it did work for me.

Another member posted an entry above to boot Android from Grub2 which worked for him so if you are planning to install Grub2 on Slackware and boot Android with it, you might take a look at that example and modify it to suit your system.

Or you could put Grub from Android in the MBR again and use a chainload entry to boot Slackware.

try to explain him that SYSLINUX is the most reliable boot loader, far more reliable/older/stable/better than grub.

Has anyone got that to work yet?

I installed FreeBSD Unix, Slackware GNU/Linux, Android-x86 Linux 9.2. The first two boot each other (and every other OS I used) fine. Chainloading, LILO says for Android there's no valid boot signature on that partition...

Someone got it to at least partially work, described on on a questions website. If another thread could be started, I'd consider using an alternative used by Slackware... it installs LILO for users/programmers but in classic boot mode uses syslinux... please don't reply about that here (without agreement of original poster) any more than GRUB... really hate things getting off-topic because the topic is about LILO, and I love LILO...

I don't see any reasons why it shouldn't.
Post #1 contains totally normal linux & initrd command lines, I'm sure those can be applied to grub, LiLo, syslinux etc. equally.
That said, this is 4 years old and android_x86's boot command might have changed meanwhile.

The thing is, it doesn't (for many reasons.)

Some other examples are appending 'androidboot.selinux=permissive,' 'acpi_sleep=s3_bios,s3_mode,' but the second might be for specific hardware. For android-9.0-r2 (x86) I've tried LILO (and GRUB2) with combinations of these and above append lines but nothing seems to work. As many say, it usually just starts printing dots until those fill up the entire screen then goes on & on. Android-x86 doesn't seem very documented, but alternatives have problems also, like KDE Plasma Mobile (unstable) and Ubuntu Touch/Unity (worst touch interface I've seen, basically unusable for me.) Anyone heard anything else on configuring Android-x86 with LILO (there's also a GRUB thread going on in recent months on this which at least if they solve it first might have the append options?)

^ Like I said, if you have a Linux command line that works under GRUB, I see no reason why the same command line shouldn't work under LILO.

Give us something to work with here.

That said, does it have to be LILO? There's also syslinux/extlinux (oops, that was mentioned already).