From owner-freebsd-stable Wed Jul 23 08:52:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26105 for stable-outgoing; Wed, 23 Jul 1997 08:52:40 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26094 for ; Wed, 23 Jul 1997 08:52:30 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id IAA15201 for ; Wed, 23 Jul 1997 08:52:22 -0700 (PDT) Message-Id: <199707231552.IAA15201@austin.polstra.com> To: stable@freebsd.org Subject: Re: /etc/rc.conf Date: Wed, 23 Jul 1997 08:52:21 -0700 From: John Polstra Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Has anyone noticed there rc.conf file mysteriously getting bigger after > >> doing cvsups to stable. Seems that I have a 600k file and comments are > >> being tagged onto the ends of the lines to form _very_ long lines, it > >> still works though. > > > > I have the same problem. Didn't think of it beeing cvsup, but it could very > well be so. I set the mode to r--r--r-- for the time beeing. For your info; > I only cvsup the ports collection. Sheesh. Come on, you guys -- make an effort, will ya?! 1. CVSup doesn't touch the /etc directory. 2. CVSup verifies the MD5 checksum of every file that it updates. 3. CVSup doesn't have a history of corrupting people's files. 4. On the other hand, there is a history of pure speculation similar to this thread, which only fuels more such nonsense, thank you very much. 5. If you really thought it was a CVSup bug, then why didn't you report it to cvsup-bugs@polstra.com? -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth