ok, so my problem goes like that:

When I try to boot I get a "kernel panic" error message and I found out that the most likely thing to cause the error is lilo loader. I used the Slax live cd to boot in order to edit lilo.conf. It boots and everything seems cool but when I try to mount /dev/hda1 as filesystem type reiserfs (which is the appropriate filesystem) I get the error: "cannot find reiserfs on hda1". Plus, I've tried to mount just by "mount /dev/hda1 /mnt/hard_c" but it asks for -t option. I JUST WANNA EDIT THE OLD LILO.CONF! (sorry for shouting....)
any ideas on this one????

thanx anyway!

knoppix automounts

I don't understand what you are trying to say.

1) What are you trying to do
2) What did you change
3) What are the error messages (exactly)

Are you trying to boot a new Slackware installation? Did you install it on hda1? Do you have Windows installed? What does the fdisk -l look like?

@randux:
1) What are you trying to do

the server doesn't boot and I try to fix it!

2) What did you change

nothing! another guy tried to install slackware on that machine and when he saw the error he dissappeared! note that I can't get in touch with him so as to find out what did he do exactly.

3) What are the error messages (exactly)

the exact error message goes like that : "kernel panic-not syncing: no init found. try passing init=option to kernel"

SOOOOOOO I guessed that trying to edit lilo.conf (i use lilo as a boot loader) is a good idea (or not?)
Yes it is a new installation and slackware is installed on hda1. No there are no windows installed.

Slackware doesn't need any information passed to the kernel from the boot loader in a standard configuration. If it's a new installation, you should probably just go through the installation again yourself. It doesn't take very long and then you will understand the steps from A-Z if you have to do it yourself.

We don't have enough information to understand what's happening.

If you want to show the output from fdisk -l and also your lilo.conf we can see if anything obvious is wrong. If not, maybe just reinstall.

@randux: I guess you're right, I better reinstall everything from scratch.... thanx anyway for your help

You are welcome. Good luck and let us know how it works out.