From owner-freebsd-current Sun Jan 3 03:30:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12811 for freebsd-current-outgoing; Sun, 3 Jan 1999 03:30:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12802 for ; Sun, 3 Jan 1999 03:30:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.48]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4645; Sun, 3 Jan 1999 12:29:41 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031037.CAA04475@dingo.cdrom.com> Date: Sun, 03 Jan 1999 12:36:45 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> I installed the new bootblocks and bootloader and it works like a >> charm. However the directions that were given in a previous mail about >> the steps required are enough to get it working but lack in some things >> (which I unfortunately have no idea about how to fix, yet). > >> 1) I have the /boot.config file but the loader complains about /boot/ >> boot.config, so should boot.config not be in /boot? > > It doesn't, as I believe I've already mentioned to you in a previous > message. The loader reads /boot/boot.conf, which is a totally different > animal. /boot.config is only required if you have not upgraded the > bootblocks; it should *not* be generally used. True, sorry, I mixed up boot.conf and loader.config, see below. >> 2) after the bootloader continues to load I get a warning that my >> kernel's symbol table doesn't match. I didn't have this problem before >> the new blocks. > > Please quote the exact message that you get. This report is useless. See below >> 3) I also got a complaint from the loader about another missing config >> file which I can't remember the name from. > > Please quote the exact message that you get. This report is useless. OK, just rebooted and wrote down some things: boot: Booting 0:da(0,a)/boot/loader @ 0x100000 text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] Can't find file /boot/loader.config total=0x12cf94 entry point=0x100000 BTX loader ... [looks good] bootstrap loader revision 0.2 Can't open /boot/boot.conf: no such file or directory ... [booting kernel] [kernel symbol table not valid] OK, so the reason for the files missing is logical since they don't exist. Btw, when I go to the CLI of the booter the ? works to get the commands and the commands itself work as well, great job. Is the symbol table not valid related to the posts I have seen about a.out kernels and ELF kernels? Any hints regarding loader.config and boot.conf are I think the last hurdles I face with the loader... [ Wishful thinking mayhaps ;) ] --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message