From owner-freebsd-current Thu Oct 7 12:19:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 56D7115326 for ; Thu, 7 Oct 1999 12:19:03 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id QAA62777; Thu, 7 Oct 1999 16:17:01 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Oct 1999 16:17:00 -0300 (ADT) From: The Hermit Hacker To: "Daniel O'Connor" Cc: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: modules: how to use? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Oct 1999, Daniel O'Connor wrote: > > On 07-Oct-99 Greg Lehey wrote: > > Well, the standard way to load a kld is with kldload(1) or kldload(2). > > I don't know if procfs works properly like this, though. > > Well I would assume (aha) that when mount cannot find procfs in the list of > FS's the kernel knows about it would try and load it just like all the others.. okay, I had started to write down the whole error message last night, until I saw that the process that died dealt with procfs and figured it was that I took the option out...I'll redo it tonight when I get home and write it all down and submit it... Just to confirm, *technically*, I should just have to comment out the options PROCFS in my kernel config, rebuild and reboot and since procfs isn't in the kernel, it will look for it as a module? Will report later tonight on what happens... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message