NetBSD Problem Report #52461

From martin@aprisoft.de  Thu Aug  3 12:26:20 2017
Return-Path: <martin@aprisoft.de>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id EEF0B7A20B
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  3 Aug 2017 12:26:19 +0000 (UTC)
Message-Id: <20170803122610.8B22F5CC761@emmas.aprisoft.de>
Date: Thu,  3 Aug 2017 14:26:10 +0200 (CEST)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: relative module pathes not documented
X-Send-Pr-Version: 3.95

>Number:         52461
>Category:       bin
>Synopsis:       relative module pathes not documented
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 03 12:30:00 +0000 2017
>Last-Modified:  Fri Aug 04 07:20:00 +0000 2017
>Originator:     Martin Husemann
>Release:        NetBSD 8.99.1
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD whoever-brings-the-night.aprisoft.de 8.99.1 NetBSD 8.99.1 (WHOEVER) #156: Mon Jul 24 09:58:27 CEST 2017 martin@seven-days-to-the-wolves.aprisoft.de:/work/src/sys/arch/sparc64/compile/WHOEVER sparc64
Architecture: sparc64
Machine: sparc64
>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


>How-To-Repeat:
see above

>Fix:
n/a

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/52461: relative module pathes not documented
Date: Thu, 3 Aug 2017 14:38:35 +0200

 On Thu, Aug 03, 2017 at 12:30:00PM +0000, martin@NetBSD.org wrote:
 > 	modload ntfs

 It turns out that this variant actually works. I must have typoed something
 when testing (or had it already loaded via absolute path and misread
 the error message).

 Hint from pgoyette@, who also points out that sysctl kern.module.verbose
 is a nice debugging option - it will print the actualy used pathes
 on the console.

 So for the documentation: a simple 

 --8<--
 ntfs
 -->8--

 in /etc/modules.conf makes NTFS available.

 Martin

From: John Nemeth <jnemeth@cue.bc.ca>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: bin/52461: relative module pathes not documented
Date: Thu, 3 Aug 2017 13:34:26 -0700

 On Aug 3, 12:30pm, martin@NetBSD.org 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.

      However, modules.conf(5) does need clarification about how
 arguments are handled.

 }-- End of excerpt from martin@NetBSD.org

From: Martin Husemann <martin@duskware.de>
To: John Nemeth <jnemeth@cue.bc.ca>
Cc: gnats-bugs@NetBSD.org
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 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	PR Database Search