directory structure
Re: messages of 19991123
Hmmm, ok, ya, that makes sense...
Re: CVS
I can not use CVS because I do not have access to a computer with both a
command line and a 'net connection. So, unless someone can point me to
a http or ftp based interface...
Re: the problem at hand
Does this accurately address all the issues.
(Note: I'm not trying to write something suitable for public
consumption, I just want to cover all the bases)
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.
[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.
Reply to: