From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: hpa@transmeta.com (H. Peter Anvin)
Cc: macro@ds2.pg.gda.pl (Maciej W. Rozycki),
randy.dunlap@intel.com (Dunlap Randy),
hpa@zytor.com ('H. Peter Anvin'),
linux-kernel@vger.kernel.org
Subject: Re: The latest instance in the A20 farce
Date: Mon, 15 Jan 2001 14:30:29 -0500 (EST) [thread overview]
Message-ID: <200101151930.f0FJUTC254802@saturn.cs.uml.edu> (raw)
In-Reply-To: <3A633716.9EA1FDF5@transmeta.com> from "H. Peter Anvin" at Jan 15, 2001 09:44:54 AM
H. Peter Anvin writes:
> "Maciej W. Rozycki" wrote:
>> On Wed, 10 Jan 2001, H. Peter Anvin wrote:
>>> URRRK. I get a feeling these specs are either there to make life extra
>>> difficult for programmers, because the people that design them are too
>>> stupid to tie their own shoes, or because they want nothing but M$
>>> factory-installed to work.
>>
>> The page is titled "PC DESIGN GUIDE - For the Microsoft Windows
>> Family of Operating Systems," so what do you expect?
>
> Kind of says it all, doesn't it?
It looks like we let Microsoft fill the design guide void.
If you were to write "PC DESIGN GUIDE - For the Linux Operating
System" and a pile of test code, then there would be an
alternative to point people at.
Complaining is pretty useless.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-15 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 23:56 Dunlap, Randy
2001-01-11 0:09 ` H. Peter Anvin
2001-01-11 10:32 ` Olaf Titz
2001-01-15 17:24 ` Maciej W. Rozycki
2001-01-15 17:44 ` H. Peter Anvin
2001-01-15 19:30 ` Albert D. Cahalan [this message]
2001-01-15 20:00 ` H. Peter Anvin
2001-01-18 12:21 ` Gerhard Mack
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 1:43 Dunlap, Randy
2001-01-11 1:59 ` H. Peter Anvin
2000-12-06 23:55 H. Peter Anvin
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=200101151930.f0FJUTC254802@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=randy.dunlap@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®