NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bin/52461: relative module pathes not documented



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

From: Martin Husemann <martin%duskware.de@localhost>
To: John Nemeth <jnemeth%cue.bc.ca@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: bin/52461: relative module pathes not documented
Date: Fri, 4 Aug 2017 09:16:04 +0200

 On Thu, Aug 03, 2017 at 01:34:26PM -0700, John Nemeth wrote:
 > On Aug 3, 12:30pm, martin%NetBSD.org@localhost wrote:
 > }
 > } >Number:         52461
 > } >Category:       bin
 > } >Synopsis:       relative module pathes not documented
 > } >Arrival-Date:   Thu Aug 03 12:30:00 +0000 2017
 > } >Originator:     Martin Husemann
 > } >Release:        NetBSD 8.99.1
 > } >Description:
 > } 
 > } Neither the modload(8) nore modules.conf(5) man page give any examples of
 > } lines usable for loading modules or to put into /etc/modules.conf.
 > } 
 > } While 
 > } 
 > } 	modload /stand/sparc64/8.99.1/modules/ntfs/ntfs.kmod 
 > } 
 > } seems to work for me right now, of course I don't want to hard wire the
 > } version number, and both the existing sysctl for the path and the modload(8)
 > } man page hint at a relative path to be usable.
 > } 
 > } However, none of the obvious things did work for me:
 > } 
 > } 	modload ntfs/ntfs.kmod 
 > } 	modload ntfs.kmod 
 > } 	modload ntfs
 > 
 >      modules.conf(5) states:
 > 
 >    FILE FORMAT
 >      Lines starting with a hash (`#') and empty lines are ignored.  All other
 >      lines are passed to modload(8).
 > 
 > thus you shouldn't be using the word, "modload", in modules.conf.
 
 I got that ;-)
 
 The above where commands run manually for testing. But probably I accidently
 had the module still loaded from testing with the absolute path and
 misinterpreted the error in the "should have worked" case.
 
 >      However, modules.conf(5) does need clarification about how
 > arguments are handled.
 
 A simple EXAMPLE section would be good enough.
 Same for modload(8), maybe with an explanation of the search path and
 the (at least two) relevant sysctls.
 
 Martin
 


Home | Main Index | Thread Index | Old Index