Stuff Michael Meeks is doing |
Older items: 2008: ( J F M A M J J A ), 2007: ( J F M A M J J A S O N D ), 2006, 2005, 2004, 2003, 2002, 2001, 2000, 1999, legacy html
/lib/modules/`uname -r`/build, and so on. Finally found
the bug is fixed in HEAD systemtap anyway, filed a SUSE issue, sent
off a trivial patch. Sadly when it runs, it does something -so- strange
to my system that it terrifies me; will come back later.
Icecream is
a sharp tool, it lets other people build software on your machine,
needs you turn off your firewall, and it requires a working
LAN. The wiki page is your friend. [update]: Martin Vidner
points out that if you don't like to disable your firewall,
it's easy to use some built-in rules; as root:
echo 'FW_CONFIGURATIONS_EXT += "iceccd icecream-scheduler"' >> /etc/sysconfig/SuSEfirewall2
/sbin/SuSEfirewall2 start
sudo zypper in -y icecream icecream-monitor # install the package < 5 secs
sudo /sbin/chkconfig --level 345 icecream on # enable icecream startup on boot
Next - decide if this is going to be the scheduler machine ?
if so:
sudo sed -i 's/ICECREAM_RUN_SCHEDULER="no"/ICECREAM_RUN_SCHEDULER="yes"/' /etc/sysconfig/icecream
Then - start the daemon everywhere:
sudo /etc/init.d/icecream start # start the daemon ...
Finally - fix your path:
export PATH="/opt/icecream/bin:$PATH";
make -j8 # and run a parallel make
But I use different distros & versions on each machine - icecream pushes enough of your compiler and toolchain across to the remote host that this shouldn't be a problem.
But I like to turn the scheduler off / unplug my laptop - fine, icecream will handle your use-case perfectly: don't fret.
My mega-server is a 64bit machine, but my laptop is 32bit - fine, icecream will handle your use-case perfectly by default. It can even do cross compiling with more tweaking.
How do I know it's working - for those burned by the
psychosomatic Gentoo experience, running 'icemon' can help overcome your
fears (albeit at the cost of too much of your CPU):

But I run SLED ... - package here.
make %{?jobs:-j%jobs} is
best handled with some rpmbuild --eval '%define jobs 8' -ba foo.spec
than otherwise, sadly much googling, manual and code reading didn't
make this at all obvious.