From owner-freebsd-questions@FreeBSD.ORG Sat May 10 19:52:23 2003 Return-Path: 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 D7BC837B401 for ; Sat, 10 May 2003 19:52:23 -0700 (PDT) Received: from web41202.mail.yahoo.com (web41202.mail.yahoo.com [66.218.93.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 70E6D43FD7 for ; Sat, 10 May 2003 19:52:23 -0700 (PDT) (envelope-from phaza7@yahoo.com) Message-ID: <20030511025223.68867.qmail@web41202.mail.yahoo.com> Received: from [64.218.84.217] by web41202.mail.yahoo.com via HTTP; Sat, 10 May 2003 19:52:23 PDT Date: Sat, 10 May 2003 19:52:23 -0700 (PDT) From: pat bey To: FREEBSD In-Reply-To: <44vfwissdb.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-question-local@be-well.no.ip.com Subject: Re: user mode X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2003 02:52:24 -0000 I Guess I should have mention that I tried rebooting, exit , and ^D. The only time I can get into multi-user mode is at boot time at the boot promt: load kernel.GENERIC # tried unload first but command wasn't recongized. But when reboot, shutdown the system or logout. Then whenever I log back in it automatically puts me back into single-user mode. The handbook offer the same suggestion that I repeatly tried. thanxs thou Lowell Gilbert wrote:pat bey writes: > Yesterday I re-compiled my kernel, went into single-user mode and now I stuck in single user mode. how could I get into multi-user mode. FBSD 4.6 We can only guess, because you didn't say what happens when you *try* to get out of multi-user mode. Normally, either "exit" or "reboot" will be the way you get out of single-user mode. If it keeps going into single-user mode on its own when you boot, then you need to pay attention to *why* it's doing that, and solve the problem. Needing an fsck is a common reason (see the handbook), but there could be others. If the new kernel is causing the problem itself, then boot the old kernel instead. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Suppressed minds have no Freedom of Choice --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.