As someone who's running a dual Opteron setup with Gentoo right now, this is pretty interesting. The noise in a standard server case is pretty awful.
Futhermore, while the problem with heat does not seem to be so acute with Opterons as it is with P4s and Xeons, it must be said that Opterons seem to lose to Xeons in floating point performance. That was a great disappointment to me since I run floating point intensive simulations (or more precisely prototypes of simulations to be run later on real, supercomputer-grade hardware) and because most of the Intel's advantage seems to come from the compiler and not from the hardware per se.
I already screen my cellphone calls. If the caller ID is "unknown" (which is the case for most telemarketers) or if it is a foreign number that I don't recognize, I won't answer it.
If telemarketers leaving voice mail becomes a problem, I'm sure that's quickly addressed by the service provider (=store no voice mail from abroad or from unknown numbers).
IBM doesn't give a ripshit about "the community" or anyone/thing else other than the Almighty Dollar...If IBM felt that it was in their short-term best interest to wipe Linux off of the face of the Earth, they would.
You've got it right.
In spite of what the participants in this OSS-IBM fantasy lovefest would like to believe, the "enemy of my enemy"-logic works out in the long term only if you're approximately in the same league as your temporary ally.
IBM can - and will - devour open source when it profits them the most.
I quote myself: "why the hell should you be
made to release it".
If Sun wants to open source Solaris 10, more power to them. I am, however, disturbed by the Slashdot mentality that open source and open protocols are the only way to go and that anyone who doesn't follow the suit is an evil monopolist. That's blind faith. That's religion. That's coercion.
There would be absolutely no open source license which would be compatible with a scheme in which Microsoft required that DRM...Because they would apply an NDA clause to it and say you can't give out the source, because someone could a) see something that is patended, b) remove the code to actually obey it, or c) tell someone how weak the security actually is.
And? Buy the license and close the source like NVidia does.
You are assuming that open source and full disclosure of all protocols is the Right Thing to Do. I don't see it that way and I'm sure Microsoft and plenty of other people don't see it that way.
If you develop a proprietary protocol that gets extremely popular, why the hell should you be made to release it to the public domain?
Wanna reverse engineer the USB to allow for interoperability?...Can't afford a new USB device?... Bought yours on sale?
How about licensing the damn scheme? As long as you have the option of buying the license, Microsoft can't be accused of exercising an illegal monopoly.
But what if your own OS license won't allow you to comply with Microsoft's terms? Well, too bad then. Just remember that it's your own license that's stopping you - not Microsoft.
Looks like Adobe Acrobat 6.0 (not the reader) still doesn't work with the Firefox - even after all Adobe upgrades and switching fast view and show-in-browser options off.
I wonder why Mozilla and Acrobat co-operate just fine?
Well, it was most certainly a joke. However, in this world that's quickly turning into a libertarian dream (i.e. a nightmare for the rest of us) of uncontrolled capitalism and neo-feudalism where consumers play the role of serfs, it's kind of starting to make sense.
I wouldn't be surprised to see that in a decade being a congressman or an MP will be officially regarded as just another profession in the same way as being a doctor or a lawyer is. They'll charge a fee for their services and the more you pay the more you'll get.
So you can't be bothered to look through the top 5 search results in Google (which are pretty useful for this question if you use something like "linux dvd burn" as search string)
"Pretty useful"? I don't think so. Do you see the solution there? I don't. Believe me, I do check Google first, but if the excerpts on the first search page don't show much promise I'm not going to go about clicking on the links.
search through hundreds of slashdot comments?
You ask a question on/. or usenet and see if anyone replies to your post. What's the problem?
I for one am sick and tired of the elitist RTFM or TTFG (try the fucking/friendly google) attitude. It's all about ego and making other people to re-invent the wheel.
I ask questions on public "forums" like/. or usenet because I really can't be bothered to figure out what niche forums I should be searching in the first place - especially when I am pretty sure that someone else on/. has already found the answer.
You don't have to answer any questions you don't feel like answering, but don't bash people for asking on-topic questions.
Can you read the document on the LCD screen without going blind or getting severe eye strain?
Ah, so I (and my friend) should just stop pointing out problems like this and be grateful for the free office suite we've been generously given?
No, it's not good enough. It's nowhere near good enough. When you spend two thirds of your typical workday writing and reading documents on screen it's imperative that you've got a high end screen (which I've got) and that the fonts are properly anti-aliased.
In short, should I want to explore switching from Windows to Linux this issue would be a real showstopper.
And yes, I could get around the problem by buying a CRT monitor but why the hell would I want to do that when the problem is with software in the first place?
Is Linux OO capable of rendering fonts using sub-pixel hinting (for LCD screens), yet?
A friend of mine with an LCD screen had trouble with the fonts and although his desktop was nicely anti-aliased Open Office stubborny refused to show anti-aliased fonts.
I bet it was fun to sneeze or blow your nose after that one!
For someone who as a student spent countless of hours reading alt.tasteless instead of working on programming projects, I was kind of disappointed by the results.
More recently I had eye surgery (detached retina) and after waking up, I asked for a video of my procedure. The damn doctor claimed that they won't give out any tapes. I was hoping to see how they popped out my eye, cut it up and further brutalized it with a cryogenic metal prod before sewing it all up together again. Curses! Foiled again!
Yes, that disturbing thought occurred to me as well when I was first shown the needles...
I don't know if it was supervisor's intention to let the trainee to do the actual puncturing. As I said, he took over the procedure after trainee's four failed attempts and he did the puncturing as well - fortunately.
I once had infected sinuses and they were treated by puncturing the nasal wall with a damn long needle and flushing out the crap that had accumulated in the cavities beyond.
Prior to the operation, local anesthetic was of course applied on the nasal wall. Incidentally, this last procedure was also conducted with a damn long needle shoved straight up my nose and it hurt like hell each time they did it. Yes, each time they did it. A trainee tried to do it four times until his supervisor finally took over and applied it successfully.
Fortunately the actual puncturing of the nasal wall was unpleasant (lots of cracking and crunching sounds when the needle is pushed up your nose) but completely painless.
Sure, if the kernel has been modified, then GPL dictates that the modifications must be released.
However, if you don't modify the kernel or any of the tools you don't have to release the source code of your application. My bet is that they went the NVidia road: a binary module.
I've never understood the argument that going slow is more dangerous than going faster. The only way low speed limits can be a danger is that the roads are crowded with road-raging hotheads who have way too high an opinion of their driving skills and who're hellbent on passing everybody.
When I still drove a car (gave it up for more greener options: bicycle and public transporation), I was perfectly happy with a 40 mph limit on our highways and 15 mph in the urban areas. The only hazards I ever ran into were elks and the idiots who just had to speed in order at their destination a few minutes early.
Futhermore, while the problem with heat does not seem to be so acute with Opterons as it is with P4s and Xeons, it must be said that Opterons seem to lose to Xeons in floating point performance. That was a great disappointment to me since I run floating point intensive simulations (or more precisely prototypes of simulations to be run later on real, supercomputer-grade hardware) and because most of the Intel's advantage seems to come from the compiler and not from the hardware per se.
If telemarketers leaving voice mail becomes a problem, I'm sure that's quickly addressed by the service provider (=store no voice mail from abroad or from unknown numbers).
You've got it right.
In spite of what the participants in this OSS-IBM fantasy lovefest would like to believe, the "enemy of my enemy"-logic works out in the long term only if you're approximately in the same league as your temporary ally.
IBM can - and will - devour open source when it profits them the most.
I quote myself: "why the hell should you be made to release it".
If Sun wants to open source Solaris 10, more power to them. I am, however, disturbed by the Slashdot mentality that open source and open protocols are the only way to go and that anyone who doesn't follow the suit is an evil monopolist. That's blind faith. That's religion. That's coercion.
mankinds best interest
Uh... ok. Right. Whatever.
Yes. In theory. I believe in realpolitik.
You missed my point. That's a problem with the license that SUSE and Mandrake chose - not with the Microsoft's license or with the way they operate.
You are perfectly free to license their protocol. Period. It's just too bad if you can't license the protocl because of the license YOU chose.
Microsoft is playing by the book here. If you think the rules protect "monopolists", you should lobby to change the rules.
And? Buy the license and close the source like NVidia does.
You are assuming that open source and full disclosure of all protocols is the Right Thing to Do. I don't see it that way and I'm sure Microsoft and plenty of other people don't see it that way.
If you develop a proprietary protocol that gets extremely popular, why the hell should you be made to release it to the public domain?
Constitution can always be rewritten.
Ever heard of WTO and the harmonization of IP laws?
How about licensing the damn scheme? As long as you have the option of buying the license, Microsoft can't be accused of exercising an illegal monopoly.
But what if your own OS license won't allow you to comply with Microsoft's terms? Well, too bad then. Just remember that it's your own license that's stopping you - not Microsoft.
I hate to download yet again all 11 megabytes just because of a single bug.
I wonder why Mozilla and Acrobat co-operate just fine?
I wouldn't be surprised to see that in a decade being a congressman or an MP will be officially regarded as just another profession in the same way as being a doctor or a lawyer is. They'll charge a fee for their services and the more you pay the more you'll get.
Let's try googling for DVD burning linux free .
"Pretty useful"? I don't think so. Do you see the solution there? I don't. Believe me, I do check Google first, but if the excerpts on the first search page don't show much promise I'm not going to go about clicking on the links.
search through hundreds of slashdot comments?
You ask a question on /. or usenet and see if anyone replies to your post. What's the problem?
I for one am sick and tired of the elitist RTFM or TTFG (try the fucking/friendly google) attitude. It's all about ego and making other people to re-invent the wheel.
I ask questions on public "forums" like /. or usenet because I really can't be bothered to figure out what niche forums I should be searching in the first place - especially when I am pretty sure that someone else on /. has already found the answer.
You don't have to answer any questions you don't feel like answering, but don't bash people for asking on-topic questions.
Why is the lack of sub-pixel AA then listed as an issue in the Open Office bug database?
Ah, so I (and my friend) should just stop pointing out problems like this and be grateful for the free office suite we've been generously given?
No, it's not good enough. It's nowhere near good enough. When you spend two thirds of your typical workday writing and reading documents on screen it's imperative that you've got a high end screen (which I've got) and that the fonts are properly anti-aliased.
In short, should I want to explore switching from Windows to Linux this issue would be a real showstopper.
And yes, I could get around the problem by buying a CRT monitor but why the hell would I want to do that when the problem is with software in the first place?
A friend of mine with an LCD screen had trouble with the fonts and although his desktop was nicely anti-aliased Open Office stubborny refused to show anti-aliased fonts.
Searching OpenOffice.org revealed this:
The issue has been classified as "an enhancement", has 3 votes and thus won't be fixed anytime soon!
I suppose everyone running OO on Linux (except for those three persons) is using a traditional monitor and couldn't care less about sub-pixel hinting.
For someone who as a student spent countless of hours reading alt.tasteless instead of working on programming projects, I was kind of disappointed by the results.
More recently I had eye surgery (detached retina) and after waking up, I asked for a video of my procedure. The damn doctor claimed that they won't give out any tapes. I was hoping to see how they popped out my eye, cut it up and further brutalized it with a cryogenic metal prod before sewing it all up together again. Curses! Foiled again!
I don't know if it was supervisor's intention to let the trainee to do the actual puncturing. As I said, he took over the procedure after trainee's four failed attempts and he did the puncturing as well - fortunately.
Prior to the operation, local anesthetic was of course applied on the nasal wall. Incidentally, this last procedure was also conducted with a damn long needle shoved straight up my nose and it hurt like hell each time they did it. Yes, each time they did it. A trainee tried to do it four times until his supervisor finally took over and applied it successfully.
Fortunately the actual puncturing of the nasal wall was unpleasant (lots of cracking and crunching sounds when the needle is pushed up your nose) but completely painless.
Wasn't 9th the most overturned appeals court?
However, if you don't modify the kernel or any of the tools you don't have to release the source code of your application. My bet is that they went the NVidia road: a binary module.
Why should they publish it?
Check out the SecurityFocus Incidents-mailing list for details.
When I still drove a car (gave it up for more greener options: bicycle and public transporation), I was perfectly happy with a 40 mph limit on our highways and 15 mph in the urban areas. The only hazards I ever ran into were elks and the idiots who just had to speed in order at their destination a few minutes early.