CVS commit logs removed by CVS update

2012-11-17 Thread Stefan Esser
To my big surprise I found that "cvs update" removed all the CVS logs from "/usr/cvs/CVSROOT-*/commitlogs/*" (collection cvsroot-all). While I do use SVN to keep source and ports updated on my system, I was used to scan the CVS log files for commit messages of interest, to locate commit messages w

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Ivan Klymenko
В Sat, 17 Nov 2012 15:00:06 -0500 grarpamp пишет: > http://www.freebsd.org/news/2012-compromise.html > http://it.slashdot.org/story/12/11/17/143219/freebsd-project-discloses-security-breach-via-stolen-ssh-key > > This is not about this incident, but about why major opensource > projects need to

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Michael Ross
On Sat, 17 Nov 2012 21:11:43 +0100, Ivan Klymenko wrote: В Sat, 17 Nov 2012 15:00:06 -0500 grarpamp пишет: http://www.freebsd.org/news/2012-compromise.html http://it.slashdot.org/story/12/11/17/143219/freebsd-project-discloses-security-breach-via-stolen-ssh-key This is not about this incide

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Chris Rees
On 17 Nov 2012 21:00, "Michael Ross" wrote: > > On Sat, 17 Nov 2012 21:11:43 +0100, Ivan Klymenko wrote: > >> В Sat, 17 Nov 2012 15:00:06 -0500 >> grarpamp пишет: >> >>> http://www.freebsd.org/news/2012-compromise.html >>> http://it.slashdot.org/story/12/11/17/143219/freebsd-project-discloses-se

FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread grarpamp
http://www.freebsd.org/news/2012-compromise.html http://it.slashdot.org/story/12/11/17/143219/freebsd-project-discloses-security-breach-via-stolen-ssh-key This is not about this incident, but about why major opensource projects need to be using a repository that has traceable, verifiable, built-in

Re: Jumbo Packet fail.

2012-11-17 Thread Adam McDougall
On 11/17/2012 5:32 PM, Zaphod Beeblebrox wrote: I recently started using an iSCSI disk on my ZFS array seriously from a windows 7 host on the network. The performance is acceptable, but I was led to believe that using Jumbo packets is a win here. My win7 motherboard adapter did not support jumb

Re: Jumbo Packet fail.

2012-11-17 Thread Zaphod Beeblebrox
On Sat, Nov 17, 2012 at 6:54 PM, Adam McDougall wrote: > On 11/17/2012 5:32 PM, Zaphod Beeblebrox wrote: [my description of MTU not having effect on MSS, deleted] > Did you reboot or alter the existing route so it also uses the higher MTU? I > realize that need is not obvious. Check netstat -rn

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Adrian Chadd
[snip] There's a git repository. It's public. You can look at what goes into the FreeBSD git clone to get your assurance that things aren't being snuck in. People are using it, right now. Honestly, I'd rather see subversion grow this kind of cryptographic signing of each commit in the short term

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Robert Simmons
On Sat, Nov 17, 2012 at 11:55 PM, Adrian Chadd wrote: > Those who want to use git can use it, right now. Honest. Yup: https://github.com/freebsd/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To u

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Perry Hutchison
[trimmed some of the lists] Chris Rees wrote: > ... git doesn't work with our workflow. I'm sure the workflow itself is documented somewhere, but is there a good writeup of _how_ git doesn't work with it, e.g. what capabilit{y,ies} is/are missing? Seems this might be of interest to the git deve

Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]

2012-11-17 Thread Konstantin Belousov
On Sat, Nov 17, 2012 at 11:05:40PM -0800, Perry Hutchison wrote: > [trimmed some of the lists] > > Chris Rees wrote: > > ... git doesn't work with our workflow. > > I'm sure the workflow itself is documented somewhere, but is > there a good writeup of _how_ git doesn't work with it, e.g. what >