Handover Phist blithely blithered
> I have a system at home I use for everything. Personal use (Slack 10.0),
> Gaming (Windows) and work (RHEL - RedHat Enterprise Linux). It has 4 hard
> drives, 2 IDE and 2 SATA, a cdrw, and a DVD Rom. Just recently I
> installed RHEL on hdb. Windows is on hda and Slack is on sda. sdb is
> used for storage. After installing RHEL, Slack became FUBAR. On boot no
> startup scripts are executable. No name is given to the machine and
> login is impossible as TTYs are inaccessable. If I log in to RHEL, mount
> the Slack partitions and chroot, everything seems hunky-doryish and I
> can do nifty things such as post to AOLS saying "Hey look what I screwed
> up!".

Very strange one indeed, this one! And tracked down to the symlink
between /bin/sh and /bin/bash. I replaced it with sh -> bash as opposed
to sh -> /bin/bash

ln -s bash sh

while chrooted to the old system, and next boot was hunky-dory. Odd
since the structure hasn't changed in the least. The install of RHEL on
a separate disk was the catalyst for this. Got me on why.


Thanks to Alan Hicks for assistance.

--
AMERICAN WASTE