I know it is a stupid subject - but I will explane:
Before the changes I had Windows XP on hda and Linux Mandrake 9.0 on hdb.
Disc with XP worked slower than it should so I changed the disc with Mandrake from secundary master into sec. slave. So now:
XP on hda, Mandrake on hdc.

But now - I can't start Linux! It tries to start from hdb5 but since that disc is now hdc - it says:
Karnel panic: No init found. Try passing init= option to karnel.
Since I'm a Linux newbie I didn't understand how to pass it? Anyway, I tried to start it from boot diskete (spelling?). But it's the same. Then I went to Windows and changed the file syslinux.cfg. There was a line:
append initrd=initrd.img root=/dev/hdb5
and I changed it into
append initrd=initrd.img root=/dev/hdc5

Now, starting of Linux went a little deeper - but it still shows errors but there is an option that I press Ctrl+D (the computer restarts) or to enter root passward. I login as root - and now I have a command line! I see that all the files are ok (why shouldn't they be?) - but I don't know what to do?

Question: What to do now?
Thanks

I was on the same, and resolved it, so look at :

http://www.linuxquestions.org/questi...threadid=40516

HTH

Thanks for the help - but when I try to change the files (lilo.conf and fstab) it says that they are readonly!
When I try to save them (in vi) it says that I should override it with '!', so I enter :w!, but again it says that it was unable to change the file....
Maybe it's because my CD was on hdc (now it is on hdd) so Linux thinks that I want to write on CD which is readonly?
What should I do?

Wait a second.

hda = master on First ide controller.
hdb = slave on first ide controller.
hdc = master, second ide controller
hdd = slave, second ide controller.

If your mandrake disk was hdb before you unplugged it, it was the primary slave, not the secondary master. If you plugged it in as a slave on the second IDE cont, it would be hdd, not hdc as you may think. I'm confused.

This may not be the best way to deal with this, but the way I'd do it is to *restore* the original disk layout. Edit the fstab to change it to match the new setup you've planned and reboot. It is always better to plan ahead.

Also when your system boots up, the BIOS will transfer control to the first disk that has a *readable* boot sector. When dual-booting, it is always a better thing to let the linux boot loader load windows, so maybe you should place the linux hard-drive in such a way that the BIOS finds it first. safest eg: primary master.

In single user mode, the root partition is mounted read only, you need to re-mount it with rw (read write) flag
-NSKL

BTW Ja sam iz NS, ako imas vremena javi mi se da se upoznamo guesswho AT ciaoweb.it
Sorry guys, i just noticed hes from my home country.. .

Thanks everybody - mission complete.
I did what nxny said right after my last message. I changed the fstab file and lilo.config. It seemed that that won't be good either since Linux reported the same error. But the booting from floppy went good and I started Linux normaly. After that I changed a setting in lilo configuration (Mandrake Control Center) and changed it back so that it detects that I changed something... and everything worked out.
It's nice to be back in Linux.
Thanks...