From owner-freebsd-questions Mon Feb 8 06:03:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08440 for freebsd-questions-outgoing; Mon, 8 Feb 1999 06:03:40 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from techpower.net (techpower.net [205.133.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08403 for ; Mon, 8 Feb 1999 06:03:35 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.9.2/8.9.1) with ESMTP id IAA48012; Mon, 8 Feb 1999 08:41:43 -0500 (EST) (envelope-from hometeam@techpower.net) Date: Mon, 8 Feb 1999 08:41:43 -0500 (EST) From: hometeam To: Andreas Gustafsson cc: freebsd-questions@FreeBSD.ORG Subject: Re: Building boot floppies In-Reply-To: <199902081321.PAA12367@guava.araneus.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need to compress the kernel before copying over if your making a new boot floppy with new boot blocks. Then mount floppy after booting in boot.conf you can add the currdev=diskx option then at boot time you will not have to enter the command manually. Just gz the kernel I don't know if this is the perfect way ...I do know it works.. On Mon, 8 Feb 1999, Andreas Gustafsson wrote: > I'd like to build a customized FreeBSD boot floppy, but I keep running > into problems. Here is what I've tried so far: > > 1. My first thought was to try the 3.0-RELEASE fixit floppy to see > whether I could modify it to suit my purposes. This failed due to the > bug already reported in PR #9051. > > 2. I found a procedure for building an emergency boot floppy in the > "backup" section of the FreeBSD handbook > . This didn't work > either, because I could not get all the files to fit on the floppy > even though I built a stripped-down kernel with only the most > essential device drivers. I thought the kernels on boot floppies were > generally compressed, but these instructions don't seem to mention > compression at all - why? > > 3. After upgrading to 3.0-STABLE, I tried building a PicoBSD "net" > floppy. This failed, too: > > ... > strip crunch1 > Warning: Object directory not changed from original /usr/sup/src/release/picobsd/net/crunch1 > ln: /mnt/stand/reboot: File exists > -> ERROR while building ../net/crunch1... > -> Aborting ./populate > # > > Is there any working, documented way of building a FreeBSD boot floppy > without doing a full "make release"? > -- > Andreas Gustafsson, gson@araneus.fi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message