From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 2 18:24:48 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 035AB1065674 for ; Sat, 2 Apr 2011 18:24:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D55808FC1E for ; Sat, 2 Apr 2011 18:24:47 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 8C08346B45; Sat, 2 Apr 2011 14:24:47 -0400 (EDT) Date: Sat, 2 Apr 2011 19:24:47 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Oleksandr Dudinskyi In-Reply-To: Message-ID: References: <000001cbea59$eb1c4b00$c154e100$@com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org Subject: Re: GSoC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 18:24:48 -0000 On Fri, 1 Apr 2011, Oleksandr Dudinskyi wrote: > I should like more specifically disclose my plan of action. One of the main > tasks is find the places where registered errors, subsequently error > analysis (their type) and separation errors related to disk and modifying > the output format. There are different types of errors such as soft, hard, > transport, device not ready, recoverable and other. Currently, presence the > problem of reports and the majority error logs built as an individual files. > Necessary changes in the kernel, which provide the emergence a database that > processes information from several sources. The current kernel can't report > what specific operations were errors, this further compounds the consistency > problem. Reports of drivers errors requires a change. Systematization format > recording of errors also is a priority,that we get and where the error > occurred. Hi Oleksandr: This sounds like a potentially interesting project, but it remains a bit abstract to me, which makes me worry about it as a GSoC project. Strong proposals typically have a well-defined and easily characterised objective (1-2 sentences), and 3-4 intermediate deliverables. I worry that what you've described may be a bit too researchy for a summer project, but I'm willing to be convinced otherwise! Could you flesh out in a bit more detail how what you have in mind would work: are there new daemons? system calls? will you reuse existing logging or error-handling infrastructure? what is the namespace for errors? how will it affect current operations? We don't need perfect answers to these questions yet, but a slightly more worked out example might help resolve my concerns. Thanks! Robert