Re: m68k boot-floppies [by way of BVM]

["Nick Holgate" <holgate@debian.org>]

>                      What about the directory layout of both vme trees?
> Do you need a bvme6000install.tgz and a  mvme16xinstall.tgz?
> With just the usual stuff, drivers.tgz and boote/resuce in images-1.44?
> Or anything else, special, etc?
> Or no tgz at all?
>  

resc1440bvme6000.bin -> bvme6000/images-1.44/rescue.bin
root1440bvme6000.bin -> bvme6000/images-1.44/root.bin
drv14bvme6000-1.bin  -> bvme6000/images-1.44/drivers.bin
resc2800bvme6000.bin -> bvme6000/images-2.88/rescue.bin  [1]
driversbvme6000.tgz  -> bvme6000/drivers.tgz
sys_mapbvme6000.gz   -> bvme6000/sysmap.gz
rootbvme6000.bin     -> bvme6000/rootbvme6000.bin [2]
linuxbvme6000        -> bvme6000/linuxbvme6000 [2]
tftplilo.bvme        -> bvme6000/tftplilo.bvme [3]
README.gz            -> bvme6000/tftplilo.txt [3]
tftplilo.conf        -> bvme6000/tftplilo.conf [4]
bvmbug-G.bin         -> bvme6000/bvmbug-G.bin [5]
bvmbug.txt           -> bvme6000/bvmbug.txt.txt [5]
debian-vme.txt       -> bvme6000/install.txt [6]

resc1440mvme16x.bin  -> mvme16x/images-1.44/rescue.bin
root1440mvme16x.bin  -> mvme16x/images-1.44/root.bin
drv14mvme16x-1.bin   -> mvme16x/images-1.44/drivers.bin
driversmvme16x.tgz   -> mvme16x/drivers.tgz
sys_mapmvme16x.gz    -> mvme16x/sysmap.gz
rootmvme16x.bin      -> mvme16x/rootmvme16x.bin [2]
linuxmvme16x         -> mvme16x/linuxmvme16x [2]
tftplilo.mvme        -> mvme16x/tftplilo.mvme [3]
README.gz            -> mvme16x/tftplilo.txt [3]
tftplilo.conf        -> mvme16x/tftplilo.conf [4]
debian-vme.txt       -> mvme16x/install.txt [6]

[1] for binary-1 CD boot
[2] no name change makes it easier for tftp
[3] from m68k-vme-tftplilo_*.deb
[4] from boot-floppies/m68k-specials
[5] from slink/.../m68k-support.tgz
[6] from slink/.../m68k-support.tgz needs updating

I think this is right?

Nick
---------------------------------------------
Nick Holgate <holgate@debian.org>
PGP key from public servers : Key ID DF3E8223