text:
Talk:/dev/random

FreeBSD claims are wrong
It seems some claims for the FreeBSD implementation in the article are incorrect. Since no sources are given, I'd like to change them to something better, since I have no idea, where the FreeBSD /dev/random device never blocks statement originally came from.

FreeBSD documentation (http://www.freebsd.org/cgi/man.cgi?query=random&apropos=0&sektion=4&manpath=FreeBSD+10.0-stable&arch=default&format=html) clearly states that /dev/{u,}random will block if there is not enough entropy and has done so since at least 5.0-RELEASE.

https://wiki.freebsd.org/201308DevSummit/Security/DevRandom has a lot of discussion going on on improving /dev/random on FreeBSD. Most importantly: ''Both Yarrow and Fortuna need to accumulate a certain amount of entropy before they can start generating random numbers. Until that happens, reads from /dev/random will block.'' dhke (talk) 09:22, 28 April 2014 (UTC)

Should this all really be in the FreeBSD section?
In 2004, Landon Curt Noll tested the FreeBSD 5.2.1 version of /dev/random and found that it was not a cryptographically strong random number generator because its output had multiple uniformity flaws according to the Billion bit test. Similar flaws were found in the Linux 2.4.21-20, Solaris 8 patch 108528-18, and Mac OS X 10.3.5 implementations of /dev/random.

 * I'm removing that part altogether per WP:NOR: the only reference is a link to the web page of the person who added that paragraph. I can't see any reliable-looking source (e.g. academic paper) referenced on that web page. Lamellae (talk) 22:06, 13 August 2013 (UTC)

Typical?
The article says:

 * It is typically used for providing a character stream for encryption, incompressible data, or securely overwriting files.

No. These are not typical uses but rather they are just some of the typical uses. But it is no more secure to overwrite a file with random data than it is do to do will nulls, so that is a poor and inefficient way of overwriting files!

Paul Beardsell 23:27, 27 Sep 2004 (UTC)

Actually, I (and apparently the U.S. gov't) disagree.

The DoD regulation for deleting files securely states that overwriting with random material (maybe up to 5 times) will ensure that any orderly data is gone. If you only use 0s and 1s, the possibility is there that a clever recovery could analyze the HD and determine if parts are not totally zeroed out. Theoretically, this would permit an attacker/recovery expert to locate segments of files. Random overwrite makes this impossible: the underlying structure is now totally random. nneonneo 18:48, 30 January 2006 (UTC)

 * This is wrong. First, the DoD would rather you melt or grind the media. Second, it's silly to go to extreme measures defeating an exotic threat without also addressing the problem of bad block replacement relocating your data. Your data may be all over the drive, never overwritten, because the hard drive decided that a sector was about to fail. It is better to be fast, just in case you get interrupted by the enemy, and so that you are not tempted to skip the operation. 24.110.60.225 03:08, 5 July 2006 (UTC)

 * Using a journaling file system carries a similar risk. IMHO, the most reliable way to ensure that deleted data is unreadable is to never write unencrypted data to the platter in the first place. Failing that, overwriting with several passes of random data is best, precisely because it decreases the signal-to-noise ratio for any attacker trying to read the old bits. See Peter Gutmann's 1996 paper Secure Deletion of Data from Magnetic and Solid-State Memory for a thorough discussion of the issues.

 * That said, /dev/random is unsuitable for wiping disks simply because it's slow, even if you use urandom. I use it to seed a fast CSPRNG and use that for the overwriting. Unless you expect a major corporation or intelligence agency to try to read your disk, and have data they would find interesting, it works well enough. Tualha (Talk) 17:46, 24 November 2006 (UTC)

How do we know...
How do we know that stuff that comes from /dev/random isn't actually XOR'd with what goes into /dev/null? That /dev/null info has to go back into the machine somehow, or else it might collect inside the CPU fan and hinder that source of information.

This /dev/random seems like it could be hazardous if overused--it could overflow into /dev/zero and junk up the whole system. There should be a /dev/monitor that puts information back into the entropy pool and junks the pool when it gets close to overflowing. Though where this junk goes to could be a problem. There should probably be some type of information bottle that the user could change when necessary.

This bottle of potentially valuable information could then be sold to an InfoDump, which would distill the sticky black stuff into clear, pure inert information and sell the excess junk to some bigger InfoDump... --Ihope127 23:58, 11 July 2005 (UTC)

 * Sounds to me as if it's already overflowed into your brain. Wiseguy ;) Tualha (Talk) 17:46, 24 November 2006 (UTC)

Confusion
I am confused. urandom takes the output of random, and applies additional transformations? In which case, why is it called a "pseudo-random" number generator? I associate psuedo-random with purely numerical algorithms that produce predictable, but hopefully acceptable output given a seed. Sdedeo 22:24, 2 September 2005 (UTC)

 * /dev/urandom is the non-blocking form of /dev/random. It outputs exactly what /dev/random does up until the entropy pool runs out, at which point it uses a different PRNG to generate values. Thus, it is non-blocking, but output isn't guaranteed to be of high quality. nneonneo 18:35, 30 January 2006 (UTC)

 * This is probably not true. /dev/urandom continues to give out pseudo random numbers with the same algoritm, but without adding new entropy to its pool (and possibly missing some other transformation because of that). --LPfi (talk) 11:29, 11 May 2009 (UTC)

 * Not "probably"; it's just wrong.
 * /dev/random and /dev/urandom share a pool of entropy, which is fed with supposedly-random bits from external events. Each time data is added to that pool, it is "stirred", i.e. its contents are scrambled. That pool is used to feed two further pools, one for urandom and one for random. These are also stirred when bits are added to them. So the two generators should never generate the same sequence; they do not share a seed.
 * Neither random nor urandom output bits from their respective pool; the contents of all the pools are supposed to be seriously secret. Rather the data in the respective pool is passed through a CSPRNG to generate random bits securely (and without exposing the contents of the pool). Each pool is thus used as a fancy sort of seed for the respective CSPRNG. Provided the pool is never exposed, the two CSPRNGs can go on generating unpredictable random bits until the heat-death of the Universe.
 * The "quality" of the numbers generated by these two processes is exactly the same; but /dev/random will block when it thinks it has "used up" all its entropy, while /dev/urandom will carry on outputting bits. It doesn't switch to a new, lower-quality CSPRNG; it just carries on the same as before, using the same seed, as if nothing has changed (and in reality, nothing significant has changed).
 * So the reason for adding new random bits to these pools is to mitigate the risk of the pool being exposed (or known in advance). It is falsely claimed in the documentation for urandom that its use "depletes the entropy pool". It is theoretically possible to reverse-engineer the pool contents given a sufficiently-long stream of bits from the output of [x]random; that is, given enough output, and a method for reversing a secure hash given its output, one could determine the contents of the pool. in practice, for pools the size of those used in these generators, that would require ridiculous amounts of time, given even very conservative assumptions (of the order of billions of billions of times the age of the Universe, using theoretically-optimal computing equipment, and consuming gigantic amounts of power, like the entire output of a star). Seriously, it can't be done.
 * So the threat is not "depletion of entropy"; it's that someone gains root on your computer, and inspects the contents of your pool. Or more seriously, that your computer is at an early stage of booting, and (a)no external random events have yet been detected, and (b) it has not been possible to  initialise your pool using data from a previous session (perhaps you have no persistent storage; perhaps this is the first time it has booted). These are both real and serious risks. But they are not caused by depletion of entropy.
 * Urandom does not use the same pool as random, except indirectly; they both refill their respective pool from the shared pool. Neither will ever output the same bits that one could have got from the other, had one read the other instead.
 * Some people believe that, after drawing some number of bits from urandom equal to the size of its pool, the output of that RNG can no longer be relied on as "random", because all of the true randomness has sort-of been drained away. That is nonsense, and exposes a serious misunderstanding of how a CSPRNG works and what it does.
 * I'm sorry if I seem grumpy; I have been trying all day to find the source of the belief that a CSPRNG that is seeded with random data can have its entropy depleted. I have found no plausible arguments that this is the case. I have seen it asserted quite a lot; and I have read a small number of articles that convincingly debunk it. The idea seems to come from the man page for /dev/urandom in Linux (and some people claim that this belief arose in Linux circles). I have the greatest respect for the person I believe authored that page, and I don't believe he writes nonsense about this kind of thing; and that is why I have been looking for another source.
 * Note that the term "entropy", in this context, means something different from the entropy of James Maxwell, or the entropy of quantum mechanics. It means, roughly, "unpredictable data". That is, whether some data is entropy or not, depends on the context. If your adversary can't predict it, you can consider it entropy and use it to seed random functions (that's right - whether it counts as entropy or not also depends on who your adversary is). The arrival-time of hardware interrupts might be entropy, for these purposes; but if your adversary can, using a super-accurate timer, measure the arrival-times of your keystrokes, then they stop being entropy; they become just data that is useless for seeding RNGs.

 * I would like to "weave" this information into the article; but I don't know how to proceed. Most information on the web about this subject is misleading or wrong (including the man page of /dev/urandom). There's very little stuff about this that isn't web articles; we're talking about software that wasn't invented until the late 90s. And even places where experts discuss this kind of thing are full of misleading nonsense. I can collect some sources, but none of them is going to be a newspaper of record, or a book published by a respectable publisher, or anything like that; at best they'll be blogs, or less satisfyingly comments to threads on Hacker News or the Linux Kernel mailing list.
 * Incidentally, it's not that hard to find people who would like to see /dev/random abolished, because it serves no purpose, and only causes confusion and pain. The reason seems to be backward compatibility, and because this code is part of the Linux kernel, and because there is a religious belief that kernel changes must never "break userland".
 * So I've put it here. If you can find really good sources (good enough to blow away the nonsense), please add them here, or in the article. MrDemeanour (talk) 19:40, 3 October 2019 (UTC)

Python Code
f=open('/dev/random', 'r') print repr(f.read(10)) '\xb6.\x06\xd4\x93\x8d\r\x86\x19W'

I am not sure how to parse this. Looks like there are Unicode characters (prefixed with \) and Ascii characters with the forward slash...

To get random letters from /dev/random, you would likely try code like this: f=open('/dev/random', 'rb') charset='abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890' print ''.join([charset[ord(i)%len(charset)] for i in f.read(100)]) f.close This generates 10 random characters in [a-zA-Z0-9]. There is a slight bias that must be noted: due to the limited range of a byte, the letters appearing earlier in the string will appear slightly more frequently than those appearing last. nneonneo 19:07, 30 January 2006 (UTC)
 * /dev/[u]random generate bytes in the entire possible range (0x00 - 0xFF). Thus, there isn't any particular pattern, the bytes are meant to be used in a crypto ky, for example.
 * 1) Run me using sudo on most systems!

 * 2.25 1.25
 * 2.36 5.23
 * 9.26 25.2
 * 30.25 5.22
 * 1.1 2.30 41.36.4.129 (talk) 04:37, 29 January 2023 (UTC)

Others uses of /dev/random and /dev/urandom

 * /dev/urandom can be used to test a sound card,headphones...

cat /dev/urandom > /dev/dsp

Other operating systems
Maybe there are others, but for certain there's NoiseSYS - a device driver which runs under DOS and provides RANDOM and URANDOM (RANDOM$ and URANDOM$ in later versions) which do the same. As DOS allows device names to be preceeded by /DEV the /DEV/RANDOM is a fully possible solution under DOS. maybe that should be mentioned?

