On Wed, 27 Oct 1999 11:33:37 -0400, you wrote:
>I'm not sure what the message line is or even the install line. I have
>neither of these in my /etc/lilo.conf ofcourse I dont use Caldera .. <
>Slackware ! > I bet these may be the culprit. if you change anything in this
>file just re-run lilo :
># lilo
>
>and reboot .. I couldn't Imagine it being anywhere else ...
>
>
Well, that didn't help....its waits at the boot: prompt (which is new
and good) but once you hit Enter or it times out, you're back to the
$%&$ graphic screen....I'm enclosing lilo.conf and inittab here...I
was wondering about the s0 line with the booterd and such...could that
have something to do with it??
George
[root@eagle /etc]# more lilo.conf
#
# general section
#
boot = /dev/hda1
# install = /boot/boot.b
# message = /boot/message
prompt
# wait 30 seconds (300 10ths) for user to select the entry to load
timeout = 300
#
# default entry
#
# image = /boot/vmlinuz-2.2.5-modular
image = /vmlinuz
label = linux
root = /dev/hda1
vga = 274
read-only
append = "debug=2"
#
# additional entries
#
image = /boot/vmlinuz-2.2.5-modular
label = linux-old
root = /dev/hda1
vga = 274
read-only
append = "debug=2"
[root@eagle /etc]# more inittab
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg,
<[EMAIL PROTECTED]>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
# Modified for COL by Raymund Will
#
# The runlevels used by COL are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode (including initialisation of network
interfaces,
# if you do have networking)
# 2 - Multiuser, (without NFS-Server und some such)
# (basically the same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# (should be equal to 3, for now)
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
# Default runlevel.
id:5:initdefault:
# System initialization.
s0::sysinit:/bin/bash -c 'C=/sbin/booterd; [ -x $C ] && $C'
si::sysinit:/bin/bash -c 'C=/etc/rc.d/rc.modules; [ -x $C ] && $C
default'
s2::sysinit:/bin/bash -c 'C=/etc/rc.d/rc.serial; [ -x $C ] && $C'
bw::bootwait:/etc/rc.d/rc.boot
# What to do in single-user mode.
~1:S:wait:/etc/rc.d/rc 1
~~:S:wait:/sbin/sulogin
l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
# Trap CTRL-ALT-DELETE
ca:12345:ctrlaltdel:/sbin/shutdown -t3 -r now
# Action on special keypress (ALT-UpArrow).
kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let
this work."
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -h +5 "Power Failure; System Shutting
Down"
# If battery is fading fast -- we hurry...
p1::powerfailnow:/sbin/shutdown -c 2> /dev/null
p2::powerfailnow:/sbin/shutdown -h now "Battery Low..."
# If power was restored before the shutdown kicked in, cancel it.
po:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown
Cancelled"
# Run gettys in standard runlevels
1:12345:respawn:/sbin/getty tty1 VC linux
2:2345:respawn:/sbin/getty tty2 VC linux
3:2345:respawn:/sbin/getty tty3 VC linux
4:2345:respawn:/sbin/getty tty4 VC linux
5:2345:respawn:/sbin/getty tty5 VC linux
6:2345:respawn:/sbin/getty tty6 VC linux
# Run kdm in runlevel 5
kdm:5:respawn:/opt/kde/bin/kdm -nodaemon > /var/log/kdm 2>&1
George, MR. Tibbs & The Beast Kasica
Waukesha, WI USA
[EMAIL PROTECTED]
http://www.netwrx1.com
ICQ #12862186
Zz
zZ
|\ z _,,,---,,_
/,`.-'`' _ ;-;;,_
|,4- ) )-,_..;\ ( `'_'
'---''(_/--' `-'\_)
