Re: Possible changed to initial README files in boot-floppies -walter
Hi Walter,
Can you resend this as a diff against the current version, it makes it easier to
evaluate changes.
Thanks,
David
Sun, Apr 22, 2001 at 01:30:50PM -0400 wrote:
> Hi David, I have split up the initial README.txt into
> three files (I suppose it could just stay as one file)
> README.txt, INSTALL.txt and MANIFEST.txt.
>
> -walter
>
>
> ----------------------------README.txt-------------------------------------------
>
>
> The Debian Installation System
> ==============================
>
> Quick Orientation
>
> The purpose of this README is to acquaint the reader with the
> contents of the directory where the file you are currently
> reading resides. If you wish to return to this directory you
> should go to
>
> <debian>/dists/woody/main/disks-i386/current/
>
> where the word `<debian>' may indicate an FTP area, Web distribution
> area, or official Debian CD-ROM. All the files required for installation
> can be found within this directory and subdirectories.
>
> Full information on how to install Debian can be found in the
> documentation located under the `doc' subdirectory. Documentation
> is available in several formats and languages. Bookmark and read
> <URL:http://www.debian.org/releases/woody/> for errata, security
> alerts, and other updated information.
>
> For the impatient, quick install instructions can be found in the
> file INSTALL.txt. However, the reader is nonetheless STRONGLY
> encouraged to read the aforementioned mentioned FULL documentation
> in the doc/ subdirectory but perhaps you'll be able to get through
> the install without it. If you get stuck review the FULL documentation.
>
> A more detailed description of the contents of this directory is
> in MANIFEST.txt
>
> -------------------------------------------------------- INSTALL.txt file--------
>
>
>
> The Debian Installation System
> ==============================
>
> Quick Orientation
>
> The purpose of this README is to acquaint the reader with the
> contents of the directory where the file you are currently
> reading resides. If you wish to return to this directory you
> should go to
>
> <debian>/dists/woody/main/disks-i386/current/
>
> where the word `<debian>' may indicate an FTP area, Web distribution
> area, or official Debian CD-ROM. All the files required for installation
> can be found within this directory and subdirectories.
>
> Full information on how to install Debian can be found in the
> documentation located under the `doc' subdirectory. Documentation
> is available in several formats and languages. Bookmark and read
> <URL:http://www.debian.org/releases/woody/> for errata, security
> alerts, and other updated information.
>
> CDROM Install
> =============
>
> Even though the Debian Installation System is also called the
> `boot-floppies', it is possible (in fact, DESIRABLE) to install
> Debian without the use of floppies at all. For instance, you may
> be able to install Debian from an official Debian bootable CD-ROM,
> from the network, or from another operating system. The recommended
> approach is to boot using an official Debian cdrom.
>
>
>
> Floppies Install
> ================
>
> If you either do not have a cdrom or you have a computer that
> can NOT boot a cdrom (go into your BIOS setup to see whether you
> are able to tell the computer to boot from the cdrom) then you
> will have to use the boot floppy images in this directory.
>
> Windows/Dos Users
> -----------------
>
> For new users to Linux who are currently running Windows/Dos
> you are advised to choose one of the following approaches:
>
> A. Run Linux within DOS.
>
> People who may want to use this method
> --------------------------------------
>
> This method is recommended for those who have no room
> on their hard drive as it is probably solely to Windows/Dos
> also for for those who are curious about Linux and just want to
> give it a "try".
>
> Running Linux in Dos
> --------------------
>
> Specifically run the DOS batch script `install.bat' in the
> current directory. If this fails it may be due to some hardware
> issue in which case you should go to a different flavor, that is,
> to one of the subdirectories
>
> ide/, idepci/ or compact/
>
> and read the README.txt files to determine which of the flavors
> would appeal the most to your computer. Once you have decided
> try running the `install.bat' batch script in one of these
> subdirectories.
>
>
> B. Copy the boot floppies files to floppy disks.
>
> It is RECOMMENDED that you use NEW floppies as used ones can
> fail to boot.
>
> Change directory to images-<size-of-your-floppies>/ and copy
> the image files `rescue.bin', `root.bin' to separate floppy
> disks, that is, one file per disk using the command DOS utility
> `rawrite2.exe' in the dosutils subdirectory:
>
> rawrite2 -f <file> -d a
>
> where a refers to the a: floppy drive on your computer.
> In addition to the `rescue.bin' and `root.bin' image files
> are the files `driver-*.bin' files which contain extra hardware
> drivers not contained in the `rescue.bin' image. In most cases
> you will not need these images so it may well be sufficient
> to simply copy `rescue.bin' and `root.bin'.
>
> Next, read "Beginning of Full Install" below.
>
>
> UNIX/Linux Users
> ================
>
> You proceed by essentially as in B. above but instead run
> the dd command (this is with respect to GNU dd):
>
> dd of=/dev/fd0 if=<file> bs=1024
>
> If you are naturally suspicious, you can make sure the image was
> successfully written:
>
> cmp /dev/fd0 <file>
>
>
>
> Beginning of Full Install
> =========================
>
> AFTER you have read the general documentation in the
> `doc' subdirectory you should put the disk containing
> the `rescue.bin' into the the floppy drive that your
> computer checks at boot time for floppies. If your
> computer successfully boots you should be prompted to
> insert the disk containing the `root.bin' image. Once
> this loads you will end up with a minature Debian system
> which represents the beginning of the installation process
> of the full Debian system as described in the documention
> in the `doc' subdirectory that you have finished reading.
>
> ------------------------- MANIFEST.txt files begins-------------
>
>
>
>
>
> ** Layout Of The Installation Files
>
> The general organization of files in this directory is described
> below. If you are copying a subset of these files to local disk or
> what have you, you should retain the internal directory structure,
> since the installation system will be looking for files in these
> locations.
>
> README.txt - a very short intro pointing the reader to the file
> he should focus on first
>
> MANIFEST.txt - this file
>
> INSTALL.txt - a quick installation instruction set for the
> impatient.
>
> doc/
>
> The Debian GNU/Linux Installation Manual, the Beginner's Guide for
> `dselect', and the Release Notes may be found here in several
> computer readable and printable formats. Please, Read The Fine
> Manual (RTFM) before you begin!
>
> <flavor>/
>
> There are several `flavors' of installation disk available. In
> some cases the images contain a Linux kernel compiled with
> certain options that make it work better on some hardware. See
> below for information about why you might need to use a flavor.
>
> Also in this directory are files for a particular flavor which
> are not disk images, but may be helpful for network
> installations or installations from another operating system.
>
> During a network, NFS, or CD-ROM install, the install software
> knows how to find these files, once you have indicated the
> <debian> directory. If you plan to copy these files to a spot
> on your hard drive in anticipation of using the installer's
> "from a mounted partition" option, you do not need to duplicate
> the directory structure of the <debian> archive, but you do need
> to make sure you get a matched set of images, all of the same
> <flavor>, or things probably won't work correctly.
>
> The flavors available for this architecture are `compact', 'idepci',
> and `ide'.
>
> compact .... A Linux kernel with some non-critical device
> drivers removed, and a few of the more common PCI
> device drivers compiled into the kernel itself.
> See images-1.44/compact/README.txt
>
> idepci .... Similar to compact, but even more PCI device drivers
> are compiled into the kernel, and SCSI is removed.
> See images-1.44/idepci/README.txt
>
> ide ..... Specialized kernel for those who require the UDMA66
> IDE patch. This may be needed if you have a
> Promise Ultra66 IDE controller, among others.
> See images-1.44/ide/README.txt
>
> images-<size>/<flavor>/
>
> Directory containing disk images of <flavor> and size <size>. The
> disk images are indicated by the file extension `.bin'. In particular
> you should find the files:
>
> rescue.bin - rescue disk image, containing the kernel and a boot
> loader.
>
> root.bin - root disk image, containing the root file system. NOT
> required unless are you are installing from floppies.
>
> driver-#.bin - (# represents a single digit) are the device driver disk
> images, containing kernel modules you can load for hardware
> for which there is not a driver built into the kernel. For
> instance, you can use this to install a driver for your network
> adapter; once you have installed that driver, you can install
> the rest of the system over the network. Other modules include
> PPP, parallel support, etc. NOT required UNLESS are you are
> installing from floppies.
>
> drivers.tgz - a compressed tar archive containing the same modules as the above
> disk images. These are used when installation kernel and drivers
> from local disk or CD rather than from floppies. Use the file from
> the appropriate subdirectory based on what flavor you are using,
> if any.
>
>
> basecont.txt (MY comment: does not appear to exist?)
>
> In the toplevel directory and within the toplevel flavor directories we have the files:
>
> install.bat - DOS batch script for booting into the installation system from
> DOS. A different version of this batch file is available for
> each flavor.
>
> linux - A Linux kernel image, used by the batch script above.
>
>
> kernel-config - parameters that the Linux kernel `linux' was compiled with
>
Reply to: