Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!bcm.tmc.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!news.internetMCI.com!darwin.sura.net!gwu.edu!seas.gwu.edu!kopti From: kopti@seas.gwu.edu (Juzer T. Kopti) Newsgroups: comp.unix.bsd.bsdi.misc Subject: BSDI and Linux's LILO Date: 16 Feb 1996 05:23:36 GMT Organization: George Washington University Lines: 22 Message-ID: <4g14co$6kh@cronkite.seas.gwu.edu> NNTP-Posting-Host: 128.164.9.3 X-Newsreader: TIN [version 1.2 PL2] I have a 1gig drive as my primary and a 850meg as my secondary. The 1gig is shared by Win95 and Linux and I use Linux's boot manager, LILO to select either of the two. I just loaded BSD/OS v2.1 on my 850meg (fully dedicated to BSD/OS). I then booted linux to reinitialise LILO to add for the third OS installed. Basically the BSDI part in lilo.conf looks like below. # BSDI bootable partition begins other = /dev/hdb label = bsdi table = /dev/hdb loader = /boot/wdboot # BSDI bootable partition ends I have to specify in the loader line the exact boot blocks indicating where BSD/OS would commence booting from /dev/hdb. Since I cannot even directly boot to BSDI, can someone tell me what is the appropriate entry to use for the 'loader' line which would indicate the boot blocks ?? Thanx Juzer