SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Rep:
Slackware's LILO was overwritten by Vector's LILO
hi just would like to ask, in my Slackware's LILO, i have the following (and THIS IS My Default Loader)
Windows
Slackware
VectorLinux
Zenwalk 4
OpenBSD
when i was installing vector 5.8, i missed that it's LILO should be placed in the root partition and NOT in the MBR... but i chosed the MBR option SO my slack's LILO, was overwritten by vector's LILO... NOW i can't see my slack's LILO..
hmmm is it erased? ? how can i retrieve my slack's LILO again? thanks
i have tried chroot (using my slack cd 1 ) though i still saw my slack's partition and lilo.conf BUT i can't anymore retrieve my slack's LILO... please help
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
yup i did it.. BUT the problem is.. everytime i mount slack's partitions .. it cant read the /boot .. in short.. every time i mount them.. it shows no contents BUT when i check "df -h" it shows space usage ...
my slack's partitions:
/boot
/tmp
/usr
/var
/home - its ok even its not mounted (For the chroot activity)
/swap
/
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
Quote:
Originally Posted by masonm
Ok, easier solution. Boot into Vector, edit it's lilo.conf to show Slack. Run lilo. Reboot into Slack and rerun lilo from there.
sir IF im getting it right, meaning I will MAKE vector the main MBR? and place slack on it? ok.. since i have listed 2 versions of vector
this 2 were detected in the LILO config section while reading vector 5.8,
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054
Rep:
Install the lilo in Slack's Root (not MBR) from the Slackware Login,
in the vector's lilo.conf do other=/dev/<place where slack is installed> and install the vector lilo to the MBR. Chain Loading is much less troublesome beleive me. Don't try to use a common lilo.
But I really hope you try and manage to use a common lilo... the way I told is a really poor HACK.
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
Quote:
Originally Posted by duryodhan
Install the lilo in Slack's Root (not MBR) from the Slackware Login,
in the vector's lilo.conf do other=/dev/<place where slack is installed> and install the vector lilo to the MBR. Chain Loading is much less troublesome beleive me. Don't try to use a common lilo.
But I really hope you try and manage to use a common lilo... the way I told is a really poor HACK.
the bad news is i cant anymore BOOT slackware.. after the CHROOT attempt.. i tried editing vector's lilo thru the CD.. placing its lilo on ROOT instead of the MBR..
then after doing so.. after a reboot..
i cant anymore load any distro even my windows.. (
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
thanks to MASONM.. followed his advice.. now im able to boot my winXX and newly installed VL 5.8 (but i think my modem /dev/ttyS0 was not configured)
note:
i think that i messed up my /boot (slack)..even if i addded slack in my vector's MBR.. errors/ warnings are shown in the output of /sbin/lilo -v -v .. il update this thread once i have copied the saved output in my text file.. (just forgot to copy it in my usb flash drive)
in short.. i cant anymore boot my slackware.. but il still search on this one..
Distribution: slackware 12.0, Vector Linux STD 6.0 and 5.8, ZenWalk 4.6.1, OpenBSD 3.9
Posts: 389
Original Poster
Rep:
here is the output when i edited vector 5.8 lilo.conf :
Quote:
vector:/~
root:# /sbin/lilo -v -v
LILO version 22.7.2.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 07-Jul-2006 and compiled at 14:14:35 on Jul 26 2006.
Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=2
0300 2E1B2E1A /dev/hda
1600 542D2676 /dev/hdc
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 3
device codes (canonical) = 3
mode = 0x03, columns = 80, rows = 25, page = 0
Using BITMAP secondary loader
Calling map_insert_data
Secondary loader: 19 sectors (0x3800 dataend).
Warning: The boot sector and map file are on different disks.
bios_boot = 0x80 bios_map = 0x81 map==boot = 0 map S/N: 542D2676
Mapping bitmap file /boot/bitmap/boot.bmp -> boot-lava.bmp
Calling map_insert_file
Bitmap: 603 sectors.
BIOS data check was okay on the last boot
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.