From owner-freebsd-current Mon Dec 28 15:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11294 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:29:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11265 for ; Mon, 28 Dec 1998 15:29:31 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id AAA75940; Tue, 29 Dec 1998 00:25:48 +0100 (CET) To: Julian Elischer cc: Peter Wemm , Alfred Perlstein , Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-reply-to: Your message of "Mon, 28 Dec 1998 15:11:31 PST." Date: Tue, 29 Dec 1998 00:25:47 +0100 Message-ID: <75938.914887547@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A T405 with 64k RAM :-) Poul-Henning In message , Jul ian Elischer writes: >Transputer co-processor board... > >what do I win? > >julian > > >On Tue, 29 Dec 1998, Peter Wemm wrote: > >> Alfred Perlstein wrote: >> > >> > On Mon, 28 Dec 1998, Pat Barron wrote: >> > >> > > I know someone asked this, but I have not seen an answer: Could someone >> > > provide a list of exactly what was purged? It would be handy to know >> > > things like, "this was purged, and is absolutely *not* coming back", or >> > > "this was purged, but is being considered for reinstatement", but what I >> > > really want to know is *exactly* what is now (today) gone, that used to be >> > > there. >> > >> > voxware, lkms, vinum(an lkm) >> >> - DSI_SOFT_MODEM >> - bqu driver >> - 3c505 (note, *NOT* 3c905) >> - pcvt >> - broken (not updated for CAM) scsi drivers: nca, sea, wds, uha >> - ft >> - wcd (use acd instead) >> - voxware >> - lkm building (all lkm's have a corresponding kld) >> >> The vinum KLD module was accidently broken - it shared it's sources with >> the LKM. >> >> And 10 points to the first person who can tell me what 'bqu' was without >> looking it up. :-) >> >> > voxware may come back, vinum is definetly coming back as kld >> >> The jury is out on pcvt and voxware.. My feeling is that there's more than >> enough support for both to revive them. >> >> Vinum is already fixed (I hope), and should also now support being >> compiled into the kernel ("pseudo-device vinum") as well. >> >> > basically klms which have been deemed bad by -core are gone, as well as >> > voxware. >> >> LKM's have been deemed sub-optimal by just about everyone. We are in a >> situation where the KLD system is a superset of LKM's and it's a lot of >> work duplicating effort to keep LKM's working. LKM's are a.out only while >> KLD's are a.out and ELF, and both formats work on either format kernel.. >> KLD's work with DDB, KLD's can be auto-loaded by the kernel (and are >> already for filesystems). >> >> While I'd have liked the LKM retirement to be a little more peaceful and >> with more warning, I'm not all that sad that support has gone for >> building new LKMs that have already got *working* KLD equivalents. I for >> one would like to remove kernel support for LKM's as well. >> >> Cheers, >> -Peter >> -- >> Peter Wemm Netplex Consulting >> "No coffee, No workee!" :-) >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message