Re: bin/58820: modload does not properly search the module path

["Michael van Elst via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR bin/58820; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/58820: modload does not properly search the module path
Date: Sun, 10 Nov 2024 13:29:16 -0000 (UTC)

 martin%NetBSD.org@localhost writes:
 
 >[/tmp] master-of-confusion # modload usbverbose
 >modload: usbverbose: No such file or directory
 
 >But also the full filename does not work:
 >[/tmp] master-of-confusion # modload usbverbose.kmod
 >modload: usbverbose.kmod: No such file or directory
 
 It's either a file path (if it includes a '/'), absolute or relative to
 the current directory, and then it needs the same suffix as the file.
 
 Or it is a module name and then the path $base/$name/$name.kmod is used.
 That e.g. seems to work fine when you use /etc/rc.d/modules.
 
 In the latter case, a chroot is NOT honored. The kernel always accesses
 module files on the true root.
 
 The code looks broken though. In many places the name (with or without a '/')
 is treated just like a module name, e.g. to check for already loaded modules.