Just for the record (in case someone else runs into this thread), the entire
problem was rsync setup all along. I'm going to spend some time next week
figuring out why rsync wasn't set up correctly in the first place; I'd
followed the quick start pretty closely in the manual. All I have is
/etc/xinetd.d/rsync.presis~ and I'm sure there's something that SIS is
expecting (me? a sub-utility?) to do to get an rsync daemon ready for client
pulls.
Thanks to Bernard and Ole especially for following up.
Anyway, the necessary bits (all default locations):
[boot]
path = /usr/share/systemimager/boot
[scripts]
path = /var/lib/systemimager/scripts
[overrides]
path = /var/lib/systemimager/overrides
[image-name]
path = /var/lib/systemimager/images/image-name
The last part needs to be repeated for all images created, and updated
whenever you set up a new image. It's this dynamic part that leads me to
believe I'm ignoring some utility that SIS uses to update rsyncd.conf.
My test node is up and running merrily, looking exactly like the golden image
but with a different IP address! Fermi SL 4, IBM x330 with IBM x330 head
node / mgmt node (for test purposes, all in one).
DHCP woes were red herring, I'm new to dhclient's output, what with it being
so noisy.
Setting USELOGGER=1 on kernel append line in syslinux.cfg was what got me to
this point in debugging. Still, it would be nice to find out how to edit the
initrd.img properly; again, cp -a gave me several errors and the resulting
tree was missing several directories.
Regards,
Dan W.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
