Patrick Dowler wrote: > I agree with what Bernard says here: rebuild 4.0.0 asap so users with kernel > < > 2.6.22 aren't bitten by the bug. > > As for rsync, I am not sure I followed but is it a bug in rsync generally > that > is fixed in 3?
Yes. > > Since rysnc is generally supplied by the linux distribution separately, I > would not like to see SI require something that will conflict with what is > provided by the base system. That's a headache and will just leave a lot of > users back at SI 3.9.x until their distro goes to rsync 3. For fedora (which > we use), that means a new release (at least f8, maybe f9) as they would not > put it into an existing release as an update (if I understand the policy, and > the policy is why we use fedora). There's a misunderstanding here... using rsync 3.0.0pre4 wouldn't introduce any additional requirements. It will be only used by systemimager itself to build the initrd_template and the BOEL initrd.img (read: it'll be automatically shipped into the systemimager initrd). -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
