From owner-freebsd-hackers Thu Jun 3 13: 8:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.mindspring.com (smtp3.mindspring.com [207.69.200.33]) by hub.freebsd.org (Postfix) with ESMTP id 68B5B1599E for ; Thu, 3 Jun 1999 13:08:34 -0700 (PDT) (envelope-from ahasty@mindspring.com) Received: from mindspring.com (user-33qso9g.dialup.mindspring.com [199.174.97.48]) by smtp3.mindspring.com (8.8.5/8.8.5) with ESMTP id QAA18304; Thu, 3 Jun 1999 16:08:30 -0400 (EDT) Message-ID: <3756E0FA.67F0D88F@mindspring.com> Date: Thu, 03 Jun 1999 13:09:30 -0700 From: Amancio Hasty X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, schimken@cs.rpi.edu Subject: Re: 3.2-stable, panic #12 References: <199906031735.NAA37037@cs.rpi.edu> <199906031938.MAA99463@apollo.backplane.com> <3756DD11.3F943D5F@mindspring.com> <199906031955.MAA99584@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I really have gone over and over the issue of the "Dark Side " of core not just with myself but with other hackers and I am afraid that there is no easy solution on sight aside from having a commercial entity where individuals are held accountable and when they step way out of line they can be fire. Perhaps you are correct and this is the best organizational model that we can have and we just have to accept it and live with it. BTW: The linux camp is in a similar situation -- had a chat with VA Research where I pointed out a simple behavior problem with Linux : I do an ftp download in a linux box and periodically I see a slight pause -- VA research snap back saying that the problem was due to the VM / Scheduler and that they couldn't fix it because Linus held tight control over that section of the kernel. I would like to know who took your commit priviliges away. Amancio Matthew Dillon wrote: > : > :Silly me , I was wondering what happen to you . I vote that your commit > :priviliges should not be taken away by the "Dark Side" of core and > :should be re-instated. > : > :Also wondering if this is perhaps a good time to split up FreeBSD > :along commercial / professional lines -- we can leave the silly > :core group along and proceed forward with a business model. > : > : Cheers, > : Amancio > : > > No, FreeBSD should not be split up. The current organization has all > the right stuff, but certain issues that should have begun to get > addressed years ago were left to rot. All that is needed is a reality > check. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message