boot-floppies for sparc layout

[Adam Di Carlo <adam@onshore.com>]

We are changing the file layout for boot floppies.  Below is my
proposed layout and some commentary by Bruce Sass.  I'd like some
commentary from you sparc folks on wether you find this helpful or
not, or if you spot some problems with it.

Please CC debian-boot@lists.debian.org on your replies.
-- 
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
<apharris@arroz:19991123> ls -1FR
.:
README
base-contents.txt
base2_2.tgz
disks-1.44/
doc/
md5sum.txt
root.tar.gz
sun4cdm/
sun4u/
tftpboot.img

./disks-1.44:
base-1.bin
base-10.bin
base-11.bin
base-2.bin
base-3.bin
base-4.bin
base-5.bin
base-6.bin
base-7.bin
base-8.bin
base-9.bin
root.bin

./doc:
ch-administrivia.en.html
ch-boot-floppy-techinfo.en.html
ch-dselect-conclusion.en.html
ch-dselect-glossary.en.html
ch-dselect-intro.en.html
ch-dselect-main.en.html
ch-hardware-req.en.html
ch-init-config.en.html
ch-install-methods.en.html
ch-partitioning.en.html
ch-post-install.en.html
ch-preparing.en.html
ch-rescue-boot.en.html
ch-welcome.en.html
dselect-beginner.en.html
dselect-beginner.en.txt
fdisk.txt
footnotes.en.html
install.en.html
install.en.pdf
install.en.txt

./sun4cdm:
disks-1.44/
drivers.tgz
linux-a.out
tftpboot-noultra.img

./sun4cdm/disks-1.44:
driver-1.bin
rescue.bin

./sun4u:
disks-1.44/
drivers.tgz
linux-a.out

./sun4u/disks-1.44:
driver-1.bin
rescue.bin


---------------------- commentary by Bruce Sass

Directory Structure
-------------------
The files necessary to install Debian have been sorted according to
platform[1], architecture[2] and installation media capacity[3]; this
forms the primary directory structure.  e.g.:

	disks-m68k/atari/disks-1.44/
	disks-m68k/atari/disks-720/
	disks-m68k/mac/disks-1.44/
	disks-sparc/sun4cdm/disks-1.44/
	disks-i386/disks-1.44/
	disks-i386/disks-1.20/

Furthermore, there are a variety of idiosyncrasies and special features
for some systems that makes multiple versions of the installation files
attractive.  These alternate versions have been placed in subdirectories
under the most suitable primary directory[4].  e.g.:

	disks-i386/raid/
	disks-i386/disks-1.44/safe/


File Placement
--------------
Files are placed in the above directories as close to the top level as
possible.  What this means is that a file common to all versions of the
installation available for a specific platform, will be placed in the
top level directory for that platform; a file common to all versions
available for a specific architecture, will be placed in the directory
for that architecture.  e.g.:

	disks-sparc/tftpboot.img
	disks-sparc/root.tar.gz
	disks-sparc/sun4cdm/linux
	disks-sparc/sun4cdm/tftpboot-noultra.img
	disks-sparc/sun4cdm/disks-1.44/resc1440.bin
	disks-sparc/sun4cdm/disks-1.44/drv14-1.bin
	disks-sparc/sun4u/linux-sun4c
	disks-sparc/sun4u/disks-1.44/resc1440-sun4u.bin
	disks-sparc/sun4u/disks-1.44/drv14-sun4u-1.bin

	disks-i386/disks-1.44/safe/README-safe


-----
[1] A "platform" is defined by the microprocessor (or processor family) 
    that is used in a computer.  (alpha, i386, m68k, powerpc, sparc)

[2] An "architecture" is defined by the microprocessor and supporting
    integrated circuits that are used in a computer.  If a platform has
    only one architecture, there will be no "architecture" directory.

[Note -- I object to the use of 'architecture' in this sense.  I call
it a subarchitecture. -- ADC]

[3] The "installation media capacity" is the size of floppy disk the
    files are intended to reside on (2880, 1440, 1200 or 720Kb).  The
    tarballs used to generate these disk image files can be found under
    the primary directory for the architecture they are applicable to.

[4] The "most suitable primary directory" refers to a directory of the
    primary directory structure that reflects the level at which the
    alternate version diverges from the standard version.  That is to
    say, if a version with an alternate kernel has been created to
    accommodate the needs of some users of a specific architecture, the
    files needed to install that version will appear in a sub-directory
    of the directory for that architecture.  e.g.:  The "safe" option,
    available on the i386 platform, is an example of a version that has
    diverged from the standard version because of issues related to 3.5"
    floppy drives, as such the safe/ is a sub-directory of the 1.44Mb
    media directory.