From owner-freebsd-hackers Sun Mar 14 12:37:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles161.castles.com [208.214.165.161]) by hub.freebsd.org (Postfix) with ESMTP id EC54915449 for ; Sun, 14 Mar 1999 12:37:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA08229; Sun, 14 Mar 1999 12:30:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903142030.MAA08229@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier Cc: ru@ucb.crimea.ua (Ruslan Ermilov), hackers@freebsd.org Subject: Re: [BTX loader]: boot command doesn't work as expected In-reply-to: Your message of "Sat, 14 Mar 1999 22:15:09 +0200." <199903142015.WAA09907@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 12:30:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi! > > > > boot -c - works > > boot /kernel - works > > boot -c /kernel - doesn't work > > > > Any clue? > > What are you actually getting, when it doesn't work? Is the -c option > simply ignored? I ask because I've tried about 8 times here, using > various permutations, and got some unexpected results. Though, in all > cases, I did get a "config>" prompt. Is the behavior consistently > reproducible? The loader explicitly checks argv[1] for a kernel name in command_boot. If you put an argument first, the kernel name will be passed to the MD boot code as an argument as well. Not what the user wantsm for sure. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message