From owner-freebsd-hackers Sat Oct 17 12:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11981 for freebsd-hackers-outgoing; Sat, 17 Oct 1998 12:07:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11965 for ; Sat, 17 Oct 1998 12:07:07 -0700 (PDT) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id PAA20683; Sat, 17 Oct 1998 15:06:45 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA28666; Sat, 17 Oct 1998 15:06:45 -0400 Date: Sat, 17 Oct 1998 15:06:45 -0400 From: cmascott@world.std.com (Carl Mascott) Message-Id: <199810171906.AA28666@world.std.com> To: hackers@FreeBSD.ORG Subject: Does 3.0 mount(2) autoload filesystem KLDs? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the new KLD system in 3.0, does mount(2) still fail if the required filesystem module is not already loaded? I always thought that this was a design flaw in 2.x: programs should not need to know or care whether filesystem code is statically or dynamically loaded. If a program asks to mount a filesystem, mount(2) should just do whatever is necessary to mount it. As an example of how this causes problems in 2.x, consider the case where cd9660 is an LKM that is not loaded and one runs sysinstall from hard disk. Sysinstall fails if it tries to access the CD-ROM (see PR misc/6752). -- Carl Mascott cmascott@world.std.com uunet!world!cmascott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message