From owner-freebsd-arch@FreeBSD.ORG Wed Apr 2 01:03:31 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08EED106564A; Wed, 2 Apr 2008 01:03:31 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id B98BA8FC21; Wed, 2 Apr 2008 01:03:30 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m3213Jhl043507; Tue, 1 Apr 2008 18:03:19 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m3213JEt043506; Tue, 1 Apr 2008 18:03:19 -0700 (PDT) Date: Tue, 1 Apr 2008 18:03:19 -0700 (PDT) From: Matthew Dillon Message-Id: <200804020103.m3213JEt043506@apollo.backplane.com> To: "Martin Fouts" References: <20080330231544.A96475@localhost> <200803310135.m2V1ZpiN018354@apollo.backplane.com> <200803312125.29325.qpadla@gmail.com> <200803311915.m2VJFSoR027593@apollo.backplane.com> <200803312006.m2VK6Aom028133@apollo.backplane.com> <200803312254.m2VMsPqZ029549@apollo.backplane.com> <200804011733.m31HXF6e039649@apollo.backplane.com> <200804012014.m31KEvTJ041049@apollo.backplane.com> <200804012325.m31NPwM1042551@apollo.backplane.com> Cc: Christopher Arnold , arch@freebsd.org, qpadla@gmail.com, freebsd-arch@freebsd.org Subject: RE: Flash disks and FFS layout heuristics X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2008 01:03:31 -0000 :> chip solution : :It's not a single chip or even two chips. It doesn't run linux. Keep :guessing wrong, Matt. I'm not guessing at all. I don't really give a damn about your embedded project, or your constant innuendo's about what it does or does not do. If you decide you want to talk about it, that's up to you. Personally speaking, I love talking about the projects I've done. I love talking about the cool technical details and the hard problems that had to be solved. I'm talking about the embedded world in general and how it functions these days. What made you think I was talking about YOUR particular project? I have no information... getting anything from you is like pulling teeth, you are wholely unwilling to part with a single meaningful detail and yet you expect to have a technical conversation by referencing it? Give me a break. Again, if you want to have an actual conversation, then the ball is in your court. You clearly believe that I am not qualified to have that conversation... well, put your money where your mouth is then. If you think my reasoning is so bad, then say something meaningful that directly addresses it, in technical terms. Hell, you can even quote papers rather then produce your own thoughts if you think it is relevant. The devil is in the details. That's what technical conversations are for. If I went by your logic I would have never written Diablo, or dmail, or a database, or numerous filesystems, or HAMMER, or gotten involved with OSs (people kept saying they were harder then micro os's. Oops, I guess they weren't after all!). Sheesh. -Matt