According to Theodore Feder, president of the ARS, "There are underlying copyrights to the works of Miro, and they are putting it up without having the rights"
He's thinking of patents. Copyrights only cover a specific creation of a work. If Google's work was created entirely by them then there's no legal issue here, no matter what ARS thinks. Feder needs to talk to a lawyer before making public statements like that. It only makes him look woefully ignorant of the law (and greedy at the same time).
MySQL responds by getting Solid Information Technology, a proprietary database vendor, to take its solidDB Storage Engine for MySQL open source, under the GPL, starting in June.
Why? InnoDB was already GPL'd. Why not continue to use and develop it? Instead MySQL is going to switch to something completely different with source no one has seen yet (therefore no one outside of Solid is familiar with the codebase). What's to stop Oracle for making Solid Tech a great offer and buying them up? Then MySQL could be starting this cycle over again.
Maybe they didn't include basic information on purpose so that you'd RTFAs they linked to.
If you had bothered to read the article you would see that not one of those three individuals were mentioned. The other links are all 404s or have no relevant information on these people.
Re:Am I the only one scared of this?
on
Google Calendar
·
· Score: 1
How is this different from someone using Yahoo Mail or Yahoo Calendar? Other companies offer similar search, mail, calendar services for years and no one complains but then Google does it and all of a sudden it's bad? Please explain.
Yes, but it is supported by RedHat? When you are paying for an OS and getting the support that doesn't mean they will support any software that you install. Since they don't ship with KDE I doubt that their support staff would officially support KDE that was compiled and installed by the customer.
I work for a Fortune Global 500 company and we still use stand alone fax machines with paper output. Not everyone has jumped on the integrated techno bandwagon.
The folks sleeping on the streets of the Tenderloin want their WiFi!
Nice attempt at a troll. If you had bothered to read the article you would have seen the following:
Both companies would share the cost of installing the necessary equipment, estimated at up to $12 million. San Francisco will pay nothing and actually reap some fees by leasing city property as perches for Wi-Fi antennas.
Re:Nothing beats yahoo and mutt
on
Gmail vs Pine
·
· Score: 1
You cannot modify pine and distribute it; you have to make a patch of your changes, and distribute that along with a copy of the source code.
That's no different from qmail and it hasn't stopped all of the qmail people from beating their chests about how superior qmail is to every other MTA.
I wrote a similar letter but it sent it via snail mail to both the city manager and the mayor. You should try that instead. It might make more of an impact than email.
Transparency and window animations. Whoop-dee-do. As a non-Windows-programming end user what I want to know is what new features are in Vista that are going to help me accomplish real work? What's in Vista that should be worth my time and money to upgrade? How will those be better than what I already have in WinXP and Win2000? If you are a beta tester, please let me know. And I don't use IE or MS Paint.
I thought that Sun already had their grid available and that no one wanted to use it because they would have to agree to be in a marketing campaign. Is this still the case? The terms of service on the network.com site redirects to an error page.
When a business purchases software (or anything else) the manufacturer implicitly warrants that the item is suitable for its intended purpose.
You haven't read an end user license agreement lately, have you? In all the ones that I have seen the manufacturer doesn't guarantee that the software will do anything, including its intended purpose.
Besides, the average marine has about a high school education, no morals and a low threshold for the sanctity of life. They might as well be robots anyways.
I don't agree with the US war machine's actions either but I think you are making a blanket statement here that just isn't true. There are a lot of functions in the military beyond pointing a gun at and killing another person. Thinking that they are all mindless ground pounders just isn't the reality. Many people join the military because they wither enjoy the structure that it provides or they realize that they need that to help get their act together. Or they may want a good guaranteed job that they can retire from in 20 years. The military can help you learn a lot about different fields. Some people make a career out of it, be it working in electronics, security, computers, medicine, research, aviaton, or logistics planning. There are a lot of career paths there with much variety.
Vacuum is asinine. Any command that needs to be run
periodically under threat of complete and total data corruption should
not be. That's right. Only PostgreSQL makes you vacuum or else your
transaction ids overflow. This is modern?
Vacuuming is just a form of garbage collection. It's a byproduct of
how Postgres is designed to handle transactions. Until recently,
users have had to handle this housekeeping function manually, a
requirement which has scared people away. However, for the most part
vacuuming isn't something that you should have to worry about any
more. As of Postgres 8.1 autovacuum can be enabled which handles
everything automatically.
Here is a little background on why vacuuming is used:
When a user starts a transaction to a database the
database will show data that was valid as of the start of the
transaction. So if I issue a select that takes some time to return results and another user updates rows that I would be selecting after I issue my select, I will only see data that was valid at the time of my select rather than the newly updated data.
When that other user updated a row I was selecting from, a new row is
inserted (or written to a previously deleted row). Any new
transactions that select this row will get the new row rather than the
old one my long-running transaction is still seeing. Once my
transaction is complete, then the row with the old data isn't needed
any more because newer data is in another row. This is called a non-overwriting storage manager.
What vacuum does is look for these unused rows. It goes through the
tables in the background and sees if any transactions are using that
data. If no transactions are using the row it marks them as free for
the storage manager to write to. Future inserts can use that row to
store data rather than adding to the end of the file. Vacuum doesn't
move any data in this way. It's just marking rows that can be
overwritten with new data. It's completely unobtrusive and a normal
part of keeping the database running.
Some databases take a different approach. For example, Oracle uses an
overwriting storage manager. When you update a row the data in the
row is physically overwritten. To handle transactions, Oracle keeps
what it calls a REDO log. The REDO log is like a journal in a
journaled filesystem. It keeps track of all changes to to the data in
the database. Any transactions that were open before the update to a
DB row will notice that the data was updated and will then look at the
REDO log to see what the correct data should be for their transaction.
I have heard that implementing an overwriting storage manager like
Oracle has is very complicated, much more complicated than a
non-overwriting storage manager like Postgres uses. I'm not a DB
programmer so I don't know if that is true. I also heard a while back
that the Postgres developers were investigating overwriting storage
manager algorithms but I don't know what came of that.
Now, back to vacuum. In Postgres there is "vacuum full" which
will move data around. It is used to compact the datafile to
remove the space that's marked as unused and shrink your datafile size. You should rarely, if ever,
have to use this as your unused rows will be used by new inserts. At
least "vacuum full" is easier than the Oracle equivilent which is:
CREATE TABLE my_temp_table AS SELECT * FROM my_old_table; TRUNCATE TABLE my_old_table; INSERT INTO my_old_table SELECT * FROM my_temp_table; DROP my_temp_table;
Again, "vacuum full" is rarely, if ever, needed. The Oracle
equivilent would be more rare to need due to how Oracle's storage
manager works.
I think you've answered your own question. Unix mantra: do one thing and do it well. SSH is the encrypted transport layer. No other communication layer needs encryption.
So we should manually establish an SSH connection from our mail server to every MTA that we are communicating with? We should also establish a manual SSH connection for IM connections to every IM server that we connect with? SSH isn't a panacea.
This article has me wondering about something. Why aren't we encrypting things by default? Why isn't encryption being built into the protocol when it's designed? It always seems that it gets tacked on afterwards, if at all, and we're worse off in the long run for it. Take VNC for example. If you want that encrypted you're told to send it over SSH. Wouldn't it be great if VNC traffic was encryped by design right from the start? The same applies to any other traffic (VoIP, IM, whatever). What happens is that many people don't encrypt because of the difficultly or they don't know any better. Unencrypted traffic is sent putting them at risk.
We know the network is hostile and retrofitting encryption onto something after the fact doesn't always work either because too many people using the unencrypted protocol, it's too hard to configure (as opposed to being mostly automatic like ssh connections), or just general security ignorance. What's really holding us back?
Slashdot Mirror
So in Europe you can hold a copyright on an idea?
They flew?
This page might have some ideas.. Also see this page for a howto on setting up the mail server.
How is this different from someone using Yahoo Mail or Yahoo Calendar? Other companies offer similar search, mail, calendar services for years and no one complains but then Google does it and all of a sudden it's bad? Please explain.
I work for a Fortune Global 500 company and we still use stand alone fax machines with paper output. Not everyone has jumped on the integrated techno bandwagon.
I wrote a similar letter but it sent it via snail mail to both the city manager and the mayor. You should try that instead. It might make more of an impact than email.
Well, the image slideshow doesn't start on its own.
News flash: No one really lives in the Star Trek universe.
One chicken was able to live without a head. I say let Ballmer and Gates go and let the inmates run the asylum.
Transparency and window animations. Whoop-dee-do. As a non-Windows-programming end user what I want to know is what new features are in Vista that are going to help me accomplish real work? What's in Vista that should be worth my time and money to upgrade? How will those be better than what I already have in WinXP and Win2000? If you are a beta tester, please let me know. And I don't use IE or MS Paint.
I thought that Sun already had their grid available and that no one wanted to use it because they would have to agree to be in a marketing campaign. Is this still the case? The terms of service on the network.com site redirects to an error page.
Here is a little background on why vacuuming is used:
When a user starts a transaction to a database the database will show data that was valid as of the start of the transaction. So if I issue a select that takes some time to return results and another user updates rows that I would be selecting after I issue my select, I will only see data that was valid at the time of my select rather than the newly updated data.
When that other user updated a row I was selecting from, a new row is inserted (or written to a previously deleted row). Any new transactions that select this row will get the new row rather than the old one my long-running transaction is still seeing. Once my transaction is complete, then the row with the old data isn't needed any more because newer data is in another row. This is called a non-overwriting storage manager.
What vacuum does is look for these unused rows. It goes through the tables in the background and sees if any transactions are using that data. If no transactions are using the row it marks them as free for the storage manager to write to. Future inserts can use that row to store data rather than adding to the end of the file. Vacuum doesn't move any data in this way. It's just marking rows that can be overwritten with new data. It's completely unobtrusive and a normal part of keeping the database running.
Some databases take a different approach. For example, Oracle uses an overwriting storage manager. When you update a row the data in the row is physically overwritten. To handle transactions, Oracle keeps what it calls a REDO log. The REDO log is like a journal in a journaled filesystem. It keeps track of all changes to to the data in the database. Any transactions that were open before the update to a DB row will notice that the data was updated and will then look at the REDO log to see what the correct data should be for their transaction.
I have heard that implementing an overwriting storage manager like Oracle has is very complicated, much more complicated than a non-overwriting storage manager like Postgres uses. I'm not a DB programmer so I don't know if that is true. I also heard a while back that the Postgres developers were investigating overwriting storage manager algorithms but I don't know what came of that.
Now, back to vacuum. In Postgres there is "vacuum full" which will move data around. It is used to compact the datafile to remove the space that's marked as unused and shrink your datafile size. You should rarely, if ever, have to use this as your unused rows will be used by new inserts. At least "vacuum full" is easier than the Oracle equivilent which is:
Again, "vacuum full" is rarely, if ever, needed. The Oracle equivilent would be more rare to need due to how Oracle's storage manager works.We know the network is hostile and retrofitting encryption onto something after the fact doesn't always work either because too many people using the unencrypted protocol, it's too hard to configure (as opposed to being mostly automatic like ssh connections), or just general security ignorance. What's really holding us back?