i suggested the rpm -e, then the make install, cause that is how you get
the binaries :)
it has nothing to do with the rc.d stuff.
darn redhat. i am sorry, but that code was stable in USE, but not stable
in DESIGN. now we have to deal with "upgrading" 5.2 (read 'fixing').
allan
ps- i LIKE redhat- went to school in durham :)
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
On Sun, 28 Feb 1999, Chris Price wrote:
>
> On Sun, 28 Feb 1999, m. allan noah wrote:
>
> > is your system redhat 5.2? if so, do:
> >
> > rpm -e raidtools
>
> I did this. Raid1 array os working just peachy.
>
>
> >
> > and edit /etc/rc.d/rc.sysinit and remove the section on starting raid
> > (about 30 lines, do :/raid to find it in vi)
> >
> > then edit /etc/rc.d/init.d/halt, and remove the lines about raid (about
> > 4lines)
> >
>
> I did not do these things. rc.sysinit references the obsolete
> raidadd command, so i am assuming that it needs to go.
>
> Here is section from rc.sysinit:
> #############################################################################
> # Add raid devices
> if [ -f /proc/mdstat -a -f /etc/raidtab -a -x /sbin/raidadd ]; then
> echo "Starting up RAID devices."
> raidadd -a
>
> rc=$?
>
> if [ $rc = 0 ]; then
> raidrun -a
> rc=$?
> fi
>
> # A non-zero return means there were problems.
> if [ $rc -gt 0 ]; then
> echo
> echo
> echo "*** An error occurred during the RAID startup"
> echo "*** Dropping you to a shell; the system will reboot"
> echo "*** when you leave the shell."
>
> PS1="(RAID Repair) \#"; export PS1
> sulogin
>
> echo "Unmounting file systems"
> umount -a
> mount -n -o remount,ro /
> echo "Automatic reboot in progress."
> reboot
> fi
> fi
> ############################################################################
>
> I assume thre is something similar in the halt script.
>
> My question is, do i need to do a make install after editing the
> rc.sysinit and halt scripts? If so, what exactly does the make install
> do that I need to run it again (remember, my system has been running fine
> for about 3 weeks now).
>
>
> THANKS!!
>
> Chris
>
>
>
