Bug 59847
Summary: | rpm reports "failed to stat /proc/bus/usb" on installation or installation test | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alexander Stohr <alexander.stohr> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
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: | 2002-02-14 12:51:23 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
Alexander Stohr
2002-02-13 20:52:09 UTC
This is probably a packaging, not an rpm, problem. What package were you trying to install? Kernel? Were you installing into a chroot or otherwise unusual environment? package is selfmade but contains only a few binaries, X11 modules and shell scritps. thre is really no relevance to USB bus by design. The package is derived from another spec file that is some 24 months old. The main change are just the filenames and one subdir name of the contained files. its a chroot environment, a second harddisk with with a nearly original RedHat 7.2 system. The only thing is that the running kernel and the related proc filesystem do not provide USB support and thus not entry /proc/bus/usb. If in doubt , i can provide the RPM - but its most likely related to the missing kernel feature. Any hints on how i should analyze the package for determining its dependencys better? I suspect that the problem is in you spec file. Check for actions that require /proc mounted (even in a chroot) in the packages %post et al scriptlets. rpm itself does not care whether /proc is mounted or not. The origin of the problem was an invalid entry in /etc/mtab. Due to the nature of a chroot execution a few of the system files are taken from the embedded environment. After manually deleting the usb line in the file two further lines did fault (one of them was for /dev/cdrom). I feel like its a bit odd if rpm is forced to check any mounted devices before it is allowed to continue. It might be nice to ensure systems sanity when there is intention for using specific resources, but if i cant disable such check i think its no good. At least when i just want to check the integrity of an rpm package by applying "-i --test --nodep" i would prefer beeing able to ignore the initial testing of /etc/mtab because its doing "stat"s on things that have nothing to do with my target. I am not gone to the source code of rpm so far, there are better people around for doing this. Anyways, i consider the root cause to be tracked down now - its a combination of system setup and a specific insane(?) habit of the rpm executeables initialisation code. OK, this looks like WORKSFORME to me. Okay, that looks like RPM is INSANE to me. ;-) |