I've had problems with even "good" (though poorly shielded) cables just being near power cables or other sources of electromagnetic noise.
If DVI is possible with your monitor/video card, try that.
"...first step would be to simply reformat the hard drive. If you can't do that - good luck..."
Ditto. I feel bad for people who balk at re-formatting their hard drive. They always ask me if there is an easier way. Unfortunately, reformatting is the easy way. Trying to clean out rootkits and nasty spy/adware requires a lot of knowledge, even with the excellent free tools available. (Thanks, sysinternals, lavasoft and safer-networking.org).
The engineering company I work for uses MediaWiki as well. It is perfect for storing all sorts of random information. All those "knowledge management" apps that try to categorize all your info in one fixed structure always end up being more work to maintain, and there's always information that just doesn't fit into the system. Wikis are easier to organize (therefore easier to get information out of) and easier to get information into as well. I tried some of the other Wikis, but MediaWiki ended up being easier to install and more powerful to boot.
"Controversies aside, JBoss has emerged as a credible alternative to commercial J2EE App Servers..."
JBoss is not an alternative to commercial J2EE App Servers, because it is a commercial J2EE App Server. It's an alternative to proprietary J2EE App Servers.
Some people might think I'm being pedantic, but I think that the distinction is important.
The gist of it is that no further evolution will occur unless humans can be separated into isolated groups.
No. The article doesn't say that (nor is it true). I think what the original poster meant to say is that no further speciation will occur unless humans are seperated from each other. Any biologist could have told you that.
I can't claim to go all the way back to ZDTV, but for more than a year I watched TSS nearly every day. G4 completely ruined it though. I'm sure that some marketoid decided that they would have "synergy" or some such shit. I actually liked Alex, but the stupid crap that they would cover on that show just got on my nerves. Damn you, "G4: TV for Gamers".
I'll add that I think that the best distro to learn the guts of Linux on is Gentoo. Go the full compile-it-yourself route. There are easy to follow, step by step instructions, and they take the time to tell you why you're doing everything. By the time you have it installed (and it will take a while), you'll be a virtual expert on Linux.
Of course, you shouldn't limit yourself to just one distro, and Gentoo probably isn't the easiest to manage. I like Debian stable for server things because it is so easy to keep up to date.
Browsercam is a good resource. Of course, you can't test functionality with it, but your layout is where you will run into the most browser bugs.
Ultimately, the best route I've found is to stick like glue to the standards and don't use nested tables or rely on Javascript.
As long as you stick valid HTML 4.01 or XHTML and CSS, the rendering bugs for IE5+/Win and IE5+/Mac are pretty well known. Older browsers can easily be sent plain text or minimal styling with media or @import hacks. Spend a lot of time lurking on the CSS-d mailing list.
Where do you find out about the "well-known" rendering bugs? There are a ton of sites out there about them, but I like PositionIsEverything and the CSS-Discuss Wiki.
Re:Other DVRs work
on
VoIP Questioned
·
· Score: 3, Informative
The TiVo thing is patently false. TiVos do work without a phone line for initial setup - I know, that's how I set mine up.
That's stupid - there's no such thing as black box code. If a computer can read it, a person can use a computer to read it. There's no such thing as black box code. That's the "soft" part of software.
In order to have "black box" information of any kind (code or no), you have to have some physical device that does not let that information out. A "black box" that can't be opened without destroying the information.
So they're going to make a law that requires "black box code", but there is no such thing. Brilliant.
I work for a small company that only has three full-time employees (including me). I use two Debian boxes (cheap-o machines that are just retired desktops with some big cheap IDE hard drives in them) running Samba. I use the rsync mirroring technique I found here.
One box is the "live" server and the other mirrors the live server every night. If the main server dies (which happened once - power supply failure), I can "promote" the backup server by changing one line in its Samba configuration. As a bonus, the backup server keeps "snapshots" back a week or two.
Here's a possible (and I think most likely) situation for you:
Person "A" is playing some game with his cell phone in his pocket and has forgotten to lock the key pad. He accidentally dials person "B" while he's talking about bombs or something in his video game. Person "B" doesn't realize what happened and makes a fuss. The cops get called in and track down person "A". Felony charges ensue.
If that was the case, then I don't think a crime actually occured - if anything, person "B" or the restaurant manager are at fault. Did they actually talk to the guy on the phone? Did they try to call him back? I would have looked for a bit more confirmation before I called the cops and evacuated the restuarant.
Microsoft doesn't actually have anything to loose by giving this patch to pirates of its operating system. For one thing, if they had less pirates they would loose valuable market share (their greatest asset). The number of pirates who would actually buy a copy of Windows to get SP2 is negligable, so it's not like they're giving up some big potential revenue stream. Factor in the reduction in bad press that MS gets every time there's a worm and Microsoft's continued policy of supporting pirated copies of Windows makes all the sense in the world. They'd have to be stupid to do otherwise.
Of course the curtailing of various worms is nice for the Internet at large. Just because an action serves Microsoft's interest doesn't mean that it can't serve everyone else's interests too. (Except for the fact that it perpetuates Microsoft's choke-hold on the IT industry, but since when did we worry about the long-term good when a short-term good is in front of us?)
I'm sure that the extra bandwidth will cost Microsoft thousands of dollars, but it's cheap PR for them.
Maybe I'm not the target of this particular troll, since I don't believe that there's any "conspiracy". Microsoft is just doing what is best for Microsoft. That's what it always does (and should do - it is a business after all).
Apache 2.x can be run in multi-threaded mode, but it can still do multiprocess just as well (if not better) than 1.3.x.
The multi-thread capabilities of Apache 2 in no way detract from its multi-process capabilities. You can run in just multi-thread mode, just multi-process mode or any balance between the two that you want. The multi-thread capabilities were added to address performance problems on platforms that were not very efficient at spawning new processes (Windows and others).
If there are still some PHP libraries that are not thread-safe (and you need those libraries), just don't run in multi-threaded mode. If you're on Linux, that's probably what you were doing anyway. (If you're on Windows - well, why the hell are you running a production server on Windows?)
Of course, there are valid reasons to stick with 1.3.x. For example:
No real point in transitioning existing installations - 1.3.x is probably good enough that it's not worth the hassle to change to 2.x.
Your vendor is behind the times (I found that Debian's support for 2.x isn't as good as it is for 1.3.x yet).
I'm sure there is a third reason I can't remember.
In general, I follow the "2.x is default for new installations" philosophy.
The funny thing about trademark law is that you can loose your trademark if you don't send out threatening letters like our FightForRock admin got. Combine this with a company that has a trademark that is very close to a generic term (and generic terms are not trademarkable) and you get a legal department that is pretty much forced to by hyper-paranoid about trademarks. This leads to a sort of little-big-man syndrome, where the company acts like it thinks everyone is picking on it.
So HardRadio has a chip on it's shoulder. FightForRock accidentally stepped on their shoes, and now HardRadio has been forced into a legal pissing contest.
What do you do when the short guy gets all pissy at you for no good reason? You can either kick his scrawny ass (which is usually more trouble than it's worth) or you can smile and apologise for whatever minor thing set him off and be on your way. Those are pretty much FightForRock's options. I don't see that HardRadio really has a case, but it's probably more trouble than it's worth to kick their asses in court.
-------
P.S. This post was designed specifically to propogate negative stereotypes about short people. Tall Power!
Why are they going through all this trouble? Don't they know that CSS was broken years ago? Haven't they ever downloaded Handbrake?
I've had problems with even "good" (though poorly shielded) cables just being near power cables or other sources of electromagnetic noise. If DVI is possible with your monitor/video card, try that.
Ditto. I feel bad for people who balk at re-formatting their hard drive. They always ask me if there is an easier way. Unfortunately, reformatting is the easy way. Trying to clean out rootkits and nasty spy/adware requires a lot of knowledge, even with the excellent free tools available. (Thanks, sysinternals, lavasoft and safer-networking.org).
The engineering company I work for uses MediaWiki as well. It is perfect for storing all sorts of random information. All those "knowledge management" apps that try to categorize all your info in one fixed structure always end up being more work to maintain, and there's always information that just doesn't fit into the system. Wikis are easier to organize (therefore easier to get information out of) and easier to get information into as well. I tried some of the other Wikis, but MediaWiki ended up being easier to install and more powerful to boot.
What the heck database are you using? Any SQL database engine worth its salt has count(*) properly optimized.
JBoss is not an alternative to commercial J2EE App Servers, because it is a commercial J2EE App Server. It's an alternative to proprietary J2EE App Servers.
Some people might think I'm being pedantic, but I think that the distinction is important.
I love SQL and relational databases myself, but what would be the point of using such a system in this case?
No. The article doesn't say that (nor is it true). I think what the original poster meant to say is that no further speciation will occur unless humans are seperated from each other. Any biologist could have told you that.
So - AOL successfully thwarted a potential sexual predator... what's the lawsuit about?
Don't forget Kingdom of Loathing.
Thanks for the link! The program is very nice. But who mirrored the source code?
I can't claim to go all the way back to ZDTV, but for more than a year I watched TSS nearly every day. G4 completely ruined it though. I'm sure that some marketoid decided that they would have "synergy" or some such shit. I actually liked Alex, but the stupid crap that they would cover on that show just got on my nerves. Damn you, "G4: TV for Gamers".
Um - isn't that just Jabber?
I totally second this.
I'll add that I think that the best distro to learn the guts of Linux on is Gentoo. Go the full compile-it-yourself route. There are easy to follow, step by step instructions, and they take the time to tell you why you're doing everything. By the time you have it installed (and it will take a while), you'll be a virtual expert on Linux.
Of course, you shouldn't limit yourself to just one distro, and Gentoo probably isn't the easiest to manage. I like Debian stable for server things because it is so easy to keep up to date.
Synergy
They should have called the movie Bourne Again.
Browsercam is a good resource. Of course, you can't test functionality with it, but your layout is where you will run into the most browser bugs.
Ultimately, the best route I've found is to stick like glue to the standards and don't use nested tables or rely on Javascript.
As long as you stick valid HTML 4.01 or XHTML and CSS, the rendering bugs for IE5+/Win and IE5+/Mac are pretty well known. Older browsers can easily be sent plain text or minimal styling with media or @import hacks. Spend a lot of time lurking on the CSS-d mailing list.
Where do you find out about the "well-known" rendering bugs? There are a ton of sites out there about them, but I like PositionIsEverything and the CSS-Discuss Wiki.
The TiVo thing is patently false. TiVos do work without a phone line for initial setup - I know, that's how I set mine up.
That's stupid - there's no such thing as black box code. If a computer can read it, a person can use a computer to read it. There's no such thing as black box code. That's the "soft" part of software.
In order to have "black box" information of any kind (code or no), you have to have some physical device that does not let that information out. A "black box" that can't be opened without destroying the information.
So they're going to make a law that requires "black box code", but there is no such thing. Brilliant.
I work for a small company that only has three full-time employees (including me). I use two Debian boxes (cheap-o machines that are just retired desktops with some big cheap IDE hard drives in them) running Samba. I use the rsync mirroring technique I found here.
One box is the "live" server and the other mirrors the live server every night. If the main server dies (which happened once - power supply failure), I can "promote" the backup server by changing one line in its Samba configuration. As a bonus, the backup server keeps "snapshots" back a week or two.
Here's a possible (and I think most likely) situation for you:
Person "A" is playing some game with his cell phone in his pocket and has forgotten to lock the key pad. He accidentally dials person "B" while he's talking about bombs or something in his video game. Person "B" doesn't realize what happened and makes a fuss. The cops get called in and track down person "A". Felony charges ensue.
If that was the case, then I don't think a crime actually occured - if anything, person "B" or the restaurant manager are at fault. Did they actually talk to the guy on the phone? Did they try to call him back? I would have looked for a bit more confirmation before I called the cops and evacuated the restuarant.
Microsoft doesn't actually have anything to loose by giving this patch to pirates of its operating system. For one thing, if they had less pirates they would loose valuable market share (their greatest asset). The number of pirates who would actually buy a copy of Windows to get SP2 is negligable, so it's not like they're giving up some big potential revenue stream. Factor in the reduction in bad press that MS gets every time there's a worm and Microsoft's continued policy of supporting pirated copies of Windows makes all the sense in the world. They'd have to be stupid to do otherwise.
Of course the curtailing of various worms is nice for the Internet at large. Just because an action serves Microsoft's interest doesn't mean that it can't serve everyone else's interests too. (Except for the fact that it perpetuates Microsoft's choke-hold on the IT industry, but since when did we worry about the long-term good when a short-term good is in front of us?)
I'm sure that the extra bandwidth will cost Microsoft thousands of dollars, but it's cheap PR for them.
Maybe I'm not the target of this particular troll, since I don't believe that there's any "conspiracy". Microsoft is just doing what is best for Microsoft. That's what it always does (and should do - it is a business after all).
The PostgreSQL advocacy site has some case studies about its adoption. Most of them are pretty terse, but the PDF ones are more in-depth.
Apache 2.x can be run in multi-threaded mode, but it can still do multiprocess just as well (if not better) than 1.3.x.
The multi-thread capabilities of Apache 2 in no way detract from its multi-process capabilities. You can run in just multi-thread mode, just multi-process mode or any balance between the two that you want. The multi-thread capabilities were added to address performance problems on platforms that were not very efficient at spawning new processes (Windows and others).
If there are still some PHP libraries that are not thread-safe (and you need those libraries), just don't run in multi-threaded mode. If you're on Linux, that's probably what you were doing anyway. (If you're on Windows - well, why the hell are you running a production server on Windows?)
Of course, there are valid reasons to stick with 1.3.x. For example:
In general, I follow the "2.x is default for new installations" philosophy.
The funny thing about trademark law is that you can loose your trademark if you don't send out threatening letters like our FightForRock admin got. Combine this with a company that has a trademark that is very close to a generic term (and generic terms are not trademarkable) and you get a legal department that is pretty much forced to by hyper-paranoid about trademarks. This leads to a sort of little-big-man syndrome, where the company acts like it thinks everyone is picking on it. So HardRadio has a chip on it's shoulder. FightForRock accidentally stepped on their shoes, and now HardRadio has been forced into a legal pissing contest. What do you do when the short guy gets all pissy at you for no good reason? You can either kick his scrawny ass (which is usually more trouble than it's worth) or you can smile and apologise for whatever minor thing set him off and be on your way. Those are pretty much FightForRock's options. I don't see that HardRadio really has a case, but it's probably more trouble than it's worth to kick their asses in court. ------- P.S. This post was designed specifically to propogate negative stereotypes about short people. Tall Power!