Date: Thu, 22 May 2014 19:47:56 -0600 From: Ian Lepore <ian@FreeBSD.org> To: Erich Dollansky <erichsfreebsdlist@alogt.com> Cc: freebsd-stable@FreeBSD.org, freebsd-stable-local@be-well.ilk.org Subject: Re: strange svn problem on FreeBSD 10 STABLE Message-ID: <1400809676.1152.300.camel@revolution.hippie.lan> In-Reply-To: <20140523092755.4d56eb21@X220.alogt.com> References: <20140522144628.72655b16@X220.alogt.com> <44fvk1q0dr.fsf@lowell-desk.lan> <20140523092755.4d56eb21@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2014-05-23 at 09:27 +0800, Erich Dollansky wrote: > Hi, > > On Thu, 22 May 2014 11:49:36 -0400 > Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> wrote: > > > Erich Dollansky <erichsfreebsdlist@alogt.com> writes: > > > > > > I probably could have been a lot more help if you'd included the > > output of "uname -a" and "svn info" in your message. And your kernel > > configuration file, although even better than that would be trying the > > GENERIC configuration and showing the results of that. > > > I just compiled the kernel with SC on and VT off without any problems. > Turning VT on again and SC off and I results in the original error > messages. It seems to me that the source tree got damaged during the > interruptions and svn does not notice it. > > > Good luck. > > It seems the best method for the moment. > > Erich Based on the error messages you report, the part of the tree that might be damaged is src/sys/conf/files*. From a glance at the config code it looks like that error is generated if it reads through conf/files and conf/files.amd64 and others that are included from your kernel config, and it didn't find any lines that contained "optional vt". The thing is, that appears on a pretty good number of lines, so it's hard to picture the damage that caused just that error and no others. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1400809676.1152.300.camel>