First thing, I don't want to break m68k building, so any changes might
well not make sarge. That said ....

Currently m68k generates 14 initrd's arranged by subarch, except for 
cdrom and cdrom22 (see [0]).

I pretty much like the arrangement, everybody shares cdrom images and
you look in your subarch's directory for everything else (and thus
ignore everyone else's junk).

But 14 initrd's take a while to build on m68k hardware and I plan to add
more. It seems that most of the build time comes from building the
trees.

If we instead look at how many separate trees are actually needed, there
would be five. All the 2.2 kernel stuff looks just like 2.4 stuff in the
tree except for /lib/modules (which turns out to be minimal). The
images only differ in actual image generation (same for floppy). I could 
now add q40 without building a new initrd, for instance. 

        cdrom           - all subarchs
          cdrom22       - all subarchs, 2.2 kernel
        hd-media        - amiga, atari (not currently built)
          hd-media22    - mac
        nativehd        - amiga, atari 
          nativehd22    - mac (atari?)
        floppy
          atari
          bvme6000
          mvme147
          mvme16x
        netboot         - all vme
        
The only cost in size is /lib/modules and keymaps. The build system
would also have to change to accommodate building multiple initrds out
of one tree (how to do change the makefile to do that doesn't seem 
obvious to me).

So do I go with the an image-based layout? I like the way it looks,
but users will have to be in different directories to download the 
pieces. What other problems am I getting into?

        cdrom/
                bvme6000-boot.img.gz
                initrd.gz
                initrd22.gz
        floppy/
                atari-boot.img.gz
                atari-root.img.gz
                bvme6000-boot.img.gz
                bvme6000-root.img.gz
                mvm147-boot.img.gz
                mvm147-root.img.gz
                mvm16x-boot.img.gz
                mvm16x-root.img.gz
        hd-media/
                initrd.gz
                initrd22.gz
        nativehd/       
                initrd.gz
                initrd22.gz
                atari/
                        bootargs
                        bootstra.prg
        netboot/
                initrd.gz
                tftplilo.bvme
                tftplilo.conf
                tftplilo.mvme
                tftplilo.txt

        kernels/
                vmlinuz-2.4.26-amiga
                vmlinuz-2.2.25-atari
                vmlinuz-2.4.26-atari
                vmlinuz-2.2.25-bvme6000
                vmlinuz-2.4.26-bvme6000
                vmlinuz-2.2.25-mac
                vmlinuz-2.2.25-mvme147
                vmlinuz-2.4.26-mvme147
                vmlinuz-2.2.25-mvme16x
                vmlinuz-2.4.26-mvme16x
        tools/
                rawwrite.ttp
                

[0] Current m68k d-i directory listing.

cdrom-initrd.gz
cdrom22-initrd.gz
amiga/
        nativehd-initrd.gz
        vmlinuz-2.4.26-amiga
atari/
        bootargs
        bootstra.prg
        floppy-boot.img.gz
        floppy-root.img.gz
        nativehd-initrd.gz
        rawwrite.ttp
        vmlinuz-2.2.25-atari
        vmlinuz-2.4.26-atari
bvme6000/
        cdrom-boot.img.gz
        floppy-boot.img.gz
        floppy-root.img.gz
        netboot-initrd.gz
        tftplilo.bvme
        tftplilo.conf
        tftplilo.txt
        vmlinuz-2.2.25-bvme6000
        vmlinuz-2.4.26-bvme6000
mac/
        hd-media-initrd.gz
        nativehd-initrd.gz
        vmlinuz-2.2.25-mac
mvme147/
        floppy-boot.img.gz
        floppy-root.img.gz
        netboot-initrd.gz
        tftplilo.conf
        tftplilo.mvme
        tftplilo.txt
        vmlinuz-2.2.25-mvme147
        vmlinuz-2.4.26-mvme147
mvme16x/
        floppy-boot.img.gz
        floppy-root.img.gz
        netboot-initrd.gz
        tftplilo.conf
        tftplilo.mvme
        tftplilo.txt
        vmlinuz-2.2.25-mvme16x
        vmlinuz-2.4.26-mvme16x

Thanks,

Stephen

-- 
Stephen R. Marenka     If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

Attachment: signature.asc
Description: Digital signature

Reply via email to