I have installed slack 10.
When i turn on pc, kernel boots fine, it mounts / partition, but then
the problem and here is pull down:
INIT: version 2.84 booting
INIT: cannot execute "/etc/rc.d/rc.S"
INIT: entering runlevel: 3
INIT: cannot execute "/etc/rc.d/rc.M"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"
INIT: cannot execute "/sbin/agetty"

Silly question time.

is /bin and /etc in your root partition? Are there any other partitions that it appears to have problems accessing? Do you have access to a boot CD like KNOPIX? If so I would suggest that you boot to the CD, mount root then go see if "/sbin/agetty", "/etc/rc.d/rc.M", and "/etc/rc.d/rc.S" are there. Assuming that they are take a look at there permisions, you may have to compare the numbers to the /etc/passwd and /etc/groups file respectivly.

Good Luck

The boot cd disk also pulls down these strange errors, but i mounted that slack 10 hd to the slack 9.1 on the second pc. /bin /etc is in my root partition, files present, permisions ok but what about comparing to passwd and groups, what u mean?

In some cases if you are booting a linux box to LIVE CD and mounting a partition, when you look at the owner and group as displayed on a 'ls -l' it is possible that it will not show you the names of the group / owner instead it might show your the owner # and the group #. If this were to have happened you could have taken note of these numbers and compared them to the numbers in the '/etc/passwd' [for users] and '/etc/groups' [for groups] to translate the numbers back to the common name. To ensure that that the files have the ownership that you want.