From owner-freebsd-hackers Tue Aug 20 13:36:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA01428 for hackers-outgoing; Tue, 20 Aug 1996 13:36:08 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA01366 for ; Tue, 20 Aug 1996 13:35:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA15016 for ; Tue, 20 Aug 1996 22:35:51 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA18905 for freebsd-hackers@freebsd.org; Tue, 20 Aug 1996 22:35:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA17519 for freebsd-hackers@freebsd.org; Tue, 20 Aug 1996 22:11:21 +0200 (MET DST) From: J Wunsch Message-Id: <199608202011.WAA17519@uriah.heep.sax.de> Subject: Re: Making Bootable Disks To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 20 Aug 1996 22:11:21 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608201429.JAA20513@brasil.moneng.mei.com> from Joe Greco at "Aug 20, 96 09:29:21 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Joe Greco wrote: > > > Is it outlined/described anywhere how to make a bootable system floppy? > > > > disklabel -Brw fd0 > > newfs ... /dev/rfd0a (look into /etc/disktab for the options) > > mount /dev/fd0a /mnt > > cp /kernel /mnt > > umount /mnt > > With all due respect Joerg, that's nice but not very useful :-) The kernel > alone will take 2/3 the floppy. The question was about a ``bootable floppy'', not about a useful one. ;-) Actually, that's the ``classical'' boot/root floppy pair approach. You load the kernel off the boot floppy, and then provide a root floppy as the root f/s. The minimal contents of a (marginally) useful root floppy is /sbin/init, /bin/sh, and /dev/console. Everything else is optional. crunchgen is a nice tool to create the contents of the root floppy. The installation floppy, while still using the name ``boot.flp'' (for hysterical reasons -- root.flp has just been eliminated recently, but didn't server for exactly this purpose for more than a year now), is another matter: it uses a builtin MFS acting as the root file system. I think you can also create something like the MFSROOT floppy now with Julian's new floppy creation tools (/usr/src/release/floppies/). Both approaches have its pros and cons. The boot/root pair has the disadvantage of a more complicated handling (you gotta swap floppies after loading the kernel), and of blocking the floppy drive while running. The MFS root system has the disadvantage of a more complicated system to manipulate the kernel or the contents of the root file system. It also requires a much bigger memory footprint (unless you're going to back the MFS on floppy swap space ;-). Dennis wasn't exactly specific about the purpose of his question, thus i couldn't answer it much better. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)