Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I installed Gentoo from stage1 today. Never tried Gentoo, but I always hear good stuff about it. After completing the install, I didn't install LILO, as I already have it installed to the MBR. I just booted to Slack, edited lilo.conf, then ran /sbin/lilo and I keep getting this error:
Added Slackware *
Fatal: open /boot/kernel-2.4.20-gentoo-r8: No such file or directory
I know kernel-2.4.20-gentoo-r8 is there. Did mkdir /dev/hda6 /gentoo : ls /gentoo/boot and it's in there. I tried /sbin/lilo while hda6 was mounted and not mounted. Here is disk setup:
you say /gentoo/boot is on /dev/hda6, but in lilo.conf you try to load /boot/kernel-2.4.20-gentoo-r8 on /dev/hda6.
lilo just can't find the /gentoo dir IMO.
Structure on the /dev/hda6 partition should be /boot, not /gentoo/boot, no?
It isn't /gentoo/boot. I just created that dir in slack so I could view the contents of /boot on the gentoo partition. I had this problem before I did that though. After it wouldnt work, I did mkdir /gentoo mount /dev/hda6 /gentoo just so I could list the contents and be sure I was using the correct kernel name. I didn't add it to fstab or anything like that.
Copy the gentoo kernel and initrd from /gentoo/boot the slackware /boot directory. NOTE: It's not enough to just mount the gento directory because lilo is looking in the slack /boot directory:
cp /gentoo/boot/kernel-2.4.20-gentoo-r8 /boot
cp /gentoo/boot/initrd-2.4.20-gentoo-r8 /boot
Change the /etc/lilo.conf entry like this:
image = /gentoo/boot/kernel-2.4.20-gentoo-r8
label = gentoo
root = /dev/hda6
initrd = /gentoo/boot/initrd-2.4.20-gentoo-r8
NOTE: This way is better than above but you always need to have gentoo mounted at /gento before running lilo.
First fdisk /dev/hda and make /dev/hda6 bootable. Next do a chroot /gentoo and make sure the gentoo /etc/lilo.conf is like this:
boot = /dev/hda6
vga = 791
image = /boot/kernel-2.4.20-gentoo-r8
label = gentoo
root = /dev/hda6
initrd = /boot/initrd-2.4.20-gentoo-r8
Then run lilo from gentoo.
NOTE: This will put lilo on the /dev/hda6 boot partition.
Now you can exit the chroot and you are back to slackware. You need to change slackware lilo.conf like this:
other = /dev/hda6
label = Gentoo
table = /dev/hda
And run lilo again in slackware.
I'm sure there are other ways to do it also.
<edit> Also rather than doing chroot /gentoo you could just edit /gentoo/etc/lilo.conf and when you run lilo do it like this:
Damn. I figured your suggestions would DEFINITELY fix me up, but I still get the same error. I tried the #1 suggestion first, nope. HOW the hell can lilo NOT find kernel--- when it's located in the same directory as my slack kernel?! Of course, I edited and saved lilo.conf first, to look for the kernel at /boot/kernel----.
Then, I tried the 2nd suggestion (which I think I already tried while hacking away at it) and it didn't work either. Why won't lilo recognise the image??
As for #3, I don't even a lilo.conf in gentoo right now (never emerged it), and am a little leary of installing it from there. The reason being, is right now from slack (completely configured as I need it) I can't get lilo to boot gentoo, so whats to say from gentoo I wont be able to get slack to boot? I have the slack live cd, knoppix, and all that, but I don't want to create any more problems than I already have
Simply, create a mount point in Slackware for the Gentoo partition which contains Gentoo's kernel - then mount the partition into the mountpoint in Slackware - once youve done this then put an entry for Gentoo in lilo.conf (while inside Slackware) - make sure you take into account the temporary mounted nature of the Gentoo partition inside Slack:
It did. I just copy/pasted Skyline's text into lilo.conf and /sbin/lilo passed. The only thing I did differently was mount /dev/hda6 @ /mnt/gentoo. I suppose it's possible I had a typo, but I have been fooling with this for 2 hours and typed the gentoo entry over 20x during that time. Hard to believe I had a typo each time, especially when I checked each entry over hardcore each time.
Also, the entry you saw above that I posted was copy/pasted directly from lilo.conf...
Yep, thanks guys! Now I have new problems to solve, lol. Getting some kernel errors, haven't got X configured properly yet (have to use ps2 adapter for mouse) and don't have internet yet, WHEEEEE!!!! I'll get it worked out though. I got so used to Slack, I'll have to learn some new stuff for Gentoo. At least I can copy most of my settings for stuff like internet from slack. Going to try using my Slack kernel. It's custom and works perfect on my hardware.