Hi Kent: On Fri, Aug 22, 2008 at 2:09 PM, Brodie, Kent <[EMAIL PROTECTED]> wrote:
> Even though I didn't believe it would be the cause, I finally snagged a > crossover cable from the closet-of-goodies and re-imaged my client. > Eliminating variables is what we sysadmins just gotta do. Even when it > feels stupid. Actually, in case you didn't know, most nics (gigabit) would automatically flip the bit so you don't need a cross-over cable to connect them. A straight-through cable would do fine. > What I don't get is, why does rsync _NOT_ have any issues when I do > stuff like build the golden client image etc, and I only see this > behavior after net-booting? It's the same freaking set of files.... > "when is rsync not really rsync"? That is not entirely true. There are three versions of rsync in play here: 1) rsync of your server 2) rsync of your golden client 3) rsync of SystemImager initrd (which should be 3.0.0) It is possible the "culprit" is rsync 3.0.0, so perhaps we should update that to a more recent version... > Not to mention any ideas on a switch/port setting that might make my HP > procurve switch play nice? Not entire surely... is this a new or old switch? Glad that you got things sorted out... somehow :-) Cheers, Bernard ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
