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.
I had a slackware 9.1, mandrake 9.2 on same hard drive...
What I want is to create a LILO....
The problem is when I configure slackware to be the LILO, and choose mandrake to boot, the modules are not loaded but the first time I tried to boot mandrake (without slackware directly mandrake), it boots perfectly fine and has GUI looks....now that I had my slackware....it seems what it loads when mandrake is chose from LILO dialog box is the slackware's kernel and after then the mandrake's kernel is loaded (I look at the logo, TUX, not a star).
Help me on how to restore the mandrake's boot procedure....
I tried to copy the kernel of mandrake to my slackware's /boot....it boot (with the star logo) but then a kernel panic issued.....
your lilo.conf file is likely configured incorrectly. FYI, you cannot just replace a kernel with another without using lilo to create the boot loader and map files. you must run lilo again after overwriting your old kernel so the information contained in the boot sector and in the /boot files is appropriate for the kernel, otherwise 'kernel panic'.
Well, I tried it once but with same distribution slackware....though versions are different 8.0, 9.0....I copied the kernel and configured my lilo.conf and boot just fine....
then the parameters passed by lilo to the two kernels were identical. as a general rule of thumb, run lilo after overwriting kernels to avoid the headache.
same problem, but I am still a newbie... First I installed Mandrake 9.2, I have a boot partition, mounted at /boot, a home partition at /home, swap and 2 partitions one for Mandrake, one for Slack.
When I installed Slack and told it to set hda1 as /boot and hda6 as /home, the installer overwrited my kernel and booting in mandrake gave lots of problems(but it booted), booting in Slack didn't work. I didn't install a bootloader for SLack but used LILO from Mdk configured as in the help on http://www.slackware.org.
Since this only gave problems, I repared Mdk and reinstalled slack, but now only sharing my home partition(hda6). When installing LILO from the Slackinstall it worked, but I wasn't able to boot in mdk and if I didn't I wasn't able to boot in slack...
Now how could I solve this? Is it a good idea to share my home partition in the first place? Would it be possible to share that boot partition?
yes. install mandrake, rename your kernel, configure lilo.conf to reflect name change, run lilo, install slack, dont run lilo, manually configure lilo.conf on your mandrake partition to add the slackware partition, run lilo in mandrake, reboot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.