From owner-freebsd-stable Tue Oct 24 16:44:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A740537B4C5 for ; Tue, 24 Oct 2000 16:44:20 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9ONgT422124; Tue, 24 Oct 2000 16:42:29 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: mike Cc: stable@FreeBSD.ORG Subject: Re: FRUSTRADED! Shoot me? In-Reply-To: Message from mike of "Tue, 24 Oct 2000 15:06:54 PDT." <20001024220654.20563.qmail@web5205.mail.yahoo.com> Date: Tue, 24 Oct 2000 16:42:29 -0700 Message-ID: <22120.972430949@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (date) init: can't exec '/usr/libexec/getty' for port > /dev/ttyv0 to /dev/ttyv7. No such file or directory. Which comes from this part of init(8): argv[0] = "sh"; argv[1] = _PATH_RUNCOM; argv[2] = runcom_mode == AUTOBOOT ? "autoboot" : 0; argv[3] = 0; sigprocmask(SIG_SETMASK, &sa.sa_mask, (sigset_t *) 0); setprocresources(RESOURCE_RC); execv(_PATH_BSHELL, argv); stall("can't exec %s for %s: %m", _PATH_BSHELL, _PATH_RUNCOM); Since you're already a source stud (anyone who's not is supposed to do binary upgrades :), you may want to investigate all the variables represented in the code above. Is /bin/sh properly executable? Is /etc/login.conf messed up in any way that would cause the setprocresources() call to do bad things to the subsequent execv()? Does adding any additional debugging to this section of init yield any clues? Good luck debugging this one - I've never seen it so it must be something unique about your configuration there. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message