The comments so far are pretty inane and clearly come from windows users.. any word on how it impacts a dual-boot box? does it render your lilo or grub setup useless? I would personally be very upset if it screwed up my boot setup, and reasonably so, I think. imho, hese kinds of things should raise the hackles of the tech community, and linux users in general enough to give the vendor some serious shit.
or the source IP address of the sender is not registered to the same domain that the mail originates from
Do you mean that the server should ensure the source IP isn't masqueraded, or that the originating domain in the From: header should match the domain of the IP address? In the latter case, refusing mail from mismatched domains would prevent me from using my email address at school when I send mail from home via my ISP. That's an important convenience I wouldn't want to give up, and I suspect that many more people use this feature.
I do agree with the rev DNS lookups and I think most well-configured SMTP servers already do that.
No, the press release says there's no "Linux" code and "Linux-ARM" code in older releases. They have yet to indicate whether there's any GPL'ed code in older releases.
later issues of the supporting software have had to have function names removed (along with a strategy of tokenising textual messages and compressing binaries)
In other words, that's the last time we're stupid enough to ship unstripped binaries!
The PR also explicitly denies using Linux source, rather than GPL'ed source. Reading between the lines, these guys know full well that they're in breach and they're trying to finesse the situation.
Once upon a time there was twm. Once I'd learned how to configure it, they brought out fvwm. Great! Even more customization features! Then there was the wretched mess called fvwm2, with its Windows95 wannabe look-and-feel, followed shortly thereafter with Enlightenment. Wasn't E so cool? You could pixmap everything, and rxvt could do transparent backgrounds. Far out! Only trouble of course was that it was a CPU killer and ground my box to a halt. So I switched to Afterstep. Nice and clean and minimalist. Then WindowMaker (still my favourite), with the clip, and easy keybindings for jumping straight to the virtual desktop of your choice. Then E made a short-lived comeback, only to be boondoggled by sawmill. Or was it sawfish? By then I was so window-manager punch drunk that in a fit of insanity I went back to twm, and then WMaker again. Wait! what's this? metacity? (Somebody please explain to me how I can force new Mozilla instances to appear on workspace 3 and new Evolution instances on wsp 4-- oops, did I just mention two more products that were total rewrites over previously functional products?).
Every new window manager claims lightweight!, from scratch! with new uber-cool foo-controls and bar-widgets (not to mention antialiased wysiwyg thingys).
Now, don't get me wrong, only hardcore l33t h4x0rs still use twm, but clearly the commercial software industry isn't the only place that suffers from reinventing the wheel and forcing the user to learn about its fancy new gearshift.
I don't know how the core team manages its repositories, or what their submission policy is, but I would interpret this move as analogous to revoking MD's write access to cvs. I'm sure he's 'welcome' to continue to submit patches, just like any other schmoe. And of course, he's always free to fork..
Absolutely. And the mark of a brilliant scientist is one who sees how to transfer existing knowledge about one domain into another.
That being said, I highly doubt that Park's research has much to do with database mutexes. The courses I've taken in concurrency pretty much left me baffled. There's a lot more to it than thread safety.
or even better, read his publications. While deadlocks are deadlocks, his research isn't about databases but concurrency. If there wasn't technical merit to his work his peers would reject his publications.
If it's already been done then his peers would have rejected his publications. Just because it sounds like something you've heard of doesn't mean that it's an inferior technology.
It was an interesting piece, but it was posted before this afternoon's news conference, so I'm not sure if it was written before the data about the sensors was made public. Chances are Time's expert would revise some of his speculations based on that evidence.
Disaster magnitude? Hmm. Do you measure that in dollars, lives lost, or shaken public confidence? My first thought this morning was: why don't I get this upset over a downed twin-engine aircraft with seven passengers? Somehow this is bigger, but I hope it's not just because the plane they were flying was a lot more expensive..
I was in grade 8 when Challenger exploded, and I still remember Columbia's first flight and the excitement it generated.
You might be right about the end of the western world's publicly funded involvement in manned space flight, and I suspect that the visions we had as kids of building even modest colonies in space will not be realized within our lifetimes.
Obviously this is a tragic day for the families of those involved, but I think we will all come to mourn the loss of that dream of living in space. I wonder what Arthur C. Clarke is thinking about this.
The first round of globalization took place during the '80s. It was the free trade agreement between Canada and the US, followed shortly thereafter by NAFTA. Throughout the negotiations, Canadians bitched and whined that we'd lose our jobs to the cheap labour in, first, the States, and then Mexico. And from the blue-collar perspective, that was basically true. At the same time we complained about brain drain, where all our best engineers would end up stateside pulling in massive salaries.
The fact of the matter seems to be that American labour, while slightly more productive than Canadian, has also become much more expensive. True, many well-educated Canadians head south for the moula, but most stay right here, enjoying a lower cost of living at the cost of a little less take-home pay. Not to mention the lower likelihood of being shot.;-)
No surprise that well-educated offshore engineers will make for stiff competition when you can just scp the night's code back to the US. All that being said, it still remains somewhat true that the most ambitious foreign techies all eventually end up heading for the States, where the opportunities are considered to be better. It's all about the American Dream, baby!
I'm not referring to license issues wrt plugins, but the claim on the deb list that the app needs to be customized to the present hardware- i386 vs i686, MMX, etc, etc. The only problem I see with this approach is that of ensuring the dependencies are detected properly, but that's the whole point of apt, rpm, and autoconf, at varying levels of abstraction. What's the difference if the debian installer does it or the user does it ten minutes later?
1. Distribute the rpm or deb as a tar archive that installs in/tmp 2. make sure the rpm or deb depends on all the nifty things you want to include, as well as gcc. 3. post-install:
#!/bin/sh cd/tmp/mplayer-src; ./configure --prefix=/usr make make install cd/tmp rm -rf./mplayer-src
Jamie, your mistake was that you tried to install prebuilt binaries. Granted, there are UI issues with all of these players, but I'll only trust beta software to function on my machine if I build it from source. Otherwise you can almost guarantee that those RH 7.2 rpms were actually built on a 6.2 box using libc5 and exporting to deb and then back to rpm, or some other such nonsense.
That's a local problem, between the user and AOL's DNS servers. The article is descibing a different, higher-level problem between, for example, AOL's DNS servers and the root-level servers. If an AOL user's machine makes ten DNS requests for the same host, only one request should propagate past AOL's nameservers, but instead a misconfigured DNS will propagate all ten.
I can suddenly see lots of slashdot users thinking-- oh, I should fix my firewall, I have all these DNS requests; but that's normal operation for a client workstation. Your firewall would be broken only if all your DNS queries failed, and you'd know it pretty fast if that were the case.
The problem being that any of your neighbours can tune in and listen to your call. SMTP has the same problems- not even rudimentary encryption, no verification of the sender's identity, an architecture that encourages wide open relays, etc, etc.
Sure, but they pass those costs on to their subscribers. I think I should clarify my point-- if spam were a real problem for *big* business, then we would have solved the problem years ago with high quality filters and legislation.
Isn't it funny that pr0n makes up nearly the rest of the remaining 50%, and we're not holding conferences on how to eliminate it from the net..;-)
I agree w/ you re the obsolescence of SMTP-- it's like 900MHz portable phones-- an idea past its time.
The best anti-spam method I've seen, bar none, is a friend of mine's opt-in method. His filters indicate the email addresses of people whose mail he's willing to accept, and dumps the rest in his spam folder. Just like call display- the messages that matter get to him and the junk gets junked. For personal email, I think this is the answer-- people with important personal things to say don't rely on email to do it, so if you miss a few, that's ok. Business-related email, is of course, another story, but I figure if SPAM were really a problem for businesses, it would already be solved.
I've been a fan for several years, but when the live CD's started to come out I thought- uh,oh, this is going to cost, and I stopped buying. $10 is a reasonable price to pay for those shows. I wonder if they'll turn a blind eye to people trading the album art from the CD releases of the same shows..
Yes, there's something strange about this article.. it starts off with some interesting stuff, and then some reasonable speculation, and then degrades into some pseudo-religious political rant about DRM and the music industry.
As I read this I couldn't help but thing about RGB displays. The visual world is populated by a wide spectrum of photons of different frequencies, but due to our anatomy, our sensitivity peaks at three wavelengths, approximately red, green and blue. The entire color TV and video industry exploits this fact and achieves huge amounts of compression by transmitting three signals at these peak wavelengths. While I recognize that there are some certain mechanical elements in hearing, it seems to me that if this guy's arguments are sound, then we would have observed similar effects from watching TV-- that the absence of unperceived wavelengths would cause damage. Of course we all recognize that TV's bad for your health, but I don't think it causes the kind of damage he's alluding to.
Why prozac and not aspirin or tylenol? Safe, low cost pain killers have had a huge impact on people's lives, and spawned the entire pharmaceuticals juggernaut.
Slashdot Mirror
The comments so far are pretty inane and clearly come from windows users.. any word on how it impacts a dual-boot box? does it render your lilo or grub setup useless? I would personally be very upset if it screwed up my boot setup, and reasonably so, I think. imho, hese kinds of things should raise the hackles of the tech community, and linux users in general enough to give the vendor some serious shit.
what does it do to wine?
or the source IP address of the sender is not registered to the same domain that the mail originates from
Do you mean that the server should ensure the source IP isn't masqueraded, or that the originating domain in the From: header should match the domain of the IP address? In the latter case, refusing mail from mismatched domains would prevent me from using my email address at school when I send mail from home via my ISP. That's an important convenience I wouldn't want to give up, and I suspect that many more people use this feature.
I do agree with the rev DNS lookups and I think most well-configured SMTP servers already do that.
No, the press release says there's no "Linux" code and "Linux-ARM" code in older releases. They have yet to indicate whether there's any GPL'ed code in older releases.
later issues of the supporting software have had to have function names removed (along with a strategy of tokenising textual messages and compressing binaries)
In other words, that's the last time we're stupid enough to ship unstripped binaries!
The PR also explicitly denies using Linux source, rather than GPL'ed source. Reading between the lines, these guys know full well that they're in breach and they're trying to finesse the situation.
sh,csh,tcsh,bash,zsh,msh,ksh...
vi,emacs,pico,vim,xemacs,lucid-emacs...
mail,pine,elm,mutt...
Once upon a time there was twm. Once I'd learned how to configure it, they brought out fvwm. Great! Even more customization features! Then there was the wretched mess called fvwm2, with its Windows95 wannabe look-and-feel, followed shortly thereafter with Enlightenment. Wasn't E so cool? You could pixmap everything, and rxvt could do transparent backgrounds. Far out! Only trouble of course was that it was a CPU killer and ground my box to a halt. So I switched to Afterstep. Nice and clean and minimalist. Then WindowMaker (still my favourite), with the clip, and easy keybindings for jumping straight to the virtual desktop of your choice. Then E made a short-lived comeback, only to be boondoggled by sawmill. Or was it sawfish? By then I was so window-manager punch drunk that in a fit of insanity I went back to twm, and then WMaker again. Wait! what's this? metacity? (Somebody please explain to me how I can force new Mozilla instances to appear on workspace 3 and new Evolution instances on wsp 4-- oops, did I just mention two more products that were total rewrites over previously functional products?).
Every new window manager claims lightweight!, from scratch! with new uber-cool foo-controls and bar-widgets (not to mention antialiased wysiwyg thingys).
Now, don't get me wrong, only hardcore l33t h4x0rs still use twm, but clearly the commercial software industry isn't the only place that suffers from reinventing the wheel and forcing the user to learn about its fancy new gearshift.
I don't know how the core team manages its repositories, or what their submission policy is, but I would interpret this move as analogous to revoking MD's write access to cvs. I'm sure he's 'welcome' to continue to submit patches, just like any other schmoe. And of course, he's always free to fork..
Absolutely. And the mark of a brilliant scientist is one who sees how to transfer existing knowledge about one domain into another.
That being said, I highly doubt that Park's research has much to do with database mutexes. The courses I've taken in concurrency pretty much left me baffled. There's a lot more to it than thread safety.
or even better, read his publications. While deadlocks are deadlocks, his research isn't about databases but concurrency. If there wasn't technical merit to his work his peers would reject his publications.
If it's already been done then his peers would have rejected his publications. Just because it sounds like something you've heard of doesn't mean that it's an inferior technology.
It was an interesting piece, but it was posted before this afternoon's news conference, so I'm not sure if it was written before the data about the sensors was made public. Chances are Time's expert would revise some of his speculations based on that evidence.
Disaster magnitude? Hmm. Do you measure that in dollars, lives lost, or shaken public confidence? My first thought this morning was: why don't I get this upset over a downed twin-engine aircraft with seven passengers? Somehow this is bigger, but I hope it's not just because the plane they were flying was a lot more expensive..
I was in grade 8 when Challenger exploded, and I still remember Columbia's first flight and the excitement it generated.
You might be right about the end of the western world's publicly funded involvement in manned space flight, and I suspect that the visions we had as kids of building even modest colonies in space will not be realized within our lifetimes.
Obviously this is a tragic day for the families of those involved, but I think we will all come to mourn the loss of that dream of living in space. I wonder what Arthur C. Clarke is thinking about this.
The first round of globalization took place during the '80s. It was the free trade agreement between Canada and the US, followed shortly thereafter by NAFTA. Throughout the negotiations, Canadians bitched and whined that we'd lose our jobs to the cheap labour in, first, the States, and then Mexico. And from the blue-collar perspective, that was basically true. At the same time we complained about brain drain, where all our best engineers would end up stateside pulling in massive salaries.
;-)
The fact of the matter seems to be that American labour, while slightly more productive than Canadian, has also become much more expensive. True, many well-educated Canadians head south for the moula, but most stay right here, enjoying a lower cost of living at the cost of a little less take-home pay. Not to mention the lower likelihood of being shot.
No surprise that well-educated offshore engineers will make for stiff competition when you can just scp the night's code back to the US. All that being said, it still remains somewhat true that the most ambitious foreign techies all eventually end up heading for the States, where the opportunities are considered to be better. It's all about the American Dream, baby!
I'm not referring to license issues wrt plugins, but the claim on the deb list that the app needs to be customized to the present hardware- i386 vs i686, MMX, etc, etc. The only problem I see with this approach is that of ensuring the dependencies are detected properly, but that's the whole point of apt, rpm, and autoconf, at varying levels of abstraction. What's the difference if the debian installer does it or the user does it ten minutes later?
1. Distribute the rpm or deb as a tar archive that installs in /tmp
/tmp/mplayer-src;
./configure --prefix=/usr /tmp ./mplayer-src
2. make sure the rpm or deb depends on all the nifty things you want to include, as well as gcc.
3. post-install:
#!/bin/sh
cd
make
make install
cd
rm -rf
Jamie, your mistake was that you tried to install prebuilt binaries. Granted, there are UI issues with all of these players, but I'll only trust beta software to function on my machine if I build it from source. Otherwise you can almost guarantee that those RH 7.2 rpms were actually built on a 6.2 box using libc5 and exporting to deb and then back to rpm, or some other such nonsense.
That's a local problem, between the user and AOL's DNS servers. The article is descibing a different, higher-level problem between, for example, AOL's DNS servers and the root-level servers. If an AOL user's machine makes ten DNS requests for the same host, only one request should propagate past AOL's nameservers, but instead a misconfigured DNS will propagate all ten.
I can suddenly see lots of slashdot users thinking-- oh, I should fix my firewall, I have all these DNS requests; but that's normal operation for a client workstation. Your firewall would be broken only if all your DNS queries failed, and you'd know it pretty fast if that were the case.
The problem being that any of your neighbours can tune in and listen to your call. SMTP has the same problems- not even rudimentary encryption, no verification of the sender's identity, an architecture that encourages wide open relays, etc, etc.
Sure, but they pass those costs on to their subscribers. I think I should clarify my point-- if spam were a real problem for *big* business, then we would have solved the problem years ago with high quality filters and legislation.
Isn't it funny that pr0n makes up nearly the rest of the remaining 50%, and we're not holding conferences on how to eliminate it from the net..
I agree w/ you re the obsolescence of SMTP-- it's like 900MHz portable phones-- an idea past its time.
The best anti-spam method I've seen, bar none, is a friend of mine's opt-in method. His filters indicate the email addresses of people whose mail he's willing to accept, and dumps the rest in his spam folder. Just like call display- the messages that matter get to him and the junk gets junked. For personal email, I think this is the answer-- people with important personal things to say don't rely on email to do it, so if you miss a few, that's ok. Business-related email, is of course, another story, but I figure if SPAM were really a problem for businesses, it would already be solved.
C'mon, he's just looking for prior art before he patents his device!
I've been a fan for several years, but when the live CD's started to come out I thought- uh,oh, this is going to cost, and I stopped buying. $10 is a reasonable price to pay for those shows. I wonder if they'll turn a blind eye to people trading the album art from the CD releases of the same shows..
Yes, there's something strange about this article.. it starts off with some interesting stuff, and then some reasonable speculation, and then degrades into some pseudo-religious political rant about DRM and the music industry.
As I read this I couldn't help but thing about RGB displays. The visual world is populated by a wide spectrum of photons of different frequencies, but due to our anatomy, our sensitivity peaks at three wavelengths, approximately red, green and blue. The entire color TV and video industry exploits this fact and achieves huge amounts of compression by transmitting three signals at these peak wavelengths. While I recognize that there are some certain mechanical elements in hearing, it seems to me that if this guy's arguments are sound, then we would have observed similar effects from watching TV-- that the absence of unperceived wavelengths would cause damage. Of course we all recognize that TV's bad for your health, but I don't think it causes the kind of damage he's alluding to.
Why prozac and not aspirin or tylenol? Safe, low cost pain killers have had a huge impact on people's lives, and spawned the entire pharmaceuticals juggernaut.