From owner-freebsd-doc Sat Jul 13 9: 9:57 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EBE337B400 for ; Sat, 13 Jul 2002 09:09:52 -0700 (PDT) Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD2AC43E31 for ; Sat, 13 Jul 2002 09:09:51 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-155.adsl.datanet.hu [195.56.48.155]) by mx1.datanet.hu (DataNet) with ESMTP id 1902426A271 for ; Sat, 13 Jul 2002 18:09:49 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g6DG9tF4084267 for ; Sat, 13 Jul 2002 18:09:56 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g6DG9tnE084266 for freebsd-doc@FreeBSD.ORG; Sat, 13 Jul 2002 18:09:55 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sat, 13 Jul 2002 18:09:55 +0200 From: Szilveszter Adam To: freebsd-doc@FreeBSD.ORG Subject: Re: docs/40265: bootfloppies Message-ID: <20020713160955.GD805@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-doc@FreeBSD.ORG References: <20020707150214.GE5610@canyon.nothing-going-on.org> <200207131350.GAA26131@eskimo.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <200207131350.GAA26131@eskimo.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello folks, So, the easy part first. I did the necessary changes to the Handbook sources to correctly refer to kern.flp and mfsroot.flp, however, I just got mail from bmah stating that at one time, the (then only) boot floppy image was indeed called boot.flp. This was quiet long time ago, so the question is: do we want to support FreeBSD versions this old in the Handbook? If so, the patches need rewording to mention the change in the image naming convention. If not, the patches may be the solution for now. I can do the first option too, just tell. -- Regards: Szilveszter ADAM Szombathely Hungary --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="books::handbook::backups::chapter.sgml.patch" Index: backups/chapter.sgml =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v retrieving revision 1.47 diff -u -r1.47 chapter.sgml --- backups/chapter.sgml 29 Apr 2002 12:14:05 -0000 1.47 +++ backups/chapter.sgml 13 Jul 2002 15:35:24 -0000 @@ -485,7 +485,7 @@ fix-it floppies Second, determine that the boot and fix-it floppies - (boot.flp and fixit.flp) + (kern.flp, mfsroot.flp and fixit.flp) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot messages. If all your devices are listed and functional, skip on to @@ -504,7 +504,7 @@ after your last backup may be irretrievably lost. Write-protect the backup tapes. - Fourth, test the floppies (either boot.flp + Fourth, test the floppies (either kern.flp, mfsroot.flp and fixit.flp or the two custom bootable floppies you made in step two.) and backup tapes. Make notes of the procedure. Store these notes with the bootable floppy, the @@ -696,10 +696,11 @@ at the boot: prompt). Skip the following paragraph. - If you are using the boot.flp and + If you are using the kern.flp, + mfsroot.flp and fixit.flp floppies, keep reading. Insert the - boot.flp floppy in the first floppy drive and - boot the computer. The original install menu will be displayed on + kern.flp floppy in the first floppy drive and + boot the computer. Insert mfsroot.flp floppy when you are asked to. The original install menu will be displayed on the screen. Select the Fixit--Repair mode with CDROM or floppy. option. Insert the fixit.flp when prompted. --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="books::handbook::disks::chapter.sgml.patch" Index: disks/chapter.sgml =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v retrieving revision 1.89 diff -u -r1.89 chapter.sgml --- disks/chapter.sgml 1 Jul 2002 15:55:56 -0000 1.89 +++ disks/chapter.sgml 13 Jul 2002 15:35:07 -0000 @@ -1727,7 +1727,7 @@ fix-it floppies Second, determine that the boot and fix-it floppies - (boot.flp and fixit.flp) + (kern.flp, mfsroot.flp and fixit.flp) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot messages. If all your devices are listed and functional, skip on to @@ -1746,7 +1746,7 @@ after your last backup may be irretrievably lost. Write-protect the backup tapes. - Fourth, test the floppies (either boot.flp + Fourth, test the floppies (either kern.flp, mfsroot.flp and fixit.flp or the two custom bootable floppies you made in step two.) and backup tapes. Make notes of the procedure. Store these notes with the bootable floppy, the @@ -1938,10 +1938,11 @@ at the boot: prompt). Skip the following paragraph. - If you are using the boot.flp and + If you are using the kern.flp, + mfsroot.flp and fixit.flp floppies, keep reading. Insert the - boot.flp floppy in the first floppy drive and - boot the computer. The original install menu will be displayed on + kern.flp floppy in the first floppy drive and + boot the computer. Insert the mfsroot.flp floppy when you are asked to. The original install menu will be displayed on the screen. Select the Fixit--Repair mode with CDROM or floppy. option. Insert the fixit.flp when prompted. --dDRMvlgZJXvWKvBx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message