UNIX systems?
Is /dev/random a typical device of a UNIX system? I thought that this was introduced with the Linux kernel and adopted by OpenBSD/FreeBSD a bit later and by Solaris a lot later. Anybody has knowledge on that? -Anonymous
 * Sure. Theodore Ts'o <tytso@mit.edu> (pronounced "Cho", with a long O sound) wrote it for Linux. FreeBSD cloned it, badly, failing to do the entropy accounting that is so critical to preventing undiscovered hash/cipher weaknesses from affecting the randomness quality. Solaris is indeed recent. MacOS X has a /dev/random too. 24.110.60.225 03:17, 5 July 2006 (UTC)
 * MacOS X uses the FreeBSD Yarrow implementation -Anonymous
 * Wait, I thought it was part of AT&T UNIX? 71.81.37.151 05:47, 21 November 2006 (UTC)
 * If MacOS X uses the Yarrow thing, I think the article should say so (as it does for FreeBSD). Karadoc** (talk) 06:50, 28 January 2008 (UTC)
 * +1 (I agree) for the MAIN article to include a new section *before* Linux called "Unix," or "*nix." Currently (top to bottom), the WIKI sections are Linux, then FreeBSD, then OpenBSD, then "macOS and iOS," and lastly, "Other operating systems." I believe *nix supersedes all other listings for /dev/[u]random - no? By the way, I am having the craziest hardest time finding a good source on the web detailing the history, evolution, invention process for /dev/random - can anyone kindly help me out please? Thanks in advance! Vid2vid (talk) 04:46, 23 May 2019 (UTC)
 * Not unless some other UN*X had it before Linux. Otherwise, well, no.
 * As of System V Release 4.2, there's no sign of a /dev/random in any UNIX from AT&T, so it doesn't appear to be "part of AT&T UNIX". There's no sign of it in the most recent version of the Single UNIX Standard, so it's not part of "UNIX" in that sense, either. Guy Harris (talk) 07:27, 23 May 2019 (UTC)

Did you say "true random number generator" ?
How an algorithm could be "truely" random without any external source such as the decay of an isotope ? The quality of /dev/random output can't be truely random, indistinguishable from random maybe but truely random it's not. —Preceding unsigned comment added by 83.115.108.91 (talk) 08:14, 28 March 2008 (UTC)

 * I know it's been a long time since the posting of this question, but I hate to leave an unanswered question on the page. Hardware random number generator states that the noise is generated from quantum phenomena, such as thermal noise or the photoelectric effect, which are truly random.  This noise is gathered into the entropy pool that /dev/random uses.  So why could it NOT be truly random, if the sources it retrieves from are?  I can agree that /dev/urandom (the unlocked source) could potentially be less truly random, but /dev/random is by far well enough for high-security purposes. PseudoOne (talk) 21:02, 21 January 2009 (UTC)

The Billion bit test has found multiple uniformity flaws in a number of /dev/random implementations. In fact, I have never found a /dev/random implementation that did not suffer from at least one uniformity flaw, except maybe those /dev/random implementations that bypassed the standard /dev/random driver code and directly accessed a Cryptographically sound hardware source. ( BTW: The sited page lists observed flaws in the FreeBSD 5.2.1, Solaris 8 patch 108528-18, Linux 2.4.21-20, OS X 10.3.5 implementations of /dev/random. Not listed are a numer of more recent tests under RedHat Linux, OS X, FreeBSD, etc.)

Based on my testing experience, I would hesitate to call /dev/random a Cryptographically secure pseudorandom number generator. The output appears to be statistically distinguishable from a true random source. chongo (talk) 03:48, 3 July 2009 (UTC)

I don't think the reference you cite (for your claim that no /dev/random implementation is cryptographically strong) is credible. I'm a cryptographer, and I think that page has misunderstood randomness testing. In my view, that page is not from a credible source, it is not verifiable, it has not been replicated. It is making an extraordinary claim, and extraordinary claims require stronger substantiation than that. The claims that /dev/random is flawed should be deleted from the Wikipedia article: they are not credible. (21:14, 29 July 2010 (UTC)) —Preceding unsigned comment added by 128.32.153.194 (talk)

/dev/urandom not used for cryptographically secure random number generation
As of Feb, 03, 2011 the article has a sentence: "This means that the call will not block, but the output may contain less entropy than the corresponding read from /dev/random. Thus, it may not be used as a cryptographically secure pseudorandom number generator, but it may be suitable for less secure applications."

The first sentence is true. The entropy of say a 1000 digit number taken from /dev/random will contain more entropy than a 1000 digit number taken from /dev/urandom. However, this does not imply that /dev/urandom is not appropriate for use in cryptography. So long as the internal state maintained by /dev/urandom contains more bits than the keys, nonces, etc. generated, it is perfectly suitable for use as a cryptographically secure random number generator.

Consider that Java's SecureRandom number generator is implemented to seed itself from /dev/urandom: http://www.java2s.com/Open-Source/Java-Document/6.0-JDK-Platform/solaris/sun/security/provider/NativePRNG.java.htm Then read the documentation for the SecureRandom class: http://download.oracle.com/javase/1.4.2/docs/api/java/security/SecureRandom.html which clearly states: "This class provides a cryptographically strong pseudo-random number generator (PRNG)."

If /dev/urandom were not a valid cryptographically secure psuedorandom number generator, then it would not be used as the basis for the the SecureRandom implementation. Many applications use /dev/urandom to obtain seed material, keys, nonces, etc. 67.129.215.3 (talk) 22:54, 3 February 2011 (UTC)

 * No, if it does not contain sufficient entropy there is a chance of a distinguishing attack. That it may still provide the basis for a cryptographically secure pseudorandom generator such as SecureRandom does not mean that it is cryptographically secure "as is". What is required though is a suitable randomness extractor to extract the entropy into a uniformly distributed value. The statement that /dev/urandom may not be suitable for cryptographic purposes is directly from the man page. Nageh (talk) 23:00, 3 February 2011 (UTC)

 * I don't see that sentence anywhere in the man page, in fact it says: "If you are unsure about whether you should use /dev/random or /dev/urandom, then probably you want to use the latter. As a general rule, /dev/urandom should be used for everything except long-lived GPG/SSL/SSH keys."  The man page is plainly advocating using /dev/urandom for all other cryptographic purposes. 67.129.215.3 (talk) 16:36, 4 February 2011 (UTC)

 * Huh? Did you click on the link I provided to you? I quote:
 * "A read from the /dev/urandom device will not block waiting for more entropy. As a result, if there is not sufficient entropy in the entropy pool, the returned values are theoretically vulnerable to a cryptographic attack on the algorithms used by the driver. Knowledge of how to do this is not available in the current unclassified literature, but it is theoretically possible that such an attack may exist. If this is a concern in your application, use /dev/random instead."
 * Nageh (talk) 16:41, 4 February 2011 (UTC)

 * The man page is very confusing here, and honestly, something just is not right there. I don't know how /dev/urandom is implemented internally but I have changed the article accordingly. The statement that /dev/urandom is suitable as a CSPRG is worrisome as there may be efficient distinguishing attacks when the pool's entropy is very low. In a way, the man page is contradicting itself. Also see the analysis by Noll, who found flaws even in the uniform distribution of /dev/random, which means that neither /dev/urandom nor /dev/random are CSPRGs by the actual definition. Nageh (talk) 17:12, 4 February 2011 (UTC)

 * Note that nowhere in that sentence does it say /dev/urandom is not cryptographically secure. What it says is that if there are breaks in the algorithm underlying the pseudorandom generations (Which may be AES, SHA-256, etc.) then it may be feasible to distinguish the output of /dev/urandom from a random source.  Currently this is in theory possible but requires exponential time to do so.  Look at the definition for Cryptographically_secure_pseudorandom_number_generator.  Is this the same definition used in this article?  To me it seems to differ from the overly strict perfect randomness which this article seems to suggest is meant by cryptographically secure.  See: http://www.lavarnd.org/faq/crypto_strong.html  A source doesn't have to be perfectly random to be suitable for cryptographic purposes.  Note that even the best and most robust RNG's fail some tests some of the time: http://www.lavarnd.org/what/nist-test.html 67.129.215.3 (talk) 20:43, 4 February 2011 (UTC)
 * Let me clarify. First, it is obvious that if some cryptographic primitive used is breakable then so is the PRG built on it. Second, any primitive is breakable in exponential time because that refers to a brute-force complexity. Third, there is a precise definition for what it means for a PRG to be CS. It says that for a certain input key size (the seed) the CSPRG is indistinguishable from a truly random sequence in polynomial complexity assuming that the key has been selected uniformly at random. How can you create a seed of uniform distribution from an entropy source that is biased? Right, you attempt to measure the entropy in given data and extract it into a seed that is close to uniform distribution. So assuming the internal CSPRG is secure and the randomness extractor is secure the overall /dev/random is secure as well (i.e., a CSPRG). Now what happens when you don't get a uniform distribution for the seed because of insufficient entropy? In this case you have one more assumption in stating that /dev/urandom is a CSPRG. But an algorithm can only be a CSPRG as long as no polynomial-time distinguishing attack exists. And that was my initial concern since the man page warns against the use of /dev/urandom for some applications. Sorry, but if you don't have the highest trust in your design you cannot call it a CSPRG. That is best practice, btw: see the Handbook of Applied Cryptography, which explicitly discards certain hash-based PRG designs as being CS. Anyway, I think the current wording in the article is quite spot on (as you seem to agree below). Nageh (talk) 21:53, 4 February 2011 (UTC)
 * I think your changes look good 67.129.215.3 (talk) 21:11, 4 February 2011 (UTC)

Probably you should check http://www.2uo.de/myths-about-urandom/ — Preceding unsigned comment added by 138.4.128.32 (talk) 16:12, 29 March 2016 (UTC)

Writing to /dev/random
(In Linux), who says that you can add entropy by writing to /dev/random? I don't see this in any of the Linux man pages. — Preceding unsigned comment added by 17.209.4.116 (talk) 19:54, 13 July 2011 (UTC)

Citation for usage of device driver noise
In response to the opening paragraph needing a citation:

"It allows access to environmental noise collected from device drivers and other sources.[citation needed] "

It can be found here: http://www.kernel.org/doc/man-pages/online/pages/man4/random.4.html#DESCRIPTION — Preceding unsigned comment added by 66.76.35.131 (talk) 19:41, 31 July 2012 (UTC)

Size of the pool
Is there a standard pool size ? If not what is it dependent of ? --Martvefun (talk) 09:00, 10 August 2012 (UTC)

 * This page isn't for questions and answers, but see http://www.kernel.org/doc/man-pages/online/pages/man4/random.4.html

 * That's for Linux kernels and indicates that, for Kernel 2.6, the entropy pool size is 4096 bits. For other Unix-like systems this may be different. For instance on OpenBSD the entropy pool is 2048 words (16384 bits). Needless to say increasing the size of the entropy pool doesn't automatically create more entropy if none is available. --TS 18:48, 10 August 2012 (UTC)

Cross-article contradiction
The /dev/random article asserts that, /dev/random is suitable for generating one-time pads or keys. But, the one-time pad article asserts the opposite. The /dev/random article has a citation while the one-time pad article does not. Also, the citation link given is broken, so I can not establish the credibility of these statements one way or the other. I have come across come across the link: http://www.kernel.org/doc/man-pages/online/pages/man4/random.4.html#DESCRIPTION, but it only claims that "/dev/random should be suitable for uses that need very high quality randomness such as one-time pad or key generation". The article in question does not provide any references to assert this claim. How should this be approached? Lyle Stephan (talk) 18:41, 5 November 2012 (UTC)
 * Be careful. There is a loose and a strict interpretation of a "one-time pad". In the strict interpretation, you need a truly random stream to encipher your data. In the loose interpretation, your stream may be pseudo-random, something what a stream cipher implements. In explanation, only a truly random key stream can provide you information-theoretic (perfect) secrecy, whereas a pseudo-random stream (such as provided by /dev/random) provides you computational security. The common principle is that you may use the key stream only once. Nageh (talk) 18:54, 5 November 2012 (UTC)
 * I need to slightly correct myself. /dev/random is meant to provide close-to-truly random output data. The extent to which it is random (in an information-theoretic sense) is debatable, but it does not provide "true" randomness. Nageh (talk) 20:37, 5 November 2012 (UTC)
 * I agree with you. I will try and find a source that will allow us to include the caveat that you mentioned. That should resolve it Lyle Stephan (talk) 15:50, 6 November 2012 (UTC)

