From: [EMAIL PROTECTED] on behalf of Paul Greidanus
Sent: Thu 06/07/2006 21:43
To: [email protected]
Subject: Re: [Sisuite-devel] Portable Systemimager
Ok.. I've done a little testing and playing and I have gotten a
working
prepareclient (big deal, just startup rsync) that still needs some
work
to figure out how to work with BSD disklabels, and
OpenBSD's
partitioning. (This is for an OpenBSD test of
portable-systemimager).
I think it should be easy enough to add "if OS"
statements to wrapper
some of the changes. What's the best way to be
able to commit this sort
of thing? branch?
Anyone else out there
interested in working with this sort of thing?
Paul Greidanus
wrote:
> Hi All,
>
> I've been thinking about what it would
take to make systemimager, at
> least the core of it, portable across many
platforms, mostly because I
> have to deploy a bunch of machines with
differing operating systems, and
> it would be very nice to just have a
single product to take care of it.
>
> I'm thinking, the first step
would be to make systemimager know if it's
> runnining on Linux, and
compartmentalize the linux pieces, and leave
> only a very striped down
core? Each other OS would have to then build
> up "modules" or
something to allow them to be used?
>
> I'm going to take a swing at
some of this, using OpenBSD as the first
> non-Linux test, partially
because I need it, and partially because the
> installer and everything
about OpenBSD is pretty simple, and therefore
> easy enough to move into
the systemimager regieme (unlike something like
> Solaris, or
dare-to-dream.. Windows). The installer for OpenBSD is a
> single
script, that actually resembles the systemimager install script
> in it's
flow through the installation.
>
> The most basic common functions
that we'd need are:
> 1) si_prepareclient
> 2) si_getimage
>
3) some sort of kernel/initrd/bsd.rd or something that can net-boot,
>
needs to have busybox in it.
> 4) installation script
> 5)
si_updateclient
> 6) boel_binaries.tgz that works with the correct
kernel/bsd.rd
>
> One change that would be important, would be for
si_prepareclient to
> save the output of uname, possibly uname -a, to a
file, so that getimage
> knows what sort of autoinstall script it should
build for this client?
> (or is this already here?)
>
>
Is any of this thought process rational? Is it something that's
>
"commitable" to systemimager? Should I even be thinking of
commiting
> this sort of thing, or should this be a
fork?
>
>
Using Tomcat but need to do more?
Need to support web services, security?
Get stuff done quickly with
pre-integrated technology to make your job easier
Download IBM WebSphere
Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sisuite-devel
mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
