I usually use my iPod at work and when travelling in vehicles OTHER than my car (like on airplanes)
At home, I usually listen to streamed internet radio. These streams would be XM if they were easier to play under Linux (it's possible, but it's a pain but doesn't work too well)
In my car - XM all the way, it lets me know what to fill my iPod with.:)
They did come up with a good solution to the problem (although only for all new classes, not the existing ones that still can/free) - New classes not eligible for/free get a hefty XP bonus from 1-20 if they have a Lv50 on their account.
Given that large power plants are extremely efficient (I believe approaching theoretical limits on efficiency in terms of input and output temperature, with "output temperature" being outside air temp), I have a feeling these thermoelectric generators will have almost no benefit (if any) in large power plants.
They might have some benefit for running a few accessories in automotive uses, where the exhaust gases are still quite hot. (Getting good efficiency usually means killing your power/weight ratio, which is why large power plants are so much more efficient than automotive IC engines - power plants don't care about power/weight ratio at all.)
It looks like this new research could result in significant advances for any application for which Peltier coolers or generators have been previously considered - the goal seems to be a more efficient and/or lower-cost form of Peltier junction.
I don't know how many times people have requested SOME method of enabling edge-flipping in Metacity, even via Gconf, and had it shot down by Havoc Pennington.
Hell, the GNOME devs seem to actively sabotage any attempt to combine GNOME and edge-flipping. In the early days of GNOME, in theory any window manager that complied with some specific guidelines was supposed to work well with GNOME - Well, the GNOME devs seem to have pulled a Microsoft and WMs other than Metacity that are compliant with that interface standard (I forget what it was) no longer play with GNOME. (I used Sawfish instead of Metacity just for edge flipping for a while, until Sawfish no longer worked acceptably with GNOME.) There was a utility called Brightside that worked around Metacity's braindeadness quite well in one GNOME version. Guess what - the GNOME devs changed everything Metacity depended on and it no longer even compiles with recent versions of GNOME. That was the final straw for me - after being a GNOME fan/user for years and quite anti-KDE, I'm now a KDE user and while I'd love to go back if I could (there are quite a few things about KDE I find annoying), I'll take KDE's annoyingness over GNOME's current crippleware state any day of the week.
Regarding the article summary's claim of Godwin's Law - In my opinion, Godwin's Law only applies when using the original definition of Nazi, not the added one.
i.e. Godwin's Law applies when some entity is directly compared to the German Nazi party, not when someone is called a " Nazi" using the "added" definition - it doesn't apply to this particular fight.
Addicted? No - Given how rarely a non-MMOG can really engage me compared to an MMOG, I feel that I get more for my money with other non-gaming products than standalone non-MMOG games. i.e. when not playing MMOGs, I just go do something else outside of my apartment (drinks at a bar, ice skating, etc.)
s/WoW/other MMOG/ and you've taken huge chunks out of the pool.
If not for DAoC and EVE, I would've been tempted to buy the following:
Half-Life 2 Battlefield 1942/BF2 Joint Operations A few others - Oblivion looks pretty cool.
Other than MMOGs, the only games I've bought in the past 4-5 years were iD Software products, and that was a mixture of desire for the product itself (they make good games) and desire to support a company that actively supported Linux gaming. (Yes, a MAJOR factor in purchasing Quake 4 and Doom 3 was that they had native Linux ports.)
Number of movies released in a particular month != total number of movies available
I believe that prior to this particular month, HD-DVD was consistently ahead of Blu-Ray. Declaring a winner based on a single months' worth of statistics (especially at this early point when both formats are in their infancy) is utterly idiotic.
It may be that in the name of "security from internal malware" (I cannot see any reason for SPI firewalls to exist in NAT routers other than to protect the outside world from internal machines infected with malware, and the behavior of Netgear's SPI implementation confirms this suspicion that SPI is all about protecting the world from you instead of the other way around.), Apple added some sort of SPI firewall to their new routers.
I am not too familiar with other vendor implementations, but I know that Netgear's SPI firewalls usually seem to serve no purpose other than to classify outbound DNS requests as some sort of DoS flood and block it, among other things in the general class of "breaking stuff that is supposed to work", including Contivity VPNs (A coworker recently confirmed this for me, the moment he killed the SPI firewall on his Netgear router he no longer had to open up 4279374072903 ports to get Contivity to work reliably.) Apple's may be similar.
You said that you couldn't establish any sort of a VPN connection (Implying that the router cannot be used for any VPN connectivity), rather than only not being able to establish one with a specific client known for not playing well with NAT routers.
"The issue seems to be that, without setting your computer as the DMZ in the base station settings, you can't establish a VPN connection with an external VPN server from your computer."
No, the issue is that without this workaround, you can't connect one specific VPN client (Nortel Contivity) to an external VPN server. All of the problem reports except for one are with Nortel Contivity, a VPN client which is notorious for being finicky as far as working with NAT routers. Trust me, we use it where I work and it breaks with a LARGE variety of routers from various manufacturers.
I know nothing about this Checkpoint client, but it is probably similar to Contivity (In theory, an IPSec implementation, but one that is so badly mangled that it won't speak to any other IPSec implementation other than the one it was specifically designed with. That mangling seems to be related to its tendency to not work well with many NAT routers.)
It seems that every complaint in that thread is regarding Nortel's Contivity VPN system.
As someone whose employer uses Contivity, I can say that without a doubt, Contivity *sucks*. It is in theory an IPSec implementation, but it is a massively mangled one that suffers from endless problems, especially with NAT. Numerous coworkers of mine have had problems with Contivity and a wide variety of routers from various manufacturers. About the only router that seems to work well with Contivity is one running DD-WRT. For some reason, DD-WRT Just Works.
Yeah, but very often if that "cog" breaks, the whole system breaks, and hence the MTBF of the system would be unacceptably low if the individual components were unreliable.
This is a Bad Thing when a "cog" breaking means an aircraft crashes and people die.
Or even in an item with three "cogs", if that "cog" breaks during a firefight with insurgents - well, you're screwed.
I admit, things could be done a bit more efficiently and still remain rugged, but in general, the problem lies not with the vendor in most cases, but with the customer. The customer (Uncle Sam) has been screwed over by so many shady vendors in the past that everyone is now universally strangled with paperwork to prove that they're not shady and are providing what the customer is paying them for, small company, large company, honest company, or shady scumbag company.
"The fact that he's measuring AC (which is very surprising since the laptops don't have any ready access to AC outside of the power brick AFAIK) make it less likely though."
Most voltmeters in AC mode will happily measure DC, just not accurately. No way to tell for sure unless he connected an oscilliscope (which he did not).
Unlike AC-coupled scopes, most multimeters set to measure AC will also measure DC, but will not do so accurately as in addition to rectifying and filtering the input, they perform corrections in order to display either Vpeak or Vrms.
Unless he scoped it and saw a 60 Hz signal, just because the voltmeter read something when in AC mode doesn't mean that it's actually AC.
I have an E1705 and while the first one was a dud (which Dell happily replaced), the new one has zero problems whatsoever.
That's my point. They can re-release code under the V3 all they want, but they cannot revoke the existing V2 licenses already out there in the wild. Those already existing V2 branches can form the basis for new V2-only forks, in a similar manner to how the last revision of XFree86 released under the old license became the basis for the (now dominant) X.org fork.
Nothing other than developer interest/feelings is preventing the same thing happening if the FSF forces a V3 upgrade for future releases.
"Of course all changes to the GPLv2 programs can be moved to GPLv3 but not the other way." No they can't. As another person has said, the GPLv3 is inherently incompatible (at least in all released forms) with the GPLv2.
The "way out" for the FSF in this regard is that most GPLv2 software has the "GPLv2 or later" clause in it, allowing for a more restrictive license ONLY if that license is a later revision of the GPL. Not all GPLv2 software has that "or later" clause attached - it's optional.
Because while the modules are officially legal, the kernel devs and some users (such as Stallman I'm sure) really don't like them.
So while the kernel does not make any attempt to prevent loading such modules (if they were illegal, don't you think that the kernel would forbid loading non-GPL modules and/or the module writer would not explicitly advertise to the kernel that they were using a license other than GPL?), it does complain because some idealists want to know that their system isn't "pure".
And in the case of that software, the question will be, while GNU owns the copyright, they don't necessarily own the developers, and they essentially can't "revoke" the GPL2 license for existing software, they can only "upgrade" future releases to the GPLv3 as I understand it.
Nothing is preventing the last v2 codebase from being forked. Once that happens, the question will be how many of the developers are loyal to the FSF/GPLv3, and how many would rather stick with GPLv2? The answer to that question will determine just how badly the fork hurts the open-source community. There's a pretty good chance it would wind up like Xorg, with the majority of the developers moving to the fork and the community as a whole benefiting significantly in the long run.
I think what he meant (and he completely botched his attempt to say it) is that seperately distributed drivers are not considered part of the kernel, and hence do not have to be GPL. I am not sure, but I believe that the GPL applied to the Linux kernel has been specifically modified to allow this, either that or the way the driver interface behaves permits for linking in non-GPL kernel modules at runtime.
Either way, non-GPL kernel modules are allowed. They are frowned upon by the kernel developer community, but allowed.
While not as much of a contributor to "social multiplayer gaming" as Wii Sports might be, the Super Smash Bros. series definately started the whole "party game" trend that Wii Sports continued.
During my junior and senior year of college, many of my friends were of the opinion that for the most part, one should not watch TV or play video games at a party. Super Smash Brothers was the one exception - It got played at quite a few parties, especially my senior year. Like a previous poster's comments about Goldeneye for N64, it was able to keep a large number of people amused (not just the four actually playing the game) for rather extended periods of time. In fact, I recall one night when our neighbors (who were all close friends of ours, we intentionally got two four-bedroom apartments across the hall from each other) were hosting a party. Prior to attending, many of my apartmentmates decided to play SSB for a bit. Within an hour or so, most of the guests of the neighbor's party were either watching or playing the game in our apartment.
Of course, the fact that we were playing on my LCD projector probably had something to do with it. SSB is amazing on a ten-foot screen.:)
Slashdot Mirror
Agreed.
:)
I usually use my iPod at work and when travelling in vehicles OTHER than my car (like on airplanes)
At home, I usually listen to streamed internet radio. These streams would be XM if they were easier to play under Linux (it's possible, but it's a pain but doesn't work too well)
In my car - XM all the way, it lets me know what to fill my iPod with.
They did come up with a good solution to the problem (although only for all new classes, not the existing ones that still can /free) - New classes not eligible for /free get a hefty XP bonus from 1-20 if they have a Lv50 on their account.
Given that large power plants are extremely efficient (I believe approaching theoretical limits on efficiency in terms of input and output temperature, with "output temperature" being outside air temp), I have a feeling these thermoelectric generators will have almost no benefit (if any) in large power plants.
They might have some benefit for running a few accessories in automotive uses, where the exhaust gases are still quite hot. (Getting good efficiency usually means killing your power/weight ratio, which is why large power plants are so much more efficient than automotive IC engines - power plants don't care about power/weight ratio at all.)
It looks like this new research could result in significant advances for any application for which Peltier coolers or generators have been previously considered - the goal seems to be a more efficient and/or lower-cost form of Peltier junction.
No, it doesn't cure the flu. The vaccine will do almost nothing if you are already infected.
It will prevent you from getting it in the first place, but won't cure it once you already have it.
s/everything Metacity depended on/everything Brightside depended on/
I don't know how many times people have requested SOME method of enabling edge-flipping in Metacity, even via Gconf, and had it shot down by Havoc Pennington.
Hell, the GNOME devs seem to actively sabotage any attempt to combine GNOME and edge-flipping. In the early days of GNOME, in theory any window manager that complied with some specific guidelines was supposed to work well with GNOME - Well, the GNOME devs seem to have pulled a Microsoft and WMs other than Metacity that are compliant with that interface standard (I forget what it was) no longer play with GNOME. (I used Sawfish instead of Metacity just for edge flipping for a while, until Sawfish no longer worked acceptably with GNOME.) There was a utility called Brightside that worked around Metacity's braindeadness quite well in one GNOME version. Guess what - the GNOME devs changed everything Metacity depended on and it no longer even compiles with recent versions of GNOME. That was the final straw for me - after being a GNOME fan/user for years and quite anti-KDE, I'm now a KDE user and while I'd love to go back if I could (there are quite a few things about KDE I find annoying), I'll take KDE's annoyingness over GNOME's current crippleware state any day of the week.
Regarding the article summary's claim of Godwin's Law - In my opinion, Godwin's Law only applies when using the original definition of Nazi, not the added one.
i.e. Godwin's Law applies when some entity is directly compared to the German Nazi party, not when someone is called a " Nazi" using the "added" definition - it doesn't apply to this particular fight.
Quake 4's dramatic reversal was extremely well done. Probably one of the best examples so far in this discussion.
Addicted? No - Given how rarely a non-MMOG can really engage me compared to an MMOG, I feel that I get more for my money with other non-gaming products than standalone non-MMOG games. i.e. when not playing MMOGs, I just go do something else outside of my apartment (drinks at a bar, ice skating, etc.)
s/WoW/other MMOG/ and you've taken huge chunks out of the pool.
If not for DAoC and EVE, I would've been tempted to buy the following:
Half-Life 2
Battlefield 1942/BF2
Joint Operations
A few others - Oblivion looks pretty cool.
Other than MMOGs, the only games I've bought in the past 4-5 years were iD Software products, and that was a mixture of desire for the product itself (they make good games) and desire to support a company that actively supported Linux gaming. (Yes, a MAJOR factor in purchasing Quake 4 and Doom 3 was that they had native Linux ports.)
Number of movies released in a particular month != total number of movies available
I believe that prior to this particular month, HD-DVD was consistently ahead of Blu-Ray. Declaring a winner based on a single months' worth of statistics (especially at this early point when both formats are in their infancy) is utterly idiotic.
"Open" has been overloaded to the point of meaningless for years, if not decades.
The Open Group, anyone?
It may be that in the name of "security from internal malware" (I cannot see any reason for SPI firewalls to exist in NAT routers other than to protect the outside world from internal machines infected with malware, and the behavior of Netgear's SPI implementation confirms this suspicion that SPI is all about protecting the world from you instead of the other way around.), Apple added some sort of SPI firewall to their new routers.
I am not too familiar with other vendor implementations, but I know that Netgear's SPI firewalls usually seem to serve no purpose other than to classify outbound DNS requests as some sort of DoS flood and block it, among other things in the general class of "breaking stuff that is supposed to work", including Contivity VPNs (A coworker recently confirmed this for me, the moment he killed the SPI firewall on his Netgear router he no longer had to open up 4279374072903 ports to get Contivity to work reliably.) Apple's may be similar.
You said that you couldn't establish any sort of a VPN connection (Implying that the router cannot be used for any VPN connectivity), rather than only not being able to establish one with a specific client known for not playing well with NAT routers.
"The issue seems to be that, without setting your computer as the DMZ in the base station settings, you can't establish a VPN connection with an external VPN server from your computer."
No, the issue is that without this workaround, you can't connect one specific VPN client (Nortel Contivity) to an external VPN server. All of the problem reports except for one are with Nortel Contivity, a VPN client which is notorious for being finicky as far as working with NAT routers. Trust me, we use it where I work and it breaks with a LARGE variety of routers from various manufacturers.
I know nothing about this Checkpoint client, but it is probably similar to Contivity (In theory, an IPSec implementation, but one that is so badly mangled that it won't speak to any other IPSec implementation other than the one it was specifically designed with. That mangling seems to be related to its tendency to not work well with many NAT routers.)
It seems that every complaint in that thread is regarding Nortel's Contivity VPN system.
As someone whose employer uses Contivity, I can say that without a doubt, Contivity *sucks*. It is in theory an IPSec implementation, but it is a massively mangled one that suffers from endless problems, especially with NAT. Numerous coworkers of mine have had problems with Contivity and a wide variety of routers from various manufacturers. About the only router that seems to work well with Contivity is one running DD-WRT. For some reason, DD-WRT Just Works.
Yeah, but very often if that "cog" breaks, the whole system breaks, and hence the MTBF of the system would be unacceptably low if the individual components were unreliable.
This is a Bad Thing when a "cog" breaking means an aircraft crashes and people die.
Or even in an item with three "cogs", if that "cog" breaks during a firefight with insurgents - well, you're screwed.
I admit, things could be done a bit more efficiently and still remain rugged, but in general, the problem lies not with the vendor in most cases, but with the customer. The customer (Uncle Sam) has been screwed over by so many shady vendors in the past that everyone is now universally strangled with paperwork to prove that they're not shady and are providing what the customer is paying them for, small company, large company, honest company, or shady scumbag company.
"The fact that he's measuring AC (which is very surprising since the laptops don't have any ready access to AC outside of the power brick AFAIK) make it less likely though."
Most voltmeters in AC mode will happily measure DC, just not accurately. No way to tell for sure unless he connected an oscilliscope (which he did not).
Unlike AC-coupled scopes, most multimeters set to measure AC will also measure DC, but will not do so accurately as in addition to rectifying and filtering the input, they perform corrections in order to display either Vpeak or Vrms.
Unless he scoped it and saw a 60 Hz signal, just because the voltmeter read something when in AC mode doesn't mean that it's actually AC.
I have an E1705 and while the first one was a dud (which Dell happily replaced), the new one has zero problems whatsoever.
That's my point. They can re-release code under the V3 all they want, but they cannot revoke the existing V2 licenses already out there in the wild. Those already existing V2 branches can form the basis for new V2-only forks, in a similar manner to how the last revision of XFree86 released under the old license became the basis for the (now dominant) X.org fork.
Nothing other than developer interest/feelings is preventing the same thing happening if the FSF forces a V3 upgrade for future releases.
"Of course all changes to the GPLv2 programs can be moved to GPLv3 but not the other way."
No they can't. As another person has said, the GPLv3 is inherently incompatible (at least in all released forms) with the GPLv2.
The "way out" for the FSF in this regard is that most GPLv2 software has the "GPLv2 or later" clause in it, allowing for a more restrictive license ONLY if that license is a later revision of the GPL. Not all GPLv2 software has that "or later" clause attached - it's optional.
Because while the modules are officially legal, the kernel devs and some users (such as Stallman I'm sure) really don't like them.
So while the kernel does not make any attempt to prevent loading such modules (if they were illegal, don't you think that the kernel would forbid loading non-GPL modules and/or the module writer would not explicitly advertise to the kernel that they were using a license other than GPL?), it does complain because some idealists want to know that their system isn't "pure".
And in the case of that software, the question will be, while GNU owns the copyright, they don't necessarily own the developers, and they essentially can't "revoke" the GPL2 license for existing software, they can only "upgrade" future releases to the GPLv3 as I understand it.
Nothing is preventing the last v2 codebase from being forked. Once that happens, the question will be how many of the developers are loyal to the FSF/GPLv3, and how many would rather stick with GPLv2? The answer to that question will determine just how badly the fork hurts the open-source community. There's a pretty good chance it would wind up like Xorg, with the majority of the developers moving to the fork and the community as a whole benefiting significantly in the long run.
I think what he meant (and he completely botched his attempt to say it) is that seperately distributed drivers are not considered part of the kernel, and hence do not have to be GPL. I am not sure, but I believe that the GPL applied to the Linux kernel has been specifically modified to allow this, either that or the way the driver interface behaves permits for linking in non-GPL kernel modules at runtime.
Either way, non-GPL kernel modules are allowed. They are frowned upon by the kernel developer community, but allowed.
While not as much of a contributor to "social multiplayer gaming" as Wii Sports might be, the Super Smash Bros. series definately started the whole "party game" trend that Wii Sports continued.
:)
During my junior and senior year of college, many of my friends were of the opinion that for the most part, one should not watch TV or play video games at a party. Super Smash Brothers was the one exception - It got played at quite a few parties, especially my senior year. Like a previous poster's comments about Goldeneye for N64, it was able to keep a large number of people amused (not just the four actually playing the game) for rather extended periods of time. In fact, I recall one night when our neighbors (who were all close friends of ours, we intentionally got two four-bedroom apartments across the hall from each other) were hosting a party. Prior to attending, many of my apartmentmates decided to play SSB for a bit. Within an hour or so, most of the guests of the neighbor's party were either watching or playing the game in our apartment.
Of course, the fact that we were playing on my LCD projector probably had something to do with it. SSB is amazing on a ten-foot screen.