Hi

I have 3 issues.

1)What do I need to do to get my num lock to turn on during boot?

2)When I log out from a user other than root, I do not have an option to turn off the computer...I go directly to signon screen. Then I have to log on as root. When I log off as root, then I have the various options that I need.

3) When I do log off and shut down computer I get to "power down" but my computer will not turn off.. It worked okay with Mandrake.

Thanks for any help....

Here are some of your answers to your questions:

1. Num Lock, (look at Config-HOWTO document, where I quoted this from)
Numlock on by default, add these lines to /etc/rc.d/rc.sysinit:
for tty in /dev/tty[1-9]*; do
setleds -D +num < $tty
done

2. Assuming you are using gdm to login in/out, as root run the gnome desktop and go thru the gnome menus until you find the login setup. In that configuration routine, you can enable the system controls (reboot, shutdown, reconfigure login from login screen, etc.)

3. To get your computer to shut the power at the end of the shutdown command (assuming that you have installed the 'bare.i' kernel), mount your install cd and from the kernels/bareacpi.i directory, copy the bzImage to your /boot directory, adn rename it to vmlinuz. (Copy the System.map and the config, also). You should have chosen the bareacpi.i kernel during the installation, if you want to use a preconfigured kernel and want to do power control.

The other alternative is to rebuild your kernel to match your system hardware, and remove the unused drivers for hardware you don't have. But if you have not done this before, I suggest you do a lot of reading on the subject of kernel rebuild, first. And be familiar with your hardware, specifically the make/model of your hardware items (video card, monitor capability, sound hardware, network hardware, etc.)

HuMJohn

Hi

Could not find /etc/rc.d/rc.sysinit...What I found is /etc/rc.d/rc.sysvinit. which I could not open with an editor.
Note the "V" in sysVinit.
Thanks

You may put the same script into the rc.local file. but have the full path to setleds file: thusly:

for tty in /dev/tty[1-9]*; do
/usr/bin/setleds D +num < $tty
done

Hi

Place the script in sysvinit. Num lock turns on @ the very end of boot process, but turns off when system goes into GUI . GUI starts up automatically(default runlevel is 4). Do I need to place this script in a certain order in sysvinit.. see below
#!/bin/sh
#
# rc.sysvinit This file provides basic compatibility with SystemV style
# startup scripts. The SystemV style init system places
# start/stop scripts for each runlevel into directories such as
# /etc/rc.d/rc3.d/ (for runlevel 3) instead of starting them
# from /etc/rc.d/rc.M. This makes for a lot more init scripts,
# and a more complicated execution path to follow through if
# something goes wrong. For this reason, Slackware has always
# used the traditional BSD style init script layout.
#
# However, many binary packages exist that install SystemV
# init scripts. With rc.sysvinit in place, most well-written
# startup scripts will work. This is primarily intended to
# support commercial software, though, and probably shouldn't
# be considered bug free.
#
# Written by Patrick Volkerding <volkerdi@slackware.com>, 1999
# from an example by Miquel van Smoorenburg <miquels@cistron.nl>.

# Run an init script:
startup() {
case "$1" in
*.sh)
sh "$@"
;;
*)
"$@"
;;
esac
}

# Set onlcr to avoid staircase effect.
stty onlcr 0>&1

if [ "$runlevel" = "" ]; then
runlevel=$RUNLEVEL
export runlevel
prevlevel=$PREVLEVEL
export prevlevel
fi

# Run kill scripts in the previous runlevel if not "none"
if [ ! "$prevlevel" = "N" ]; then
for script in /etc/rc.d/rc$prevlevel.d/K* ; do
if [ -x $script ]; then
startup $script stop
fi
done
fi

# Now do the startup scripts:
for script in /etc/rc.d/rc$runlevel.d/S* ; do
if [ -x $script ]; then
startup $script start
fi
done

for tty in /dev/tty[1-9]*; do
setleds -D +num < $tty
done

Thanks for your help...