Bug 161037
Summary: | chroot segv on rescue cd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daryll <daryll> |
Component: | busybox | Assignee: | Ivana Varekova <varekova> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
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: | 2005-06-21 13:56:09 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
Daryll
2005-06-20 05:17:04 UTC
I suspect the issue is mixing the two OS versions. Did you test the mismatched versions? The reason I think that might be the problem, is that I just updated my FC3 system to the packages in updates-testing and now if I attempt to boot any of my old kernels (2.6.11-1.27 for example) it reports a core dump very early in the init process. If I boot the kernel 2.6.11-1.35 (which is also in updates testing) then everything works fine. We needed a rescue disc from FC4 because it had SATA drivers that aren't in EL3. Maybe this isn't supposed to work? I test fc4 rescue CD on a RHEL3 system and it works fine. Probably there is some mistake on the system you want to chroot which causes this error. |