Parabolic reflectors - such as a satellite dish - have only a single point of focus, whereas elliptical reflectors have two. The stunt in xkcd requires a fraction of an ellipse, not a parabola, and it therefore would not work. If you're going to geek out with an xkcd reference, at least do it properly!
Most MTAs are configured to send a bounce if message delivery permanently fails. That is, google won't be sending the bounce, but your mailserver will if google permanently refuses the message.
How do you think water gets to higher altitudes? Were it not for the sun, all of the water would stream down to the lowest point it could reach, and that would be that. Hydro is only "renewable" because the sun is constantly adding energy to the system, in the form of heat causing evaporation.
Photos don't testify at trials, people do. Generally if you have photographic evidence you need to have the cameraperson testify, and they will need to testify that they took the picture and establish (sometimes by establishing chain of custody/development procedures) that the picture reflects what they saw and how someone edited or added things.
I'd like to second the "get things in writing" sentiment, and share a small story -- I was somewhat new to a job, and my pointy haired boss wanted me to run a certain undocumented script that a previous employee had written because he thought it would do what he wanted, but what the script would do when ran was unclear, as was what the intended effect was... and it was clear the script was doing things like truncating tables and doing lots of inserts and otherwise being destructive, and because I had no idea what it would do if I ran it (or, for that matter, what my boss thought it would do/wanted it to do) I sent him an email outlining that I really had no idea what following his directions would do, it could cause massive data loss and the crash of the fairly critical system it was a part of, and that if he really wanted me to run it without further examination (which he ended up wanting) to email me back and say so.
This boss was notorious for receiving emails and then walking up to your cubicle and saying "yeah, got your email, that sounds good" - evading having to give a reply in email. So I sent the email, grabbed a drink, and went up to the roof deck to wait for him to get the email, fail to find me in person, and reply to the email. It worked without a hitch (both the attempt to get an email out of him and the actual script, for the curious)
And now it's a great story for myself and my coworkers (who were aware of and supportive of the roof hiding the whole time)
There's actually a big difference between not specifying an alt tag and setting alt="" - it's similar to the difference between a NULL and an empty string in a database.
Specifying alt="" is explicitly telling the user agent that no text is needed (just an empty string will suffice!) to replace this image if you can't/won't display the image. Not specifying an alt tag gives no direction at all to the useragent about what to do if it can't handle the image itself.
Because it evicts my precious video files in favor of less important data.
Why is this decision wrong? Sure, you've got more domain knowledge than the kernel, but I'd be curious as to real world cases where you would know better than the OS in cases like this. LRU is a pretty good mechanism for determining what needs to be removed from a cache and flushed to disk, no?
Is it sad that I can't tell whether this is a joke or not?
ed is generally regarded as having a far steeper learning curve than vi, yet it has significantly fewer commands than vi, so I think it could go either way.
Anyone who says that Lars living Fry's old life breaks continuity does not understand paradox-free time travel.
To resolve common time travel paradoxes, you simply allow for any backward travel to essentially fork() the universe, and then both universes continue on accordingly. It was suggested in the movie that the two possible outcomes of this are destroying the universe (running out of system resources, fork() never returning) and also, a 'doom' factor causing the two universe processes to re-converge at a point.
I'm pretty comfortable with the fact that Seymour waited there until his death and never saw Fry again, AND that Seymor saw Fry again the next day. They both are equally valid, even though they appear to contradict.
I'm also a sucker for endings that pull on your heartstrings - and this movie ranked up there with Jurassic Bark for emotional response at the end.
I did apologize to those who watched it with me, however, as they weren't really futurama fans, and all of the in-jokes were a bit much for them. I found myself having to explain why santa was a robot who killed things, etc.
Does anyone know how strong the sales were? I'm trying to decide whether I should buy my own copy - I don't really ever buy DVDs, but I will to keep Futurama alive!
Having a threaded kernel or having fine-grained locking is hardly a reasonable barrier for "proper SMP support." If I have two processors and they can be both running code at the same time, it's SMP support - everything else is just icing.
On virtually every CPU bound application, the time is spent not in the kernel, but in userland.
I'd like to echo that, but in my case (and surely I'm not alone) using the source (UTSL!) is not a last resort, rather, it's usually the second or third thing I do. The first thing I do is check the native documentation (man page, documentation from a website), the second thing - and this is only if it's a popular application and I received a specific/distinct error message - is I google for the behavior, the third thing is the source, and then the fourth is consulting/asking other people about it.
For some projects - postfix comes to mind - I have the source around (I use FreeBSD on my desktop and install software with the ports system, so any software I've installed there I have the source waiting in a work directory in/usr/ports - this is the big benefit, as I see it, of having much larger disks now than I did 10 years ago) and I actually will check the source before I read a lot of the detailed documentation. Once you've peeked under the hood for one thing and gotten a rough idea of how the code is laid out, it quickly becomes faster to go back to it than to go to the documentation.
If we lived in a world of waterfall development and top-down project management, the importance of source would be greatly diminished unless you were tracking down a bug. But the reality is we don't often have very good specifications or documentation, and when there is discordance between the source and the documentation in the open source world, sometimes the bug is in the documentation, not the code. That's an important distinction.
Where I live (Washington DC) the police respond very slowly (if at all) to 911 calls in poorer neighborhoods, and when they do roll through these parts, they hassle whoever they find, bring in helicopters and floodlamps to intimidate people (I had an artificial sun shining into my window every night for a week), and sometimes shoot and kill unarmed people, sometimes children.
If you think local law enforcement is there to help everyone, then well, you either must live in Mayberry or I have a bridge in New York to sell you.
I agree entirely that the US needs to stop supporting economic and military processes that destroy livelihoods across the world. But that doesn't appear to be happening anytime soon, so for as long as the US is training paramilitaries and militarizes on how to oppress their own people, for as long as neoliberalism is ensuring that borders are open to capital, the borders should be open to people.
There is a pro-immigration slogan that is used, We didn't cross the border, the border crossed us. And if you're familiar with American history, you'd know that Mexico (Spain), Canada (Britain and France), and the British American colonial forces/United States all waged war on the native population of the Americas, and that later the US went to war with Mexico, and that people were displaced and large swaths of land annexed. US policy was to destroy indigenous culture: both military, economic, and social forces were brought to bare to attempt to destroy traditional ways. The reservation is the embodiment of this policy. Policies that aim to destroy a national or ethnic identity are defined by the United Nations as genocide.
I think a lot of people don't want to come to terms with the fact that a large chunk of this country wasn't found empty, rather, it was conquered, and it was cleansed. I bring this up for one reason: Most of the Latinos that I know have very significant indigenous American features. Yes, there are white Hispanics, the descendants of the settlers from Spain and elsewhere, but they are not the majority. The majority of Latinos, who are legally considered 'immigrants,' that I know are indigenous to the continent, including areas (recall that in desert areas, people are often nomadic) that are now annexed by the US. So, I ask you: who is the immigrant? who is the one being generous, and who is the one taking what's not theirs?
Recall that the US military was actively fighting (killing) the indigenous of this country through 1891, with the last notable massacre being at Wounded Knee at the end of 1890. My grandfather was born in 1893. Recall that native languages were generally unwelcome in schools (even on reservations) until 1990, when Bush I signed the Native American Languages Act into law. This isn't ancient history, it's today. It's now, it's our fathers, it's our grandfathers, and it's our great-grandfathers. And make no mistake about it - if wealth can be inherited and preserved for so long (Rockefeller's great grandchildren?) then so can liens, and one day, they will come due.
Except BD discs have a higher capacity than HD-DVD discs, so you'd be able to encode the blu-ray content at a higher bitrate, holding all else the same.
I don't see what's wrong with being penalized for using "\n" instead of endl - endl is more portable, as it does not assume that \n is used for newlines. I believe endl also forces the stream to be flushed, whereas \n does not.
What graphics? I just rewatched the movie a couple days ago, and I didn't notice any graphics that didn't fit in the period.
The unrealistic part of the movie has to do with the AI capabilities of the program and the complexity of the system overall, and the fact that the military would connect WOPR to a modem and have it answer incoming calls.
I consider not running things as root a more significant risk then the possibility of "users" breaking a nologin user account. On any "important" system, the only users would be administrators anyway, wouldn't it?
I don't think so, said machine would be utterly useless.... If there is a lesson of the last 30 years, it's that if you are supplying any sort of input data, you are a 'user' of the application. If you send an email to a host, you are using that host's MTA, if you are visiting a website, you are a user of apache. It needn't matter that you aren't a user with your own account on the system. Vulnerabilities are real - format string, buffer overflow, lack of validation, injection...
Really, it's security in layers. I think AppArmor is the type of solution that lets you do what you really want --- limit the syscalls that the application can execute with root privilege -- and then there's yet another layer of security.
I think discussion of jury nullification in the history of the US isn't complete without mentioning the time and place it was most actively used -- the post-civil war south, to acquit white people accused of crimes against black people.
Time after time, people accused of lynching, Klan violence, and similar were let go by the juries. Until very, very recently this was the norm, and not the exception. It is worth mentioning.
That being said, while I am not a fan of the Klan, I am a fan of jury nullification... and of picking fair juries.
Slashdot Mirror
Parabolic reflectors - such as a satellite dish - have only a single point of focus, whereas elliptical reflectors have two. The stunt in xkcd requires a fraction of an ellipse, not a parabola, and it therefore would not work. If you're going to geek out with an xkcd reference, at least do it properly!
Most MTAs are configured to send a bounce if message delivery permanently fails. That is, google won't be sending the bounce, but your mailserver will if google permanently refuses the message.
How do you think water gets to higher altitudes? Were it not for the sun, all of the water would stream down to the lowest point it could reach, and that would be that. Hydro is only "renewable" because the sun is constantly adding energy to the system, in the form of heat causing evaporation.
Make it the MAC address and everyone on your segment can guess it.
Unless wikipedia and every site I've found on google is wrong, P4 phosphors are white. Sure you don't mean P1?
http://en.wikipedia.org/wiki/Monochrome_monitor
That's the only benchmark that matters if all you're planning to do with the machine is compile the Linux kernel.
Photos don't testify at trials, people do. Generally if you have photographic evidence you need to have the cameraperson testify, and they will need to testify that they took the picture and establish (sometimes by establishing chain of custody/development procedures) that the picture reflects what they saw and how someone edited or added things.
Public key cryptography solved the key exchange problem years ago. Why send keys in the mail?
I'd like to second the "get things in writing" sentiment, and share a small story -- I was somewhat new to a job, and my pointy haired boss wanted me to run a certain undocumented script that a previous employee had written because he thought it would do what he wanted, but what the script would do when ran was unclear, as was what the intended effect was... and it was clear the script was doing things like truncating tables and doing lots of inserts and otherwise being destructive, and because I had no idea what it would do if I ran it (or, for that matter, what my boss thought it would do/wanted it to do) I sent him an email outlining that I really had no idea what following his directions would do, it could cause massive data loss and the crash of the fairly critical system it was a part of, and that if he really wanted me to run it without further examination (which he ended up wanting) to email me back and say so.
This boss was notorious for receiving emails and then walking up to your cubicle and saying "yeah, got your email, that sounds good" - evading having to give a reply in email. So I sent the email, grabbed a drink, and went up to the roof deck to wait for him to get the email, fail to find me in person, and reply to the email. It worked without a hitch (both the attempt to get an email out of him and the actual script, for the curious)
And now it's a great story for myself and my coworkers (who were aware of and supportive of the roof hiding the whole time)
The difference is that the XFree86-Xorg divide contained quite a few peeved formerly XFree86 developers.
What established pidgin developers are preparing to jump ship?
There's actually a big difference between not specifying an alt tag and setting alt="" - it's similar to the difference between a NULL and an empty string in a database.
Specifying alt="" is explicitly telling the user agent that no text is needed (just an empty string will suffice!) to replace this image if you can't/won't display the image. Not specifying an alt tag gives no direction at all to the useragent about what to do if it can't handle the image itself.
Why is this decision wrong? Sure, you've got more domain knowledge than the kernel, but I'd be curious as to real world cases where you would know better than the OS in cases like this. LRU is a pretty good mechanism for determining what needs to be removed from a cache and flushed to disk, no?
Is it sad that I can't tell whether this is a joke or not?
ed is generally regarded as having a far steeper learning curve than vi, yet it has significantly fewer commands than vi, so I think it could go either way.
Anyone who says that Lars living Fry's old life breaks continuity does not understand paradox-free time travel.
To resolve common time travel paradoxes, you simply allow for any backward travel to essentially fork() the universe, and then both universes continue on accordingly. It was suggested in the movie that the two possible outcomes of this are destroying the universe (running out of system resources, fork() never returning) and also, a 'doom' factor causing the two universe processes to re-converge at a point.
I'm pretty comfortable with the fact that Seymour waited there until his death and never saw Fry again, AND that Seymor saw Fry again the next day. They both are equally valid, even though they appear to contradict.
http://en.wikipedia.org/wiki/Grandfather_paradox
Nope, I loved it too.
I'm also a sucker for endings that pull on your heartstrings - and this movie ranked up there with Jurassic Bark for emotional response at the end.
I did apologize to those who watched it with me, however, as they weren't really futurama fans, and all of the in-jokes were a bit much for them. I found myself having to explain why santa was a robot who killed things, etc.
Does anyone know how strong the sales were? I'm trying to decide whether I should buy my own copy - I don't really ever buy DVDs, but I will to keep Futurama alive!
Having a threaded kernel or having fine-grained locking is hardly a reasonable barrier for "proper SMP support." If I have two processors and they can be both running code at the same time, it's SMP support - everything else is just icing.
On virtually every CPU bound application, the time is spent not in the kernel, but in userland.
I'd like to echo that, but in my case (and surely I'm not alone) using the source (UTSL!) is not a last resort, rather, it's usually the second or third thing I do. The first thing I do is check the native documentation (man page, documentation from a website), the second thing - and this is only if it's a popular application and I received a specific/distinct error message - is I google for the behavior, the third thing is the source, and then the fourth is consulting/asking other people about it.
For some projects - postfix comes to mind - I have the source around (I use FreeBSD on my desktop and install software with the ports system, so any software I've installed there I have the source waiting in a work directory in /usr/ports - this is the big benefit, as I see it, of having much larger disks now than I did 10 years ago) and I actually will check the source before I read a lot of the detailed documentation. Once you've peeked under the hood for one thing and gotten a rough idea of how the code is laid out, it quickly becomes faster to go back to it than to go to the documentation.
If we lived in a world of waterfall development and top-down project management, the importance of source would be greatly diminished unless you were tracking down a bug. But the reality is we don't often have very good specifications or documentation, and when there is discordance between the source and the documentation in the open source world, sometimes the bug is in the documentation, not the code. That's an important distinction.
Where I live (Washington DC) the police respond very slowly (if at all) to 911 calls in poorer neighborhoods, and when they do roll through these parts, they hassle whoever they find, bring in helicopters and floodlamps to intimidate people (I had an artificial sun shining into my window every night for a week), and sometimes shoot and kill unarmed people, sometimes children.
If you think local law enforcement is there to help everyone, then well, you either must live in Mayberry or I have a bridge in New York to sell you.
I agree entirely that the US needs to stop supporting economic and military processes that destroy livelihoods across the world. But that doesn't appear to be happening anytime soon, so for as long as the US is training paramilitaries and militarizes on how to oppress their own people, for as long as neoliberalism is ensuring that borders are open to capital, the borders should be open to people.
There is a pro-immigration slogan that is used, We didn't cross the border, the border crossed us. And if you're familiar with American history, you'd know that Mexico (Spain), Canada (Britain and France), and the British American colonial forces/United States all waged war on the native population of the Americas, and that later the US went to war with Mexico, and that people were displaced and large swaths of land annexed. US policy was to destroy indigenous culture: both military, economic, and social forces were brought to bare to attempt to destroy traditional ways. The reservation is the embodiment of this policy. Policies that aim to destroy a national or ethnic identity are defined by the United Nations as genocide.
I think a lot of people don't want to come to terms with the fact that a large chunk of this country wasn't found empty, rather, it was conquered, and it was cleansed. I bring this up for one reason: Most of the Latinos that I know have very significant indigenous American features. Yes, there are white Hispanics, the descendants of the settlers from Spain and elsewhere, but they are not the majority. The majority of Latinos, who are legally considered 'immigrants,' that I know are indigenous to the continent, including areas (recall that in desert areas, people are often nomadic) that are now annexed by the US. So, I ask you: who is the immigrant? who is the one being generous, and who is the one taking what's not theirs?
Recall that the US military was actively fighting (killing) the indigenous of this country through 1891, with the last notable massacre being at Wounded Knee at the end of 1890. My grandfather was born in 1893. Recall that native languages were generally unwelcome in schools (even on reservations) until 1990, when Bush I signed the Native American Languages Act into law. This isn't ancient history, it's today. It's now, it's our fathers, it's our grandfathers, and it's our great-grandfathers. And make no mistake about it - if wealth can be inherited and preserved for so long (Rockefeller's great grandchildren?) then so can liens, and one day, they will come due.
Except BD discs have a higher capacity than HD-DVD discs, so you'd be able to encode the blu-ray content at a higher bitrate, holding all else the same.
Am I missing something?
I don't see what's wrong with being penalized for using "\n" instead of endl - endl is more portable, as it does not assume that \n is used for newlines. I believe endl also forces the stream to be flushed, whereas \n does not.
What graphics? I just rewatched the movie a couple days ago, and I didn't notice any graphics that didn't fit in the period.
The unrealistic part of the movie has to do with the AI capabilities of the program and the complexity of the system overall, and the fact that the military would connect WOPR to a modem and have it answer incoming calls.
I'm not sure if you've noticed, but all across the world forests are shrinking at an alarming rate.
I don't think so, said machine would be utterly useless.... If there is a lesson of the last 30 years, it's that if you are supplying any sort of input data, you are a 'user' of the application. If you send an email to a host, you are using that host's MTA, if you are visiting a website, you are a user of apache. It needn't matter that you aren't a user with your own account on the system. Vulnerabilities are real - format string, buffer overflow, lack of validation, injection...
Really, it's security in layers. I think AppArmor is the type of solution that lets you do what you really want --- limit the syscalls that the application can execute with root privilege -- and then there's yet another layer of security.
I think discussion of jury nullification in the history of the US isn't complete without mentioning the time and place it was most actively used -- the post-civil war south, to acquit white people accused of crimes against black people.
Time after time, people accused of lynching, Klan violence, and similar were let go by the juries. Until very, very recently this was the norm, and not the exception. It is worth mentioning.
That being said, while I am not a fan of the Klan, I am a fan of jury nullification... and of picking fair juries.