From: Dave Goldberg <david.goldberg6@verizon.net>
Subject: Re: Running "The Same" GNUS from multiple machines.
Date: Thu, 28 Dec 2006 13:45:44 -0500 [thread overview]
Message-ID: <x7bqlnj1uv.fsf@davestoy.homelinux.org> (raw)
In-Reply-To: <87bqlo8463.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu\, 28 Dec 2006 15\:51\:16 +0100")
i guess it depends on how often and to how many places one needs to
sync it. Most of the systems i use have my home directory in AFS
space and so I don't need to do any synchronization at all. However I
maintain a local home directory on my laptop since AFS doesn't work
when I've only got ssh access. I use unison to keep that local home
and my AFS home in sync on a fairly regular basis, similar to the
offline files stuff in Windows though not quite as automatic. I
imagine that if I had to synchronize much more than that I would
eventually tire of it as well.
--
Dave Goldberg
david.goldberg6@verizon.net
prev parent reply other threads:[~2006-12-28 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 1:56 Allen S. Rout
2006-12-28 8:54 ` Simon Josefsson
2006-12-28 14:42 ` Allen S. Rout
2006-12-28 14:51 ` Simon Josefsson
2006-12-28 18:45 ` Dave Goldberg [this message]
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=x7bqlnj1uv.fsf@davestoy.homelinux.org \
--to=david.goldberg6@verizon.net \
/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 NNTP newsgroup(s).