From owner-freebsd-hackers Tue Feb 16 7:24:31 1999 Received: (from root@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29691 for freebsd-hackers; Tue, 16 Feb 1999 07:24:30 -0800 (PST) (envelope-from peter) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA27424 for ; Tue, 16 Feb 1999 07:01:42 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 24800 invoked from network); 16 Feb 1999 14:54:59 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 16 Feb 1999 14:54:59 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id JAA01466; Tue, 16 Feb 1999 09:54:59 -0500 (EST) Message-Id: <199902161454.JAA01466@y.dyson.net> Subject: Re: inode / exec_map interlock ? In-Reply-To: <199902160752.XAA21863@apollo.backplane.com> from Matthew Dillon at "Feb 15, 99 11:52:34 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 16 Feb 1999 09:54:59 -0500 (EST) Cc: dyson@iquest.net, tony@dell.com, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > :> > :> ( Matt sticks out his tongue and makes a face ) > :> > :There are issues and problems with exec_map and the issue needs to be revisited. > :However, you are not exposing the modified VM code for review, so it isn't easy to > :2nd guess what you are doing. > > All major changes have been CC'd to you and DG. But the best answer I > get is on the order of ( paraphrased ) "I might be able to look at it > in a few days, or maybe never". > Please refer to my comments on suggested design requirements (specifically those on 10 Jan 99). If you violated those suggestions, maybe it is important to require formal review. Regressions aren't what FreeBSD needs. I happen to think in terms of higher level design issues (coding, programming and indenting are superficial to me). Does this mean that I have to start resolving design concepts to code? Geesh, I am very busy, and writing code to correct mistakes is really not fair to me. Maybe you should take on the attitude of encompassing more developers into your fold, and then *wait* until testing and information is returned before committing. Then, if there are comments that are contrary to your creation, DISCUSS that with the *experts* rather than ignoring something that you don't want to hear. It seems that a mature developer would wait until a process can complete. You have innundated people with code, and review is more complex than just looking at syntax issues. If you are indeed such a fast programmer, and since important ideas are being overlooked, maybe more time should be spent understanding what is going on. * The term *experts* isn't due to arrogance, but due to 4-5years of experience and mistakes. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message