How protect bash history file, do audit alike in server
Am 08.08.2012 23:03, schrieb firstname.lastname@example.org:
> Les Mikesell wrote:
>> On Wed, Aug 8, 2012 at 2:56 PM, <email@example.com> wrote:
>>> <flame, but not to you, Heng Su>
>>> VCS's that let multiple people check the same object out at the same
>>> time.... You're *exactly* back where you were before people were using
>> Errr, what? No sensible VCS forces you to wait for someone else to
>> finish their portion of the work.
> You're wrong. I've worked in small and large teams, and *ALWAYS* we
> checked out with locks. If two people need to work on one file, then
> either they need to work together on one copy, and check it back in
> together, or the file needs to be split into more than one, so that one
> person can work on each. This is the way it was at a medium sized
> environmental company I worked at (that was working on ISO 9000), and it
> was the way it was at a Baby Bell I worked at, and it was the way it was
> when I worked on the City of Chicago 911 system.
> I have vehemently been against the fad of the last half a dozen or so
> years, with multiple people checking out and working on the same file.
> I've seen hours or days of a developer's work wiped out, when a team lead
> hacked some quick fixes, then merged the file back in.
It seems you are vehemently against the development model the Linux
kernel is thriving on. Or perhaps you just never had a chance to look at
CentOS mailing list