Bug 1800

Summary: lilo: boot 2.0.36 single = multi vt s ??
Product: [Retired] Red Hat Linux Reporter: aap
Component: initscriptsAssignee: David Lawrence <dkl>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-28 05:00:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description aap 1999-03-25 23:03:40 UTC
is this a bug or a feature ??

yes that is not a mis print 2.0.36

I have a driver that only works in 2.0.36 :(

Comment 1 Bill Nottingham 1999-03-28 01:01:59 UTC
It can't open the initial console. From Documentation/devices.txt:
The console device, /dev/console, is the device to which system
messages should be sent, and on which logins should be permitted in
single-user mode.  Starting with Linux 2.1.71, /dev/console is managed
by the kernel; for previous versions it should be a symbolic link to
either /dev/tty0, a specific virtual console such as /dev/tty1, or to
a serial port primary (tty*, not cu*) device, depending on the
configuration of the system.

Comment 2 Bill Nottingham 1999-03-28 05:00:59 UTC
What you can do is, for example, is remake /dev/console
as major 4, minor 0. (rm /dev/console ; mknod /dev/console c 4 0);
while this is the old behavior and won't be include in RH,
it should allow you to boot both kernels.