From owner-freebsd-questions@FreeBSD.ORG Sat Oct 1 12:49:22 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7DD916A41F for ; Sat, 1 Oct 2005 12:49:22 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 375EB43D49 for ; Sat, 1 Oct 2005 12:49:22 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 30826 invoked from network); 1 Oct 2005 12:49:19 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Oct 2005 12:49:19 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id D034040; Sat, 1 Oct 2005 08:49:18 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Aleksandar Kacanski References: <20050930222251.37125.qmail@web35607.mail.mud.yahoo.com> From: Lowell Gilbert Date: 01 Oct 2005 08:49:18 -0400 In-Reply-To: <20050930222251.37125.qmail@web35607.mail.mud.yahoo.com> Message-ID: <448xxdflm9.fsf@be-well.ilk.org> Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Problem upon upgrade ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 12:49:22 -0000 Aleksandar Kacanski writes: > Hello, > I have issue with booting procedure after performing > upgrade from 5.3 to 5.4 > > Error appears after booting in multi-user mode. > init: can't get /dev/console for controlling terminal: > operation not permitted. > Could someone point me to what might be causing this > problem... *Is* there a /dev/console? What are its permissions? Make sure you are at securelevel -1 to make it easier to identify what is happening.