They explained the part about it being pushed to all devices by saying that they had been including a backdoor in their product for years. They never did explain how it could possibly be cross-platform though.
I'm not intimately familiar with the BitTorrent protocol, but I believe each chunk is checked (with SHA-1 I think) to ensure that everything was transmitted successfully. Having to resend chunks due to data loss would slow down a download, but losing a few packets shouldn't cause any major problems.
Back when eDonkey was still fairly popular, I remember the lMule devs (GNU/Linux port of eMule) were aware of this technique and planned on incorporating it in lMule. BitTorrent became popular, lMule forked many times, and we never got around to it. I'm not aware of any current P2P apps that do it. The problem is that the technique, as they describe it, requires a central trusted server that both sides can connect to. With Skype that's fine, but it's a problem when you're dealing with something that's supposed to be entirely P2P. I don't remember this limitation, so either I have a bad memory or there's some way around it.
All I can say is, pray that IPv6 doesn't get adopted or it will be even worse.
Why? There will be more IPs, but if everyone has a permanent IP it will be easier to block offenders and infected machines.
I know there's plenty of OSS going on for OSX and it's even got the bash kernel so you can compile pre-existing OSS apps that were written for it
BASH is a shell, not a kernel. Having it installed won't help you compile anything.
what language do you write that in? C? and out of curiousity, where do you go to school?
Re:I am seeing red lights, alarms, sirens, the WOR
on
Managed ASP Web Hosts?
·
· Score: 1
I would _not_ recommend 1and1 for anything. In my experience their support has been awful, even when the problem is their fault. I had a situation where they refused to place a bad hard drive (DMA suddenly stopped working), and finally had to move to a new host.
According to the OpenBSD i386 supported hardware website, out of the cards reviewed, only Adaptec and LSI cards are compatible with OpenBSD. However, Adaptec has refused to provide documentation so that the OpenBSD project may improve the drivers. "Note: In the past year Adaptec has lied to us repeatedly about forthcoming documentation so that RAID support for these (rather buggy) raid controllers could be stabilized, improved, and managed.
As a result, we do not recommend the Adaptec cards for use."
Other *nix variants might support the Adaptec and Promise cards a little more, but the hardware fully supported by OpenBSD is generally well-supported across all *nix variants.
Out of the cards reviewed, only the one from LSI is worth buying. Adaptec may have a little support, but it's not a good idea to purchase any RAID cards from them until they start providing better documentation.
Xen is ok, but it doesn't have the performance or the reliability of vmware.
Do you have anything to back this claim up? I moved several virtual machines from VMWare GSX to Xen a few months ago, and noticed an immediate performance increase. I've had just as many reliability problems as I had with VMWare.. none.
It isn't that I disagree with his intention, but clearly access to source is not a pre-requisite to this freedom. A legion of dedicated game protecton crackers stand as eloquent testimony to that fact.
Having access to the actual source code and reverse engineering a program are two entirely different of things. Making changes to a program by reverse engineering it is several orders of magnitude harder than modifying source code that is already available.
This means the only Freedom lost is the freedom to force other people tell you how they modded your code - and I'm not at all comfortable with "freedoms" that force other people to do anything - if only because someday one of those people is probably going to be me.
The freedom in question is the freedom to make changes to GPL'ed source. The GPL in no way forces anyone who makes a change to your code to release the modified source. What it does force them to do is to release the source if they release binaries, so that users of the modified program retain their freedom to modify it. This is what worries me about The Pirate Party's stance: the party's goal is to give everyone more freedom, but in doing so, they run the risk of removing some freedom (that is, the freedom to modify the program by means of modifying the source). Yes, it's true that one could reverse engineer/decompile/whatever the program, but that is _much_ harder than modifying freely-available source. Realistically, very few people are going to go to the trouble of reverse engineering or decompiling a large program just to make a few modifications.
The important thing the GPL does is safeguard certain freedoms of human beings. I can't find the reference I was looking for, but Wikipedia [wikipedia.org] gives these freedoms as
the freedom to study and modify a program
My point is that the GPL is no longer able to provide you with the freedom to study and modify a program if the GPL is no longer valid. Anyone could make changes to a GPL program and distribute binaries without distributing the modified source, thus infringing on the above freedom. Whether or not this is a big deal is another discussion entirely.
You're missing the distinction between Free as in speech and free as in beer. Everything would be free as in beer, but wouldn't be Free. The point of the GPL isn't to keep people from charging money for software, it's to ensure that the source code remains available for anyone to modify. Without the GPL, software might be free of charge, but we have no way to ensure that it remains Free.
Re:Linus' new philosophy of development in main tr
on
Linux 2.6.16 released
·
· Score: 1
Get the hell out of the stable branch! Vanilla 2.6 kernels are _not_ considered stable by Linus, the kernel devs, or anyone else important for that matter. If you want a stable vanilla kernel, use 2.4.. 2.6 is bleeding edge.
"we lost Bin Laden" We got the other guy though, Hussain. and the best thing about that is that he's being tried in Iraq. The fact that we can't capture a single guy who's been keeping a low profile and has good friends who's pocketbooks look like the US treasury doesn't suprise me at all. But then again, that's Bush's fault. Of course if we'd caught him, then it would have cost to much and that would also be Bush's fault. Let me guess, you don't like him do you?
Yes, we got Hussein, what's your point? Iraq was not responsible for the attack on the WTC. I don't know whether or not they provided Al Quaeda with financial support, but if they did, so what? Saudia Arabia is a much larger financer of terrorism, yet we don't invade their country. Who made the United States the Protector of the World? It isn't the United States' job to depose rulers and reshape countries that they do not like. In addition, the United States has no right to launch a pre-emptive strike on a sovereign nation. Whether or not we are "losing" in Iraq is irrelevant, we shouldn't be there in the first place.
Most of the less popular games require a little bit of tweaking before they work properly. I've never had any of the games that they list as working not work, some just require time spent tweaking Cedega and in-game settings.
I've never had a problem with earbuds being too loud. I always pay attention to the noise level, and my current ones (the cheap Sony ones that are frequently given out on airline flights) can't be heard 1m from my ear.
As far as normal headphones go, what brand/model would you recommend for the best direction of noise (so you can hear it, but others can't)?
I wrote this a while back, I seem to remember something about it not working right but don't remember what. "I will cover updating loki_update, but this should apply to updating anything from Loki.
First, download the update file. I did this with the command: wget ftp://sunsite.dk/mirrors/lokigames/updates/loki_up date/loki_update-1.0.12-x86.run Make it executable, and then run it with the --keep paramater. This will create a directory named loki_update-1.0.12-x86. Enter that directory. Get the version of loki_patch that works with newer versions of glibc from here. Make sure you are in the new loki_update directory, and then replace the loki_patch in bin/Linux/x86/ with the loki_patch you just downloaded. Now, just run update.sh and the update should proceed normally.
This has been tested with Tribes 2 in addition to loki_update. The only difference was that to completely update Tribes 2, you must install many patches in the order they were released. I used loki_update to show what patches needed to be installed, and then simply installed then with the method described above." Basically you just need a binary that is compatible with your current glibc version. I'm sure there's a way to install an older glibc version and make the game use that instead, but I don't know how.
The only part that doesn't work out of the box for me is the installer and Loki Upgrader, there's a patched version floating around that works fine with newer glibcs.
what games are you talking about? UT? UT 2k3/2k4? ET? Quake 3? Quake 4? Alpha Centauri? All of the above work fine with my 2.6 kernel, and most certainly aren't new. Or are you referring to glibc versions, not kernel versions? In that case, the problem can be fixed in various ways, such as making available an older version of glibc for use by that game.
Unless your drives are encrypted, that's not going to stop them when they boot from a livecd.
They explained the part about it being pushed to all devices by saying that they had been including a backdoor in their product for years. They never did explain how it could possibly be cross-platform though.
I'm not intimately familiar with the BitTorrent protocol, but I believe each chunk is checked (with SHA-1 I think) to ensure that everything was transmitted successfully. Having to resend chunks due to data loss would slow down a download, but losing a few packets shouldn't cause any major problems.
Back when eDonkey was still fairly popular, I remember the lMule devs (GNU/Linux port of eMule) were aware of this technique and planned on incorporating it in lMule. BitTorrent became popular, lMule forked many times, and we never got around to it. I'm not aware of any current P2P apps that do it. The problem is that the technique, as they describe it, requires a central trusted server that both sides can connect to. With Skype that's fine, but it's a problem when you're dealing with something that's supposed to be entirely P2P. I don't remember this limitation, so either I have a bad memory or there's some way around it.
All I can say is, pray that IPv6 doesn't get adopted or it will be even worse.
Why? There will be more IPs, but if everyone has a permanent IP it will be easier to block offenders and infected machines.
I know there's plenty of OSS going on for OSX and it's even got the bash kernel so you can compile pre-existing OSS apps that were written for it
BASH is a shell, not a kernel. Having it installed won't help you compile anything.
what language do you write that in? C?
and out of curiousity, where do you go to school?
I would _not_ recommend 1and1 for anything.
In my experience their support has been awful, even when the problem is their fault. I had a situation where they refused to place a bad hard drive (DMA suddenly stopped working), and finally had to move to a new host.
You know what would even be cooler?? If one of those friends was a girl.
Oh come on, be realistic.
According to the OpenBSD i386 supported hardware website, out of the cards reviewed, only Adaptec and LSI cards are compatible with OpenBSD.
However, Adaptec has refused to provide documentation so that the OpenBSD project may improve the drivers.
"Note: In the past year Adaptec has lied to us repeatedly about forthcoming documentation so that RAID support for these (rather buggy) raid controllers could be stabilized, improved, and managed. As a result, we do not recommend the Adaptec cards for use."
Other *nix variants might support the Adaptec and Promise cards a little more, but the hardware fully supported by OpenBSD is generally well-supported across all *nix variants.
Out of the cards reviewed, only the one from LSI is worth buying. Adaptec may have a little support, but it's not a good idea to purchase any RAID cards from them until they start providing better documentation.
I suggest you RTFA before posting. The data is encrypted, and cannot be decrypted without your PIN.
Xen is ok, but it doesn't have the performance or the reliability of vmware.
Do you have anything to back this claim up?
I moved several virtual machines from VMWare GSX to Xen a few months ago, and noticed an immediate performance increase. I've had just as many reliability problems as I had with VMWare.. none.
VisualBasic, like just about every other language, has its place.
And it's called hell.
Having access to the actual source code and reverse engineering a program are two entirely different of things. Making changes to a program by reverse engineering it is several orders of magnitude harder than modifying source code that is already available.
This means the only Freedom lost is the freedom to force other people tell you how they modded your code - and I'm not at all comfortable with "freedoms" that force other people to do anything - if only because someday one of those people is probably going to be me.
The freedom in question is the freedom to make changes to GPL'ed source. The GPL in no way forces anyone who makes a change to your code to release the modified source. What it does force them to do is to release the source if they release binaries, so that users of the modified program retain their freedom to modify it.
This is what worries me about The Pirate Party's stance: the party's goal is to give everyone more freedom, but in doing so, they run the risk of removing some freedom (that is, the freedom to modify the program by means of modifying the source). Yes, it's true that one could reverse engineer/decompile/whatever the program, but that is _much_ harder than modifying freely-available source. Realistically, very few people are going to go to the trouble of reverse engineering or decompiling a large program just to make a few modifications.
My point is that the GPL is no longer able to provide you with the freedom to study and modify a program if the GPL is no longer valid. Anyone could make changes to a GPL program and distribute binaries without distributing the modified source, thus infringing on the above freedom.
Whether or not this is a big deal is another discussion entirely.
You're missing the distinction between Free as in speech and free as in beer.
Everything would be free as in beer, but wouldn't be Free. The point of the GPL isn't to keep people from charging money for software, it's to ensure that the source code remains available for anyone to modify. Without the GPL, software might be free of charge, but we have no way to ensure that it remains Free.
yes, of course it's correct grammar in the UK..
Get the hell out of the stable branch!
Vanilla 2.6 kernels are _not_ considered stable by Linus, the kernel devs, or anyone else important for that matter.
If you want a stable vanilla kernel, use 2.4.. 2.6 is bleeding edge.
"we lost Bin Laden" We got the other guy though, Hussain. and the best thing about that is that he's being tried in Iraq. The fact that we can't capture a single guy who's been keeping a low profile and has good friends who's pocketbooks look like the US treasury doesn't suprise me at all. But then again, that's Bush's fault. Of course if we'd caught him, then it would have cost to much and that would also be Bush's fault. Let me guess, you don't like him do you?
Yes, we got Hussein, what's your point? Iraq was not responsible for the attack on the WTC. I don't know whether or not they provided Al Quaeda with financial support, but if they did, so what? Saudia Arabia is a much larger financer of terrorism, yet we don't invade their country. Who made the United States the Protector of the World? It isn't the United States' job to depose rulers and reshape countries that they do not like. In addition, the United States has no right to launch a pre-emptive strike on a sovereign nation.
Whether or not we are "losing" in Iraq is irrelevant, we shouldn't be there in the first place.
Most of the less popular games require a little bit of tweaking before they work properly. I've never had any of the games that they list as working not work, some just require time spent tweaking Cedega and in-game settings.
I've never had a problem with earbuds being too loud. I always pay attention to the noise level, and my current ones (the cheap Sony ones that are frequently given out on airline flights) can't be heard 1m from my ear.
As far as normal headphones go, what brand/model would you recommend for the best direction of noise (so you can hear it, but others can't)?
I wrote this a while back, I seem to remember something about it not working right but don't remember what.
p date/loki_update-1.0.12-x86.run
"I will cover updating loki_update, but this should apply to updating anything from Loki.
First, download the update file.
I did this with the command: wget ftp://sunsite.dk/mirrors/lokigames/updates/loki_u
Make it executable, and then run it with the --keep paramater. This will create a directory named loki_update-1.0.12-x86. Enter that directory.
Get the version of loki_patch that works with newer versions of glibc from here.
Make sure you are in the new loki_update directory, and then replace the loki_patch in bin/Linux/x86/ with the loki_patch you just downloaded.
Now, just run update.sh and the update should proceed normally.
This has been tested with Tribes 2 in addition to loki_update. The only difference was that to completely update Tribes 2, you must install many patches in the order they were released. I used loki_update to show what patches needed to be installed, and then simply installed then with the method described above."
Basically you just need a binary that is compatible with your current glibc version. I'm sure there's a way to install an older glibc version and make the game use that instead, but I don't know how.
Gentoo, but I think they worked fine on (older) versions of RHL aswell
The only part that doesn't work out of the box for me is the installer and Loki Upgrader, there's a patched version floating around that works fine with newer glibcs.
what games are you talking about?
UT? UT 2k3/2k4? ET? Quake 3? Quake 4? Alpha Centauri?
All of the above work fine with my 2.6 kernel, and most certainly aren't new. Or are you referring to glibc versions, not kernel versions? In that case, the problem can be fixed in various ways, such as making available an older version of glibc for use by that game.