From owner-freebsd-hackers Thu Jun 8 23:42:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id D4C7337C210; Thu, 8 Jun 2000 23:42:25 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA07275; Fri, 9 Jun 2000 00:42:23 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <394091E1.F93783BF@softweyr.com> Date: Fri, 09 Jun 2000 00:42:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: kerneld for FreeBSD References: <200006090323.UAA01210@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > The issue is with really small ram embedded systems. > > Making things CAPABLE of being small is different from making > > them dynamicly loadable. > > Nobody in their right mind is going to produce a "really small ram" > embedded system that features the sort of nondeterminism that > "automatically" (read 'randomly') unloading modules would involve. Actually, embedded programmers are more likely to link everything in the kernel so they don't have to worry about calling drivers that aren't loaded. A pretty conservative lot, in general. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message