the first time i installed slackware i did not get this message

the 2nd time i had to install (not slackware's fault), i managed to get slackware installed and began the configuration process (as described by JetBlackz in Simply Linux) in any event, for some reason the /bin/sh refused to behave properly

i'm making the assumption that this might be a semi-common occurance so rather than 'babylon' i'll simply asked for the 10 most common causes for this and what to look for.

other than that, i was having some partitioning problems (converted a ntfs to fat32 using system commander) when all hell broke out.... forcing me to rely on slackware only to find out that slack itself had managed to get nailed requiring a clean reinstall that as mentioned ran into this strange /bin/sh problem and basically shut me down...

thanks a bunch

- perry

Why did you double post? You started this converstation/thread in another forum and again here, why? A member with more than 200 posts should know better really, I would expect more. If you felt your post was more suitable here, you should report it to move it.

I have requested to have this one closed at this time as I replied to your existing one.

No need to reply here, this thread will be closed and if you would like to have your other post moved, report it and request to have it moved.

Regards.

Ppl FUP to: http://www.linuxquestions.org/questi...hreadid=120472