If you prefer to use the Linux LILO utility over BeOS’s bootman, you’re nuts. But if you really want to, here are step-by-step instructions (note, however, that bootman does a great job of booting most operating systems, is much easier to configure, and is more visually appealing). It’s also important to note that even if you use bootman, Linux still requires the presence of LILO. However, since bootman is installed in the master boot record (MBR), LILO must be configured to reside in the boot partition, rather than in the MBR. You can do this by booting Linux from a floppy and re-running the LILO configuration utility. That said, here’s all you need to know:
in Windows:
1. extract zbeos file from BeLaunch (Windows boot utils for BeOS/x86).
in Linux:
2. copy zbeos into /boot/ directory in linux (there should be boot.b, chain.b, vmlinuz*, …)
3. backup your /etc/lilo.conf file
4. edit your /etc/lilo.conf file like this:
Hepcat719 (mjdavis@ilstu.edu) offers this lilo.conf to replace the old one; this should cause fewer problems…

--
bboot=/dev/hda
root=/dev/hda5
install=/boot/boot.b
map=/boot/map
vga=normal
delay=200
prompt
timeout=200
message=/boot/message
other=/dev/hda1
	label=win
	alias=w
	table=/dev/hda
image=/boot/vmlinuz-2.2.15.ppp.rtc
	alias=l
	label=Linux
    vga=0x0f07
	read-only
other=/dev/hdb2
	label=Be
	alias=b
	table=/dev/hdb
--

5. run lilo -v to get verbose info what your lilo manager does.
6. reboot your machine
7. answer be when you are prompted by LILO: and it should work (at least it works for me here)