Bug 14167 - Serial Installation Failure
Summary: Serial Installation Failure
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.2
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Brock Organ
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-17 18:11 UTC by Mark J. Watson
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-08-16 15:46:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark J. Watson 2000-07-17 18:11:43 UTC
Red Hat Linux 6.0 allowed a serial install by modifying the boot disk to
timeout and answer:

boot: linux serial

This was no longer available in 6.1 and 6.2. Will it be supported in future
versions of Red Hat Linux?

Comment 1 Mark J. Watson 2000-07-18 16:33:21 UTC
One of the main perks of having a serial installation method is building server
systems. It drops the cost of the server by several hundereds of dollers. That
money can be used on something that the end-user can use (e.g. RAM). To use the
serial terminal installation method it is not necessary to have a serial
terminal (use minicom and a null modem cable).

The old serial terminal install didn't give you a command prompt at com1 like
the SPARC version does. If the installation method becomes supported again you
might want to make it similar to the SPARC version and echo the following line
into the inittab file.

S0:23:respawn:/sbin/getty ttyS0 DT9600 vt100

Comment 2 Michael Fulbright 2000-07-25 14:28:50 UTC
Brock please verify serial installs work with current development tree.

Comment 3 Brock Organ 2000-08-16 15:46:27 UTC
hmmm ... I believe the "linux serial" option may be obsoleted ... do you have
any luck using:

boot: linux text console=ttyS0,9600n8 

(verified and tested i386 NFS install using "linux text console=ttyS0,9600n8"
using the Pinstripe public beta ...)

Comment 4 Brock Organ 2000-08-22 20:57:38 UTC
please reopen this bug if I have misdiagnosed your problem, or if youu have
other information on it ... thanks for your report!


Note You need to log in before you can comment on or make changes to this bug.