From owner-freebsd-arch  Wed Jun 20  0:12:24 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2BC4337B401; Wed, 20 Jun 2001 00:12:22 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.247.138.115.Dial1.SanJose1.Level3.net [209.247.138.115])
	by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA08471;
	Wed, 20 Jun 2001 00:12:20 -0700 (PDT)
Message-ID: <3B304CF4.3A57593E@mindspring.com>
Date: Wed, 20 Jun 2001 00:12:52 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Baldwin <jhb@FreeBSD.org>
Cc: arch@FreeBSD.org, Peter Pentchev <roam@orbitel.bg>,
	Nate Williams <nate@yogotech.com>
Subject: Re: new kldpath(8): display/modify the module search path
References: <XFMail.010619232327.jhb@FreeBSD.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

John Baldwin wrote:
> 
> On 20-Jun-01 Terry Lambert wrote:
> > What is the interaction with /etc/modules.old, when you are
> > booting a /kernel.old?
> 
> In -current (which is where kldconfig(8) is going, btw) all
> modules live with their correspnding kernel in the same
> directory under /boot.  Thus modules and kernel are in sync
> for kernel.old, kernel, and
> kernel.fix_it_after_joe_random_committer_broke_it.

I thought this change was backed out, after everyone
hated it?

Even so, what ensures that the path is not reset by some rc
file to /boot/kernel, when the kernel that you booted was
/boot/kernel.old/kernel.ko?

I don't see that putting the modules under /boot with the
kernel module itself grants any protection from a bogus
mismatched module coming in as the result of a kldpath
command in an rc file in /usr/local/etc/rc.d, or /etc,
for that matter.

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message