[K12OSN] Project MueKow

[Jim McQuillan]

On Tue, 1 Mar 2005, Jim Kronebusch wrote:

> > Please read through it, and give us some feedback.  This is still in
> the very early stages, and we haven't written any code yet, but it is
> > something that we are excited to move forward with.
>
> This may be a crazy question, but under this format is there a way we
> could choose an independent platform to use to build the LTSP
> Root-Trees?  Say I used Fedora as a base, could I install Debian as the
> /opt/ltsp/i386 directory with the " debootstrap --arch i386 sarge
> /opt/ltsp/i386 http://ftp.debian.org/debian"?  If so could we install a
> ppc based distro with whatever commands that distro would need?

The problem is, 'debootstrap' doesn't exist on Fedora.  So you can't run
that command on a fedora machine to build a debian client tree.

And installing a PPC client tree on an x86 server is going to be tricky,
even if the distros are the same.  The problem there is that we can't
run the Pre-install and Post-install scripts in the PPC packages,
because they likely try to execute PPC binaries, and that won't fly on
an x86 server.  So, the trick there is unpack a big ole tarball into the
client tree directory.  Then, boot the PPC client, and run any
additional installation commands that might be necessary.

Jim McQuillan
jam at Ltsp.org



>
> If this is feasable could there be a menu driven script where we could
> choose the distro (the script would have the up to date syntax for
> pulling the correct packages), and then be prompted for a directory name
> (maybe default to /opt/ltsp/i386) where we could enter whatever we
> wanted?
>
> I my opinion if this is possible it would provide excellent versatility.
> We could run whatever base distro we fealt best for a server base, then
> install as many different linux flavors to serve thins as we wanted in
> /opt/ltsp/i386/debian
> /opt/ltsp/i386/fedora
> /opt/ltsp/i386/ubuntu
> /opt/ltsp/ppc/yellowdog
> /opt/ltsp/ppc/ubuntu
>
> You get the idea.  I don't know how we would choose what we booted from
> the clients, we know that using the vendor code and such works with
> determining ppc/i386/pxe/etc but how we would determine the different
> flavors for each architecture I don't know.  What if each architecture
> had a boot menu that was updated upon each flavor install under that
> directory base?  So the above example would load a base kernel dependant
> on architecture and then display something like a grub boot menu but to
> choose your flavor instead of a kernel version, then that menu pointed
> you down the correct nfs path and found the correct kernel paths in
> tftp?
>
> Just some thoughts, I wish I knew more so I could determine if the above
> makes me sound insane :-)
>
>
> --
> This message has been scanned for viruses and
> dangerous content by the Cotter Technology
> Department, and is believed to be clean.
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>