Skip to contentSkip to conversation

Problem with the current HP PA setup of debian

parisc-linux Christoph Plattner 2 participants 2 messages Feb 13, 2002 – Feb 14, 2002

lore
Share & tools
lore
#0 lore raw

Hello PA-RISC hackers !

Since the last update a few days ago (apt-get dist-upgrade), I cannot login as ROOT on the console (/dev/ttyS0), although /etc/securetty' includes ttyS0'.

Login with a non-root user is ok, and a `su' with root password also succeeds. Only the initial login as root fails !

My `/etc/securetty':
# /etc/securetty: list of terminals on which root is allowed to login. # See securetty(5) and login(1).
console
# Standard consoles
tty1
tty2
tty3
tty4
tty5
tty6
tty7
tty8
tty9
tty10
tty11
tty12
ttyS0
ttyB0
# Same as above, but these only occur with devfs devices vc/1
vc/2
vc/3
vc/4
vc/5
vc/6
vc/7
vc/8
vc/9
vc/10
vc/11
vc/12

My `/etc/inittab':
# Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

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
# Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# Action on special keypress (ALT-UpArrow). kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."

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

# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
1:2345:respawn:/sbin/getty 38400 tty1
#2:23:respawn:/sbin/getty 38400 tty2
#3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal) #
T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #X0:23:respawn:/sbin/getty -L ttyB0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

I hope anybody knows already the problem !

Bye
Christoph P.

Signature · 3 lines
-------------------------------------------------------
private:	[email protected]
company:	[email protected]
#1 lore raw
Quoted 5 lines · Christoph Plattner

Hello PA-RISC hackers !

Since the last update a few days ago (apt-get dist-upgrade), I cannot login as ROOT on the console (/dev/ttyS0), although /etc/securetty' includes ttyS0'.

Hi Christoph,

I had a lot of problems with the latest debian libc6 packages, downgrading them again to 2.2.4-7 cured all my problems. All 2.2.5-X (X=1..3) libc6 packages seem broken. Maybe this also helps in your case ?

Regards,
Helge