If you haven't used iostat before: Run "iostat -x 2" to get a report of block device utilization every two seconds. Ignore the first report; it details utilization since system boot. All subsequent reports will be for the period after the previous report.
If you can repeat your earlier tests, and want to see if there's actually a Linux bug, compare numbers when the program opens DBs before forking, and when it opens them after. If you're seeing bad latency in the former case, but similar B/s, that might indicate a bug. If you're seeing much higher %system (CPU), that might be a bug. Maybe. Otherwise, it's probably an indication that the program behaves differently in those cases, which is not a Linux bug.
so it's not the *actual* loadavg that is relevant but that the *relative* loadavg before and after that one simple change was so dramatically shifted from "completely unusable and in no way deployable in a live production environment" to a "this might actually fly, jim" level.
That's not loadavg, that's IO latency. You should probably be using iostat to get useful numbers.
loadavg is completely useless when discussing system performance, it is in no way related.
I'll start with: LMDB is awesome, and I am super SUPER impressed with OpenLDAP's benchmarks over the last several years. I do not question LMDB's worth.
I'm just not really sure that this letter is evidence thereof. The author got poor performance from a SQL database with no indexing, which degraded as the number of records grew? You don't say! A database that has to do a full scan for reads performs poorly?
Surprise about load average seems equally naive. If you fork a bunch of processes that are doing IO, of COURSE the load increases. Load is a measure of the number of processes not sleeping. That's all it is. I don't understand his surprise that a system steadily doing a great deal of IO would show a lot of time spent in IO calls in profiling.
Reading that letter made me cringe. It didn't help that it sounds like another NSA project.
From the CVE, I'm pretty sure the problem isn't limited to CGI written in Bash. The problem affects any CGI that *calls* bash, which means any call to system() in any language is going to cause a problem.
I seriously doubt that she considered your holding the door open an assult. She probably considered it disrespectful, and unless you are equally likely to hold a door for any person, then it could certainly be considered condescending from a certain point of view.
The issue isn't that intent doesn't matter, it is that intent doesn't matter more than the subjective experience of the second party. Their perception of your actions is equally important to your intent. When you are able to accept other people as equals, and not as subordinates, you'll understand why that's the right way to handle the situation.
Again, that doesn't mean that a complaint is always valid. Mediation is intended to determine both intent and perception, to explain both to each party, and whenever possible, to provide guidelines for everyone to ensure that future interactions don't create further offense.
the problem is that it doesnt matter if any harassment or assault happens these days. all there needs to be for sexual assault/harassment is for someone to "feel" abused, intent no longer matters.
You're correct in identifying the standard that is used for sexual harassment. If someone feels harassed, then the issue is treated as harassment. That is not, however, the problem or a problem. It doesn't mean that you'll be fired or even disciplined as a result of the complaint. All it means is that when an employee submits a harassment complaint, that HR treats the complaint seriously and investigates each complaint consistently. If they find that the complaint warrants discipline, then the offending person will be disciplined. Otherwise, there may simply be mediation to remedy the situation.
Your attitude, ganjadude, that treating harassment claims seriously based on the subjective experience of the person making the claim is "the" problem almost certainly indicates that you take criticism poorly. The problem with harassment is that people against whom complaints are made often retaliate against the person making the complaint rather than accepting criticism and working to create an environment where people feel safe.
We have more than enough people telling us how difficult things are and how we shouldn't try
We also hear more than enough people telling us that the climate will change unless we stop burning fossil fuels. Do you want someone to tell you how to make ongoing burning of fossil fuels "work" too? It won't.
If a lot of people are telling you a thing, you might want to consider that they may be right.
I was talking to a friend of mine recently about OpenSSL, and the developers' complaint that they aren't receiving financial or development support from some of the companies that use and benefit most from the software. My point of view is that if you, as a developer, need financial or development support from the users of your software, you need to tell them so. If you don't tell them what support you need in exchange, then you aren't going to get it. The best place for the terms of that agreement is your license. If your license demands nothing in return for your software, very often you will receive nothing for your software. While this is an unpopular opinion, I believe it is their own fault, and not the fault of the users of their software, that they aren't getting the support that they need.
I think it's easy to make the argument that Linux is more significant than GNU. Android is a Linux operating system, without GNU. DD-WRT and similar systems are Linux, without GNU. However, I personally think that Linux is less significant than the GPL. The license gave us a means to collaborate, to create open systems, and to get the support that we need for the software that we develop.
I saw a talk on Ceph at LISA '13 and it seemed pretty cool, except that afterward I wasn't able to find any documentation specifically about making backups of Ceph object stores.
In general, I think backup infrastructure on Linux isn't great. I'm working to make that better, but generating interest in backup infrastructure is a hard sell. Shameless plug: https://bitbucket.org/gordonme...
You do not badmouth your former employer, no matter what they did
To quote Chris Rock, "Ain't nobody above an ass whoopin."
It's certainly true that if you publicly air your grievances against a former employer, you'll probably never work there or with those people in the future. However, there is definitely a time when you are certain that you no longer want to work with those people, and a time when it's appropriate to warn the community that they hire from that employment comes with serious issues.
Personally, I think we have just as much responsibility to our community of co-workers as we do to our employer. People who never speak up are abdicating the responsibility that we have to each other.
I don't think TV would be less patentable with a digital circuit. I am advocating abolishment of software patents. That is, the software itself should not be subject to patent. If I have a general purpose computing device, I should be able to create software for any function that the device is capable of.
My understanding is that active matrix displays refresh one line at a time, but display the entire image during the scan. In any case, that isn't really the point. The point is that his invention has been fundamental to display technology since the time of the invention. It is an excellent example of technology worthy of patent.
If you have something valuable to contribute, I'd be happy to respond to it.
I finished a book a while ago that I think really illustrates why software patents are objectionable, and what's wrong with the patent system as a whole, today.
The book is "The Last Lone Inventor" by Evan I. Schwartz. It describes the work of Philo T. Farnsworth to create television. During the time that Philo was working on television, many scientists employed by the radio industry were also working to develop usable video transmission technology, with inferior designs. Most of their work involved mechanical television cameras that used spinning wheels. Philo's invention was all electronic. It scanned, transmitted, and displayed a line at a time to create a two dimensional image. This remained the fundamental technology in displays at least until LCD and plasma screens replaced CRT.
Now, while many other patent related problems were well demonstrated by the book, the one most clearly related to software patents pertains to the intent of the patent system. Patents are not, as they are often regarded today, a recognition that an inventor owns his ideas. Ideas are not property, and have never been recognized as such. Patents are a recognition that some inventions rely on information that isn't obvious. Some inventions require the inventors to test and improve their inventions for years before they can be brought to market. Underlying the patent system is the belief that this work will not be done, that inventors will not fund years of experimentation and development, if they don't believe that they'll be able to sell that invention to recover the costs of its development. In a free market, competitors will be able to offer the same invention at a lower cost than its inventor, because the competitors did not have to invest in the development of the invention. Patents attempt to create an incentive to invent by ensuring that inventors who do invest in development are given a limited monopoly on their invention.
However, patents aren't free. It is not enough for the inventor to merely offer his invention to the market to receive patent protection on it. An inventor is also required to completely disclose how the invention works. After the patent period expires, the public must be able to continue using the invention independent of the inventor.
That is the fundamental purpose of the patent system: to benefit the public by providing it with the knowledge required to reproduce the invention. It is the public's benefit, not the inventors, that is the goal of the patent system. The inventor's benefit is simply the means to achieve that goal. The Constitution of the United States reflects this: To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries
Philo's work was exactly the progress of science that the patent system was intended to promote. His invention required tremendous investment to create. His idea was sound, but a great deal of experimentation was required to create a working device. Other highly skilled scientists were not able to create a working device on their own, or created working devices of significantly lesser quality. The exact properties of the materials and components used in the camera and television set were not previously known, and were discovered through Philo T. Farnsworth's experimentation and development.
The invention of television was worthy of patent protection.
Software development isn't like the invention of television in ANY way.
Software development does involve testing cycles, but otherwise almost never involves the kind of experimentation involved in the invention of television, because the exact properties of computer operations are previously known. Computers perform a limited number of operations, exactly according to a specification, and exactly the same every time. Because the behavior of the system is known in advance, the uncertainty inherent in real world material inventions does not exist in software development.
Why would you presume that? These modems typically have just one IP address, and I would presume that they NAT using the same one for the XFINITY wireless and for the home user. If a third party records a download of child porn or copyrighted material, they don't have access to the internal identity of the machine, they would only have the IP address Lacking clarification, I think the prudent thing to do is assume that the IP address is going to be the subscriber's, and that this could create the appearance of liability.
IPv4 space is very limited. I really doubt that Comcast is going to double their required network size by assigning separate addresses to the home subscriber and to the XFINITY wireless user. This could be a real problem.
If you haven't used iostat before: Run "iostat -x 2" to get a report of block device utilization every two seconds. Ignore the first report; it details utilization since system boot. All subsequent reports will be for the period after the previous report.
If you can repeat your earlier tests, and want to see if there's actually a Linux bug, compare numbers when the program opens DBs before forking, and when it opens them after. If you're seeing bad latency in the former case, but similar B/s, that might indicate a bug. If you're seeing much higher %system (CPU), that might be a bug. Maybe. Otherwise, it's probably an indication that the program behaves differently in those cases, which is not a Linux bug.
so it's not the *actual* loadavg that is relevant but that the *relative* loadavg before and after that one simple change was so dramatically shifted from "completely unusable and in no way deployable in a live production environment" to a "this might actually fly, jim" level.
That's not loadavg, that's IO latency. You should probably be using iostat to get useful numbers.
loadavg is completely useless when discussing system performance, it is in no way related.
I'll start with: LMDB is awesome, and I am super SUPER impressed with OpenLDAP's benchmarks over the last several years. I do not question LMDB's worth.
I'm just not really sure that this letter is evidence thereof. The author got poor performance from a SQL database with no indexing, which degraded as the number of records grew? You don't say! A database that has to do a full scan for reads performs poorly?
Surprise about load average seems equally naive. If you fork a bunch of processes that are doing IO, of COURSE the load increases. Load is a measure of the number of processes not sleeping. That's all it is. I don't understand his surprise that a system steadily doing a great deal of IO would show a lot of time spent in IO calls in profiling.
Reading that letter made me cringe. It didn't help that it sounds like another NSA project.
In the other case the other person can't access Internet as he wants due to actively being suppressed by the first user.
I can't actually tell if that sentence describes the person using BitTorrent, or the person using BitHammer.
Tor is ineffective if Javascript is enabled
I don't know what you're talking about. Tor's FAQ notes that they leave Javascript enabled by default.
Because it's more similar to Android AOSP than OEM ROMs are.
There are some interesting things in CM for Nexus and Google Play devices, but most of the time I'd expect CM to replace the ROM on other handsets.
From the CVE, I'm pretty sure the problem isn't limited to CGI written in Bash. The problem affects any CGI that *calls* bash, which means any call to system() in any language is going to cause a problem.
I seriously doubt that she considered your holding the door open an assult. She probably considered it disrespectful, and unless you are equally likely to hold a door for any person, then it could certainly be considered condescending from a certain point of view.
The issue isn't that intent doesn't matter, it is that intent doesn't matter more than the subjective experience of the second party. Their perception of your actions is equally important to your intent. When you are able to accept other people as equals, and not as subordinates, you'll understand why that's the right way to handle the situation.
Again, that doesn't mean that a complaint is always valid. Mediation is intended to determine both intent and perception, to explain both to each party, and whenever possible, to provide guidelines for everyone to ensure that future interactions don't create further offense.
the problem is that it doesnt matter if any harassment or assault happens these days. all there needs to be for sexual assault/harassment is for someone to "feel" abused, intent no longer matters.
You're correct in identifying the standard that is used for sexual harassment. If someone feels harassed, then the issue is treated as harassment. That is not, however, the problem or a problem. It doesn't mean that you'll be fired or even disciplined as a result of the complaint. All it means is that when an employee submits a harassment complaint, that HR treats the complaint seriously and investigates each complaint consistently. If they find that the complaint warrants discipline, then the offending person will be disciplined. Otherwise, there may simply be mediation to remedy the situation.
Your attitude, ganjadude, that treating harassment claims seriously based on the subjective experience of the person making the claim is "the" problem almost certainly indicates that you take criticism poorly. The problem with harassment is that people against whom complaints are made often retaliate against the person making the complaint rather than accepting criticism and working to create an environment where people feel safe.
We have more than enough people telling us how difficult things are and how we shouldn't try
We also hear more than enough people telling us that the climate will change unless we stop burning fossil fuels. Do you want someone to tell you how to make ongoing burning of fossil fuels "work" too? It won't.
If a lot of people are telling you a thing, you might want to consider that they may be right.
Comcast is in the wrong posision, here:
http://arstechnica.com/tech-po...
That might help explain why there is an ongoing cross-species obesity epidemic.
http://science-beta.slashdot.o...
Trivia: you mean "newspeak". It's a reference to 1984:
http://en.wikipedia.org/wiki/N...
It is not a reference to news.
I was talking to a friend of mine recently about OpenSSL, and the developers' complaint that they aren't receiving financial or development support from some of the companies that use and benefit most from the software. My point of view is that if you, as a developer, need financial or development support from the users of your software, you need to tell them so. If you don't tell them what support you need in exchange, then you aren't going to get it. The best place for the terms of that agreement is your license. If your license demands nothing in return for your software, very often you will receive nothing for your software. While this is an unpopular opinion, I believe it is their own fault, and not the fault of the users of their software, that they aren't getting the support that they need.
I think it's easy to make the argument that Linux is more significant than GNU. Android is a Linux operating system, without GNU. DD-WRT and similar systems are Linux, without GNU. However, I personally think that Linux is less significant than the GPL. The license gave us a means to collaborate, to create open systems, and to get the support that we need for the software that we develop.
I saw a talk on Ceph at LISA '13 and it seemed pretty cool, except that afterward I wasn't able to find any documentation specifically about making backups of Ceph object stores.
In general, I think backup infrastructure on Linux isn't great. I'm working to make that better, but generating interest in backup infrastructure is a hard sell. Shameless plug:
https://bitbucket.org/gordonme...
... all the while running Linux on their servers.
You do not badmouth your former employer, no matter what they did
To quote Chris Rock, "Ain't nobody above an ass whoopin."
It's certainly true that if you publicly air your grievances against a former employer, you'll probably never work there or with those people in the future. However, there is definitely a time when you are certain that you no longer want to work with those people, and a time when it's appropriate to warn the community that they hire from that employment comes with serious issues.
Personally, I think we have just as much responsibility to our community of co-workers as we do to our employer. People who never speak up are abdicating the responsibility that we have to each other.
I don't think TV would be less patentable with a digital circuit. I am advocating abolishment of software patents. That is, the software itself should not be subject to patent. If I have a general purpose computing device, I should be able to create software for any function that the device is capable of.
So you FULLY support software patents, wherever the software in question controls a (finicky) physical object?
I said software patents should be abolished. I'm not sure what led you to the conclusion that I support software patents.
Concrete examples: GIF was patented, but PNG was not, and is superior.
RSA was patented, but AES (Rjindael) is not.
I don't think it's at all accurate to say that "nobody" will invest in advanced computing algorithms without patents.
My understanding is that active matrix displays refresh one line at a time, but display the entire image during the scan. In any case, that isn't really the point. The point is that his invention has been fundamental to display technology since the time of the invention. It is an excellent example of technology worthy of patent.
If you have something valuable to contribute, I'd be happy to respond to it.
I finished a book a while ago that I think really illustrates why software patents are objectionable, and what's wrong with the patent system as a whole, today.
The book is "The Last Lone Inventor" by Evan I. Schwartz. It describes the work of Philo T. Farnsworth to create television. During the time that Philo was working on television, many scientists employed by the radio industry were also working to develop usable video transmission technology, with inferior designs. Most of their work involved mechanical television cameras that used spinning wheels. Philo's invention was all electronic. It scanned, transmitted, and displayed a line at a time to create a two dimensional image. This remained the fundamental technology in displays at least until LCD and plasma screens replaced CRT.
Now, while many other patent related problems were well demonstrated by the book, the one most clearly related to software patents pertains to the intent of the patent system. Patents are not, as they are often regarded today, a recognition that an inventor owns his ideas. Ideas are not property, and have never been recognized as such. Patents are a recognition that some inventions rely on information that isn't obvious. Some inventions require the inventors to test and improve their inventions for years before they can be brought to market. Underlying the patent system is the belief that this work will not be done, that inventors will not fund years of experimentation and development, if they don't believe that they'll be able to sell that invention to recover the costs of its development. In a free market, competitors will be able to offer the same invention at a lower cost than its inventor, because the competitors did not have to invest in the development of the invention. Patents attempt to create an incentive to invent by ensuring that inventors who do invest in development are given a limited monopoly on their invention.
However, patents aren't free. It is not enough for the inventor to merely offer his invention to the market to receive patent protection on it. An inventor is also required to completely disclose how the invention works. After the patent period expires, the public must be able to continue using the invention independent of the inventor.
That is the fundamental purpose of the patent system: to benefit the public by providing it with the knowledge required to reproduce the invention. It is the public's benefit, not the inventors, that is the goal of the patent system. The inventor's benefit is simply the means to achieve that goal. The Constitution of the United States reflects this:
To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries
Philo's work was exactly the progress of science that the patent system was intended to promote. His invention required tremendous investment to create. His idea was sound, but a great deal of experimentation was required to create a working device. Other highly skilled scientists were not able to create a working device on their own, or created working devices of significantly lesser quality. The exact properties of the materials and components used in the camera and television set were not previously known, and were discovered through Philo T. Farnsworth's experimentation and development.
The invention of television was worthy of patent protection.
Software development isn't like the invention of television in ANY way.
Software development does involve testing cycles, but otherwise almost never involves the kind of experimentation involved in the invention of television, because the exact properties of computer operations are previously known. Computers perform a limited number of operations, exactly according to a specification, and exactly the same every time. Because the behavior of the system is known in advance, the uncertainty inherent in real world material inventions does not exist in software development.
Why would you presume that? These modems typically have just one IP address, and I would presume that they NAT using the same one for the XFINITY wireless and for the home user. If a third party records a download of child porn or copyrighted material, they don't have access to the internal identity of the machine, they would only have the IP address Lacking clarification, I think the prudent thing to do is assume that the IP address is going to be the subscriber's, and that this could create the appearance of liability.
IPv4 space is very limited. I really doubt that Comcast is going to double their required network size by assigning separate addresses to the home subscriber and to the XFINITY wireless user. This could be a real problem.
So can we all get on the bandwagon with Fedora and start using NSS instead?
http://fedoraproject.org/wiki/...
This link cannot be shared enough:
http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/