All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: EvilTypeGuy <eviltypeguy@qeradiant.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: In great need
Date: 25 Oct 2001 16:13:38 -0400	[thread overview]
Message-ID: <1004040819.11884.24.camel@phantasy> (raw)
In-Reply-To: <20011025150858.E4535@virtucon.warpcore.org>
In-Reply-To: <20011025143701.B4535@virtucon.warpcore.org> <20011025194528.4512.qmail@eklektix.com>  <20011025150858.E4535@virtucon.warpcore.org>

On Thu, 2001-10-25 at 16:08, EvilTypeGuy wrote:
> > I think you're thinking of _Linux_Device_Drivers_.  The authors are working
> > on an updated edition of the kernel book, but it's not out yet.
> > 
> > jon
> 
> Yes, but the understanding linux kernel does include some material on 2.4,
> granted it's mostly previews of the 2.4 arch, but it's there nonetheless...

True, it does have a paragraph or two at the end of each chapter on what
2.4 is including, but its still entirely a 2.2 book otherwise.  Also,
there is no 2E so I can understand the confusion.  On the other hand,
Linux Device Drivers does have a 2E, and it is 2.4 oriented.

Regardless, I think both books are great.

	Robert Love


  reply	other threads:[~2001-10-25 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 15:32 In great need Patrick Ouellet
2001-10-25 15:58 ` Rik van Riel
2001-10-25 18:52   ` Daniel Phillips
2001-10-25 19:37     ` EvilTypeGuy
2001-10-25 19:45       ` Jonathan Corbet
2001-10-25 19:54         ` Tahar
2001-10-25 20:08         ` EvilTypeGuy
2001-10-25 20:13           ` Robert Love [this message]
2001-10-26 16:41   ` basic questions of memory management Hong Hsu
2001-10-25 16:34 ` In great need Jonathan Corbet
2001-10-25 20:10   ` Daniel Phillips
     [not found] <fa.jh1e0kv.4k8ujg@ifi.uio.no>
2001-10-25 16:14 ` John Weber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1004040819.11884.24.camel@phantasy \
    --to=rml@tech9.net \
    --cc=eviltypeguy@qeradiant.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.