Slackware installation
:newbie:
total noob question.... if I want to install two different distros of linux on a machine, is there a rule of thumb for installing LILO? Case in point: I have an old P2-350, and I have Win98SE, DamnSmallLinux and Slackware 9.1 installed on it. If I use the LILO from Slackware, it works fine, but DSL has issues with the NIC. If I use the LILO from DSL, Slackware had issues with modprobe and Xfree86. Why?? Anyone know if there is a specific reason for this or if its just a fluke? Setup is: P2-350Mhz 96MB PC-100 SDRAM /dev/hda1 - Win98SE (800MB Partition) /dev/hda2 - DSL (500MB Partition) /dev/hdb1 - Slackware 9.1 (2.2GB Partition) 3Com 10Mbit NIC 8MB Intel Starfighter AGP 40x CR-ROM |
Anyone??
|
Quote:
|
OK.. Here is the lilo.conf file from DSL (minus all the non-essentials).
vga=791 lba32 boot=/dev/hda install=/boot/boot-menu.b map=/boot/map prompt append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce" image=/boot/vmlinuz-2.4.22-xfs root=/dev/hda2 label=DamnSmallLinux image=/boot/vmlinuz root=/dev/hdb1 label=Slackware other=/dev/hda1 label="Win98SE" As for the modprobe issue, when I try to boot into Slackware, it says "Can't open dependancies file /lib/modules/2.4.22-xfs/modules.dep (no such file or directory)" |
what is this line for
Quote:
|
Quote:
Looks like lilo is trying to boot Slackware with Damn Small Linux's kernel. Try to copy Slackware's kernel to the /boot directory under DSL with a name like vmlinuz-slackware, then for slackware's image= line, put image=/boot/vmlinuz-slackware. Then re-run lilo from DSL. |
All times are GMT -5. The time now is 03:52 AM. |