Wrong. We have the source. Has there ever been a feature in Linux you couldn't say no to in rebuilding the kernel? We have the source, we have the source, we have the source, god that feels good to say. Great googely moogely Joshua, we have the source!
However, I agree that submitted source should be considered for inclusion. I've worked on systems that had MAC. I've always felt a need for more granular security than all(root) or nothing.
However, I have never felt that the NSA serves the constitution. More likely "National Security is more important than the Bill of Rights." Who do we allow to make this decision without checks and balances. No such agency? Where does their budget show up? If you don't consider them a threat to privacy then maybe I should contact a friend there and post what p0rn sites you've been surfing.
Oh, and BTW: Kennedy Clinton spy Ft. Meade FBI terrorist South Africa World Trade Center plutonium kibo Delta Force Qaddafi genetic counter-intelligence NORAD, CIA Waco, Texas ammunition AK-47 PLO North Korea counter-intelligence class struggle [Hello to all my fans in domestic surveillance] Nazi assassination Ft. Bragg smuggle Treasury kill bubba cigar monica John Gilmore Lennon Lenin terrorist javascript popup
My Nader vote won't help Bush, even though I'm in the swing state of Oregon. I have traded my Nader vote for a Gore vote with a friend in a state already won by Bush. Thus Gore gets votes in a swing state where their needed and Nader gets general population votes for federal matching funds. See http://www.nadertrader.org
The main difficulty that most programmers face when moving to CVS is that fact that it doesn't lock files. Programmers used to locking systems always believe it would be pure chaos without locking. However, locking systems like VSS and RCS have disadvantages, especially when a team is large or separated by several time zones.
In fact, rarely do two person's changes to the same source file result in conflicts. CVS merges 90% of all changes with no intervention. When it can't it allows the programmer to manually resolve the conflict.
I've used both types of systems over the last twenty years (including VSS, SCCS, RCS, etc.), and have come to prefer CVS. A GUI really isn't an advantage with a system like cvs, since you're not constantly having to use it. With CVS once you do a checkout, you have your own completely writable repository. Usually once a day you do:
cvs update -Pd
to merge changes in the master repository to your copy. The only other time you need to use it is on checking files in. It's not like you need to use it every time you want to edit a file. I consider it much more work to use a GUI-base locking system like VSS. You canstantly have to think about source control when your programming. With CVS you only think about it when you do a checkin.
New programmers usually take a couple of weeks to get the mindset, but in the long run are more productive.
As far as binary files, you need to mark them binary, CVS will not do deltas on them, i.e. each rev will be a complete copy.
The only thing CVS doesn't do well is handle merges to files like MS resource files. Also the way DevStudio handle resource.h (storing next available resource in the file itself) make it somewhat touchy to automatic merges.
After a week or two of really using CVS, most open minded programmers will adapt and begin to like it. And they'll never want to go back to a locking system.
P.S. Someone will probably point out that VSS can be set to use nonlocking, but it doesn't have the intelligence to do automatic merges like CVS.
Slashdot Mirror
Wrong. We have the source. Has there ever been a feature in Linux you couldn't say no to in rebuilding the kernel? We have the source, we have the source, we have the source, god that feels good to say. Great googely moogely Joshua, we have the source!
Well, except spy on US citizens.
However, I agree that submitted source should be considered for inclusion. I've worked on systems that had MAC. I've always felt a need for more granular security than all(root) or nothing.
However, I have never felt that the NSA serves the constitution. More likely "National Security is more important than the Bill of Rights." Who do we allow to make this decision without checks and balances. No such agency? Where does their budget show up? If you don't consider them a threat to privacy then maybe I should contact a friend there and post what p0rn sites you've been surfing.
Oh, and BTW: Kennedy Clinton spy Ft. Meade FBI terrorist South Africa World Trade Center plutonium kibo Delta Force Qaddafi genetic counter-intelligence NORAD, CIA Waco, Texas ammunition AK-47 PLO North Korea counter-intelligence class struggle [Hello to all my fans in domestic surveillance] Nazi assassination Ft. Bragg smuggle Treasury kill bubba cigar monica John Gilmore Lennon Lenin terrorist javascript popup
My Nader vote won't help Bush, even though I'm in the swing state of Oregon. I have traded my Nader vote for a Gore vote with a friend in a state already won by Bush. Thus Gore gets votes in a swing state where their needed and Nader gets general population votes for federal matching funds. See
http://www.nadertrader.org
The main difficulty that most programmers face when moving to CVS is that fact that it doesn't lock files. Programmers used to locking systems always believe it would be pure chaos without locking. However, locking systems like VSS and RCS have disadvantages, especially when a team is large or separated by several time zones.
In fact, rarely do two person's changes to the same source file result in conflicts. CVS merges 90% of all changes with no intervention. When it can't it allows the programmer to manually resolve the conflict.
I've used both types of systems over the last twenty years (including VSS, SCCS, RCS, etc.), and have come to prefer CVS. A GUI really isn't an advantage with a system like cvs, since you're not constantly having to use it. With CVS once you do a checkout, you have your own completely writable repository. Usually once a day you do:
cvs update -Pd
to merge changes in the master repository to your copy. The only other time you need to use it is on checking files in. It's not like you need to use it every time you want to edit a file. I consider it much more work to use a GUI-base locking system like VSS. You canstantly have to think about source control when your programming. With CVS you only think about it when you do a checkin.
New programmers usually take a couple of weeks to get the mindset, but in the long run are more productive.
As far as binary files, you need to mark them binary, CVS will not do deltas on them, i.e. each rev will be a complete copy.
The only thing CVS doesn't do well is handle merges to files like MS resource files. Also the way DevStudio handle resource.h (storing next available resource in the file itself) make it somewhat touchy to automatic merges.
After a week or two of really using CVS, most open minded programmers will adapt and begin to like it. And they'll never want to go back to a locking system.
P.S. Someone will probably point out that VSS can be set to use nonlocking, but it doesn't have the intelligence to do automatic merges like CVS.