From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 15:19:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CA4316A4CE; Sat, 10 Jan 2004 15:19:31 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57B6343D46; Sat, 10 Jan 2004 15:19:30 -0800 (PST) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (c-24-130-160-161.we.client2.attbi.com[24.130.160.161]) by comcast.net (rwcrmhc11) with SMTP id <20040110231929013005g7uve>; Sat, 10 Jan 2004 23:19:29 +0000 Date: Sat, 10 Jan 2004 15:19:28 -0800 (PST) From: Doug Barton To: Craig Rodrigues In-Reply-To: <20040110212511.GA636@crodrigues.org> Message-ID: <20040110151659.I9450@znfgre.qbhto.arg> References: <20040109152441.F24587@carver.gumbysoft.com> <20040110212511.GA636@crodrigues.org> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd-current@freebsd.org" cc: Robert Watson Subject: Re: can't exec /usr/libexec/getty for /dev/ttyv1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2004 23:19:31 -0000 On Sat, 10 Jan 2004, Craig Rodrigues wrote: > On Fri, Jan 09, 2004 at 08:00:39PM -0500, Robert Watson wrote: > > > > init: can't exec getty `/usr/libexec/getty` for /dev/ttyv1: No souch file or directory > > > > init: can't exec getty `/usr/libexec/getty` for /dev/ttyv2: No souch file or directory > > > Hmm, very strange. It looks like mergemaster borked my files in > /etc/rc.d (i.e. I did not have any files in this directory after > running the mergemaster). mergemaster never borks anything unless you tell it to. :) That said, there was a window of a couple days when a patch I did recently to prompt a user to remove _stale_ files in /etc/rc.d/ could give false positives, and therefore recommend that you remove files that should stay around. Make sure you've updated to the latest sources, the bug has been fixed for a while now. Doug -- This .signature sanitized for your protection