Update needed
" They indicated that none of these /dev/random implementations were cryptographically secure because their outputs had uniformity flaws." The reference is dated from 8 years ago.I wonder if the flow still exists(They may be fixed now) in particular for linux Thanks.Ytrezq (talk) 19:59, 28 February 2013 (UTC)

Citation needed for OpenBSD arc4 section
Citation needed for OpenBSD arc4 section. IMHO, much of this article seems outdated or inaccurate. For example, I searched the OpenBSD mailing list, and I couldn't find any cited reference to the reason for the rc4 to arc4 rename. — Preceding unsigned comment added by Zacts (talk • contribs) 20:34, 13 May 2013 (UTC)
 * References adjusted. If somebody wants to update the whole section (e.g. correct use of present and past tense), here are the conference slides to look at: "arc4random - 1997 to present" --2001:638:401:102:250:56FF:FEB2:39C6 (talk) 07:43, 7 August 2015 (UTC)

Removed Weaknesses section
I removed the "Weaknesses" section. It was added by User:Landon Curt Noll, who also owns the website cited as a source. Seems to be WP:OR and cites a non-WP:RELY source, besides looking suspiciously like an advertisement (and probably being wrong). Manish Earth Talk • Stalk 22:19, 13 August 2013 (UTC)

Add /dev/urandom article
http://www.2uo.de/myths-about-urandom/ seems to be relevant, maybe add it? — Preceding unsigned comment added by 217.237.185.168 (talk) 07:28, 10 March 2014 (UTC)

Kroah-Hartmann and Torvalds seem to agree: https://plus.google.com/111049168280159033135/posts/AJkqHReK9x9 — Preceding unsigned comment added by 176.198.227.115 (talk) 21:17, 10 March 2014 (UTC)

FreeBSD switching from Yarrow to Fortuna
See https://svnweb.freebsd.org/base?view=revision&revision=273872; the relevant chapter of "Cryptography Engineering" can be downloaded for free from the author's site (https://www.schneier.com/fortuna.html) — Preceding unsigned comment added by 79.6.154.127 (talk) 15:01, 5 November 2014 (UTC)

Introduction/Definition
In Unix-like operating systems, /dev/random is a special file that serves as a blocking pseudorandom number generator. It allows access to environmental noise collected from device drivers and other sources. Not all operating systems implement the same semantics for /dev/random.

I think this introduction and definition flawed out of multiple reasons:
 * It defines "/dev/random" as "blocking" on "Unix-like OS"
 * The citation is flawed for multiple reasons, too.

