Bernard Li wrote:
After you ran si_prepareclient, what does the image's
/etc/systemimager/autoinstallscript.conf look like? Does it say
/dev/sdb or /dev/sda?
It had any entry of:
DISK0=/dev/sdb
But that only triggers if the DISKORDER code above it doesn't find a
disk to map it to. From the looks of the code there and also down below
in the file where it remaps references to /dev/sdb --> /dev/sda in
/etc/fstabs and others, it looks like the way I described it working is
the way the code is designed to work.
Cheers,
Bernard
P.S. Which version of SystemImager are you using?
3.6.3 compiled into rpms from source (svn checkout). Sorry I didn't
provide this in the original e-mail.
-Allen
------------------------------------------------------------------------
*From:* [EMAIL PROTECTED] on behalf of Allen
Bierbaum
*Sent:* Tue 04/04/2006 20:04
*To:* [email protected]
*Subject:* [Sisuite-users] Ignore some partitions on destination
(clone) machine
Is it possible to create an image that when installed skips over some
drives on the cloned machine?
More detail...
I have been using systemimager successfully with cluster's of machines
where I can overwrite all data on all drives of the cluster nodes. But
recently I needed to work with a cluster that has data that needs to
remain in place on one of the drives on the nodes. This is because the
cluster will be dual booting with WinXP on one drive and Linux on the
other. (yes, I know I am asking for trouble but I really need to do it).
My setup is:
- /dev/sda - WinXP (must not be overwritten)
- /dev/sdb - Linux
I want to use systemimager to manage the Linux drive for all the nodes
and ignore WinXP.
At first I saw the new option (to me anyway) of --exclude that can be
passed to si_prepareclient. It seemed appropriate since the docs say
"Do not gather partition information for DISK(s). The result of using
this option, is that DISK(s) will not be partitioned during the
auto-install process.". Unfortunately what this really means is ignore
the drives when making the image and then map the drives from the golden
client to the clones based on disk order. For example, when I used
--exclude /dev/sda on my system it did ignore the drive, but then when
setting up the clone the contents (partitions, data, etc) from the
golden client's /dev/sdb got installed onto the clones /dev/sda.
Unfortunately I lost a windows drive learning this, but that is part of
the fun of doing this type of thing right. :)
So I am looking for other ideas. One idea I have yet to try is to
reorder the drives in all the systems so sda is the Linux drive and sdb
is the WinXP drive. Then I could probably use --exclude /dev/sdb to
ignore the windows drive like I tried above but then when it maps the
drives for installation it will still get the correct drive.
For right now I am just manually editing the autoinstall scripts. Not a
great solution but it may work for a while.
If anyone has another idea please let me know.
Thanks,
Allen
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
<http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642>
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
