On Friday 12 December 2008 02:52, Mark Post wrote:
>> On 12/11/2008 at 10:36 PM, Sue Sivets <[email protected]> wrote:
>> I booted one of our sles 8 systems manually this afternoon for the first
>> time in a long time.
...
>> This system is usually booted by VM during an ipl.
>> During the boot process the system displayed the following messages:
>>     INIT: /etc/inittab: missing id field
>>     INIT: /etc/inittab: id field too long (max 4 characters)
>>
>>     INIT: cannot execute "/usr/sbin/getty"
>>     INIT: Id "cons" respawning too fast: disabled for 5 minutes
>>
>>     SCSI subsystem driver Revision:
>> 1.00
>>     Dec 11 21:30:54 suse80 kernel: SCSI subsystem driver Revision:
>> 1.00
>>     Dec 11 21:30:54 suse80 modprobe: modprobe: Can't locate module
>> block-major-65
>>
>> Can anyone shed some light on any of these for me please?
...
>It's been a couple of years since I installed one, but that kind of sounds
> like a RHEL inittab got written out by something.  Just what application
> were they trying to install?

Yup, SuSE doesn't use plain old getty anymore.  But then again, neither does
RHEL.  Both use mingetty.  It sounds like the /etc/inittab is badly
corrupted.

Here's the /etc/inittab from a SLES 8 system.  If you compare it to your
broken one, you should be able to figure out what has been changed.
        - MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA

================================================
#
# /etc/inittab
#
# Copyright (c) 1996-2002 SuSE Linux AG, Nuernberg, Germany.  All rights
reserved.
#
# Author: Florian La Roche <[email protected]>, 1996
#
# This is the main configuration file of /etc/init, which
# is executed by the kernel on startup. It describes what
# scripts are used for the different run-levels.
#
# All scripts for runlevel changes are in /etc/init.d/.
#
# This file may be modified by SuSEconfig unless CHECK_INITTAB
# in /etc/sysconfig/suseconfig is set to "no"
#

# The default runlevel is defined here
id:3:initdefault:

# First script to be executed, if not booting in emergency (-b) mode
si::bootwait:/etc/init.d/boot

# /etc/init.d/rc takes care of runlevel handling
#
# runlevel 0  is  System halt   (Do not use this for initdefault!)
# runlevel 1  is  Single user mode
# runlevel 2  is  Local multiuser without remote network (e.g. NFS)
# runlevel 3  is  Full multiuser with network
# runlevel 4  is  Not used
# runlevel 5  is  Full multiuser with network and xdm
# runlevel 6  is  System reboot (Do not use this for initdefault!)
#
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
#l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6

# what to do in single-user mode
ls:S:wait:/etc/init.d/rc S

# what to do when CTRL-ALT-DEL is pressed
ca::ctrlaltdel:/sbin/shutdown -r -t 4 now
~~:S:respawn:/sbin/sulogin /dev/ttyS0

# what to do when power fails/returns
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
#pn::powerfail:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

# for ARGO UPS
sh:12345:powerfail:/sbin/shutdown -h now THE POWER IS FAILING

# on S/390 enable console login in all runlevels
1:012356:respawn:/sbin/mingetty /dev/ttyS0
#2:012356:respawn:/sbin/agetty -L 9600 ttyS1 linux

# modem getty.
# mo:235:respawn:/usr/sbin/mgetty -s 38400 modem

# fax getty (hylafax)
# mo:35:respawn:/usr/lib/fax/faxgetty /dev/modem

# vbox (voice box) getty
# I6:35:respawn:/usr/sbin/vboxgetty -d /dev/ttyI6
# I7:35:respawn:/usr/sbin/vboxgetty -d /dev/ttyI7

# end of /etc/inittab

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to