Bug 8602 – Compaq Proliant 5000

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 8602 - Compaq Proliant 5000

Summary:	Compaq Proliant 5000

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jay Turner
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-01-19 09:33 EST by Jack Von Duhn
Modified:	2015-01-07 18:40 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-09 22:35:20 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jack Von Duhn 2000-01-19 09:33:47 EST

I have tryed to install RH6.1 on a smp system (4 CPUs and 3gb ram).  I had
turned off shadow passwording and the install seam to go OK.  After the
install finished, I rebooted and was prompted for my user/password.  When I
typed in root, or any other user that I created, I would get no prompt for
the password and get a 'Invalid login'.  To fix the problem, I re-installed
RH6.1 and when the installer ask me to reboot, I used Alt-F2 to get to a
prompt and was able to look at the mounted filesystem.  In the passwd file
it was showing the line

root:x:0:0:root:/root:/bin/bash

I did not have a shadow password file in /etc so I created one.  Then
rebooted and was able to login just fine.

Jack Von Duhn
jackvonduhn@eaton.com
216.523.4782

Comment 1 Jay Turner 2000-02-09 22:35:59 EST

This bug is fixed in the latest installer available in beta currently.

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