Date: Mon, 11 Oct 1999 12:35:48 -0700 (PDT) From: dwhite@freebsd.org To: freebsd-gnats-submit@freebsd.org Subject: i386/14266: vfsload() looks in /lkm, not /modules Message-ID: <19991011193548.5F44014A1E@hub.freebsd.org>
index | next in thread | raw e-mail
>Number: 14266
>Category: i386
>Synopsis: vfsload() looks in /lkm, not /modules
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Oct 11 12:40:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Doug White
>Release: 3.3-RELEASE
>Organization:
>Environment:
FreeBSD tbone.egroups.net 3.3-STABLE FreeBSD 3.3-STABLE #3: Fri Oct 8 11:54:16 GMT 1999 root@tbone.egroups.net:/usr/src/sys/compile/TBONE i386
>Description:
In src/lib/libc/gen/getvfsent.c, the structure vfs_lkmdirs is:
static const char *vfs_lkmdirs[] = {
"/lkm",
"/usr/lkm",
0,
0
};
vfspath() uses this as the list of directories to search. If the
user is root, the value of the environment variable LKMDIRS is appended
to the list.
Obviously, /lkm is nonexistent on 3.X and later systems. As a result,
when mount_msdos() (or any mount_*) tries to dynamically load the
FS module, it runs into the error.
For some reason it works as root but gives a cryptic 'No such file or
directory' error when attempting to mount as a user, regardless of
vfs.usermount sysctl.
>How-To-Repeat:
Mount a filesystem with an unloaded KLD module but not compiled into
the kernel, such as msdos.
>Fix:
Change references to 'lkm' to 'modules'.
WORKAROUND: ln -s /modules /lkm
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991011193548.5F44014A1E>