IANAL, but I always tough the "NO WARRANTY" disclamer as simply pro forma. I.E. it is useless and is there just for clarifying things.
If you brought the software, it should come with an warranty, if the software comes to you for free, or you pay just for the delivery, you shouldn't expect any warranty. You can't just throw your responsabilities out with a post-deal "contract" or the absense of one. At least most consumer laws I've saw work like that (I've never saw US' one).
The only thing that will put other companies out of selling Linux is if it is not profitable. As the only thing that will put them into selling Linux is if it is profitable.
Name calling has no place at the above paragraph, so, let people flame;)
Yep... And Debian has just released another stable, just a bit more than a year after the last one... And the new emacs is released... What is up with all those things?!?!?! Will we have perl6 and hurd released now?!?!?!
1 - Microsoft has still failed to make a big destruction "dividing and conquering" FOSS. They've by now bought 2 dying dsitros, and failed to persuade several others (RedHat included) to join them. While they are buying people, they won't be disruptive simply because people that are for sale are already useless.
2 - Microsoft can buy as much distros as they want, we can always fork new ones. If they fail to convince the community tho follow them, we'll keep working on what they don't want us to. Will MS buy all of us?
3 - Using the words 'subsides' and 'FOSS' at the same sentence is dangerous. You can easly say dumb things.
Mostly correct. But you don't want too much water mixed with the concret. It is good to keep the floor wet when building the basement, and it is good to do it on cloudy days. But you shouldn't blindly advise people to pour more water into the concret because there is an ideal amount, and too little is still better than too much.
Another nice way of keping the concret wet is covering it, so the water doesn't evaporate. That is expensive, but leads to a great streangth. (Of course, you should weight the costs and benefits.)
Also, it isn't jsut bad concret that causes cracks. New (not ever constructed) and badly compressed terrains are very common too.
Electricians think that Cat 5 wire can be treated like Romax, bend and crinked all you want
Electricians think you are supposed to "daisy chain" surround sound speaker wiring
Plumbers think the sink should go one place, electricians think the light should be centered over the sink, in a different place.
So, you must plan ahead where everything go. Project the conduits (yep use them... how can you not use them at the US?) before you start any construction. Have the plans ON PAPER so you can scream less. The eletrician only must to know on what conduit the wires are going, the plumber and contructors only need to know where to put the tubes/conduits, they don't need to know what will run inside them (of course, for the plumber it will be obvious), that make them less confused and more prone to folow your plans.
Usted debe hablar español.
Most building inspectors are not as smart as they think they are, and if you let them know this, you are screwed.
We don't have those problems around here, so I have no advice.
"If you want it to rain, just schedule for a concrete truck to show up at the time you want the rain to start."
Making your own concret is not that hard. Maybe it is cheaper, take a look, it depends a lot on the salary prices at your area.
Don't be afraid of buying equipment, make the calculations, sometimes buying new and using is cheaper than buying the products... And you get to resel them later.
"Dream big, but reality says you will spend most of your time screaming at contractors, construction workers and/or the bank. If it was easy, everyone would be doing it."
You'll scream a lot. Be prepared for it. Lots of things will go wrong by plain inconpentence, if you can be safe by a contract, do it (even if it's more expensive). Never pay before the work is done (and revised if you want to be safe).
Consult an architect, he can make your house much better and most times even cheaper. Think about hiring an engeneer if you want to do anything unusual or forecasts of how expensive it'll be. Hire someone who'll take the responsability for the construction, it seems expensive, but is worth it. And LEAVE THE BANK OUT OF IT, ask the archiect for something that you can grow if you are dreaming too hight.
"Sure, it may corrupt and lose your file, but it very rarely destroys the entire file system and lose the rest of the files on there."
Not at all. It very likely that it will destroy the filesystem. Just remember that all important information is stored toghether at the begining of the disk, and any bad write there will corrupt everything. And even don't start talking about empty space maintence, FAT disks have a tendency to shrink with time.
Compare that with ext (the original), that is also simple, and much more secure. The important data is spread through the disk, and losing part of it will just destroy only part of your files. It also manages empty space better and has less problems with fragmentation.
The reason FAT is used is because all OSes can read it.
"Remember how many times Windows 95 crashed? How many times of that did you get major FS damage? Compare and contrast with Ext2."
I remember it a bit different. From my memory, filesystem problems was one of the major problems leading to a format - reinstall. Of course, the OS didn't tell you it had filesystem problems, it just BSODed (can't find *****.sys or fatal operation while accessing virtual memory). Even Windows XP gets unstable if used over FAT. And don't forget about all those lost fragments, they don't just appear from nowhere.
The odds of a journal dealing with LaTeX depends on its area. While near all CS journals accept and lots require it, at humanities lots of journals can't even deal with it, and lots of academics never listened about LaTeX.
Stallman, however, indicated that the ban does not apply to products meant to be used primarily in business environments.
This is an interesting quote. It appears I'm going to have to research the GPL v3 a little bit further.
That is real. The rationale from the FSF is that corporate entities want restricted hardware for a variety of reasons*. So they'd better focusing their energy at the weak party (customers) that seems to sufer more from that.
* Maybe good reasons, maybe not. There is no judgment about that at the GPLv3 rationale. My oppinion is that they aren't good reasons (even more now, after the last draft) and their oppinion will change at future.
So, their plans B, C, D... are just like plan A: "you break our patents" FUD? That is exactly my point, they are playing that game for too long already, with not so good results.
"If it doesn't seem strange that we are able to talk about a "Novell punishment clause" in a license designed to keep things free, I think you have a limited definition of free.
GPLv3 won't punish Novell. Didn't you read the license? Of the FAQ? Or the rationale? Or anything? The terms that punish that deal don't retroact to deals as old as Novell's. What GPLv3 will do is avoiding any other deal like that.
"...it is impossible to imagine how any such system can be built in the future, regardless of technological progress."
That never applied to space travel and pocket computers, as it doesn't currently apply to antigravity, perpetual motion and sharks with lasers. Altough we are quite sure the last can't be done, we can at least imagine them.
Compacting your data before encription is fine (and even better before steanography)... But if you need more than one level of encription, you are using the wrong algorithm.
Using 2 or more passes of a weak algorithm won't (generaly) turn it into a strong one. You shouldn't count on it.
I'd like to think that smart people would rather say something like "I won't open that can of worms" instead of getting into hightly dangerous lottery-like crimes. But I can't really convince myself... I still think that smart people don't get caugth.
"As Gates did while playing poker in college, Microsoft always has more than one strategy that it's pursuing. There's almost certainly plan B, and its not going to be pretty."
Microsoft is playing that "You break our patents" game for a lot of time, with less than ideal results... That lets me wondering if there really is a plan B. Maybe there is no other possible plan for choosing now, since if there was one, we could trust Microsoft to find it.
When you try to win against a huge and very adaptative competitor (that is FOSS), you eventualy get out of cards. It is too early to be certain, but Microsotf may be on that situation.
Slashdot Mirror
I've already answared that post...
Microsoft can try all they want, we'll always have Debian.
IANAL, but I always tough the "NO WARRANTY" disclamer as simply pro forma. I.E. it is useless and is there just for clarifying things.
If you brought the software, it should come with an warranty, if the software comes to you for free, or you pay just for the delivery, you shouldn't expect any warranty. You can't just throw your responsabilities out with a post-deal "contract" or the absense of one. At least most consumer laws I've saw work like that (I've never saw US' one).
And funny... (Maybe a bit trollish too.)
3) Dell wants to see if it is profitable to sell Linux BEFORE it commits a lot of resources into it.
The only thing that will put other companies out of selling Linux is if it is not profitable. As the only thing that will put them into selling Linux is if it is profitable.
Name calling has no place at the above paragraph, so, let people flame ;)
Yep... And Debian has just released another stable, just a bit more than a year after the last one... And the new emacs is released... What is up with all those things?!?!?! Will we have perl6 and hurd released now?!?!?!
The world is a crazy place.
1 - Microsoft has still failed to make a big destruction "dividing and conquering" FOSS. They've by now bought 2 dying dsitros, and failed to persuade several others (RedHat included) to join them. While they are buying people, they won't be disruptive simply because people that are for sale are already useless.
2 - Microsoft can buy as much distros as they want, we can always fork new ones. If they fail to convince the community tho follow them, we'll keep working on what they don't want us to. Will MS buy all of us?
3 - Using the words 'subsides' and 'FOSS' at the same sentence is dangerous. You can easly say dumb things.
Carnot's theorem applies to any thermal machine. The actual implementation doesn't matter.
If not, one would break 2nd law by putting a thermal machine feeding a thermal pump.
Not exactly what you need it for, but where you need it for.
Mostly correct. But you don't want too much water mixed with the concret. It is good to keep the floor wet when building the basement, and it is good to do it on cloudy days. But you shouldn't blindly advise people to pour more water into the concret because there is an ideal amount, and too little is still better than too much.
Another nice way of keping the concret wet is covering it, so the water doesn't evaporate. That is expensive, but leads to a great streangth. (Of course, you should weight the costs and benefits.)
Also, it isn't jsut bad concret that causes cracks. New (not ever constructed) and badly compressed terrains are very common too.
So, you must plan ahead where everything go. Project the conduits (yep use them... how can you not use them at the US?) before you start any construction. Have the plans ON PAPER so you can scream less. The eletrician only must to know on what conduit the wires are going, the plumber and contructors only need to know where to put the tubes/conduits, they don't need to know what will run inside them (of course, for the plumber it will be obvious), that make them less confused and more prone to folow your plans.
We don't have those problems around here, so I have no advice.
Making your own concret is not that hard. Maybe it is cheaper, take a look, it depends a lot on the salary prices at your area.
Don't be afraid of buying equipment, make the calculations, sometimes buying new and using is cheaper than buying the products... And you get to resel them later.
You'll scream a lot. Be prepared for it. Lots of things will go wrong by plain inconpentence, if you can be safe by a contract, do it (even if it's more expensive). Never pay before the work is done (and revised if you want to be safe).
Consult an architect, he can make your house much better and most times even cheaper. Think about hiring an engeneer if you want to do anything unusual or forecasts of how expensive it'll be. Hire someone who'll take the responsability for the construction, it seems expensive, but is worth it. And LEAVE THE BANK OUT OF IT, ask the archiect for something that you can grow if you are dreaming too hight.
Now you gota be kidding...
Not at all. It very likely that it will destroy the filesystem. Just remember that all important information is stored toghether at the begining of the disk, and any bad write there will corrupt everything. And even don't start talking about empty space maintence, FAT disks have a tendency to shrink with time.
Compare that with ext (the original), that is also simple, and much more secure. The important data is spread through the disk, and losing part of it will just destroy only part of your files. It also manages empty space better and has less problems with fragmentation.
The reason FAT is used is because all OSes can read it.
I remember it a bit different. From my memory, filesystem problems was one of the major problems leading to a format - reinstall. Of course, the OS didn't tell you it had filesystem problems, it just BSODed (can't find *****.sys or fatal operation while accessing virtual memory). Even Windows XP gets unstable if used over FAT. And don't forget about all those lost fragments, they don't just appear from nowhere.
The odds of a journal dealing with LaTeX depends on its area. While near all CS journals accept and lots require it, at humanities lots of journals can't even deal with it, and lots of academics never listened about LaTeX.
That is real. The rationale from the FSF is that corporate entities want restricted hardware for a variety of reasons*. So they'd better focusing their energy at the weak party (customers) that seems to sufer more from that.
* Maybe good reasons, maybe not. There is no judgment about that at the GPLv3 rationale. My oppinion is that they aren't good reasons (even more now, after the last draft) and their oppinion will change at future.
Thanks for the post. I've being trying to say the same for a while, but I'd never be able to say it that well.
Just to complement:
Well, DRM itself is nonsensical. The least one can expect from anyone that pushes for DRM is more nonsense.
Didn't you know that Duke Nuken Forever is being built with proprietary drivers to run on Hurd?
Ok, very cliché... But I couldn't resist the urge.
(The best part is that proprietary drivers on Hurd may be completely clear. Not even a gray zone, like Linux.)
They also told us that it has a fast memory controller and large I/O words. Those matter too.
Ok, now I stopped laugthing... :(
Do you know if it is really done that way on practice (they must overcome some economical problems to give each player it set of keys)?
So, their plans B, C, D... are just like plan A: "you break our patents" FUD? That is exactly my point, they are playing that game for too long already, with not so good results.
GPLv3 won't punish Novell. Didn't you read the license? Of the FAQ? Or the rationale? Or anything? The terms that punish that deal don't retroact to deals as old as Novell's. What GPLv3 will do is avoiding any other deal like that.
I don't think it is funny! Not even a bit!!!
I'm waiting for the first key from a hardware player to get released... Then I'll laugth. A lot.
You missed that part:
That never applied to space travel and pocket computers, as it doesn't currently apply to antigravity, perpetual motion and sharks with lasers. Altough we are quite sure the last can't be done, we can at least imagine them.
Since 0xFF = -1, I don't think that is agood idea.
Compacting your data before encription is fine (and even better before steanography)... But if you need more than one level of encription, you are using the wrong algorithm.
Using 2 or more passes of a weak algorithm won't (generaly) turn it into a strong one. You shouldn't count on it.
I'd like to think that smart people would rather say something like "I won't open that can of worms" instead of getting into hightly dangerous lottery-like crimes. But I can't really convince myself... I still think that smart people don't get caugth.
Microsoft is playing that "You break our patents" game for a lot of time, with less than ideal results... That lets me wondering if there really is a plan B. Maybe there is no other possible plan for choosing now, since if there was one, we could trust Microsoft to find it.
When you try to win against a huge and very adaptative competitor (that is FOSS), you eventualy get out of cards. It is too early to be certain, but Microsotf may be on that situation.