<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Quick note, I _do_ have build scripts for the liveCD, I just didn't
make it public because I didn't want the responsibility that comes with
giving out a tool that requires _some_ technical knowledge that most
people won't bother getting before using it. It also assumed many
things that didn't warrant me putting more time into bullet-proofing
the script ;)<br>
<br>
Here are their contents:<br>
<tt><br>
cycle.sh: that was used for tight loop devving of the liveCD (I used
vmware and booted of the ISO image)<br>
MakeCD.sh: this is supposed to replicate the entire process (sanity
check)<br>
MountTmpFS.sh: simple helper script. Note that I shouldn't pass on a
size option to tmpfs and let it use swap on an as-needed basis (source
of weird catalyst failures when you run out of space).<br>
<br>
<b>kyron catalyst # cat cycle.sh</b><br>
#!/bin/bash<br>
# Pre-cleanup<br>
find /var/tmp/catalyst/packages/ -regextype posix-extended -regex
'.*(beowulf|aufs|ldap-auth|torque).*' -exec rm -f {} \;<br>
<br>
schedtool -B -n -4 -e catalyst -f
/var/git/clustering-livecd/catalyst/livecd/2008.0/specs/amd64/livecd-stage1-minimal.spec<br>
find /var/tmp/catalyst/packages/ -regextype posix-extended -regex
'.*(beowulf|aufs|ldap-auth|torque).*' -exec rm -f {} \;<br>
schedtool -B -n -4 -e catalyst -f
/var/git/clustering-livecd/catalyst/livecd/2008.0/specs/amd64/livecd-stage2-minimal.spec<br>
<br>
<b>kyron catalyst # cat MakeCD.sh</b><br>
umount
/var/git/clustering-livecd/catalyst/livecd/2008.0/overlay/tftproot/nfsroot/x86_64/<br>
umount /var/tmp/catalyst/tmp/default<br>
<br>
rm -f /var/tmp/catalyst/packages/*/All/beowulf-head-0.1.tbz2
/var/tmp/catalyst/packages/*/All/ldap-auth-0.1.tbz2<br>
<br>
mount -t tmpfs -o size=6G,noatime catalystbuild
/var/tmp/catalyst/tmp/default<br>
catalyst -f
/var/git/clustering-livecd/catalyst/nfsroot/2008.0/specs/amd64/nfsroot_stage4.spec
|| exit 1;<br>
#catalyst -f
/var/git/clustering-livecd/catalyst/livecd/2008.0/specs/amd64/livecd-stage1-minimal.spec
|| exit 1;<br>
#mount -o bind /var/tmp/catalyst/tmp/default/stage4-amd64-nfsroot/
/var/git/clustering-livecd/catalyst/livecd/2008.0/overlay/tftproot/nfsroot/x86_64/<br>
#catalyst -f
/var/git/clustering-livecd/catalyst/livecd/2008.0/specs/amd64/livecd-stage2-minimal.spec
|| exit 1;<br>
<br>
<b>kyron catalyst # cat MountTmpFS.sh</b><br>
mount -t tmpfs -o size=7G,noatime catalystbuild
/var/tmp/catalyst/tmp/default</tt><br>
<br>
Eric<br>
<br>
Tom Stellard wrote:
<blockquote
cite="mid:d24863920903222250g7f755039m9cefe643d48cc1f2@..."
type="cite">
<pre wrap="">On Mon, Mar 23, 2009 at 7:18 AM, Eric Thibodeau <a class="moz-txt-link-rfc2396E" href="mailto:kyron@..."><kyron@...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In response to two e-mails I just got off list from Meetanshu Gupta and
Ajith Kamath, in both cases the impression is that the project is simply to
port the bootable CD to USB disk. Here is are some clarifications:
- The wiki's¹ description is misleading, booting to USB was ONE of my
suggestions with a little more details here². Quite frankly, porting to USB
should be somewhat trivial. The hardest part is to being very methodical and
making sure the process can be reproduced using, ideally, Catalyst and
little outside scripting. All of this also implies getting the catalyst
specs up to date, modifying/removing many hacks that would no longer be
required for a USB based boot (since we would now have an RW system). ***
root on JFFS2 might be of interest here ***... and so on.
</pre>
</blockquote>
<pre wrap=""><!---->
Is the idea that booting from a USB device would be added as an option
when building the liveCD image, or is booting from a USB device
supposed to replace booting from a CD?
</pre>
<blockquote type="cite">
<pre wrap="">- AuFS is used as an overlay system and is required for the NFS-booted
nodes. One might want to migrate that to a less efficient tmpfs approach
(ref: LTSP implementation as being done under Gentoo too).
- Change most of the scripts to use dialog and automate some detection/ask
questions as per what was discovered.
- ... and so on, the idea would be to implement my original proposal and
push it further. I do have it but want some feedback before I dig it out and
re-post it (Donnie, thought you had posted it as an example? If not so, feel
free to do so if it's still relevant.)
</pre>
</blockquote>
<pre wrap=""><!---->
I have been working on building the liveCD the last few days, and I am
almost finished. I have run into many problems along the way, and I
have come up with a few general ideas for things to include in my
proposal:
-Add spec files for x86.
-Update the hpc-clustering and nfsroot profiles and the catalyst spec files.
-Simplify and automate the build process with a configuration script.
-Add documentation for building the liveCD using the new configuration script.
These tasks all involve the build process, and once they have been
completed, work could begin on USB booting, JFFS2 or other areas of
interest.
It seems like a lot of work has been done to make sure the right
packages are included in the build, and that currently the biggest
challenge is updating the build process and making it easy to
duplicate. Will improving the build process, USB booting and the
related file system changes be enough work for one summer, or are
there other parts of the cluster liveCD that Gentoo developers would
like to see improved?
-Tom Stellard
</pre>
</blockquote>
<br>
</body>
</html>
|
