From owner-freebsd-current Sun Dec 27 10:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19993 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:28:12 -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 KAA19987 for ; Sun, 27 Dec 1998 10:28:07 -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 TAA68623; Sun, 27 Dec 1998 19:25:44 +0100 (CET) To: Brian Feldman cc: Mark Murray , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 13:07:07 EST." Date: Sun, 27 Dec 1998 19:25:44 +0100 Message-ID: <68621.914783144@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> We now need (tr: I would like) some kind of "ports-like" mechanism >> for kernel bits, such as example kld so devices can be written by >> the general population _and_maintained_ as ports code (kinda like > >Agree, MORE than wholeheartedly! I was thinking of proposing converting these >older drivers to modules in ports, with the associated utilities, but I thought >it would be too risque to propose. It probably is, seeing as noone wants to >maintain these drivers let alone modularize them. The ports idea brings a >question though: what do we do about device majors? Make DEVFS standard. -- 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