Summary: | kldload can choose wrong module name for hardlinked modules | ||
---|---|---|---|
Product: | Base System | Reporter: | Alan Somers <asomers> |
Component: | kern | Assignee: | Alan Somers <asomers> |
Status: | Closed FIXED | ||
Severity: | Affects Many People | CC: | cem, gjb, rgrimes, sbruno |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Alan Somers
2019-03-19 21:28:19 UTC
Couldn't we just use symlinks instead of hardlinks? There's no "right" name for a hardlink, and a .ko may contain many modules (none of which must match the .ko name). With symlinks, the canonical name would be the VREG file. (In reply to Conrad Meyer from comment #1) I've been told that the boot loader doesn't understand symlinks. Huh. That might be true. It seems like something that would be easy to fix, but yeah that's a good reason to continue to use hardlinks. Still -- I'm not sure there's a good way to get the behavior you want with hardlinks, given everything else. Well, the default install only contains 3 pairs of hardlinked modules. It shouldn't be impossible to come up with a solution that works for three things. I could even do something as petty as sort those three pairs' old halves last within kldxref. A commit references this bug: Author: asomers Date: Thu Mar 21 21:41:07 UTC 2019 New revision: 345386 URL: https://svnweb.freebsd.org/changeset/base/345386 Log: fusefs: don't check for the fusefs module during the tests It's sufficient to check for /dev/fuse. And due to bug 236647, the module could be named either fuse or fusefs. PR: 236647 Sponsored by: The FreeBSD Foundation Changes: projects/fuse2/tests/sys/fs/fusefs/utils.cc |