hint-boot.1() {
cat << EOF
	The first symptom you will notice is that the reboot
	hangs. Consider what needs to happen during a reboot:
	the system changes to runlevel 0. To do this, the shell
	scripts in /etc/rc.d/rc0.d must be run.

	You will need to hit the reset button on the computer or
	power cycle it.

EOF
}

hint-boot.2() {
cat << EOF
	Remembering the boot process, we see that the system
	boots as far as the init command.  The first program that
	init runs, rc.sysinit, fails to execute.  Other programs
	then fail to execute: /etc/rc.d/rc, /etc/X11/prefdm.
	These are all clues.

EOF
}

hint-boot.3() {
cat << EOF
	Once in rescue mode, among the things you may consider
	trying is a chroot command.  This also generates an error
	message:

		chroot: cannot execute /bin/sh: No such file or directory

	To which /bin/sh does this refer?  The one in /bin or the
	one in /mnt/sysimage/bin?  What kind of file is this?
	Why can it not be executed?

EOF
}

hint-boot.4() {
cat << EOF
	The /bin/sh about which chroot complains is
	/mnt/sysimage/bin/sh.  Doing a long listing of this file,
	note that it is a symbolic link to bash.  Understanding
	symlinks, we realize that this refers to
	/mnt/sysimage/bin/bash.  List this file.

EOF
}

hint-boot.5() {
cat << EOF
	The /mnt/sysimage/bin/bash file is missing!  This
	explains many symptoms.  Consider the files that are
	shell scripts or otherwise require shells that failed to
	run:

		o  /etc/rc.d/rc0.d scripts

		o  /etc/rc.d/rc.sysinit

		o  /etc/rc.d/rc

		o  /etc/X11/prefdm

		o  chroot (which needs to execute a shell in the
		   chroot'ed environment)

	The missing bash executable can explain all of these
	symptoms.

	What do you do about this?

EOF
}

hint-boot.6() {
cat << EOF
	You need to reinstall the bash executable.  To do this,
	you need to know what package owned /bin/bash.  To
	determine this, run:

		rpm -qf /bin/bash --root /mnt/sysimage

	This reveals that the bash package owns /bin/bash.
	Install this:

		rpm -ihv /mnt/source/Server/RPMS/bash-3* --root /mnt/sysimage --replacepkgs

	The problem with this is that this program itself may
	hang. This may be caused by the fact that the rpm
	program may need to use the /bin/bash executable to run
	scripts.

	Reboot the computer (although the rpm command may be
	hanging). The system will come up. Reinstall the bash
	package to be sure it is sane. Investigate what else
	might be wrong with the system.

EOF
}

