Summary: | update-modules: /etc/modules.d/lpfc needs an /etc/modprobe.d/lpfc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Schröpf <tobias> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ikelos |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tobias Schröpf
2009-08-11 07:24:43 UTC
And where does this 'lpfc' file come from? Don't expect us to guess from the 10000 ebuilds around there. # emerge portage-utils # qfile lpfc (In reply to comment #1) > And where does this 'lpfc' file come from? Don't expect us to guess from the > 10000 ebuilds around there. sorry for the insufficient information I delivered... but I didn't know what kind of Information you need... > # emerge portage-utils > # qfile lpfc > # qfile lpfc sys-kernel/xen-sources (/usr/src/linux-2.6.29-xen-r4/drivers/scsi/lpfc) sys-kernel/xen-sources (/usr/src/linux-2.6.30-xen-r2/drivers/scsi/lpfc) so it looks like the file this bug is about (/etc/modules.d/lpfc) doesn't belong to any package. I suppose the guy who set up this machine created it by hand. But as he isn't working here anymor I can't ask him... So this bug report is obsolete? Sorry for the inconvenience! I just followed the instructions that appeared :-) No problem, thanks for letting us know. It should just be possible to move the file from the one directory to the other, I don't believe the file format's changed between module-init-tools where the modprobe name change was made... |