public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Any alternate download sites for speakup ftp?
Date: Fri, 25 Feb 2005 12:41:57 -0600	[thread overview]
Message-ID: <20050225184157.GA4377@blackbox> (raw)
In-Reply-To: <20050225182310.GL24987@rednote.net>

Hi.  Since Bill is the maintainer for the speakup modified Fedora,
wouldn't it be better to rsync against his server?  Considering the slow
transfers to and from bumpy, rsyncing against bumpy could get the
mirrors up to date much sooner.

          Kenny
	  
On Fri, Feb 25, 2005 at 01:23:10PM -0500, Janina Sajka wrote:
> Hi, Sina:
> 
> I don't think there's much to coordinate. That's the beauty of it.
> 
> My advice is to simply run a weekly rsync via cron--something like:
> 
> rsync -avtz --delete bumpy.braille.uwo.ca::ftp/speakup/disks/* \
> [mirror.directory]
> 
> The only refinement I can think of that would probably be helpful is to
> close the directory before doing the rsync to insure that no files are
> locked by someone's download while the rsync is in process. I confess I
> don't know if this is really an issue, but I'd want to make sure that it
> isn't--or just deal with it, perhaps by chmod the tree against reads for
> the duration.


  reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Al Puzzuoli
 ` John McCann
   ` Al Puzzuoli
     ` John McCann
       ` Al Puzzuoli
       ` Sina Bahram
         ` Farhan
 ` Sina Bahram
   ` Janina Sajka
     ` Sina Bahram
       ` Janina Sajka
         ` Kenny Hitt [this message]
           ` Janina Sajka
             ` Sina Bahram
               ` Janina Sajka
                 ` Sina Bahram
           ` Sina Bahram
             ` Janina Sajka
         ` Sina Bahram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050225184157.GA4377@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).