Except that writing an empty file is not the same thing as deleting the file. In one case, the file exists, can be opened and read (with appropriate permissions,) and has size 0. In the other, the file no longer exists, cannot be opened for reading at all, and has no defined size (or any other metadata).
Deleting a file in Unix simply means removing the file's entry from it's containing directory. This is why deleting a file in Unix requires write permission on the parent directory, and has nothing to do with the permissions on the file itself.
that's the only way out of the GPL, rewrite anything not done by the forking team.
That's not quite true; it's not the only way out - you always have the option of negotiating with the original team for a different license under which to use the code.
There's nothing special in this regard about the GPL - it's the same thing with code under any other license: either use it under the existing license, negotiate a more suitable license, or write your own code.
Looks like they disabled resolution for names at liftport.com - probably after the slashdotting they got today. It was working just fine when I checked the site out earlier
Odd - I read it as saying that it recorded the votes of libertarian voters as "straight democratic party", thus the glitch bumped the republican from his rightful victory.
I didn't even realise you could read it the other way as well. Nice work there.
That is interesting -- what I meant, though, was that it must have been going faster than that when it left earth and turned its engines on for the first time, and unless it spent the whole trip decelerating from 11,200 m/s to just 2,737 m/s, that it didn't make much sense for its final velocity to be 2737m/s
Knowing Intel's history of sticking to consistent naming conventions, it'll more likely be a complete redesign, totally incompatible with BTX. and called BTX2.
Molex is a company which produces connectors for a ridiculous number of applications. Quite a lot of connectors inside a PC come from Molex, not just the hard drive power connectors.
Also, I believe that the original specification for drive power connectors called for an AMP part number, although Molex may be making a compatible part nowadays.
Your final result would be off by a factor of 1,000,000, if everything else was valid -- 2.08e-4 km/s^2 is 2.08e-1 m/s^2, not e-7.
That seemed like a ridiculous amount of accelleration, though, so I checked further, and the spacecraft's final velocity is given by the esa as 2737 m/s, not km. Interestingly, that's actually less than the earth's escape velocity by a good margin. My best guess at this point, then, is that the 2737m/s figure is the velocity imparted to the craft by the engine, not counting the initial velocity it was given by the rocket it was strapped to.
In this case, its acceleration is just 2737m/s / (3648h * 3600s/h) = 2.08*10^-4 m/s^2
At that rate, it will cross it's first football field (91.4m) in 296s, and the next one in just 122s. (It goes by the last one in just 0.033s)
Without considering the constant acceleration, the 55-year figure is worthless -- you're calculating as if every 14 months, the craft came to a dead stop, and started accelerating again.
A rough calculation is that the craft started from 0 speed, and travelled ~384,000 km in ~415 days, giving a constant accelleration of 4.46 km / day / day.
The closest mars has been to us in recent years is about 55,760,000 km (last August.) At that rate of acceleration, a spacecraft could reach it in 5000 days, or about 13.7 years. Still not as fast as the 9 months you mentioned, but a far cry from 55 years.
Actually, HTML parsers consider any length of whitespace to be equivalent to a single space character. Typing two spaces after a period in an HTML document is a waste of time, as the browser will render it as a single space anyway.
To be entirely accurate, the preface doesn't say anything about the GAO. It's the Congressional Budget Office releasing this, not the General Accounting Office.
Also, regardless of what they claim about making official policy recommendations, they certainly do make recommendations:
(from the source document)
Revisions to copyright law should be made without regard to the vested interests of particular business and consumer groups. Instead, they should be assessed with regard to their consequences for efficiency in markets for creative works and other products.
An inability to make official policy recommendations shouldn't be taken to imply that they can't express any opinion at all.
Re:Experiment in Password Abuse
on
Fun With Passwords?
·
· Score: 2, Informative
This won't work, since passwords are usually stored in an encrypted form.
Usually? Which passwords? For what application? In-house or commercial software?
There's not much that you can say is usually true about passwords. They've been implemented thousands of times, by thousands of different developers, and I've seen plenty of systems where user passwords are stored, plaintext, in a database somewhere, or in a file readable (supposedly) by administrators.
There are good ways to do passwords, and bad ways to do passwords, and there're plenty of examples of both out there; certainly enough that I don't have any trouble believing the parent poster's claims.
Where did you get that number? Sounds like you took the 12,889 figure from the story, and multiplied by.75, as the rough proportion of the earth's surface which is water.
Too bad that even the/. story mentions that they've already removed the oceanic points before giving you that number. It doesn't mention the 3000+ points which have already been recorded (though the first link in the story does), so there are actually some 16,000 points above sea level, which should represent a pretty wide range of scenery.
Well, inner classes actually did require a change to the core language (if not to the VM, then at least to the Java compiler).
Swing, Collections, JCE, and everything since have just been exensions to the Java class libraries. It's all still "Java2", and so Sun just increments the minor version number with each release.
(Java 5 sounds like a marketing decision to me, though)
Well, you're not a jackass, but it is a bit more complicated than that. Unfortunately, there doesn't seem to be any way to actually transmit information instantaneously with entangled particles. It's true that two entangled particles will undergo the same transitions at the same time, but since you can't predict in advance or control what transition will occur, it doesn't help you send any information to a person looking at the particle at the other end.
You're right, though, that it's about as secure a communication channel as you can get. It's actually the basis for quantum cryptography -- two people share a set of entangled photons, and they can guarantee that the measurements they make on them will be identical, giving them a shared secret key that no one can intercept. They still have to communicate over regular channels to actually send any real information, though.
About 1.4x10^-11 microns/zL on the highway, 8x10^-12 or so in the city.
Although I think that mileage is more commonly measured in zeptolitres per 100 Angstroms these days.
That is pretty funny -- You would think that Nature would know the difference between the German ess-tsett (ss) and Greek beta characters. They actually used 'ß' in the article.
Slashdot Mirror
That should be enough for anybody :)
Deleting a file in Unix simply means removing the file's entry from it's containing directory. This is why deleting a file in Unix requires write permission on the parent directory, and has nothing to do with the permissions on the file itself.
That's not quite true; it's not the only way out - you always have the option of negotiating with the original team for a different license under which to use the code.
There's nothing special in this regard about the GPL - it's the same thing with code under any other license: either use it under the existing license, negotiate a more suitable license, or write your own code.
In Vancouver, we drink the tap water for the free Prozac
No matter where you go, there's nothing to see but the view -- that's why the call it 'the view'
Looks like they disabled resolution for names at liftport.com - probably after the slashdotting they got today. It was working just fine when I checked the site out earlier
Yeah - it doesn't reach to the moon.
It goes 60,000 miles up, to some sort of geosynchronous tether point. If you want to go to the moon, you launch from the top of the elevator.
I didn't even realise you could read it the other way as well. Nice work there.
That is interesting -- what I meant, though, was that it must have been going faster than that when it left earth and turned its engines on for the first time, and unless it spent the whole trip decelerating from 11,200 m/s to just 2,737 m/s, that it didn't make much sense for its final velocity to be 2737m/s
Knowing Intel's history of sticking to consistent naming conventions, it'll more likely be a complete redesign, totally incompatible with BTX. and called BTX2.
Also, I believe that the original specification for drive power connectors called for an AMP part number, although Molex may be making a compatible part nowadays.
That seemed like a ridiculous amount of accelleration, though, so I checked further, and the spacecraft's final velocity is given by the esa as 2737 m /s, not km. Interestingly, that's actually less than the earth's escape velocity by a good margin. My best guess at this point, then, is that the 2737m/s figure is the velocity imparted to the craft by the engine, not counting the initial velocity it was given by the rocket it was strapped to.
In this case, its acceleration is just 2737m/s / (3648h * 3600s/h) = 2.08*10^-4 m/s^2
At that rate, it will cross it's first football field (91.4m) in 296s, and the next one in just 122s. (It goes by the last one in just 0.033s)
Without considering the constant acceleration, the 55-year figure is worthless -- you're calculating as if every 14 months, the craft came to a dead stop, and started accelerating again.
A rough calculation is that the craft started from 0 speed, and travelled ~384,000 km in ~415 days, giving a constant accelleration of 4.46 km / day / day.
The closest mars has been to us in recent years is about 55,760,000 km (last August.) At that rate of acceleration, a spacecraft could reach it in 5000 days, or about 13.7 years. Still not as fast as the 9 months you mentioned, but a far cry from 55 years.
Actually, HTML parsers consider any length of whitespace to be equivalent to a single space character. Typing two spaces after a period in an HTML document is a waste of time, as the browser will render it as a single space anyway.
So you think you vote directly for your president?
Also, regardless of what they claim about making official policy recommendations, they certainly do make recommendations:
(from the source document)
An inability to make official policy recommendations shouldn't be taken to imply that they can't express any opinion at all.
Usually? Which passwords? For what application? In-house or commercial software?
There's not much that you can say is usually true about passwords. They've been implemented thousands of times, by thousands of different developers, and I've seen plenty of systems where user passwords are stored, plaintext, in a database somewhere, or in a file readable (supposedly) by administrators.
There are good ways to do passwords, and bad ways to do passwords, and there're plenty of examples of both out there; certainly enough that I don't have any trouble believing the parent poster's claims.
Too bad that even the /. story mentions that they've already removed the oceanic points before giving you that number. It doesn't mention the 3000+ points which have already been recorded (though the first link in the story does), so there are actually some 16,000 points above sea level, which should represent a pretty wide range of scenery.
Well, inner classes actually did require a change to the core language (if not to the VM, then at least to the Java compiler).
Swing, Collections, JCE, and everything since have just been exensions to the Java class libraries. It's all still "Java2", and so Sun just increments the minor version number with each release.
(Java 5 sounds like a marketing decision to me, though)
You're right, though, that it's about as secure a communication channel as you can get. It's actually the basis for quantum cryptography -- two people share a set of entangled photons, and they can guarantee that the measurements they make on them will be identical, giving them a shared secret key that no one can intercept. They still have to communicate over regular channels to actually send any real information, though.
Here's the rest of it, BTW. (Not that I can see where any of it makes a levy on CD-R's illegal, but that's probably just me :)
Which is exactly why they're never going to catch on.
About 1.4x10^-11 microns/zL on the highway, 8x10^-12 or so in the city. Although I think that mileage is more commonly measured in zeptolitres per 100 Angstroms these days.
Hey! Someone put an 11 in there, too! What's going on here?
OTOH, at least they got "dementia" right :)