Multi OS boot in Lilo

Question

Literature on the multi-boot OS of Linux-windows covers the linux standard hard drive ID system  hda, hdb, etc.
     With devfs the nomenclature involves using disc designators.
    If one desires to multi-boot 3 or more OS systems on separate drives, what ID system is required to enable all systems to boot with lilo?
    One such reference refers to the linux system using:
          boot=/dev/hda
          prompt
         image=/boot/vmlinuz
         root=/dev/hdb1
         label=arch
   When using Arch, such a statement seems not effective with devfs..
     Suppose one starts  out with such a statement in Slackware which doesn't use devfs.  How does one then refer to arch?
          Perhaps:
              other=dev/discs/disc1/part1
              label=arch
              table=/dev/discs/disc1
    Then continuing for OS windows:
             other=/dev/discs/disc2/part1
             label=win98
             table=/dev/discs/disc2             
                         OR: should it be...
              other=/dev/hdc1
              label=win98
              table=/dev/hdc
                           AND:
              other=/dev/hdb1
              label=arch
              table=/dev/hdb
            Perhaps one cannot mix linux terms with devfs?
     Using slackware as hda, arch as hdb and win98 as hdc what lilo is correct for an hda boot-up?
           Conversely, what is right and correct if arch is the primary,slackware slave and win98 as secondary slave(CD in secondary primary slot}?
          Perhaps none of the above?

Answer 1

     The /sbin/lilo -v has been run so many times it may have burned out!!!
    The return statement in lilo caused me to rerun many, many times trying to eliminate the  "fatal error:  open : /boot/vmlinuz ....
  Tried to find vmlinuz, then tried to generate it...to no avail.
   Was afraid to restart for fear it was  ..."fatal"
    Rebooted after four hours of futility and it rebooted!!
     Subsequent googling leads me to believe that only i386 arch kernels have vmlinuz arrangements...there are no references to i686.
     Consequences of devfs are mentioned but not defined or demonstrated by concrete examples .
     Mixtures of devfs and linux are not defined.
     The example given on this post refers to .."devfs=mount" is the only place where the devfs system is referenced. 
    My approach is to use the MBR
on the arch hdd to do the booting, not a partition of the arch install.
    After that, a similar setup on slackware to boot arch and win98 along with two versions of slackware.
     Slackware boot had a ...dos option at boot time.  I have only arch in arch boot.
     Something isn't right with devfs.
    Dunno how to address it in Slackware. 
    Lilo is blind to OS'es except ..get the devfs right!
   Thanks for the encouragement teun!!!!!