Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A while ago I tried to install Slackware on my Mandrake/98 box, anywho after I re-formatted and started from scratch I tried to add Mandrake last to see if that would work. It kind of did. Slack and 98 are fine but Drake was really messed up. I didn't take a serious look at why until just now. I think I've got the culprit but I'm not sure what the best/safest solution is. I get a lot of errors trying to start Drake, it can't find the sound card or the network card or a whole bunch of other stuff. The errors I get all have the same theme: it can't find the modules at /lib/modules/2.4.22/modules.dep, I get a "file does not exist" error. This is because the file is at /lib/modules/126.96.36.199-mdk/modules.dep. So what's the best way to fix it? rename the directory? Will that brake something else? A symlink? Can the system process symlinks at an early point of the boot process before everything is up and running? Any help/hints/links would be appreciated.
I changed the image to /boot/vmlinuz-2.4.22-10mdk and initrd to boot/initrd-2.4.22-10mdk but still the same errors. The way I installed it all I set aside completely seperate partitions for Slack and Drake so there would be no overlap and I removed reference to the non-relavent partitions from each system so they won't see each other. Could booting from the Slack LILO to start the Drake setup be the problem? Others have told me that it is safe to have the two setups on the same partition but I'm always afraid that one setup will overwrite something from the other. If I wind up putting the two on the same partition to solve this have you any advice on how to get it done safely? My first attempt cost me everything on every partition, FATs included.
what i do while usding multiple linux is
i un lilo from one linux say RH9.0
here in the boot partiton i have copied the vmlinuz and initrd images from the peanut linux boot partiton to my RH9.0 boot partion
and in the lilo in RH9.0
i have the entry of these peanut
where hda4 is the root partiton of peanut
so when i boot lilo of RH 9.0 it takes the vmlinuz and initrd images from /boot of RH9.0 boot partiton and since root-=/dev/hda4 is specified so it looks for the modules section in /lib/modules of /dev/hda4 drive.
Also this can be done without copying the above , they can be maped, to their root partions, but i haven't done that yet so i cannot tell more on that
so u need to change the way it was earlier and do this copying images from ur other linux root partitons
K, you want to load the 188.8.131.52-mdk kernel, right? Well your boot loader is setup right now; it wasen't setup right. You were loading the Slackware kernel before. Now you've got Drake. The slackware kernel looks like it didn't have a modules.dep file. So, that's the reason you were getting the errors--the kernel couldn't load modules that depend on other modules.
Solution: run the depmod command and reboot. I think... Let us know how that goes.
Lol only 1.48 AM here. Sleep by day, code by night. I'm going to look into this some more for you. I love a challenge. Could we get your kernel ring buffer, please? Use: dmesg > the-path-and-name-of-some-file-for-dmesg-output
Also, I want the directory contents of /lib/modules/184.108.40.206-mdk/ and all subfolders as well. Use: tree /lib/modules/220.127.116.11-mdk/ > output-file
Tree output is non existent because I apparently don't have tree in Drake, so I'm going to see if I can remember how to make my Drake partitions seen by Slack and then Tree it from there. Should be back with the data soon.
Tree output... is going to be 50 miles long. I compressed it but I can't add attachments. I could email it to anyone who thinks looking at it could help. Here's the top of the directory structure at least:
Depmod gave me a "cannot open file for writing" error. I then realized this was because it was looking for /modules/2.4.22/modules.dep instead of /modules/2.4.22-10mdk/modules.dep so I "depmod 2.4.22-10mdk" and all it gave back were a million "unresolved symbols in..." lines. Not sure where to go from here.
did u try u out copying vmlinuz and systems.map and initrd from mandrake partiton to ur slackware partitons
if not then
mount /dev/hda9 /mnt/tmp
go to /mnt/tmp
go to boot
cp vmlinuz.initrd. system.map from there
to /boot of sklacware
edit lilo.conf accrodingly.
see the name of the initrd is same as in /lib/modules/2.4..... of ur mandrake
Are you sure you're booting mandrake? Because 1st line of ring buffer: Linux version 2.4.22 . Should be -mdk or whatever. If you are running the mandrake kernel, depmod will default to it -- it defaults to running kernel. Just type depmod, no other jazz like paths or file names. I know there's a command to check the currnet running kernel... uname. Use uname and tell us what it says.
I'm in Slack as I type this, can't get on the net from Mandrake, but I know it's Drake when I choose Drake from LILO. KDE is completely Drake, no sign of Slackware in it. I'll see what depmod and uname say to me now and brb.