Description of Problem: After doing a serial install, there is 1) no aboot.conf entry for the serial console (console=ttyS0 without console=tty0) 2) no *getty process running on the serial port 3) no /etc/securetty entry for ttyS0 to allow root login on the serial console Version-Release number of selected component (if applicable): Red Hat Linux release 7.1.90 (Roswell) How Reproducible: Very Steps to Reproduce: 1. Perform a serial installation 2. Try to boot and log in on the serial console Actual Results: Using installed aboot.conf entries, kernel messages can be directed to ttyS0, but not userspace messages (i.e. boot messages once init has started). There is now way to log in on the serial console Expected Results: To be able to send all console messages to ttyS0 and login in as user/root on serial console Additional Information: 7.1 installed mgetty, ran it on ttyS0, and added ttyS0 to /etc/securetty with a serial install 7.1 with a serial install also had a console=ttyS0 entry in the installed aboot.conf
2) and 3) should be fixed with modifications to bootloader.py to append console=ttyS0 if flags.serial is set, as kudzu should detect that /dev/console is a serial terminal on bootup and add the getty, etc.
A serail line (ttyS0) only option needs to be in aboot.conf on both the install CD and on the target install system disk. DS20L systems do not have a graphics card
*** Bug 58995 has been marked as a duplicate of this bug. ***
Fixed in RC1.
I'm closing this case because it was fixed in the Feb 22 delivery. Please let us know if you still see any problems with this issue.