Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68014
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Subject | Re: How security holes happen |
| Date | 2014-03-07 19:46 -0500 |
| Organization | IISS Elusive Unicorn |
| References | (3 earlier) <5adebc12-aa37-4139-82d8-563f46a27dc0@googlegroups.com> <mailman.7885.1394152206.18130.python-list@python.org> <e34bed3d-920b-4faa-bdef-43cf241e8cab@googlegroups.com> <mailman.7887.1394158390.18130.python-list@python.org> <ffe47689-e594-446c-b2fc-71696114abe2@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.7914.1394239805.18130.python-list@python.org> (permalink) |
On Thu, 6 Mar 2014 18:39:01 -0800 (PST), "Mark H. Harris"
<harrismh777@gmail.com> declaimed the following:
>On Thursday, March 6, 2014 8:13:02 PM UTC-6, MRAB wrote:
>>
>> The Z80's architecture and instruction set is a superset of that of the
>> 8080; the 6502's architecture and instruction set isn't a superset of,
>> or even compatible with, that of the 6800 (although it can use the same
>> I/O, etc, chips).
>
>My point is not what, but who. Motorola engineers designed the 6502. A rose
>is a rose by any other name. Its the people who count... if Motorola had listened
>to those guys, who knows ... ? neither here nor there now, or course.
And ex-IBM folk created the SDS Sigma line (later the XDS Sigma)
[Scientific Data Systems -> Xerox Data Systems].
That doesn't make my college Sigma-6 an IBM-based product (for one
thing, IBM had around 7 interrupt vectors, while the Sigma-6 had 224 or so
[it could actually assign a separate interrupt to EACH connected terminal
<G>)
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: How security holes happen Chris Kaynor <ckaynor@zindagigames.com> - 2014-03-03 14:55 -0800
Re: How security holes happen sffjunkie@gmail.com - 2014-03-04 08:41 -0800
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 04:07 +1100
Re: How security holes happen Skip Montanaro <skip@pobox.com> - 2014-03-04 11:16 -0600
Re: How security holes happen Ned Batchelder <ned@nedbatchelder.com> - 2014-03-04 15:47 -0500
Re: How security holes happen Ethan Furman <ethan@stoneleaf.us> - 2014-03-04 13:49 -0800
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 00:48 +0200
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 09:57 +1100
Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 17:59 -0500
Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:16 +0000
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-05 10:22 +1100
Re: How security holes happen Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-04 23:40 +0000
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:31 -0500
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-04 19:30 -0500
Re: How security holes happen Roy Smith <roy@panix.com> - 2014-03-04 20:57 -0500
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-05 04:11 +0000
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 08:37 +0200
Re: How security holes happen Steven D'Aprano <steve@pearwood.info> - 2014-03-05 08:26 +0000
Re: How security holes happen Ben Finney <ben+python@benfinney.id.au> - 2014-03-05 19:57 +1100
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 11:01 +0200
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 06:11 -0800
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 02:16 +1100
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-05 19:24 -0500
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 17:24 -0800
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-06 01:40 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 18:07 -0800
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-06 19:28 -0500
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 17:53 -0800
Re: How security holes happen MRAB <python@mrabarnett.plus.com> - 2014-03-07 02:13 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-06 18:39 -0800
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:46 -0500
Re: How security holes happen Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-03-07 19:43 -0500
Re: How security holes happen Neil Cerutti <neilc@norwich.edu> - 2014-03-05 14:19 +0000
Re: How security holes happen Marko Rauhamaa <marko@pacujo.net> - 2014-03-05 16:54 +0200
Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 18:42 +0000
Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-06 06:00 +1100
Re: How security holes happen Grant Edwards <invalid@invalid.invalid> - 2014-03-05 15:28 +0000
Re: How security holes happen Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-03-05 15:47 +0000
Re: How security holes happen "Mark H. Harris" <harrismh777@gmail.com> - 2014-03-05 08:37 -0800
csiph-web