[ANN] sabotage mips(el) 0.9.7+ rootfs tarballs are available

[ANN] sabotage mips(el) 0.9.7+ rootfs tarballs are available

[John Spencer]

this is based on musl 0.9.7, with all mips patches applied.
so it really is more or less 0.9.8 minus the ppc port.

it takes about 2-3 weeks to get everything built in qemu mips,
so i didnt restart the build when 0.9.8 came out.

http://mirror.wzff.de/sabotage/sabotage-0.9.7-mips-rootfs.tar.xz
http://mirror.wzff.de/sabotage/sabotage-0.9.7-mipsel-rootfs.tar.xz

sha512 checksums:
a08aaf7ca0e2eea0a7e28ea7b0ce9ba1bca4f9f50ac2cdb112e25549989b7099f0dc030641836fd0f11aa583c0106f660ad2ddff2b5710d188799d68c2649f8c  
sabotage-0.9.7-mips-rootfs.tar.xz

99de9b14d993a4bacb9d8de273ae2a25bf3c7de0fdc09f32da37411c679617e3231ce7491254480721164818d5d58901009f6b0e9c50933f2d3c7772aa7eef85  
sabotage-0.9.7-mipsel-rootfs.tar.xz

if you dont own mips hw, you can try it out in aboriginal as a chroot,
or steal the kernel from aboriginal and boot it directly.

a powerpc image will be available in a week or two.

Re: [ANN] sabotage mips(el) 0.9.7+ rootfs tarballs are available

[Rob Landley]

On 11/30/2012 08:40:15 PM, John Spencer wrote:
> 
> this is based on musl 0.9.7, with all mips patches applied.
> so it really is more or less 0.9.8 minus the ppc port.
> 
> it takes about 2-3 weeks to get everything built in qemu mips,
> so i didnt restart the build when 0.9.8 came out.

Wow, really?

Beyond distcc, I looked at cluster based approaches but they all  
leverage distro repositories. Basically you have a "master" node that  
hands out work to "slave" nodes which start out all using the same  
filesystem, the master works otu which packages it can build with out  
dependencies and hands them out to the "slave" nodes, which build them,  
create a binary package (.rpm, .deb, the portage binary thing, etc) and  
sends it back to the "master" node which loads them into the  
repository. The master then hands out more work to the idle slave nodes  
using only packages which have prerequisites that can be installed from  
the repository rather than built.

(I looked into having them all share a network root filesystem and  
having the master node update it, but running ./configure while a  
package shows up out from under you is kinky.)

I also covered setting up tun/tap for kvm/qemu here:

   http://landley.net/lxc/02-networking.html

(That covers more than you'd need, but if you have a 4-way machine you  
can get a small cluster setup that way, and each qemu instance gets a  
cpu to itself...)

Rob