No, hits=-929.5 required=5.0
	tests=AWL,DATE_IN_PAST_03_06,T_NONSENSE_FROM_40_50
	version=2.50-cvs

URL: http://www.newsisfree.com/click/-0,8613674,159/
Date: 2002-10-06T18:12:46+01:00
Back when 64KB was more memory than any computer would ever need, there was a
time when memory managers didn’t exist. But gradually, new computer systems
came out with larger amounts of memory and designers discovered ways to eat up
RAM faster than any system could dish it out. This discussion is based on
Tiburon's experiences in writing and rewriting the memory manager for Madden
NFL 97 to Madden NFL 2002.

from localhost (jalapeno [127.0.0.1])
	by example.com (Postfix) with ESMTP id 7B97316F03
	for <zzzz@localhost>; Wed,  9 Oct 2002 10:51:09 +0100 (IST)
from egwn.net (ns2.egwn.net [193.172.5.4]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g993QaK17008 for
    <zzzz-rpm@example.com>; Wed, 9 Oct 2002 04:26:36 +0100
from mx1.example.com (mx1.example.com [66.187.233.31]) by egwn.net
    (8.11.6/8.11.6/EGWN) with ESMTP id g993HEf22898 for
    <rpm-list@freshrpms.net>; Wed, 9 Oct 2002 05:17:14 +0200
from int-mx1.corp.example.com (int-mx1.corp.example.com
    [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id
    g992vTX03844 for <rpm-list@freshrpms.net>; Tue, 8 Oct 2002 22:57:29 -0400
from pobox.corp.example.com (pobox.corp.example.com
    [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id
    g993HAf02250 for <rpm-list@freshrpms.net>; Tue, 8 Oct 2002 23:17:10 -0400
from ckk.rdu.example.com (ckk.rdu.example.com [172.16.57.72]) by
    pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g993H9a05656 for
    <rpm-list@freshrpms.net>; Tue, 8 Oct 2002 23:17:09 -0400
No, hits=-7.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,KNOWN_MAILING_LIST,
	      QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,SAVE_BUCKS,
	      SIGNATURE_SHORT_SPARSE,T_NONSENSE_FROM_40_50
	version=2.50-cvs

On Mon, 2002-10-07 at 13:28, Matthias Saou wrote:
> I've never heard of any CD-ROM or DVD-ROM drive having problems with DMA...
> although there probably is since Red Hat decided to default disabling it a
> few releases back :-/
Heh. I get to see bad CDROM problems all the time. Mostly when vendors
buy crap cables to try to save $0.02/each, but there are chipsets and
drives with known DMA issues as well.
> Normally, even if you try to enable DMA and your device doesn't support it,
> it simply don't be able to make the change, and that's it. The problem IIRC
> is with crappy hardware that is supposed to support DMA but doesn't work as
> expected when it's enabled... maybe Chris could confirm this? ;-)
Usually if you enable DMA on a CDROM that can't handle it gracefully you
won't be able to read data off it relably, and that's about it. No
end_of_the_world problems, and easily fixed.
> I guess I'll settle for the /dev/dvd link change as described and putting
> the DMA tip in the %description :-)
My biggest beef with automatically setting /dev/dvd is that I always
seem to have a CD-Burner and a DVD drive (or DVD burner) in the same
box, and I usually have the DVD as the second drive /dev/cdrom1 in
"kudzu-speak". I agree that the %description is the best place for the
tip. Unless someone can come up with a way to probe CD/DVD drives to
divulge their largest supported media size without loading ide-scsi or
having that media currently in the drive.
--
Chris Kloiber
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list