Bug 4919
Summary: | Booting after HD problems | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | volchok |
Component: | initscripts | Assignee: | David Lawrence <dkl> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-09-20 21:29:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
volchok
1999-09-05 00:00:19 UTC
Weird; we haven't experienced this problem here (unless it was on a Sparc). If all else fails, you can boot with 'linux init=/bin/bash' to get a prompt. ------- Additional Comments From 10/19/99 11:10 ------- I think i fugured out this one. I looked into init scripts and found out that if there is a problem with disk script runs sulogin. After checking out the source for sulogin. I found out that it will accept only up to 15 characters of password. Mine is 18 characters. The RH6.0 manual states that MD5 passwords can be up to 256 characters. |