Ad (1): The article lists how /dev/random is handled on multiple (mainly Unix-like) Operating Systems. Seems in the majority of those /dev/random does not block indeed. A blocking /dev/random seams to be mainly a Linux characteristic -- which is okay as Linux (namely Ted T'so) "invented" it. But that should be stated explicitly, or the "blocking" characteristic should be removed.

Ad (2): The reference is Torvalds, Linus (2005-04-16). "Linux Kernel drivers/char/random.c comment documentation @ 1da177e4". On the one hand, the contents of the introduction of Linux random.c does not refer to "Unix-like Operating Systems", but to Linux specifically. On the other hand, the cited commit is not the one that created the text, but the one with which Linus /imported/ the file (among many others) from the previous repository into the "new" GIT one. Commit message: Initial git repository build. I'm not bothering with the full history, even though we have it. [..]" So Linus himself is probably /not/ the author. --2001:638:401:102:250:56FF:FEB2:39C6 (talk) 08:32, 30 July 2015 (UTC)

/dev/urandom is what you want to use for long-term cryptographic keys
"While it is still intended as a pseudorandom number generator suitable for most cryptographic purposes, it is not recommended for the generation of long-term cryptographic keys."

This sentence needs to be expunged. It's misleading and based on complete bullshit.

http://sockpuppet.org/blog/2014/02/25/safely-generate-random-numbers/

http://blog.cr.yp.to/20140205-entropy.html

Kobra (talk) 14:27, 29 September 2015 (UTC)

 * The good news is that Linux also agrees and decided to change; the article is also fixed. The bad news is that the "complete bullshit" in the manual page has not been fixed. It's partly my fault: I sent a patch but got bored by the small code review requests. My manpage-writing computer holding a clone of the linux-man-pages git repo is also in a cold room; turning on the heat is a lot of bother. Artoria2e5 🌉 05:30, 6 February 2024 (UTC)
 * I think something was changed about entropy_avail too -- there used to be something that tracks "spent entropy", which of course is silly. It's not in my proposed revision of the manual, so some more source-reading is required to hunt that down. --Artoria2e5 🌉 05:47, 6 February 2024 (UTC)

macOS No Longer Uses Yarrow
I am not an expert in these matters, but I read that macOS no longer uses Yarrow. According to this post from /r/crypto, Craig Federighi said they now use CoreCrypto and, "The NDRNG feeds entropy from the pool into the DRBG on demand. The NDRNG provides 256-bits of entropy." He also provides a link to the official Apple documenation.

I don't know enough about this topic to properly edit the macOS section of this page. I'm providing this info so someone who knows more than me can update it.

Auctoris (talk) 21:16, 23 November 2019 (UTC)

Update needed
Linux kernel 5.4.53 mixes the CPU hardware random number generator with its entropy pool using exclusive-or. I don't know when this change was introduced into

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c

Must have been after this article arose (2017?). /drivers/char/hw_random contains hardware random number drivers for Intel, AMD, Atmel, Broadcom, Niagra2(Sparc), Via, OMAP, Octeon, VirtIO, Freescale, among others.

Assumptions based upon software deterministic random number generators must be updated. /dev/random is no longer correctly described in this article. XOR-ing non-deterministic ring-oscillator noise sources with timer-based entropy obsoletes this article's software-based random number focus.

Hpfeil (talk) 19:28, 23 July 2020 (UTC)

AKJK-Android-DATA
depicts depicted entity (see also P921: main subject) depiction of painting of  motif  portrait of  landscape of represents  portrays  subject depicting  pictures Crtn32002 (talk) 15:07, 25 March 2021 (UTC)

Confusing Lead
A Wikipedia lead section should be accessible to as broad an audience as possible. As a user of random number generators, I was intrigued to find out more about how Linux handles them, but as I am not an expert in computer science, I was very confused by the terminology used in the lead. This is the first time I've come across 'blocking' and 'entropy' used in such a context. Would it be possible to come up with a more accessible lead and leave such terminology for the main text?

Also, I suggest not starting the main text with an example. That would make more sense further down the page. AstroMark (talk) 09:37, 7 February 2022 (UTC)

title: Talk:/dev/random


text:
User talk:Noraaron

It appears you haven't edited any Wikipedia articles since 28 Aug 2004, when you created "Adenolisianthus" and "Aripuana". If you happen to read this nevertheless, please know that we've received a complaint from Lena Struwe of the Gentian Research Network, indicating that this content was copied from her site without permission. As a result, it is currently proposed that we delete those articles as copyright violations. In the future, please be careful to respect other people's rights and do not add copyrighted material without permission. --Michael Snow 23:28, 27 Sep 2004 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:Noraaron


text:
Eridanus (constellation)

Eridanus is a constellation in the southern celestial hemisphere. It is represented as a river. One of the 48 constellations listed by the 2nd century astronomer Ptolemy, it remains one of the 88 modern constellations. It is the sixth largest of the modern constellations, and the one that extends farthest in the sky from north to south. The same name was later taken as a Latin name for the real Po River and also for the name of a minor river in Athens.

Stars
At its southern end is the magnitude 0.5 star Achernar, designated Alpha Eridani. It is a blue-white hued main sequence star 144 light-years from Earth, whose traditional name means "the river's end". Achernar is a very peculiar star because it is one of the flattest stars known. Observations indicate that its radius is about 50% larger at the equator than at the poles. This distortion occurs because the star is spinning extremely rapidly.

There are several other noteworthy stars in Eridanus, including some double stars. Beta Eridani, traditionally called Cursa, is a blue-white star of magnitude 2.8, 89 light-years from Earth. Its place to the south of Orion's foot gives it its name, which means "the footstool". Theta Eridani, called Acamar, is a binary star with blue-white components, distinguishable in small amateur telescopes and 161 light-years from Earth. The primary is of magnitude 3.2 and the secondary is of magnitude 4.3. 32 Eridani is a binary star 290 light-years from Earth. The primary is a yellow-hued star of magnitude 4.8 and the secondary is a blue-green star of magnitude 6.1. 32 Eridani is visible in small amateur telescopes. 39 Eridani is a binary star also divisible in small amateur telescopes, 206 light-years from Earth. The primary is an orange-hued giant star of magnitude 4.9 and the secondary is of magnitude 8. 40 Eridani is a triple star system consisting of an orange main-sequence star, a white dwarf, and a red dwarf. The orange main-sequence star is the primary of magnitude 4.4, and the white secondary of magnitude 9.5 is the most easily visible white dwarf. The red dwarf, of magnitude 11, orbits the white dwarf every 250 years. The 40 Eridani system is 16 light-years from Earth. p Eridani is a binary star with two orange components, 27 light-years from Earth. The magnitude 5.8 primary and 5.9 secondary have an orbital period of 500 years.

Epsilon Eridani (the proper name is Ran ) is a star with one extrasolar planet similar to Jupiter. It is an orange-hued main-sequence star of magnitude 3.7, 10.5 light-years from Earth. Its one planet, with an approximate mass of one Jupiter mass, has a period of 7 years.

Supervoid
The Eridanus Supervoid is a large supervoid (an area of the universe devoid of galaxies) discovered. At a diameter of about one billion light years it is the second largest known void, superseded only by the Giant Void in Canes Venatici. It was discovered by linking a "cold spot" in the cosmic microwave background to an absence of radio galaxies in data of the United States National Radio Astronomy Observatory's Very Large Array Sky Survey. There is some speculation that the void may be due to quantum entanglement between our universe and another.

Deep-sky objects
NGC 1535 is a small blue-gray planetary nebula visible in small amateur telescopes, with a disk visible in large amateur instruments. 2000 light-years away, it is of the 9th magnitude.

A portion of the Orion Molecular Cloud Complex can be found in the far northeastern section of Eridanus. IC 2118 is a faint reflection nebula believed to be an ancient supernova remnant or gas cloud illuminated by nearby supergiant star Rigel in Orion.

Eridanus contains the galaxies NGC 1232, NGC 1234, NGC 1291 and NGC 1300, a grand design barred spiral galaxy.

NGC 1300 is a face-on barred spiral galaxy located 61 (plus or minus 8) million light-years away. The center of the bar shows an unusual structure: within the overall spiral structure, a grand design spiral that is 3,300 light-years in diameter exists. Its spiral arms are tightly wound.

Meteor showers
The Nu Eridanids, a recently discovered meteor shower, radiate from the constellation between August 30 and September 12 every year; the shower's parent body is an unidentified Oort cloud object. Another meteor shower in Eridanus is the Omicron Eridanids, which peak between November 1 and 10.

Visualizations
Eridanus is depicted in ancient sky charts as a flowing river, starting from Orion and flowing in a meandering fashion past Cetus and Fornax and into the southern hemispheric stars. Johann Bayer's Uranometria depicts the river constellation as a flowing river.

History and mythology
According to one theory, the Greek constellation takes its name from the Babylonian constellation known as the Star of Eridu (MUL.NUN.KI). Eridu was an ancient city in the extreme south of Babylonia; situated in the marshy regions it was held sacred to the god Enki-Ea who ruled the cosmic domain of the Abyss - a mythical conception of the fresh-water reservoir below the Earth's surface.

Eridanus is connected to the myth of Phaethon, who took over the reins of his father Helios' sky chariot (i.e., the Sun), but didn't have the strength to control it and so veered wildly in different directions, scorching both Earth and heaven. Zeus intervened by striking Phaethon dead with a thunderbolt and casting him to Earth. The constellation was supposed to be the path Phaethon drove along; in later times, it was considered a path of souls. Since Eridanos was also a Greek name for the Po (Latin Padus), in which the burning body of Phaethon is said by Ovid to have extinguished, the mythic geography of the celestial and earthly Eridanus is complex.

Another association with Eridanus is a series of rivers all around the world. First conflated with the Nile River in Egypt, the constellation was also identified with the Po River in Italy. The stars of the modern constellation Fornax were formerly a part of Eridanus.

Equivalents
The stars that correspond to Eridanus are also depicted as a river in Indian astronomy starting close to the head of Orion just below Auriga. Eridanus is called Srotaswini in Sanskrit, srótas meaning the course of a river or stream. Specifically, it is depicted as the Ganges on the head of Dakshinamoorthy or Nataraja, a Hindu incarnation of Shiva. Dakshinamoorthy himself is represented by the constellation Orion.

The stars that correspond to Eridanus cannot be fully seen from China. In Chinese astronomy, the northern part is located within the White Tiger of the West (西方白虎, Xī Fāng Bái Hǔ). The unseen southern part was classified among the Southern Asterisms (近南極星區, Jìnnánjíxīngōu) by Xu Guangqi, based on knowledge of western star charts.

Namesakes
USS Eridanus (AK-92) was a United States Navy Crater-class cargo ship named after the constellation.

title: Eridanus (constellation)


text:
Elastance

Electrical elastance is the reciprocal of capacitance. The SI unit of elastance is the inverse farad (F−1). The concept is not widely used by electrical and electronic engineers. The value of capacitors is invariably specified in units of capacitance rather than inverse capacitance. However, it is used in theoretical work in network analysis and has some niche applications at microwave frequencies.

The term elastance was coined by Oliver Heaviside through the analogy of a capacitor as a spring. The term is also used for analogous quantities in some other energy domains. It maps to stiffness in the mechanical domain, and is the inverse of compliance in the fluid flow domain, especially in physiology. It is also the name of the generalised quantity in bond-graph analysis and other schemes analysing systems across multiple domains.

Usage
The definition of capacitance (C) is the charge (Q) stored per unit voltage (V).

$$ C = {Q \over V}$$

Elastance (S) is the reciprocal of capacitance, thus,

$$ S = {V \over Q} \. $$

Expressing the values of capacitors as elastance is not done much by practical electrical engineers, although it is sometimes convenient for capacitors in series. The total elastance is simply the sum of the individual elastances in that case. However, it is used by network theorists in their analysis. One advantage is that an increase in elastance increases impedance. This is in the same direction as the other two basic passive elements, resistance and inductance. An example of the use of elastance can be found in the 1926 doctoral thesis of Wilhelm Cauer. On his path to founding network synthesis, he formed the loop matrix A,

$$\mathbf{A}= s^2 \mathbf{L} + s \mathbf{R} + \mathbf{S} = s \mathbf{Z}$$

where L, R, S and Z are the network loop matrices of inductance, resistance, elastance and impedance respectively and s is complex frequency. This expression would be significantly more complicated if Cauer had tried to use a matrix of capacitances instead of elastances. The use of elastance here is merely for mathematical convenience, in much the same way as mathematicians use radians rather than the more common units for angles.

Elastance is also used in microwave engineering. In this field varactor diodes are used as a voltage variable capacitor in frequency multipliers, parametric amplifiers and variable filters. These diodes store a charge in their junction when reverse biased which is the source of the capacitor effect. The slope of the voltage-stored charge curve is called differential elastance in this field.

Units
The SI unit of elastance is the reciprocal farad (F−1). The term daraf is sometimes used for this unit, but it is not approved by SI and its use is discouraged. The term is formed by writing farad backwards, in much the same way as the unit mho (unit of conductance, also not approved by SI) is formed by writing ohm backwards.

The term daraf was coined by Arthur E. Kennelly. He used it from at least 1920.

History
The terms elastance and elastivity were coined by Oliver Heaviside in 1886. Heaviside coined a great many of the terms used in circuit analysis today, such as impedance, inductance, admittance, and conductance. Heaviside's terminology followed the model of resistance and resistivity with the -ance ending used for extensive properties and the -ivity ending used for intensive properties. The extensive properties are used in circuit analysis (they are the "values" of components) and the intensive properties are used in field analysis. Heaviside's nomenclature was designed to highlight the connection between corresponding quantities in field and circuit. Elastivity is the intensive property of a material corresponding to the bulk property of a component, elastance. It is the reciprocal of permittivity. As Heaviside put it, "Permittivity gives rise to permittance, and elastivity to elastance." Here, permittance is Heaviside's term for capacitance. He did not like any term that suggested that a capacitor was a container for holding charge. He rejected the terms capacity (capacitance) and capacious (capacitive) and their inverses incapacity and incapacious. The terms current in his time for a capacitor were condenser (suggesting that the "electric fluid" could be condensed out) and leyden after the Leyden jar, an early form of capacitor, also suggesting some sort of storage. Heaviside preferred the analogy of a mechanical spring under compression, hence his preference for terms that suggested a property of a spring. This preference was a result of Heaviside following James Clerk Maxwell's view of electric current, or at least, Heaviside's interpretation of it. In this view, electric current is a flow caused by the electromotive force and is the analogue of velocity caused by a mechanical force. At the capacitor, this current causes a "displacement" whose rate of change is equal to the current. The displacement is viewed as an electric strain, like a mechanical strain in a compressed spring. The existence of a flow of physical charge is denied, as is the buildup of charge on the capacitor plates. This is replaced with the concept of divergence of the displacement field at the plates, which is numerically equal to the charge collected on the plates in the charge flow view.

For a period in the nineteenth and early-twentieth centuries, some authors followed Heaviside in the use of elastance and elastivity. Today, the reciprocal quantities capacitance and permittivity are almost universally preferred by electrical engineers. However, elastance does still see some usage by theoretical writers. A further consideration in Heaviside's choice of these terms was a wish to distinguish them from mechanical terms. Thus, he chose elastivity rather than elasticity. This avoids having to write electrical elasticity to disambiguate it from mechanical elasticity.

Heaviside carefully chose his terms to be unique to electromagnetism, most especially avoiding commonality with mechanics. Ironically, many of his terms have subsequently been borrowed back into mechanics and other domains in order to name analogous properties. For instance, it is now necessary to distinguish electrical impedance from mechanical impedance in some contexts. Elastance has also been borrowed back into mechanics for the analogous quantity by some authors, but often stiffness is the preferred term instead. However, elastance is widely used for the analogous property in the domain of fluid dynamics, especially in the fields of biomedicine and physiology.

Mechanical analogy
Mechanical–electrical analogies are formed by comparing the mathematical description of the two systems. Quantities that appear in the same place in equations of the same form are called analogues. There are two main reasons for forming such analogies. The first is to allow electrical phenomena to be explained in terms of the more familiar mechanical systems. For instance, an electrical inductor-capacitor-resistor circuit has differential equations of the same form as a mechanical mass-spring-damper system. In such cases the electrical domain is converted to the mechanical domain. The second, and more important, reason is to allow a system containing both mechanical and electrical parts to be analysed as a unified whole. This is of great benefit in the fields of mechatronics and robotics. In such cases the mechanical domain is most often converted to the electrical domain because network analysis in the electrical domain is highly developed.

The Maxwellian analogy
In the analogy developed by Maxwell, now known as the impedance analogy, voltage is made analogous to force. The voltage of a source of electric power is still called electromotive force for this reason. Current is analogous to velocity. The time derivative of distance (displacement) is equal to velocity and the time derivative of momentum is equal to force. Quantities in other energy domains that are in this same differential relationship are called respectively generalised displacement, generalised velocity, generalised momentum, and generalised force. In the electrical domain, it can be seen that the generalised displacement is charge, explaining the Maxwellians' use of the term displacement.

Since elastance is the ratio of voltage over charge, then it follows that the analogue of elastance in another energy domain is the ratio of a generalised force over a generalised displacement. Thus, an elastance can be defined in any energy domain. Elastance is used as the name of the generalised quantity in the formal analysis of systems with multiple energy domains, such as is done with bond graphs.

Other analogies
Maxwell's analogy is not the only way that analogies can be constructed between mechanical and electrical systems. There are any number of ways to do this. One very common system is the mobility analogy. In this analogy force maps to current instead of voltage. Electrical impedance no longer maps to mechanical impedance, and likewise, electrical elastance no longer maps to mechanical elastance.

title: Elastance


text:
Talk:Alert dialog box

''"Generically, an alert dialog is a notice to the user that the program cannot properly continue a function due to an error or incomplete requirements.

In its most common intended use, such an alert is presented to the user when the user has entered invalid information for one of the values in an input form. Some example of user input errors that might trigger an alert dialog are: entering a date that does not exist (e.g. "February 30"), using letters in a field that should represent a quantity (number), not providing a required value, or providing a value that is outside the range of the program's capabilities (such as from arithmetic overflow).

The typical alert dialog provides only one option; to close the window. Closing an alert dialog will provide access to the original screen, where the user can make changes to the input values to alleviate the dialog's warnings."''

This passage needs a rewrite, since it reflects poor program design practice. Presenting an alert to castigate the user for entering bad form data is a method of last resort; the fact that thousands of apps do it should not be presented as the right way to do it. I agree that alerts are to be used when an exception arises that means that normal operation cannot continue. But that isn't necessarily their primary purpose. They should be used to warn the user that the NEXT thing that's about to happen could be dangerous, and to give them a chance to back out. That to me is their primary purpose. Apart from exceptions, all other uses should be listed under abuses. Graham 23:33, 27 Sep 2004 (UTC)

title: Talk:Alert dialog box


text:
Gordon Rennie

Gordon Rennie is a Scottish comics writer, responsible for White Trash: Moronic Inferno, as well as several comic strips for 2000 AD and novels for Warhammer Fantasy.

In May 2008, he announced he was leaving comics to concentrate full-time on video games which "are more fun, pay better and have a brighter future". However, he has since written several new series for 2000 AD, Titan and others.

Biography
His first work was published in Blast! magazine in 1991, a metafictional Sherlock Holmes story called "Sherlock Holmes in the Curious Case of the Vanishing Villain", painted by Woodrow Phoenix. It also had appearances by characters from other Victorian fiction including Dr Jekyll and Mr Hyde and characters from stories by Edgar Allan Poe.

He included a completely different White Trash in the same issue - a satirical journey through the USA, drawn by the New Zealand artist Martin Emond. Both these stories were later collected into one-shot graphic novels and published by Tundra Publishing. Two further planned collaborations with Phoenix, a one-shot graphic novel called Orson Welles: Special Agent! and Necronauts, later completed with Frazer Irving, were halted when Tundra Press ceased publishing in 1993.

Rennie's first major series for the 2000 AD family was Missionary Man, which began in Judge Dredd Megazine vol.2 #29 (5/93) and ran between "the Meg" and 2000 AD for 74 episodes before finishing in 2002. Other original series include Witch World (1997) and Rain Dogs (2000). He also took over the exploits of the perennial Judge Dredd villain Mean Machine (2000–2001), as well as the return of the original Rogue Trooper (2002–2004).

His works for 2000 AD include the miniseries Necronauts (2000–2001), in which Harry Houdini, Arthur Conan Doyle, Charles Fort and H. P. Lovecraft team up to defeat an alien menace that seeks to destroy the human race. This was followed up by the series Caballistics, Inc., a story about a recently privatized team of occult researchers, which included a combination of pop-cultural references and labyrinthine conspiracies.

By 2004, Rennie had become a writer on the Judge Dredd strip, following up a number of subplots initiated by its principal author, John Wagner, as well as developing his own situations and guest characters, some of whom have spun off into stories of their own. While the lengthier Judge Dredd adventures are typically scripted by Wagner, Rennie was awarded one in 2005. This story, "Blood Trails", ran for ten episodes beginning in 2000 AD prog 1440 (5/25/05).

His contribution to the series of novels expanding miniature wargaming platforms Warhammer Fantasy, Warhammer 40,000 and Battlefleet Gothic include Zavant, Ulli and Marquand, the Kal Jerico stories, Bloodquest, Execution Hour and Shadow Point.

Rennie has worked on computer games and was nominated for the 2006 BAFTA for his script on the Rogue Trooper game as well as a nomination for the 2012 Writers' Guild of Great Britain's Best Videogame Script award along with co-scriptwriters Alan Barnes and Emma Beeby.

In May 2008, he was quoted as saying ,"I got fed up with comics and quit last month to concentrate on games." Although he later said he was misquoted, and that he has not completely given up comics, as he would still be writing an ongoing series for 2000 AD. At that time, Rennie was also planning a novel on the Romans in Scotland. He has since returned to 2000 AD to write the serials Aquila, Jaegir and Survival Geeks.

He also co-wrote The Doomsday Quatrain and sections of 1001 Nights with Emma Beeby for Big Finish Productions' Doctor Who main range of audio plays.

He is known for maintaining close links with the fan community, for example by contributing to small press comics such as Solar Wind, despite a public persona he describes as "a grumpy Scottish git".

Comics
Comics work includes:
 * "Sewer Patrol" (with Robin Smith, in Toxic! #31, 1991)
 * "Sherlock Holmes in the Curious Case of the Vanishing Villain" (with Woodrow Phoenix, in Blast!, 1991, Tundra, 1992)
 * White Trash (with Martin Emond, Tundra, 1992)

 * Missionary Man:
 * "Salvation at the Last Chance Saloon" (with Frank Quitely, in Judge Dredd Megazine #2.29, 1993)
 * "A Town Called Intolerance" (with Frank Quitely, in Judge Dredd Megazine #2.30, 1993)
 * "Legend of the Unholy Drinker" (with Garry Marshall, in Judge Dredd Megazine #2.43, 1993)
 * "Bad Moon Rising" (with Frank Quitely, in Judge Dredd Megazine #2.50-2.55, 1994)
 * "Season of the Witch" (with Garry Marshall, in Judge Dredd Megazine #2.56-2.57, 1994)
 * "Sanctuary" (with Sean Longcroft, in Judge Dredd Megazine #2.58-2.59, 1994)
 * "The Undertaker Cometh" (with Simon Davis, in Judge Dredd Mega-Special #7, 1994)
 * "Treasure of the Sierra Murder" (with Simon Davis, in Judge Dredd Megazine #2.63-2.66, 1994)
 * "Medicine Show" (with Jon Beeston, in Judge Dredd Megazine #2.81, 1995)
 * "Nightriders" (with Jamie Grant, in Judge Dredd Megazine #2.82-2.83, 1995)
 * "Mississippi Burning" (with Simon Davis, in Judge Dredd Megazine 3.01-3.03, 1995)
 * "Crusader" (with Charles Gillespie, in Judge Dredd Megazine #3.17, 1996)
 * "The Big Sleazy" (with Simon Davis, in Judge Dredd Megazine #3.18-3.20, 1996)
 * "The Shootist" (with Christian Bravery, in Judge Dredd Megazine #3.26-3.27, 1997)
 * "Juggernaut" (with Henry Flint, in Judge Dredd Megazine #3.34, 1997)
 * "Storm Warnings" (with Trevor Hairsine, in Judge Dredd Megazine #3.38, 1998)
 * "The Promised Land" (with Trevor Hairsine, in 2000 AD #1177, 2000)
 * "Missionary Man: Prologue" (with Simon Davis, in 2000 AD #1091, 1998)
 * "Mardi Gras" (with Alex Ronald, in 2000 AD #1092-1096, 1998)
 * "Goin' South" (with Alex Ronald, in 2000 AD #1118-1123, 1998)
 * "Apocrypha" (with Henry Flint, in 2000 AD #1124, 1998)
 * "The Promised Land" (with Alex Ronald (1-3, 8-9), Trevor Hairsine (4), Colin MacNeil (5-7), Simon Davis (10-12), and Dean Ormston (13-15), in 2000 AD #1174-1188, 2000)
 * "Mark of the Beast" (with Jesus Redondo, in 2000 AD #1201-1204, 2000)
 * "Silence" (with Wayne Reynolds, in Judge Dredd Megazine #3.77, 2001)
 * "Place of the Dead" (with John Ridgway, in Judge Dredd Megazine #4.9-4.13, 2002)

 * Judge Dredd:
 * "Do the Wrong Thing" (with Paul Peart, in Judge Dredd Megazine #2.49 1994)
 * "Lethal Response" (with Mike Perkins, in Judge Dredd Yearbook 1995, 1994)
 * "Get Me to the Church on Time" (with Pete Venters, in Judge Dredd Megazine #3.01, 1995)
 * "Zero Tolerance" (with Enric Rebollo, in Judge Dredd Megazine #3.31-3.32, 1997)
 * "Rest Stop" (with Chris Weston, in 2000 AD #1194, 2000)
 * "The Big Lie" (with Steve Parkhouse, in 2000 AD #1224, 2001)
 * "Sino-Town" (with PJ Holden, in 2000 AD #1233, 2001)
 * "Asylum" (with Frazer Irving, in Judge Dredd Megazine vol. 4 #5, 2001)
 * "Married with Juves" (with Adrian Bamforth, in 2000 AD #1262, 2001)
 * "Safe Hands" (with Jock, in 2000 AD #1273, 2002)
 * "A Right Royal Occasion" (with Peter Doherty, in 2000 AD #1293, 2002)
 * "Waiting" (with PJ Holden, in 2000 AD #1312, 2002)
 * "One of our simps is missing" (with Anthony Williams, in Judge Dredd Megazine #4.14, 2002)
 * "War Crimes" (with Lee Sullivan, in Judge Dredd Megazine #201, 2003)
 * "Sturm und Dang" (with Carlos Ezquerra, in Judge Dredd Megazine #211-212, 2003)
 * "Holding On" (with Ian Gibson, in 2000 AD #1357, 2003)
 * "Club Sov" (with Simon Fraser, in 2000 AD #1358, 2003)
 * "Bato Loco" (with Simon Coleby, in Judge Dredd Megazine #202, 2003)
 * "Meet the Flooks" (with PJ Holden, in 2000 AD #1359, 2003)
 * "See Zammy Run" (with Inaki Miranda, in 2000 AD #1360-1361, 2003)
 * "Gulag" (with Charlie Adlard, in 2000 AD #1382-1386, 2004)
 * "Last Respects" (with John McCrea, in 2000 AD #1389, 2004)
 * "Lazarus" (with Adrian Salmon, in Judge Dredd Megazine #217, 2004)
 * "Master Moves" (with D'Israeli, in Judge Dredd Megazine #217, 2004)
 * "(This is not a) Mega-City Love Story #1: Callista" (with Ben Willsher, in 2000 AD #1423, 2004)
 * "The Magnificent Umbersons" (with PJ Holden, in Judge Dredd Megazine #235, 2005)
 * "Visiting Hour" (with Anthony Williams, in 2000 AD #1423, 2005)
 * "The Searchers" (with Carl Critchlow, in 2000 AD #1424, 2005)
 * "Missing in action" (with Ian Gibson, in 2000 AD #1429-1431, 2005)
 * "Descent" (with Boo Cook, 2000 AD #1432-1436, 2005)
 * "Radstock" (with Karl Richardson, in 2000 AD #1437-1439, 2005)
 * "Blood Trails" (with Andrew Currie, in 2000 AD #1440-1449, 2005)
 * "Matters Of Life And Death" (with Carlos Ezquerra, in 2000 AD #1452, 2005)
 * "Burned Out" (with Carl Critchlow, in 2000 AD #1461 - Judge Dredd Megazine #238, 2005)
 * "Change of Loyalties" (with Henry Flint, in 2000 AD #1466, 2005)
 * "Global Psycho" (with Ian Gibson, in 2000 AD #1468, 2005)
 * "Direct Action" (with Cam Kennedy, in 2000 AD #1477-1479, March 2006)
 * "Return to Planet Gary" (with Ian Gibson, in 2000 AD #1483, April 2006)
 * "Culling Time" (with Paul Marshall, in Judge Dredd Megazine #244, May 2006)
 * "Regime Change" (with Inaki Miranda, in Judge Dredd Megazine #246-249, June–September 2006)
 * "Fitness Test" (with Anthony Williams, in 2000 AD #1484, 2006)
 * "House of Pain" (with PJ Holden, in 2000 AD #1488-1490, 2006)
 * "Sanctuary" (with PJ Holden, in 2000 AD #1495, 2006)
 * "Judgement" (with Ian Gibson, in 2000 AD #1523-1528, 2007)
 * "Tartan Terrors" (with Jock, in 2000 AD #1540, 2007)
 * "Cit-Emp" (with Len O'Grady, in 2000 AD #1550, 2007)
 * "Trial by Dury" (with Paul Marshall, in 2000 AD #1552-1553, 2007)
 * "Test Flight" (with Colin MacNeil, in 2000 AD #1554, 2007)
 * "The Listener" (with Boo Cook, in Judge Dredd Megazine #265, 2007)
 * "The Menagerie" (with Paul Marshall, in Judge Dredd Megazine #267, 2008)
 * "Mind Games" (with Inaki Miranda, in Judge Dredd Megazine #269, 2008)
 * "Born to Zoosh" (with Nick Dyer, in 2000 AD #1634, 2009)
 * "Road Stop" (with Dave Taylor, in 2000 AD #1582-1586, 2008)
 * "It came from Bea Arthur Block" (with PJ Holden, in 2000 AD #1637-1639, 2009)
 * "Tour of Duty: Dragon's Den" (with Cliff Robinson (1-2) and PJ Holden (3-4), in 2000 AD #1668-1671, January–February 2010)
 * "The Connoisseur" (with Karl Richardson, in 2000 AD #1695-1697, July–August 2010)
 * "The Natural" (with Graeme Neil Reid, in Judge Dredd Megazine #301, September 2010)
 * "Persistent Vegetative State" (with Cliff Robinson, in 2000 AD #1726-1727, March 2011)
 * "Scream" (with Lee Carter, in 2000 AD #1737-1739, June 2011)
 * "Suicide Watch" (co-written with Emma Beeby, art by Paul Davidson and Chris Blythe, in 2000 AD #1826-1829, April 2013)

 * Mean Machine:
 * "Psycho Analysis" (with Robert McCallum, in 2000AD Sci-Fi Special 1995)
 * "Mean Streets" (with Jim Murray, in Judge Dredd Mega-Special, 1996)
 * "Close Encounters of the Mean Kind" (with Anthony Williams, in 2000AD Sci-Fi Special 1996)
 * "Born Mean" (with Kev Walker, in Judge Dredd Megazine #3.69, 2000)
 * "The Geek" (with pencils by Paul Marshall and inks by Lee Townsend, in Judge Dredd Megazine #3.69, 2000)
 * "Support Yore Local Bastich" (with Wayne Reynolds, in Judge Dredd Megazine #3.69, 2000)
 * "The Last Vidshow" (with pencils by Patrick Goddard and inks by Lee Townsend, in Judge Dredd Megazine #3.69, 2000)
 * "Butt Me Deadly" (with pencils by Patrick Goddard and inks by Lee Townsend, in Judge Dredd Megazine #3.69, 2000)

 * Harke & Burr: "Satanic Farces" (with co-writer Si Spencer and Dean Ormston, in Judge Dredd Megazine #3.04-3.07, 1995)
 * Vector 13:
 * "Case Zero: Oath of Office" (with Garry Marshall, in 2000 AD #987, 1996)
 * "Case Five: Patent Pending" (with Mike Perkins, in 2000 AD #1028, 1997)
 * "Case Six: Bodysnatchers" (with Alex Ronald, in 2000 AD #1029, 1997)
 * "Case Eight: Unhallowed Ground" (with Allan Bednar as "Neal Brand", in 2000 AD #1031, 1997)
 * "Case Zero: Shadows and Light" (with Dylan Teague, in 2000 AD #1060, 1997)
 * "Case Six: MK-Ultra" (with Alex Ronald, in 2000 AD #1067, 1997)
 * "Case Eight: Midnight Rambler" (with Paul Johnson, in 2000 AD #1069, 1997)
 * "Case Eleven: Search & Rescue" (with Cliff Robinson, in 2000 AD #1072, 1997)
 * "Case Fifteen: Time's Arrow" (with Patrick Woodrow, in 2000 AD #1076, 1998)
 * "Case Four: Einstein's Monsters" (with Cyril Julien, in 2000 AD #1081, 1998)
 * "Case Five: Seal of Solomon" (with Alex Ronald, in 2000 AD #1082, 1998)

 * Species: Human Race #1 (with pencils by Phil Hester and inks by Ande Parks, 4-issue mini-series, 1996–1997, Dark Horse, tpb, 1997, ISBN 1-56971-219-0)
 * Witch World:
 * "The Dark Man" (with Siku, in 2000 AD #1050-1052, July 1997)
 * "Wolfshead" (with Paul Johnson, in 2000 AD #1053-1054, July–August, 1997)
 * "The Anatomist" (with Will Simpson, in 2000 AD #1055-1058, August–September 1997)
 * "Closing Shadows" (with John Burns, in 2000 AD #1059-1061, September 1997)
 * Inferno!:
 * "Bloodquest" (with Colin MacNeil, in Inferno! #2, 1997)
 * "Rites of Passage" (short story, in Inferno! #4, 1998)
 * "Trespass" (with John Hicklenton, in Inferno! #8, 1998)
 * "Unearthed Remains" (with Simon Davis and Gordon Robson, in Inferno! #9, 1998)
 * Starship Troopers: "Insect Touch" #2-3 (with co-writer Warren Ellis with art by Davide Fabbri and Paolo Parente, 4-issue mini-series, 1997, Dark Horse, collected in  Starship Troopers, 1998, ISBN 1-56971-314-6)
 * Bloodquest: Eye of Terror Trilogy (with Colin MacNeil, Black Library, 256 pages, 2005, ISBN 1-84416-146-3) collects:
 * Bloodquest (104 pages, 1999, ISBN 1-84154-108-7)
 * Bloodquest: Into the Eye of Terror (54 pages, 2001, ISBN 1-84154-126-5)
 * Bloodquest: The Daemon's Mark (96 pages, 2003, ISBN 1-84416-057-2)
 * Tharg's Terror Tales (with Frazer Irving):
 * "Reefer Madness" (in 2000 AD #1263, 2001)
 * "Mars Needs Mates!" (in 2000 AD #1285, 2002)
 * "Monsters of Rock" (in 2000 AD #2004, 2003)
 * Pulp Sci-Fi:
 * "Night Shift" (with Dylan Teague, in 2000 AD #1131, 1999)
 * "Buzz Tycho's Last Stand" (with Charlie Adlard, in 2000 AD #1146, 1999)
 * "Surgical Strike" (with Trevor Hairsine, in 2000 AD #1148, 1999)
 * "Reapermen" (with Jock, in 2000 AD #1170, 1999)
 * "Chronvicts" (with Siku, in 2000 AD #1172, 1999)
 * Glimmer Rats (with Mark Harrison, in 2000 AD Prog 2000 & #1174-1182, 1999–2000, tpb, Rebellion Developments, 60 pages, hardcover, 2002, ISBN 1-904265-00-6)
 * Rain Dogs (with Colin Wilson, in 2000 AD #1213-1222, 2000, tpb, Rebellion Developments, 52 pages, hardcover, 2002, ISBN 1-904265-01-4)
 * Kal Jerico: Underhive Bounty Hunter (Necromunda series, Black Library, 176 pages, 2005, ISBN 1-84416-254-0) collects:
 * Kal Jerico (with Karl Kopinski, 54 pages, 2000, ISBN 1-84154-041-2)
 * Kal Jerico II: Contracts and Agendas (with Wayne Reynolds, 54 pages, 2001, ISBN 1-84154-209-1)
 * Necronauts (with Frazer Irving, in 2000 AD Prog 2001 and #1223-1230, 2000–2001, tpb, 64 pages, 2003, ISBN 1-904265-09-X)
 * Satanus Unchained! (with Colin MacNeil, in 2000 AD #1241-1246, 2001)
 * ZombieWorld: "Home for the Holidays" (with Gary Erskine, one-shot, 1997, Dark Horse, collected in ZombieWorld: Winter's Dregs, 2005 ISBN 1-59307-384-4)
 * Predator Omnibus: Volume 4 (352 pages, October 2008, ISBN 1-59307-990-7) collects:
 * "Nemesis" (with Colin MacNeil, two-issue mini-series, 1997)
 * "Captive" (with Dean Ormston, one-shot, 1998)
 * Storming Heaven (with Frazer Irving, in 2000 AD Prog 2002 & # 1273-1278, 2001–2002)
 * The Life and Time of Ulli & Marquand and Their Misadventures in Mordheim, City of the Damned (with Gavin Thorpe, Mike Perkins, and Karl Kopinski, Black Library, 80 pages, 2002, ISBN 1-84154-211-3)

 * Rogue Trooper (collected in Realpolitik, 144 pages, February 2007, ISBN 1-904265-94-4):
 * "What lies beneath" (with pencils by Staz Johnson and inks by David Roach, in 2000 AD #1301-1304, 2002)
 * "Weapons of War" (with Dylan Teague, in 2000 AD #1305, 2002)
 * "Overkill" (with Simon Coleby, in 2000 AD #1306-1307, 2002)
 * "Lions" (with Staz Johnson (1308) and Mike Collins (1309), in 2000 AD #1308-1309, 2002)
 * "A Visit to the Boneyard" (with pencils by Mike Collins and inks by David Roach, in 2000 AD #1310-1311, 2002)
 * "Requiem" (with Simon Coleby, in 2000 AD #1312, 2002)
 * "Angels" (with Simon Coleby, in 2000 AD Prog 2003, 2002)
 * "Ghouls" (with Staz Johnson (1344–1347) and Mike Collins (1348-1349), in 2000 AD #1345-1349, 2003)
 * "Realpolitik" (with PJ Holden, in 2000 AD #1380-1385, 2004)
 * "Condor Six Down" (with Simon Coleby, in 2000 AD #1462-1464, 2005)

 * Past Imperfect:
 * "Infamy" (with pencils by Mike Collins and inks by Lee Townsend, in 2000 AD #1316, 2002)
 * "The Red Menace" (with pencils by Adrian Bamforth and inks by Lee Townsend, in 2000 AD #1318, 2002)

 * Caballistics, Inc. (with Dom Reardon):
 * "Going Underground" (in 2000 AD #1322-1326, 2002)
 * "Moving In" (in 2000 AD #1331-1333, 2003)
 * "Breaking Out" (in 2000 AD #1337-1340, 2003)
 * "Downtime 1 - Chapter" (in 2000 AD #1363, 2002)
 * "Downtime 2 - Verse" (in 2000 AD #1364, 2002)
 * "Downtime 3 - Ness" (in 2000 AD #1365, 2003)
 * "Downtime 4 - Jonathan & Jennifer" (in 2000 AD #1366, 2003)
 * "Downtime 5 - Ravne" (in 2000 AD #1367, 2003)
 * "Downtime 6 - Kostabi" (in 2000 AD #1368, 2003)
 * "Krystalnacht" (in 2000 AD Prog 2004, 2003)
 * "Picking Up The Pieces" (in 2000 AD #1400, 2004)
 * "Creepshow" (in 2000 AD #1401-1408, 2004)
 * "Weird War Tales" (in 2000 AD Prog 2005, 2004)
 * "Northern Dark" (in 2000 AD #1443-1448, 2005)
 * "Strange Bedfellows" (in 2000 AD Prog 2006, 2005)
 * "Changelings" (in 2000 AD #1469-1474, 2006)
 * "Ashes" (in 2000 AD #1551-1558, 2007)
 * "The Nativity" (in 2000AD Prog 2008, 2007)

 * Bato Loco:
 * "True Romance" (with Simon Coleby, in Judge Dredd Megazine #208, 2003)
 * "Head Job" (with Simon Coleby, in Judge Dredd Megazine #229-230, 2005)
 * "Kiss Me Deadly" (with Andrew Currie, in Judge Dredd Megazine #290-291, 2009)
 * Daemonifuge: Judgement of Tears (with Kev Walker and Karl Richardson, Black Library, 88 pages, 2003, ISBN 1-84154-240-7)
 * Whatever Happened To?:
 * "Maria" (with Graham Manley, in Judge Dredd Megazine #215, 2004)
 * "John 'Giant' Clay" (with Rufus Dayglo, in Judge Dredd Megazine #216, 2004)
 * "Conrad Conn" (with Carlos Trigo, in Judge Dredd Megazine #218, 2004)
 * "The Gribligs" (with Steve Roberts, in Judge Dredd Megazine #219, 2004)
 * Deff Skwadron (with Paul Jeacock, Black Library, 64 pages, 2003, ISBN 1-84416-069-6)

 * Cursed Earth Koburn (with Carlos Ezquerra):
 * "Kuss Hard" (in Judge Dredd Megazine #221-223, 2004)
 * "Burial Party" (in Judge Dredd Megazine #228, 2005)
 * "The Assizes" (in Judge Dredd Megazine #239, 2005)
 * "Malachi" (in Judge Dredd Megazine #240-144, 2006)
 * Johnny Woo:
 * "A Bullet In The Head" (with PJ Holden, in Judge Dredd Megazine #231-233, 2005)
 * "A Hong Tong Ghost Story" (with PJ Holden, in Judge Dredd Megazine #298-299, 2010)
 * The 86ers:
 * "Touchdown" (with art by Karl Richardson (1-2), drawing by PJ Holden (3-6) and colours by Chris Blythe (3-6), in 2000 AD #1480-1485, 2006)
 * "Interference" (with PJ Holden, in 2000 AD #1508-1510, 2006)
 * "Walking to Eternity" (with PJ Holden, in 2000 AD Prog 2007, 2006)
 * Absalom (with Tiernan Trevallion):
 * "Noblesse Obligie" (in 2000 AD #1732-1739, May–June 2011)
 * "Sick leave" (in 2000 AD Prog 2012, December 2011)
 * "Ghosts of London" (in 2000 AD #1765-1771, January–February 2012)

Novels
Novels include: 2000 AD
 * Judge Dredd: Dredd Vs Death (Black Flame, October 2003, ISBN 1-84416-061-0)
 * Rogue Trooper: Crucible (Black Flame, October 2004, ISBN 1-84416-061-0)

Warhammer
 * Execution Hour (with Matthew Farrer, Games Workshop, August 2001, ISBN 0-7434-1165-X)
 * Zavant (Games Workshop, March 2002, ISBN 0-7434-1174-9)
 * Shadowpoint (Games Workshop, April 2003, ISBN 0-7434-4326-8)
 * Blood Royal (with Will McDermott, Necromunda series, Black Library, August 2005, ISBN 1-84416-190-0)

Video games

 * Killzone (script, 2004)
 * Rogue Trooper (script 2006)
 * Xi ("initial brainstorm writer", 2009)
 * Splatterhouse (script, 2010)
 * Aliens vs. Predator (script, 2010)
 * Highlander: The Game (cancelled 2010)
 * Risen 2: Dark Waters (script with Emma Beeby & Alan Barnes, 2012)

Awards

 * 2004 Graphic Novel of the Year, Diamond Comics Awards (for Necronauts)
 * 2006 Screenplay (video games), BAFTA nomination for writing the script for the Rogue Trooper game

title: Gordon Rennie


text:
Tremolite

Tremolite is a member of the amphibole group of silicate minerals with composition Ca2(Mg5.0-4.5Fe2+0.0-0.5)Si8O22(OH)2. Tremolite forms by metamorphism of sediments rich in dolomite and quartz, and occurs in two distinct forms, crystals and fibers. Tremolite forms a series with actinolite and ferro-actinolite. Pure magnesium tremolite is creamy white, but the color grades to dark green with increasing iron content. It has a hardness on Mohs scale of 5 to 6. Nephrite, one of the two minerals known as the gemstone jade, is a green crystalline variety of tremolite.

The fibrous form of tremolite is one of the six recognised types of asbestos. This material is toxic, and inhaling the fibers can lead to asbestosis, lung cancer and both pleural and peritoneal mesothelioma. Fibrous tremolite is sometimes found as a contaminant in vermiculite, chrysotile (itself a type of asbestos) and talc.

Occurrence
Tremolite is an indicator of metamorphic grade since at high temperatures it converts to diopside.

Tremolite occurs as a result of contact metamorphism of calcium and magnesium rich siliceous sedimentary rocks and in greenschist facies metamorphic rocks derived from ultramafic or magnesium carbonate bearing rocks. Associated minerals include calcite, dolomite, grossular, wollastonite, talc, diopside, forsterite, cummingtonite, riebeckite and winchite.

Tremolite was first described in 1789 for an occurrence in Campolungo, Piumogna Valley, Leventina, Ticino (Tessin), Switzerland.

Fibrous tremolite
One of the six recognized types of asbestos, approximately 40,200 tons of tremolite asbestos is mined annually in India. It is otherwise found as a contaminant.

title: Tremolite


text:
Talk:Colin Chapman/to do

I think organization is hard because Chapman wore many hats (when he wasn't flinging them in the air--that personal trademark should be in the article too!) simutaneously and never ceased any of them. So, it would seem chronological is out as an organizing framework. Maybe something roughly like the following would work: * Biographical information * Engineer for Bristol Aeroplane * Early trials cars and kit cars * Chapman as automobile manufacturer * Sports cars * Luxury specialty cars * Chapman as automobile racing director/designer/engineer * Sports cars and single-seater formula cars * Formula One * Chapman as industrial designer/engineer Someone with skill would then have to weave in how Chapman used racing to improve his road cars (and sometimes vice-versa). I haven't read up on it, but I can imagine that the design philosophy of a Chapman coffin would mean that it was fully capable of navigating The 2g corner.
 * Add information from these pages about Chapman's chairs, coffins, and boats, and (especially) the Lotus Microlight aircraft he designed with Burt Rutan.
 * Organize page into sections

I could see having a 1950s narrative, a 1960s narrative, etc. to put in perspective all that he was simultaneously accomplishing, but I think something like the above with perhaps a bit of interweaving, would be less repetitious and more Encyclopedic.Fotoguzzi 19:31, 28 July 2007 (UTC)
 * Find a PD or GFDL picture of Chapman
 * I would consider removing speculation linking the dual-chassis debacle with his health. [Thanks!  I see the linkage removed and the article greatly improved in other ways.] In exchange I hope someone could describe the singlemindedness that Chapman displayed when it came to, well, everything.  Examples would include his lawyerly interpretation of the rules and a mania for "purity" of design. (Would it be incorrect to imply that Chapman added material to a part only after its manufacture proved unworthy of its divinely-inspired specification?)  He designed a "perfect" space-frame car, The Mk. VIII, which virtually had to be dismantled to make adjustments to the less-than-perfect engines that were available at the time.  Could a case be made that in using springs as suspension arms and structural tubes as water conduits (early designs), or, later, engines and tubs as stressed chassis members and chassis themselves as inverted wings, that he wasn't designing parts so much as organizing systems?  To me, his desire to control every aspect of company, team, and cars, and to win based on his own cleverness, by his interpretation of the rules, may have been a strain that no heart could endure forever (and yes, this speculation is as groundless as his being done-in by the rejection of the dual-chassis [speculation which, mercifully, has been removed]).  bkm -- pdx,or,usa

title: Talk:Colin Chapman/to do


text:
Talk:Colin Chapman

Family life
I already know that throughout most of his life he was married to his wife Hazel. Does anyone else know if they both had any children?

Lostinsidemyworld 15:35, 31 July 2007 (UTC)
 * I know Colin has a son, Clive, who runs Classic Team Lotus. I don't know for sure that Hazel is Clive's mother, but that would be my guess. DH85868993 15:45, 31 July 2007 (UTC)
 * Two daughters as well, I think Sarah and Jane but I'd have to look it upMr Larrington (talk) 13:41, 8 July 2010 (UTC)

Birth Date
The authorised biography (G Crombac 1986 ISBN 0850597331) clearly and unambiguously states on page 15 that Chapmans's date of birth was 19th May 1928)

The article at http://www.oldracingcars.com/bydriver/watn.asp?letter=C was incorrect in stating 9th May and has been incorrectly quoted as a primary source. This source has now, at long last, appeared to be have been corrected. M100 (talk) 17:36, 22 February 2008 (UTC)

Add lightness
Shouldn't an article about CC include his most famous quote?24.125.19.104 (talk) 05:20, 4 August 2008 (UTC)Anon

I was actually just about to ask this same question. 216.124.10.6 (talk) 19:56, 21 October 2008 (UTC)

Other Innovations
Chapman also developed four wheel drive and turbine powered racing cars. The 4WD turbine powered Lotus 56 nearly won the 1968 Indianapolis 500. He put forth new technology at a startling pace, but what was more remarkable is that new innovations were always competitive and not merely interesting. He appears to have been a truly brilliant engineer. —Preceding unsigned comment added by 76.173.197.1 (talk) 00:51, 4 May 2008 (UTC)

No sources
Doesn't this weakness of sources lower this article to O.R., if not outright fiction? BannedBeyondAllEternity (talk) 15:43, 30 July 2012 (UTC)
 * There are actually 11 sourced citations on this article. This would only be OR if no reliable sources could be located supporting the information. Michael (talk) 20:04, 1 August 2012 (UTC)
 * The weakness in the sources is not the number (although five old car mags seems pushing it), but that they are not made clear in the article. There are paragraphs, and even sections (Career and Personal life), with no source at all. Shouldn’t you use at least some “ibid”s?

 * I was curious about the man, but “Certainly” offended me. And the rest of the article looks like intellegent and informed, but not encyclopedic. More like a conversation. Especially Innovations and legacty. “Following the race, Chapman...1987” has only one source? For all that info?

 * Someone should clean up the basics.99.172.55.172 (talk) 12:40, 2 August 2012 (UTC)

AW11 MR2 derived from Delorean
I did a little research, and other sites like http://en.wikipedia.org/wiki/Toyota_MR2 state no such relationship exists.

"http://en.wikipedia.org/wiki/Toyota_MR2":

Some rumors have persisted that the MR2 was designed by Lotus. This is a reference to the Lotus M90 (a.k.a. the X100) project, but this was scrapped after a single prototype was built. This used the same engine and gearbox as the MR2. At the time, Toyota, along with the Chapman family was a major share holder in Lotus, but General Motors later acquired majority control. However, the MR2's suspension and handling were designed by Toyota with the help of Lotus engineer Roger Becker.[6] Toyota's cooperation with Lotus during the prototype phase can be seen in the AW11, and it owes much to Lotus's legendary sports cars of the 1960s and 1970s. Toyota's active suspension technology called TEMS was not installed. Built very strong, with five bulkheads, the MR2 was quite heavy for a two-seater of its size — Preceding unsigned comment added by 68.4.76.46 (talk) 05:30, 29 October 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on Colin Chapman. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive http://web.archive.org/web/20110520091232/http://web.mac.com/dennisgray711/grayincolor/Colin_Chapman_files/Colen%20Chapman_1.jpg to http://web.mac.com/dennisgray711/grayincolor/Colin_Chapman_files/Colen%20Chapman_1.jpg

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at Sourcecheck).

Cheers.—cyberbot II  Talk to my owner :Online 03:55, 28 February 2016 (UTC)
 * Archive URL doesn't work, so I have replaced it with a working one. DH85868993 (talk) 04:28, 20 March 2016 (UTC)

Active Suspension
Didn't Lotus run active suspension before 1987? Mansell's car had it in 1983 until he got fed up with it trying to kill him IIRC. — Preceding unsigned comment added by 92.18.24.176 (talk) 20:18, 15 April 2016 (UTC)

 * Yes, the article says it was being tested on the day he died... in 1982. See Lotus 92. Eagleash (talk) 20:40, 15 April 2016 (UTC)

Tube-frame chassis paragraph
This paragraph makes no sense on many levels, quoting "Tube-frame chassis" - "the material has changed from sheet aluminium to carbon fibre". The "chassis" is better described as Monocoque, or more recently engineers referring to it as the "tub", with tubular suspension, both components once made of aluminium and now carbon fibre. ''This design concept fairly quickly replaced what had been for many decades the standard design formula in racing-cars, the tube-frame chassis. Although the material has changed from sheet aluminium to carbon fibre, this remains today the standard technique for building top-level racing cars.'' — Preceding unsigned comment added by 109.149.86.96 (talk) 22:47, 6 July 2018 (UTC)

 * I'm afraid I don't follow the logic of your comment. The paragraph you refer to (and the preceding one) is about monocoque design in motor sport. The only place that the word 'chassis' is used is in relation to the technology that monocoque designs were replacing. Pyrop  e  05:09, 8 July 2018 (UTC)

Can there be a seperate page that houses all the information on the Delorean Scandal
The Delorean scandal was so big i'm suggesting a seperate page that houses everything.MoanerTonight (talk) 13:42, 20 May 2020 (UTC)

 * It is certainly an interesting part of the later career of Chapman. If you'd like to write more about it I suggest that you start by augmenting the Delorean Motor Company page. If the amount of content on the scandal gets large enough to require spinning out to a separate page then we can discuss that when the issue arises. Pyrop  e  17:56, 20 May 2020 (UTC)

Place of Birth
I have removed contradictory information from the infobox. In my first edit I made it agree with the main text, but an editor has reverted the old information back in. As the old information is unsourced, and per MOS:INFOBOXPURPOSE, I have removed the parameter. Now looking at the place of birth, it is indeed possible that Chapman was born in Richmond, but nothing on the page says so. The source we are using for the birth is to this:, albeit without the link (I'll fix that shortly). This is a local history society page. Such pages tend to be pretty good, but their sources are often unclear. A better source would be appreciated. There is no indication in that page that his birthplace was not Muswell Hill, but the phrasing does leave the question open. If his birthplace is Richmond, that should be in the main text before it is re-added to the infobox. Sirfurboy🏄 (talk) 07:37, 23 January 2024 (UTC)

 * This page says he was born at the Orange Tree pub, Richmond and then moved to North London. It is likely correct but still the sources are unclear. Also it would be good to know when, or at what age he moved. Sirfurboy🏄 (talk) 11:14, 23 January 2024 (UTC)

title: Talk:Colin Chapman


text:
Helen Parkhurst

Helen Parkhurst (March 8, 1886 – June 1, 1973) was an American educator, author, lecturer, the originator of the Dalton Plan, founder of the Dalton School and host of Child's World with Helen Parkhurst on ABC Television Network. Parkhurst took her cues from developmental psychologist Jean Piaget and education reformers such as John Dewey and Horace Mann, producing a progressive education philosophy emphasizing the development of the "whole child".

Early life and education
Born in Durand, Wisconsin, she graduated from Wisconsin State Teachers College at River Falls in 1907, studied at the universities of Rome and Munich as well as with Maria Montessori and was awarded her M.A. in 1943 from Yale University. She taught briefly in Wisconsin, moved to Tacoma, Washington, in 1909, and returned to Wisconsin as the director of the department for the training of primary teachers at Stevens Point Normal School from 1913 until 1915. For a time, Parkhurst served as director of all Montessori schools in the United States.

Career
In 1920 she gained a disciple when college founder Belle Rennie visited from the UK. Rennie became a evangelist for the approach and she created the Dalton Association in Britain.

After further work with Montessori in Rome, Parkhurst wrote several books like Education on the Dalton Plan (1922), Work Rhythms in Education (1935), Exploring the Child's World (1951), Growing Pains (1962) and Undertow (1963) and had her own national radio and television programs. Parkhurst hosted a children's educational program on ABC Radio Network in New York City. In 1932 Belle Rennie published The Triumph of the Dalton Plan with the British educational psychologist Charles William Kimmins.

Parkhurst was a 1948 recipient of a Radio - Television Critics Award and a 1949 recipient of the 13th American Exhibition of Educational Radio Programs Award.

Parkhurst was the author of Education on the Dalton Plan, which was published in 58 languages; Exploring the Child's World, with an introduction by Aldous Huxley, and Growing Pains, a book about teenagers. Parkhurst was named one of the 100 Educators of All Time. Parkhurst was decorated by the Queen of Italy, Empress of Japan, and Queen of the Netherlands. Maria Montessori best summarized Parkhurst's career by stating, "Her intelligent activity is truly rare and precious." Eleanor Roosevelt greatly admired Parkhurst's work and played a significant role in expanding the population and resources of her school.

Legacy
Parkhurst's influence has spread across the globe, with schools in the Netherlands, England, Australia, Japan and others adopting the Dalton Plan of education. The Helen Parkhurst Exhibit at the Pepin County Museum traces the life and legacy of Parkhurst. There is a "Helen Parkhurst Dalton School" in Rotterdam and a Parkhurst Lecture Hall at UW-Stevens Point.

title: Helen Parkhurst


text:
Nam Cheong

Nam Cheong is both the Cantonese name for Nanchang and the name of a street in Sham Shui Po, Hong Kong.

In the latter context, several features have been named after Nam Cheong Street:

 * Nam Cheong Estate
 * Nam Cheong Park
 * Nam Cheong station

title: Nam Cheong


text:
User talk:Amorpheous

Welcome!

Hello, and welcome to Wikipedia. Thank you for your contributions. I hope you like the place and decide to stay. Here are a few good links for newcomers: I hope you enjoy editing here and being a Wikipedian! By the way, you can sign your name on Talk and vote pages using three tildes, like this: ~~~. Four tildes (~~~~) produces your name and the current date. If you have any questions, see the help pages, add a question to the village pump or ask me on my Talk page. Again, welcome!
 * How to edit a page
 * Editing, policy, conduct, and structure tutorial
 * Picture tutorial
 * How to write a great article
 * Naming conventions
 * Manual of Style
 * If you're ready for the complete list of Wikipedia documentation, there's also Topical index.

-- Netoholic @ 23:41, 2004 Sep 27 (UTC)

 * Thanks for the welcome. Amorpheous 17:41, 1 May 2005 (UTC)

Unreferenced BLPs
Hello Amorpheous! Thank you for your contributions. I am a bot alerting you that 1 of the articles that you created  is tagged as an Unreferenced Biography of a Living Person. The biographies of living persons policy requires that all personal or potentially controversial information be sourced. In addition, to insure verifiability, all biographies should be based on reliable sources. if you were to bring this article up to standards, it would greatly help us with the current Category:All_unreferenced_BLPs article backlog. Once the article is adequately referenced, please remove the unreferencedBLP tag. Here is the article:

Thanks!--DASHBot (talk) 21:39, 8 January 2010 (UTC)
 * 1) Teddy Dunn -

title: User talk:Amorpheous


text:
The Changeling (Star Trek: The Original Series)

"The Changeling" is the third episode of the second season of the American science fiction television series Star Trek. Written by John Meredyth Lucas and directed by Marc Daniels, it was first broadcast on September 29, 1967.

The crew of the USS Enterprise deals with a life-destroying space probe originally launched from Earth. The plot contains similarities to the later 1979 Star Trek film.

Plot
The USS Enterprise investigates a distress call from the Malurian star system. Upon arrival, First Officer Spock reports no life readings from any of the 4 billion inhabitants, despite otherwise normal recent communications. The ship's shields are suddenly activated when a meter-long cylindrical object attacks with a powerful energy bolt equivalent to 90 photon torpedoes. Captain Kirk orders return fire, but his weapon's energy is simply absorbed by the object. Following several more incoming attacks, and on the verge of his ship's destruction, Kirk hails the object. After several back-and-forth attempts, the object requests in-person communication with the Captain and allows itself to be beamed aboard the ship.

The object identifies itself as "Nomad", and refers to Captain Kirk as "the Creator". Spock reports that a Nomad space probe was launched from Earth during the early 21st century; its mission was to explore the galaxy and seek out new life, but it had been reported destroyed – a report that Spock acknowledges may have been wrong. The current Nomad has mistaken Kirk for Dr. Jackson Roykirk, the scientist who created and programmed the original probe. Nomad's new mission is to seek out and eliminate any "biological infestation" that it deems imperfect, including the entire population of the Malurian star system. Nomad states that its attempt to destroy the Enterprise had not been necessary since "the Creator" was aboard.

Left in the care of a crew member, Nomad escapes to investigate the sound of Lieutenant Uhura singing, which it detects over the intercom. Arriving on the bridge to make inquiries, it asks Uhura to "think about music" while probing her mind, which erases her memory. When Chief Engineer Scott tries to intervene, Nomad kills him, pleading self-defense. Upon learning that Kirk cannot repair Scott, Nomad offers to restore him to life. Nomad heals Scott, but cannot "repair" Uhura's memory loss; Nomad is taken to the brig. Since Uhura's brain was not damaged (only her memories erased), the medical staff proceed to re-educate her (by the end of the episode, Uhura is almost back to normal).

To uncover more information, Spock performs a Vulcan mind meld with the machine. He discovers that Nomad collided with a meteor and was severely damaged. It then wandered through space, finally coming into contact and merging with a powerful alien probe called Tan Ru, designed to obtain and sterilize soil samples from other planets. Nomad partially integrated Tan Ru's agricultural mission directives, interpreting them to mean "sterilize imperfections". The merging of the two probes imbued Nomad with Tan Ru's vast powers, sufficient to destroy life throughout an entire solar system. Kirk compares Nomad's reincarnation to the changeling legend, in which a human child is switched with a fairy child, with the latter assuming the identity of the former.

Nomad escapes from its cell, killing two guards who attempt to stop it. The probe makes its way to the engineering deck, where it begins to make adjustments to the engines, accelerating the ship beyond its normal maximum warp speed. As Kirk arrives, Nomad tells him that engine efficiency has been boosted 57%; Kirk orders it to reverse the changes since other structures on the Enterprise cannot handle the faster speed. Nomad complies.

Exasperated by Nomad's prejudice toward imperfect "biological units", Kirk points out that its own "Creator" is a biological unit. Nomad responds that it must "reevaluate". Kirk orders the probe back to the brig, and it departs under security guard. Spock then suggests to Kirk that admitting to Nomad that he, "the Creator", is imperfect was probably a mistake. Spock also observes that because Nomad has threatened to return to its "launch point", the Earth and all its inhabitants are now at risk of sterilization.

En route to the brig, Nomad kills its two security escorts and heads instead to sickbay. After examining Kirk's medical files and verifying his imperfections as a biological unit, Nomad's "reevaluation" is complete. It proceeds to engineering, incapacitates crew members and shuts down the ship's life-support systems, thus rendering the Enterprise habitable for only a short time longer.

Kirk arrives and again confronts the probe, questioning it about its mission. When Nomad declares that its directive to sterilize imperfections allows no exceptions, Kirk points out that Nomad itself is imperfect, since it has mistaken Captain Kirk for its true creator Jackson Roykirk. He then claims that Nomad has committed two other errors, by not discovering its own mistake, and by not sterilizing itself as imperfect. Nomad begins to analyze the implications of Kirk's claims, a process that causes noticeable stress to its systems. Kirk and Spock carry Nomad in a rush to the transporter room and, with a final command from Kirk to "exercise your prime function", beam it into deep space. Seconds after transport, an explosion is detected near the Enterprise and Nomad is no more. The episode ends on a humorous note, with Kirk observing that he is proud that his "son" Nomad, having healed Mr. Scott, would have made a good doctor.

Production
The episode is one of only a handful in the original series that take place entirely aboard the Enterprise. The others include "Charlie X", "Journey to Babel", "Elaan of Troyius", and "Is There in Truth No Beauty?".

The director, Marc Daniels, appears on screen as the still photo of Dr. Jackson Roykirk.

Influence
The episode is perhaps most known for being a predecessor to the 1979 film Star Trek: The Motion Picture, which also features an Earth probe that somehow merges with a powerful alien entity far from Earth and causes problems, as V'Ger. The plot arc of human imperfections and foibles confusing a powerful but malfunctioning robot (also seen in the Star Trek episode "The Return of the Archons" as well as various pieces of sci-fi pulp fiction) would go on to become a common trope in science-fiction, to the point of parody in more comedically inclined works such as Futurama.

In 2001 the writers of the Star Trek: Enterprise episode "Civilization" intentionally used the Malurians as the antagonists in reference to this episode.

Reception
In 2013, Phelim O'Neill of The Guardian made a list of representative Star Trek personal favorite episodes to watch (not necessarily the best) that included "The Changeling".

A 2015 retrospective by Keith R. A. DeCandido found the episode disappointing for The Original Series, ranking it a 4/10. He thought the concept was decent, but DeCandido felt that the tone was unfitting. Various extreme events happen in the episode - billions of Malurians are killed off-screen, Scotty is killed by NOMAD and then resurrected, Uhura has her memories wiped, and four security officers are killed. Yet the characters don't seem to grapple with this: the crew has their normal banter and are oddly blasé about the situation, and the episode closes with a joke from Kirk. He also disliked the episode leaving unexplained how Uhura was restored.

In 2016, Time magazine named NOMAD the franchise's eighth-best villain. The same year, CNET included NOMAD as one of 26 powerful spacecraft of the Star Trek franchise. Also in 2016, SyFy noted Nichelle Nichols' performance as Uhura, writing that this episode included her ninth best scene in Star Trek.