head 1.2; access; symbols RELENG_4_11_0_RELEASE:1.1.2.2 RELENG_4_11:1.1.2.2.0.16 RELENG_4_11_BP:1.1.2.2 RELENG_4_10_0_RELEASE:1.1.2.2 RELENG_4_10:1.1.2.2.0.14 RELENG_4_10_BP:1.1.2.2 RELENG_4_9_0_RELEASE:1.1.2.2 RELENG_4_9:1.1.2.2.0.12 RELENG_4_9_BP:1.1.2.2 RELENG_4_8_0_RELEASE:1.1.2.2 RELENG_4_8:1.1.2.2.0.10 RELENG_4_8_BP:1.1.2.2 RELENG_4_7_0_RELEASE:1.1.2.2 RELENG_4_7:1.1.2.2.0.8 RELENG_4_7_BP:1.1.2.2 RELENG_4_6_2_RELEASE:1.1.2.2 RELENG_4_6_1_RELEASE:1.1.2.2 RELENG_4_6_0_RELEASE:1.1.2.2 RELENG_4_6:1.1.2.2.0.6 RELENG_4_6_BP:1.1.2.2 RELENG_4_5_0_RELEASE:1.1.2.2 RELENG_4_5:1.1.2.2.0.4 RELENG_4_5_BP:1.1.2.2 RELENG_4_4_0_RELEASE:1.1.2.2 RELENG_4_4:1.1.2.2.0.2 RELENG_4_4_BP:1.1.2.2 RELENG_4:1.1.0.2; locks; strict; comment @# @; 1.2 date 2001.06.11.01.48.12; author ache; state dead; branches; next 1.1; 1.1 date 2001.04.27.21.27.54; author bmah; state Exp; branches 1.1.2.1; next ; 1.1.2.1 date 2001.06.01.18.02.54; author bmah; state Exp; branches; next 1.1.2.2; 1.1.2.2 date 2001.06.22.00.29.19; author bmah; state dead; branches; next ; desc @@ 1.2 log @ISO_* -> ISO* rename @ text @ Floppy Disk Image Instructions For a normal CDROM or network installation, all you need to copy onto actual floppies from the floppies/ directory are the kern.flp and mfsroot.flp images (for 1.44MB floppies). Getting these images over the network is easy. simply fetch the release/floppies/kern.flp and release/floppies/mfsroot.flp files from ftp://ftp.freebsd.org/pub/FreeBSD or one of the many mirrors listed at http://www.freebsd.org/handbook/mirrors.html. Get two blank, freshly formatted floppies and image copy kern.flp onto one and mfsroot.flp onto the other. These images are not DOS files! You cannot simply copy them to a DOS or UFS floppy as regular files, you need to image copy them to the floppy with fdimage.exe under DOS (see the tools directory on your CDROM or &os; FTP mirror) or the &man.dd.1; command in UNIX. For example, to create the kernel floppy image from DOS, you'd do something like this: C> fdimage kern.flp a: Assuming that you'd copied fdimage.exe and kern.flp into a directory somewhere. You would do the same for mfsroot.flp, of course. If you're creating the boot floppy from a UNIX machine, you may find that: &prompt.root; dd if=floppies/kern.flp of=/dev/rfd0 or &prompt.root; dd if=floppies/kern.flp of=/dev/floppy work well, depending on your hardware and operating system environment (different versions of UNIX have totally different names for the floppy drive). If you're on an alpha machine that can network-boot its floppy images or you have a 2.88MB or LS-120 floppy capable of taking a 2.88MB image on an x86 machine, you may wish to use the older (but now twice as large) boot.flp image which we also provide. That contains the contents of kern.flp and mfsroot.flp on a single floppy, essentially. This file should also be used as the boot file for those mastering El Torito bootable CD images. See the &man.mkisofs.8; command for more information. Going to two installation boot floppies is a step we definitely would have rather avoided but we simply no longer could due to general code bloat and &os;'s many new device drivers in GENERIC. One positive side-effect of this new organizational scheme, however, is that it also allows one to easily make one's own kern.flp or mfsroot.flp floppies should a need to customize some aspect of the installation process or use a custom kernel for an otherwise unsupported piece of hardware arise. As long as the kernel is compiled with options MFS and options MFS_ROOT, it will properly look for and boot an mfsroot.flp image in memory when run (see how /boot/loader.rc in kern.flp does its thing). The mfsroot.flp image is also just a gzip'd filesystem image which is used as root, something which can be made rather easily using &man.vnconfig.8;. If none of that makes any sense to you then don't worry about it - just use the kern.flp and mfsroot.flp images as described above. @ 1.1 log @First commit of RELNOTESng, the rewrite of the *.TXT documentation files. src/release/doc/README has additional information. Reviewed by: -current, -doc @ text @d1 1 a1 1 @ 1.1.2.1 log @MFC: RELNOTESng. I didn't MFC the changes to the release Makefile or the nuking of the *.TXT files. We're not ready for that yet. I just wanted to get the RELNOTESng sources for RELENG_4 into the repository so I can maintain the content in parallel with the *.TXT version of the release notes. These files include an SGML-ified version of RELENG_4's release notes, plus the hardware compatability lists from HEAD (minus CURRENT-specific features such as Cardbus support). @ text @d1 1 a1 1 @ 1.1.2.2 log @MFC: ISO_* -> ISO* rename. @ text @d1 1 a1 1 @