Currently the dullest blog on this planet. A great deal of effort is needed to accomplish this.
How Propaganda Works link
Get link
Facebook
X
Pinterest
Email
Other Apps
I recently read this article on How Propaganda Works and it's staggering how you can draw parallels on its (ab)use through history but also the present.
I've spent a good part of my day today in trying to understand why I can't checkout our subversion repository. I was getting this: svn: REPORT of '/svn/repos/!svn/vcc/default': 400 Bad Request google searches would make you think it's a proxy issue but I don't use or need one so after a lot of trial and errors I've found out that if you use Kaspersky Anti-Virus 6 it seems that if you use the Web Anti-Virus options with the recommended settings and you have the "Scan HTTP traffic" option on you end up with the problem above. It seems Kaspersky doesn't like the HTTP packets subversion uses so they get blocked. I really like Kaspersky and I recommend it to all but I hope they will address this issue as soon as possible as subversion is becoming the main open source VCS system. Any tips on this issue are welcome.
I've recently had the need to access a web service developed in .Net and signed with a self signed certificate. I've decided to use the JaxWS and the Metro stack to develop the client and run it on Java6. As a plus, the service was protected with username and password. The service was exposed on an IP address and I repetedly had problems in establishing a connection. In the end, thanks to this article, it was obvious that the certificate was not created with the alternative name attribute but it was not an option to change the certificate as the web service was already used by other consumers (.net clients don't suffer by this issue). So, on my quest to relax the validation, I've found out this article and code snippet, which did not compile at first (I guess package names were changed in JDK6) so I've did some trivial refactoring and now, after invoking the static methods in the client code, the SSL connection gets validated with no problems. Hope it helps and th...
After the successful install, it was obvious that both network adapters didn't work and neither did the graphic card. As my friend didn't know anything about MacOS these are some steps that might work and they might not. In order to make the ATIRadeonX1000.kext driver work (the kext is a directory containing driver stuff), you must modify the Info.Plist file and add your deviceid to the values beneath IOPCIMatch. To find out your card deviceid you need to open the system profiler and look at your graphic card. It'll show you values for deviceid, vendorid, revisionid, and eventually it will say it's kext have been loaded. What you need to do is to concatenate the deviceid and vendorid so if your deviceid is 0x71C2 you need to append the vendorid (ATI is 0x1002 as I can see) resulting in the end string 0x71C21002. Here the things get tricky, various things were tried and in the end I'd recommend the following procedure: Boot the kernel in single mode by passing -s whe...
Comments