--color=always is a really bad idea. You're shoving terminal escape codes to set the colours down any pipe to which you connect ls's stdout, e.g. `ls | awk 'length >= 3 && length = 5''. This is why --color=auto exists.
If Sun said "cat/dev/null >/path/to/file" they've really gone downhill since the 1980s when I last used Sun OS. Back then, they'd have known it's just ">/path/to/file" from the shell.
The Transputer took its model from Tony Hoare's CSP. You're right. Channels are the correct way to do this kind of thing instead of semaphores, etc. You can do them in C these days with things like LibTask.
Anyone interested in multiple threads of execution should be familiar with the excellent information presented by Russ Cox on Bell Labs and CSP Threads. This model of threading is far easier to reason about than what most of the world mucks around with, and is available to Unix as part of the Plan 9 from User Space project as libthread.
> Why not just shoot the bugger using a silencer? Advantages of using a gun...
As I understand it, the victim survived for far longer than he should of, clinging onto life. This allowed doctors to run more tests than normal and gave them time to identify the pollonium-210. Normally, a victim's early death after a few days would have left no traces as to the cause of death, unlike a gun. Once the P-210 was identified, it was fairly easy to search for traces of where it had been which is how the alleged murderer has been tracked down.
This is all based on an episode of _Panorama_ I saw bits of the other night. Perhaps the BBC web site has more information.
Yes, I meant see the red, green, and blue pixels. I've read all that I can find about the screen on the Internet but some things are still unclear; perhaps you know the answers?. Is the mono screen in front of or behind the colour one, i.e. is the colour one effectively transparent when not in use if it's in front, or does the mono one help improve the colour one's apparent resolution if it's in front.
Basically, some diagrams or close-up pics seem to be lacking. http://wiki.laptop.org/go/Hardware_specification says the effective resolution is very complex to explain and Mary Lou Jepson is planning to write up an explanation.
Did it have the final "combination" screen of reflective mono and transmissive colour? What did you think of them? I've not found many photos of it in action close up.
#(cd/tmp ; rm -r -f dir) No! Do "cd/tmp && rm -rf dir" else if the cd fails you remove./dir in error.
People use && far too little, e.g. the number of `how to install from source' guides that say "./configure; make; make install" instead of "./configure && make all check install".
Someone in the UK with time on their hands looking for a cause should contact the Office of Fair Trading since it sounds like the contract between MS and the individual is too one-sided and the OFT has a legal requirement to look into any complaint made. I understand that they work under rules that are common in most EU countries now, so maybe it would be worth doing there too.
Authors do produce PDFs ready for the publisher using tools like TeX. troff has been used for decades to do just this and with the GNU groff implementation it's still being done today, using Free Software all the way, e.g. http://troff.org/pubs.html#vpnsi. There's many more listed on that page. They're not all technical, e.g. a Collins dictionary IIRC.
Slashdot Mirror
--color=always is a really bad idea. You're shoving terminal escape codes to set the colours down any pipe to which you connect ls's stdout, e.g. `ls | awk 'length >= 3 && length = 5''. This is why --color=auto exists.
LLVM is the one to watch. Currently, llvm-gcc uses GCC's front end but Apple, a major funder of LLVM, have recently released the source to clang, their C compiler. No GCC in sight. http://llvm.org/ http://heisenbug.blogspot.com/2007/07/compiler-with-good-clang.html
If Sun said "cat /dev/null > /path/to/file" they've really gone downhill since the 1980s when I last used Sun OS. Back then, they'd have known it's just ">/path/to/file" from the shell.
The Transputer took its model from Tony Hoare's CSP. You're right. Channels are the correct way to do this kind of thing instead of semaphores, etc. You can do them in C these days with things like LibTask.
Anyone interested in multiple threads of execution should be familiar with the excellent information presented by Russ Cox on Bell Labs and CSP Threads. This model of threading is far easier to reason about than what most of the world mucks around with, and is available to Unix as part of the Plan 9 from User Space project as libthread.
> Why not just shoot the bugger using a silencer? Advantages of using a gun...
As I understand it, the victim survived for far longer than he should of, clinging onto life. This allowed doctors to run more tests than normal and gave them time to identify the pollonium-210. Normally, a victim's early death after a few days would have left no traces as to the cause of death, unlike a gun. Once the P-210 was identified, it was fairly easy to search for traces of where it had been which is how the alleged murderer has been tracked down.
This is all based on an episode of _Panorama_ I saw bits of the other night. Perhaps the BBC web site has more information.
Cheers, Ralph.
Thanks, Rik. That gets me to http://en.wikipedia.org/wiki/Subpixel_rendering which was the "missing link" I didn't have since I've never caught up with this new fangled LCD technology. :-)
Yes, I meant see the red, green, and blue pixels. I've read all that I can find about the screen on the Internet but some things are still unclear; perhaps you know the answers?. Is the mono screen in front of or behind the colour one, i.e. is the colour one effectively transparent when not in use if it's in front, or does the mono one help improve the colour one's apparent resolution if it's in front.
Basically, some diagrams or close-up pics seem to be lacking. http://wiki.laptop.org/go/Hardware_specification says the effective resolution is very complex to explain and Mary Lou Jepson is planning to write up an explanation.
Did it have the final "combination" screen of reflective mono and transmissive colour? What did you think of them? I've not found many photos of it in action close up.
People use && far too little, e.g. the number of `how to install from source' guides that say "./configure; make; make install" instead of "./configure && make all check install".
Someone in the UK with time on their hands looking for a cause should contact the Office of Fair Trading since it sounds like the contract between MS and the individual is too one-sided and the OFT has a legal requirement to look into any complaint made. I understand that they work under rules that are common in most EU countries now, so maybe it would be worth doing there too.
It's "Presumed innocent until proven guilty". It doesn't state you *are* innocent.
Authors do produce PDFs ready for the publisher using tools like TeX. troff has been used for decades to do just this and with the GNU groff implementation it's still being done today, using Free Software all the way, e.g. http://troff.org/pubs.html#vpnsi. There's many more listed on that page. They're not all technical, e.g. a Collins dictionary IIRC.
Hardly original or revolutionary. See Bell Labs's Venti filesystem, and they weren't the first either.
http://lkml.org/lkml/2005/4/10/41