quick quiz - which makes more sense, when entering single user mode:

- have 'single' start first, kill
  /etc/rc, and have it shut down all the services by itself
- have /etc/rc kill services normally, and just run 'single' last?

Yeah, I thought so.

1 files changed, 0 insertions, 21 deletions

diff --git a/rc.d/init.d/single b/rc.d/init.d/single
index 64c6806d..0ae9268e 100755
--- a/rc.d/init.d/single
+++ b/rc.d/init.d/single
@@ -16,30 +16,9 @@ if [ "$1" != "start" ]; then
    exit 0
 fi
 
-rm -f /var/lock/subsys/*
-
 # this looks nicer
 [ -x /usr/bin/clear ] && /usr/bin/clear
 
-# make sure modprobe is working
-if [ -f /proc/sys/kernel/modprobe ]; then
-	sysctl -w kernel.modprobe="/sbin/modprobe" >/dev/null 2>&1
-fi
-
-# If they want to run something in single user mode, might as well run it...
-for i in /etc/rc1.d/S[0-9][0-9]* ; do
-	# Check if the script is there.
-	[ -x "$i" ] || continue
-
-	# Reject backup files and files generated by rpm.
-	case "$1" in
-		*.rpmsave|*.rpmorig|*.rpmnew|*~|*.orig)
-			continue;;
-	esac
-	[ "$i" = "/etc/rc1.d/S00single" ] && continue
-	$i start
-done
-
 # Now go to the single user level.
 echo $"Telling INIT to go to single user mode."
 exec init -t1 S