Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 254016 - udev-135-r3 with openrc-4.1-r1 in OpenVZ VE doesn't start tty0 by default - mc segfaults.
Summary: udev-135-r3 with openrc-4.1-r1 in OpenVZ VE doesn't start tty0 by default - m...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High minor (vote)
Assignee: udev maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-06 21:06 UTC by Janusz
Modified: 2009-02-25 13:50 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janusz 2009-01-06 21:06:57 UTC
I'm using OpenVZ with Gentoo as VE. I upgraded it to use openrc-0.4.1-r1, udev-135-r3 and sysvinit-2.86-r12.

The system starts ok, but there is no /dev/tty0 and when I start screen and then launch mc in VE I get Segmentation fault.

Manually creating the device removes the problem.

Reproducible: Always

Steps to Reproduce:
1. upgrade to openrc-0.4.1-r1, udev-135-r3 and sysvinit-2.86-r12 as Portage advices.
2. launch screen
3. launch mc.

Actual Results:  
Segmentation fault

Expected Results:  
Mc launched properly.

The way to create the device is ancient but cool ;-)

mknod /dev/tty0 -c 4 0

Workaround is to not use mc at all.
Comment 1 Matthias Schwarzott gentoo-dev 2009-01-08 10:05:48 UTC
No idea why udev is not started, or does not create /dev/tty1. Have a look at Bug 253396 first.

Nevertheless mc should catch errors and not crash.
Comment 2 Matthias Schwarzott gentoo-dev 2009-02-25 13:50:34 UTC
If this still is a problem, please attach
emerge --info output and a log or screenshot of the boot process.

Please also check if udev was properly added to the sysinit runlevel, by checking
ls -l /etc/runlevels/sysinit/udev