# $NetBSD: Makefile,v 1.1 2004/07/06 12:28:20 yamt Exp $ SUBDIR+= sa1 .include component.c -> local_component.c 2014-03-13T02:04:59+00:00 pooka pooka@NetBSD.org 2014-03-13T02:04:59+00:00 45e149a519b66234672a6c1481a0ba410a6a79d2

Introduce RUMP_COMPONENT. It behaves mostly like a simplified 2010-03-01T13:12:19+00:00 pooka pooka@NetBSD.org 2010-03-01T13:12:19+00:00 510a73e003d73cee5a9e0a1b287150f5f9477a4f module which is linked into the kernel and cannot be unloaded. The main purpose is to get the proper constructors run and create any /dev nodes necessary for said component. Once more of the kernel (e.g. networking stack and device drivers) are converted to MODULE and devfs pops up from somewhere, rump components can be retired.
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component.  Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.
Use a bunch of weak symbols to determine which network components 2009-05-28T00:02:16+00:00 pooka pooka@NetBSD.org 2009-05-28T00:02:16+00:00 f731c31fa4f3c987ced0948ad82d81ac86c52ac7 are present. This works in userspace as opposed relying in link sets, which fail miserably. Later, when the networking stack becomes modularized, we can move to a dynamic scheme like with file systems. Also, this change allows us to do proper autoconfig, namely attach the loopback interface iff it is present.
are present.  This works in userspace as opposed relying in link
sets, which fail miserably.  Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.