[604] in NetBSD-Development
Using -current for NetBSD-Athena
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Fri Mar 3 12:52:33 1995
From: ghudson@MIT.EDU
Date: Fri, 3 Mar 1995 12:51:51 -0500
To: netbsd-dev@MIT.EDU
Because it's too much work to integrate Linux compatibility into a 1.0
source tree, I think we'll need to use a -current kernel for
NetBSD-Athena so that we can run third-party software. This should
also make it easier to incorporate IBCS compatibility when it works,
and other features we want, assuming most of the kernel internals
don't change too much before 1.1. Here are my plans for using a
-current kernel for NetBSD-Athena:
* We'll use a snapshot (say, what I currently have on glacier)
and incorporate bugfixes as we go.
* We will replace only the kernel, libkvm, ps, and w, and
other statically linked programs that use libkvm if there
are any.
* We will modify locore.s so that it works with the 1.0
assembler.
* Therefore, the development environment doesn't change, and
programs built on NetBSD-Athena will continue to work on a
stock 1.0 system.
* We'll still need separate Adaptec and Buslogic kernels,
because the Buslogic SCSI autoprobe still detects my Adaptec
SCSI controller and fails to boot. However, if Charles
tightens the Buslogic probing code, it will be easier to
fold in those changes so that we have a single kernel.
* So that people can switch versions of {netbsd,libkvm,ps,
w,libafs.o} all at once, I plan to package kernel-dependent
programs together somehow.
If kernel internals do change a lot before 1.1 and there are new
features we want, we'll have the machinery in place to take another
snapshot.
Once we've done this, we can talk to ACS about getting inbsdbin
directories in the Xess, Matlab, and Maple lockers.
Comments?
