Re: Proposed directory structure for the installation "disks"
Anne's proposal is very nice, though at this point I'm a little unsure
whether links are OK for the CD.
It offers "one-stop shopping:" you pick your flavor and then media, go to
the directory, and get everything you need.
It has a consistent organizing principle, namely only flavors at the top
level, and only media below that. I only proposed media and then flavors
because I thought it was more consistent with current arrangements. The
flavor first, then media order seems better because it makes life easier
for people who switch media at different steps of the install process--I
assume they have to keep the files in line with each other.
It has a great start on a readme, particularly the table at the bottom. Of
course, those in the know need to review it.
Quibbles:
I wouldn't have separate directories for harddisk, network and cdrom, even
if they are just links to the same thing. I think we should pick one name
that seems best, and explain it in the readme. I assumed that people using
networks or CD's would be able to figure out they could use harddisk, but a
more general name would be better. Some possibilities: big, unrestricted,
unlimited (hmm.. not so good for 8.3), large, disks-9.99, disks.big. After
all, there are zip drives, super diskettes, and other technologies now or
in the future. Trying to name all the media/methods which are unrestricted
by size is starting down a path which could get out of control--if having 3
links isn't already out of control! :)
P.S. Anne, thanks for helping me out about your name, and thanks for not
taking offence.
At 12:25 AM 3/5/00 +0100, J.A. Bezemer wrote:
>
>On Fri, 3 Mar 2000, Karl M. Hegbloom wrote:
>
>> Do you want the images directories under the flavor directories
>> instead, like this? What does everyone else think? Does it seem
>> more organized or more intuitive this way, or the other way?
>>
>> base2_2.tgz
>> standard/
>> drivers.tgz
>> root.bin # Only if we can't have one root.bin for ALL flavors.
>> linux
>> install.bat
>> images-1.20/
>> images-1.44/
>> images-2.88/
>> flavorA/
>
>That's more or less what I had in mind.
>
>I've done a little playing around with symlinks, and I must say I'm quite
>happy with the result. You can see my "proposed structure" for 2.2.7 at:
>
> http://www.uk.debian.org/~costar/bootdisks/disks-test/
>
>The webserver "forgets" README* files, so I've used xREADME where
>appropriate.
>
>The structure that the webserver shows is as can be found on CDs (hardlinks),
>the actual structure with symlinks (as found on FTP mirrors) is shown in the
>ls-lR.txt file.
>
>The top-level xREADME.txt file explains a few things, but I think this
>structure is very easy to understand for newbies.
>
>Only one question: how does the installation program behave when there are
>multiple copies of drivers.tgz, base2_2.tgz around (on CD or FTP/HTTP)? Maybe
>there should be some "filtering" to only show standard/cdrom/ or so when
>necessary.
>
>
>Regards,
> Anne Bezemer
>
>
Reply to: