From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263778AbTLTCDW (ORCPT ); Fri, 19 Dec 2003 21:03:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263786AbTLTCDW (ORCPT ); Fri, 19 Dec 2003 21:03:22 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:270 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id S263778AbTLTCDV (ORCPT ); Fri, 19 Dec 2003 21:03:21 -0500 Date: Fri, 19 Dec 2003 17:56:01 -0800 (PST) From: Andre Hedrick To: Jonathan Corbet cc: linux-kernel@vger.kernel.org Subject: Re: Linux Device Drivers 3rd Edition In-Reply-To: <20031219153920.28201.qmail@lwn.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jon, A map is a published reference how to move around. So yes it does give a right to use knowledge from the information expressed. If there was not a reference a manual to kernel programming, then the source is the sole manual. Now given the volital nature of the moving API, regardless of reason, any judge would likely veiw that active movement as an attempt to thwart the successful production of a "3rd Party" manual. This does not even include all the published referneces of changes deemed as publish manuals in all the mailing list archieves. On a side note, why doesn't LWN bother to investigate cases of known and provable GPL violations. I wish you well on the sales of the book, and I will by a copy this time to catch up on what I have forgotten. Cheers, Andre Hedrick LAD Storage Consulting Group On Fri, 19 Dec 2003, Jonathan Corbet wrote: > > So this is the third release to publish the documented API to the writing > > kernel level device drivers? > > I guess I see it as more of a map of the jungle as I (and my co-authors) > see it. A guide to New York does not automatically open all of the doors > of the city to you; should a guide to certain parts of the kernel be > different? > > There was an informative article in Phrack a while back on how to install > code into a running kernel via /dev/kmem. I guess that must be a > documented API too, now. > > jon >