Well, if there's one thing I'd wish for... It'd be an operator to test for the age of the document I'm searching. If I already searched for something a month ago, and to search again to check for something new, I could search for "something age:-30d".
But I don't know if would make much sense, as file date info are generally not very reliable (ex, cp --preserve-timestamps is not the default).
Repeat after me: There is no "Asimove Robotic Laws" in the real world. It's just fantasy.
Autonomous robots are controled by computer programs, and will behave as such. One can program it with security features, but it's just like any other software. There's no magic laws to control their behaviour.
Block queue IO tracing support (blktrace). This allows users to see any traffic happening on a block device queue. In other words, you can get very detailed stadistics of what your disks are doing. User space support tools available in: git://brick.kernel.dk/data/git/blktrace.git
New/proc file/proc/self/mountstats, where mounted file systems can export information (configuration options, performance counters, and so on)
Introduce the splice(), tee() and vmsplice() system calls, a new I/O method. The idea behind splice is the availability of a in-kernel buffer that the user has control over, where "splice()" moves data to/from the buffer from/to an arbitrary file descriptor, while "tee()" copies the data in one buffer to another, ie: it "duplicates" it. The in-buffer however is implemented as a set of reference-counted pointers which the kernel copies around without actually copying the data. So while tee() "duplicates" the in-kernel buffer, in practice it doesn't copy the data but increments the reference pointers, avoiding extra copies of the data. In the same way, splice() can move data from one end to another, but instead of bringing the data from the source to the process' memory and sending back to the destination it just moves it avoiding the extra copy. This new scheme can be used anywhere where a process needs to send something from one end to another, but it doesn't need to touch or even look at the data, just forward it: Avoiding extra copies of data means you don't waste time copying data around (huge performance improvement). For example, you could forward data that comes from a MPEG-4 hardware encoder, and tee() it to duplicate the stream, and write one of the streams to disk, and the other one to a socket for a real-time network broadcast. Again, all without actually physically copying it around in memory.
A move order before the attack order might take care of that. Of course it's queueing but at least your reinforcements will move in. Otherwise I prefer the attack-move command
Just use the move order after the attack, and not before.
In TA you just tell your factory "50 tanks, 50 missile launchers" and after a while you'll have those units at the specified location without further interaction.
Later in the game when you have massive production capacity, it would be useful to put the factory in two kinds of "patrol" mode: to keep the army (if the unit dies, it builds another), or to keep producing forever. You could have a plane factory just to keep 20 Peepers pattroling the front of your base, so your defence artilery can shoot visitors from far.
Slashdot Mirror
Well, a pIII can play movies and run quake3.
That's the two most demanding uses for a computer.
The rest is futile.
But if people abuse it, the adversiters will find less value on Google ads.
They are trying to protect the value of their product.
That way, Google will want to enforce it's ad (avoid ad blockers, make them more visible, etc) even more.
Or just install ubuntu without a bloated desktop environment.
There are plenty of good options around, some are even end-user friendly.
open source vendors != open source creators
Consumerism is the center of the problem.
It kills not only nature, but also ourselves.
Protection schemes make it harder, but not impossible, to break.
You could even hack the output device to get the data after it's unencrypted.
If you can play, you can copy.
I want one of those? Where are they?
wasn't it 60:01 instead?
it's a leap second, not a leap minute.
you mispelled pr0n
bleargh!
trac is much better. way cleaner and simpler interface, and _excelent_ integration with subversion.
also, it's free.
http://trac.edgewall.com/
can't wait to see it applied as an interface to computer games.
or p0rn.
If you know I know it, you should know it was a joke.
Wow! Do you have 2000 computers, or are you using virtualization on a machine with 1TB of memory?
Just add a filter to *.swf
No excuse.
The gramatical rule that says that "permanent" should not be plural is the same in the two languages. (I'm Brazilian too.)
Specially if you realize that today's multi-giga games don't offer much more, neither in fun, gameplay, and even content.
Well, if there's one thing I'd wish for...
It'd be an operator to test for the age of the document I'm searching.
If I already searched for something a month ago, and to search again to check for something new, I could search for "something age:-30d".
But I don't know if would make much sense, as file date info are generally not very reliable (ex, cp --preserve-timestamps is not the default).
yep, the default font size for monospaced text in firefox is too small (12, while proportional font is 14, IIRC)
Also check:r Senders
http://wiki.apache.org/spamassassin/AvoidingFpsFo
http://www.senderbase.org/
http://www.truste.org/
http://www.bondedsender.org/
Repeat after me: There is no "Asimove Robotic Laws" in the real world. It's just fantasy.
Autonomous robots are controled by computer programs, and will behave as such.
One can program it with security features, but it's just like any other software. There's no magic laws to control their behaviour.
and savvy users will never account for more then 10% of the users.
But I don't care if IE dominates the market, as long as the other browsers, or better the web standarts, are respected (that is, IE-only sites sucks).
i want a compile farm of these
The poor soul uses gentoo.
Some stuff I found interesting on the human-friendly changelog.
/proc file /proc/self/mountstats, where mounted file systems can export information (configuration options, performance counters, and so on)
Block queue IO tracing support (blktrace). This allows users to see any traffic happening on a block device queue. In other words, you can get very detailed stadistics of what your disks are doing. User space support tools available in: git://brick.kernel.dk/data/git/blktrace.git
New
Introduce the splice(), tee() and vmsplice() system calls, a new I/O method.
The idea behind splice is the availability of a in-kernel buffer that the user has control over, where "splice()" moves data to/from the buffer from/to an arbitrary file descriptor, while "tee()" copies the data in one buffer to another, ie: it "duplicates" it. The in-buffer however is implemented as a set of reference-counted pointers which the kernel copies around without actually copying the data. So while tee() "duplicates" the in-kernel buffer, in practice it doesn't copy the data but increments the reference pointers, avoiding extra copies of the data. In the same way, splice() can move data from one end to another, but instead of bringing the data from the source to the process' memory and sending back to the destination it just moves it avoiding the extra copy. This new scheme can be used anywhere where a process needs to send something from one end to another, but it doesn't need to touch or even look at the data, just forward it: Avoiding extra copies of data means you don't waste time copying data around (huge performance improvement). For example, you could forward data that comes from a MPEG-4 hardware encoder, and tee() it to duplicate the stream, and write one of the streams to disk, and the other one to a socket for a real-time network broadcast. Again, all without actually physically copying it around in memory.
A move order before the attack order might take care of that. Of course it's queueing but at least your reinforcements will move in. Otherwise I prefer the attack-move command
Just use the move order after the attack, and not before.
In TA you just tell your factory "50 tanks, 50 missile launchers" and after a while you'll have those units at the specified location without further interaction.
Later in the game when you have massive production capacity, it would be useful to put the factory in two kinds of "patrol" mode: to keep the army (if the unit dies, it builds another), or to keep producing forever. You could have a plane factory just to keep 20 Peepers pattroling the front of your base, so your defence artilery can shoot visitors from far.