Re: hfs boot floppy versions

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, Oct 30, 2005 at 02:31:43AM +0200, Christian Müller wrote:
> >Ok, you are confusing everything, please forget about 2.4 kernels, they 
> >are of
> >no import anymore, and forget about woody boot-floppies.
> >
> >i want you to try in turn these three floppies :
> >
> > http://people.debian.org/~luther/miboot.floppy
> >
> > http://people.debian.org/~luther/d-i/images/2005-10-29/powerpc/floppy/boot.img
> >
> > http://people.debian.org/~luther/d-i/images/2005-10-29/powerpc/floppy/ofonlyboot.img
> >
> >And for each of them report exactly and in details what happened.
> >
> >Friendly,
> >
> >Sven Luther
> >
> >
> > 
> >
> Before I forget it (all applies to oldworld beige G3revII):
> 
> * Third Time:  miboot.floppy results in red X over the little Tux-Icon 
> in the center of the grey screen, before a potential fb driver from the 
> kernel takes over

Mmm, what do you mean before a porential fb driver takes over ? Do you think
the kernel is loaded or not ?

> * 20051029:  boot.img cannot work (and it did not), because using hmount 
> [...] ; hdir you will find out that the miboot environment is missing in 
> that image, so there is no loader to take the included vmlinuz on it's 
> back.  however, using 20050615 boot.img-floppy + a little plastical 
> surgery with hfsutils to replace zImage there with the stray vmlinuz you 
> supply in 20051029 DOES work - so you ought to fix the building process 
> or whatever.

A look at the build log :

http://people.debian.org/~luther/d-i/images/2005-10-29/build_powerpc_floppy_boot.log

Shows that :

# Since miboot is not in the archive yet, but used for daily builds,
# we test for its existence, and use it if available. If not, we resort
# to some grungy HFS hacking to make believe it is there.
echo READY TO DO MIBOOT ...
READY TO DO MIBOOT ...
if [ -x /usr/bin/miboot ]; then                         \
        echo DOING MIBOOT; \
        echo device ./tmp/powerpc_floppy_boot/boot.img.new > ./tmp/powerpc_floppy_boot/miboot.conf;                     \
        echo kernel ./tmp/powerpc_floppy_boot/vmlinux.gz root=0200 load_ramdisk=1 prompt_ramdisk=1 devfs=mount debconf/priority=medium >> ./tmp/powerpc_floppy_boot/miboot.conf;        \
        miboot -c ./tmp/powerpc_floppy_boot/miboot.conf; \
        echo MIBOOT DONE; \
else                                                    \
        hmount tmp/powerpc_floppy_boot/boot.img.new; \
        hcopy -r ./tmp/powerpc_floppy_boot/vmlinux.gz :vmlinuz;         \
        hattrib -b :;                                   \
        humount;                                        \
fi

Mmm, ... investigating, it seems that for some obscure reason miboot was no
more executable, fixed, so tomorrows build should be ok.

Joeyh, i think i want to get ride of the else copy, and *NOT* build those
miboot floppies for the official realeses, since they caused more harm than
help for the sarge release.

> unlike the old 2.4 images, or those 2.2 images from woody (which I 
> obviously can't forget as each newer boot set seems to get worse - or 

Please, consider that we are all helping you out of our own free time, and the
last you could do is stay polite and stop denigrating our work without
knowledge of what is going on and such. Also, if you had filed a proper bug
report, like asked on the debian-installer page, instead of random rants, it
would have helped us find the issue earlier.

So, please change your attitude, or don't expect any further response from me
and i will only redirect all your mails to /dev/null.

... furher ranting deleted ...

Friendly,

Sven Luther