Interesting - I'd never thought of ISO9660 as a versioning FS but it is, of course.
VMS was the first OS I used extensively, and that versioning feature was something I missed when I switched to Unix machines. From memory, our VERSION_LIMIT was set to 30 by default (We were on a VAX cluster with a lot of space and not many users).
The VMS filesystem (Files 11) was an evolution of earlier DEC filesystems and had versioning buit in from the start. There's also a more user-oriented versioning filesystem which has been in development for Linux for the past few years. http://sourceforge.net/projects/versionfs/
there were certainly some old HDDs which could stall in a certain way and 'walk' across the floor,
Our local uni had a couple of Ferranti drum drives that would regularly walk around their bays. They looked like top-loading washing machines. Apparently, bolting them to the floor would have reduced the life of the bearings
they can do it the old fashioned way -- with their god damn eyes.
Then they can take those god damn eyes out, show them to the hit man and tell him to execute the last motherfucking sonofabiatch they were been looking at.
It's silly to think that developers should have full access to every single internal structure or API call.
"Tenet 6. APIs....Going forward, Microsoft will ensure that all the interfaces within Windows called by any other Microsoft product, such as the Microsoft Office system or Windows Live(TM), will be disclosed for use by the developer community generally."
http://www.microsoft.com/presspass/newsroom/winxp/ windowsprinciples.mspx
6. APIs....going forward, Microsoft will ensure that all the interfaces within Windows called by any other Microsoft product, such as the Microsoft Office system or Windows Live(TM), will be disclosed for use by the developer community generally. That means that anything that Microsoft's products can do in terms of how they plug into Windows, competing products will be able to do as well.
no one ever considers the idea that maybe Microsoft is trying to actually change it's old business practices.
Maybe they are, but you wouldn't know it from these "commandments".
Numbers 1-4 are already a fait accompli from a technical point of view. There's been nothing to stop OEMs or customers from adding their own software as defaults to any version of Windows, apart from Microsoft's shady business practices. Maybe Vista will make the process simpler, but complexity was never what stopped the Dell/Gateway/Toshiba etc of the world from changing defaults.
Numbers five and six are significant, if they happen and are not bypassed in practice, but it's really just Microsoft saying "We're not going to keep breaking the law."
Number seven and eight are non-sequiturs. Were they ever planning to incorporate Windows Live into their OS? Given the security implications, it would be an insane thing to do - so maybe they were... And what about not blocking access to non-MS websites? Gee, thanks guys. I'm glad you've decided to let us keep our Slashdot. Seriously, what the hell were they planning to do that would make it necessary to make that a core tenet?
Nine, they're saying they'll stop breaking the law again.
Ten and eleven are sneaky. They'll license communications protocols and patents "on commercially reasonable terms". Given the extremely flexible nature to the term "reasonable" you can pretty much bet they'll use the licensing terms to block all real competitors, particularly FOSS.
Number twelve, well we've seen from their behavior with ODF that Microsoft is committed to standards, as long as they're their own, and as long as they can retract the compliance if it gets in the way of their format lockin in the future.
All in all, there's a lot implied by the tenets, but the only ones which actually commit Microsoft to any changes are the ones required by law. The rest are carefully phrased to allow plausible deniability. Note also that they've said nothing about their key lockin tool - file formats. If Microsoft were serious about fair play they'd commit, in a legally binding way, to maintain fully open protocols, formats and APIs. They have not done so, so these "tenets" are nothing more than yet more spin and misdirection.
In what universe is an extra firefighter not practical?
In ours, sadly. This thing is a nice concept, but TFA says it needs 100bar water. The normal pressures for firefighting are around 8-20bar, so it'd take specialised pumping equipment and hoses for it to work.
That's not a showstopper of course, but it'd probably be cheaper just to build a conventional electric robot like Quinetiq's Talon based firefighting bot, which can pull conventional 63mm fire hoses.
Slashdot Mirror
You could build a nuclear reactor to power the waste disposal facility.
Or you can use the Dutch version where the rudder is at the other end.
VMS was the first OS I used extensively, and that versioning feature was something I missed when I switched to Unix machines. From memory, our VERSION_LIMIT was set to 30 by default (We were on a VAX cluster with a lot of space and not many users).
There are a few in regular use; http://www.linuxdevices.com/links/LK6129039469.htm l
The VMS filesystem (Files 11) was an evolution of earlier DEC filesystems and had versioning buit in from the start. There's also a more user-oriented versioning filesystem which has been in development for Linux for the past few years.
http://sourceforge.net/projects/versionfs/
Our local uni had a couple of Ferranti drum drives that would regularly walk around their bays. They looked like top-loading washing machines. Apparently, bolting them to the floor would have reduced the life of the bearings
Headline:
So where's she from then?
Then they can take those god damn eyes out, show them to the hit man and tell him to execute the last motherfucking sonofabiatch they were been looking at.
People who complain about stereotypes are always prissy whiners.
"Tenet 6. APIs. ...Going forward, Microsoft will ensure that all the interfaces within Windows called by any other Microsoft product, such as the Microsoft Office system or Windows Live(TM), will be disclosed for use by the developer community generally."
/ windowsprinciples.mspx
http://www.microsoft.com/presspass/newsroom/winxp
Stuck a pineapple up it.
Nah, you gave it a good try, so you get the credit AND you get to keep the extra O2. Just don't try to make my beer froth with that CO of yours.
Actually, they use carbon monoxide for that.
Oh dear, somebody who doesn't understand how the internets work. Here, this is a good start. http://www.w3.org/
Yeah, this one didn't last long, did it?
Nah, the Italian team won by diving down.
/bitter Australian...
Except that energy hitting the solar cells now isn't hitting the roof. You should be able to turn the aircon off...
Do you mean in Congress, the Senate or the internets?
Probably not a lot.
You can do it the other way around with Colinux - http://www.colinux.org/
Maybe they are, but you wouldn't know it from these "commandments".
Numbers 1-4 are already a fait accompli from a technical point of view. There's been nothing to stop OEMs or customers from adding their own software as defaults to any version of Windows, apart from Microsoft's shady business practices. Maybe Vista will make the process simpler, but complexity was never what stopped the Dell/Gateway/Toshiba etc of the world from changing defaults.
Numbers five and six are significant, if they happen and are not bypassed in practice, but it's really just Microsoft saying "We're not going to keep breaking the law."
Number seven and eight are non-sequiturs. Were they ever planning to incorporate Windows Live into their OS? Given the security implications, it would be an insane thing to do - so maybe they were... And what about not blocking access to non-MS websites? Gee, thanks guys. I'm glad you've decided to let us keep our Slashdot. Seriously, what the hell were they planning to do that would make it necessary to make that a core tenet?
Nine, they're saying they'll stop breaking the law again.
Ten and eleven are sneaky. They'll license communications protocols and patents "on commercially reasonable terms". Given the extremely flexible nature to the term "reasonable" you can pretty much bet they'll use the licensing terms to block all real competitors, particularly FOSS.
Number twelve, well we've seen from their behavior with ODF that Microsoft is committed to standards, as long as they're their own, and as long as they can retract the compliance if it gets in the way of their format lockin in the future.
All in all, there's a lot implied by the tenets, but the only ones which actually commit Microsoft to any changes are the ones required by law. The rest are carefully phrased to allow plausible deniability. Note also that they've said nothing about their key lockin tool - file formats. If Microsoft were serious about fair play they'd commit, in a legally binding way, to maintain fully open protocols, formats and APIs. They have not done so, so these "tenets" are nothing more than yet more spin and misdirection.
So does that make 36 tenets in total?0 7/20/2047250 7 218&tid=109
http://developers.slashdot.org/article.pl?sid=06/
http://it.slashdot.org/article.pl?sid=06/07/19/21
In ours, sadly. This thing is a nice concept, but TFA says it needs 100bar water. The normal pressures for firefighting are around 8-20bar, so it'd take specialised pumping equipment and hoses for it to work.
That's not a showstopper of course, but it'd probably be cheaper just to build a conventional electric robot like Quinetiq's Talon based firefighting bot, which can pull conventional 63mm fire hoses.
I altered my MySpace page with a text editor, you insensitive clod!
Are you going to spank me now?
Somebody should hook up a generator to that puppy...