From owner-freebsd-current Fri Jan 1 16:55:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16677 for freebsd-current-outgoing; Fri, 1 Jan 1999 16:55:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16671 for ; Fri, 1 Jan 1999 16:55:09 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA05145; Fri, 1 Jan 1999 19:54:31 -0500 (EST) Date: Fri, 1 Jan 1999 19:54:31 -0500 (EST) From: Daniel Eischen Message-Id: <199901020054.TAA05145@pcnet1.pcnet.com> To: eischen@vigrid.com, mike@smith.net.au Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) Cc: current@FreeBSD.ORG, imp@village.org, jkh@zippy.cdrom.com, peter@netplex.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Thanks for the directions. This works fine on my laptop with fd drive, > > but my home system doesn't currently have a floppy drive. It has a > > LS120 (wfd) drive and the same floppy doesn't work on it. It can't > > find /boot/loader. I suspect wfd support isn't built into boot2.c > > yet? > > Actually, it *ought* to work at that point. It wouldn't suprise me if > you had trouble booting with the LS120 as the root device, but I can't > see why boot2 can't find the loader. What do you get if you type '?' > at the boot: prompt? I got it to boot by using "0:wd(0,a)/kernel" at the prompt (wd instead of wfd). But to answer your question: No /boot/loader >> FreeBSD/i386 BOOT Default:0:fd(0,a)/kernel boot: ? >> FreeBSD/i386 BOOT Default:0:fd(0,a)/kernel boot: nothing happens when you type '?'. At first I thought it wasn't working at all because it wouldn't boot from fd0 nor wfd0, so I didn't think to try wd0 or even da0 (my system drive, which it'll boot also). Dan Eischen eischen@pcnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message