Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Ok cubed, I think I see another error in your kernel line. I've noticed that you have changed the drive designation in the ' =ide-scsi ' line from hdd to hdb and now to hda. Is this for your cdrom drive? This may or may not have an effect on your being able to boot linux. Cdrom is usually hdc.
I don't know what this means:'boot only in terminal'. I don't have grub.
As for vmlinuz, it is usually a symbolic link to the compressed kernel. If your compressed kernel is called ' vmlinuz-2.22 ', then the link will point to it.
if your windows partition is the 1st partition on the first drive, and your kernel is on the very next partition (right after windows), then the above should make it work.
this is my assumption:
-hda1 is the windows partition - also known as hd0,0
-hda2 thru hda4 are not used in the default install process
-hda5 is the linux partition that shows up as: '/' (true root) -which contains your kernel - also known as hd0,4
-hdc is actually your cd-rom drive, and describes its device type to the kernel so that it will mount correctly when linux starts up, so it must remain hdc
-since your kernel is on the next partition after your windows partition, you must find it on that partition... by default, when you partition your disks using most any linux tool, your first linux partition will be named hda5 (which is hd0,4 in the first part of the statement), and so this is where i assume your kernel to be.
-this partition is also where 'root' should point to, as in the line 'root=/dev/hda5', ok? ok.
-the hdc part is just an arguement that sets up things for you, but if you specify a different drive (like hda or hdd) you can cause the bootloader to see that drive as a device that it is not, and can mess up the 'finding' of the kernel!
- and, yes, the vmlinuz is a symbolic link to your actual kernel, and it is default on EVERY linux configuration i know or have seen. so if you can see it in your file manager, then that is the arguement you NEED to use. that way there's no guesswork, or wrong filename involved!
- hope this FINALLY gets it up and running for you.
- drop us a post to let us know how it went...
(btw, you have been a great help linuxcool, ok if i drop u an email - kinda low on friends, they seem to have all gone astray and left home on me... ho hum)
"why will we take over the world? cuz we're a community, not a company. and so far as i know, communities are what have determine the course of history, economy, and (dare i say) ... companies." :smash:
title=Red Hat Linux
kernel=/boot/vmlinuz root=/dev/hda5 hdb=ide-scsi
Before you try this out, get into linux using your boot disk and look in the /boot directory and see if can find a file called ' vmlinuz '. If it's there, then go ahead a try the code above. If not, then look for other files that might be called ' vmlinuz-2.2.13 '. Not necessarily those numbers. If you find more than one, the smaller sized one is probably the one you need. So, edit the code above and add the numbers to vmlinuz.
The vmlinuz file is there, but that last one didn't work.
I think it's time to take stock.
I've come a long way already and I know this system will (probably) boot more than one partition. At this stage, there are still strange things - I can't write grub to the mbr using
install= (fd0)+1 d (fd0) (hd0,2)/boot/grub/stage2 0x8000 p
install= (fd0)+1 d (fd0) (hd0,4)/boot/grub/stage2 0x8000 p
And of course not being able to boot linux from the floppy using grub.
But hang on, I can't get this system to talk across partitions at all! And that's odd.
I gonna go back and talk to IBM Japan about specs and stuff first then I'll try a few things and go from there but for the time being I think we should let this thread sleep.
My sought purpose for installing linux was to be a more stable platform to develop java apps. I have a more stable platform now, I just have to use a boot floppy to access it.
Simpler than I (we?) expected.
Apparently, grub was looking in the floppy itself for the vmlinuz file with the above args. (presumably, it's assuming that /boot/vmlinuz is on the currently mounted drive (fd0) which of course it's not). And the symlink for vmlinuz points to the root directory /, so it seems /boot/vmlinuz is not necessary, only /vmilinuz.
Either way a result is a result, thanks to rabidundead and linuxcool.
Something that I wish I'd read or tried earlier was the really useful <tab> searching feature with grub in the edit mode. To get a list of args, you can type root=/<tab> and it will give you the possible options. When I tried this first I got a list of files that closely resembled ... the contents of the floppy. So that was why I got the file not found error.
I take back unreservedly what I said about Windows ME not sharing. It will share but fooling it is just trickier than Win 9x.
I'll stand by 100% what I said about being a novice. Now this thread can sleep.
Is that line kernel (0,1)/vmlinuz root=/dev/hda5 hdb=ide-scsi supposed to be like that or is it supposed to look like this kernel (hd0,1)/vmlinuz root=/dev/hda5 hdb=ide-scsi?
About how grub was interpreting our previous lines, I think I know what it was doing. It was trying to find a directory called ' /boot ' on the ' boot ' partition, but there is no such directory there. It is on the ' root ' partition. That's why it couldn't find the kernel. That kernel entry is like a path list to the kernel. It's saying start in the ' boot ' partition and then find the ' /boot ' directory then locate ' /vmlinuz '. I'm talking about our previous line of code kernel (hd0,1)/boot/vmlinuz root=/dev/hda5 hdb=ide-scsi. Boy! I wish I knew that's what is was doing. Well, anyway you got it going, and that's what counts. Good luck and glad I could be of some help.
Distribution: Trying to get GENTOO 2004.2 INSTALLED... Weeeee!!!!
dang that was almost as bad as a flame war! not that you were a pain at all
anyway, way to go figuring the last part out yourself!
that's the first sign your gonna be a capable ally in the days to come.
(classic example of community, this was!)
again, and as linuxcool said, glad to help... see ya 'round!
"they came, they saw, they conquered.... one day, one house, one mind at a time. And then when all the clouds had settled, they had built an empire that would not fall.. for it was the one the people had wanted, but had never known... until now." :smash:
One of the first posts here referred to an "unofficial real DOS-mode patch for WinME". I searched and downloaded the file (mfddme13.zip). It basically patches a few system files and tells you where to copy them to. Windows ME now behaves like other versions and, most importantly for me, now works with Lilo and Mandrake 8. I'd recommend this solution to other ME users who have struggled dual booting.
I reckon that's a solution if you're computers fresh from the box and it came with 2 partitions (one of the systems - a Sharp Moebius desktop (ugly thing) I installed Redhat 7 onto also has this) but usually the recovery CD (no software CD because it's them) rewrites the partitions to factory setting which will overwrite linux when you re-install Windows ME on a single partitioned oem.