These kinds of issues (syncing files) were driving me nuts a few years ago
and I started using cvs to sync up files which worked pretty well. Now I am
using
coda and after a rocky set up and shake down phase of a few weeks it is now
working fantastic. The biggest thing to not do is to modify the same file on
both
my server and my laptop when they are not connected - something I could do
with cvs. I have a tiny Mitsubishi Amity which I take with me every day. When I
get home I plug it in to the network and forget it. Changes I've made to files
get
automatically reintegrated.
With mail files you have to be a little careful. I have seperate in boxes (using
procmail) from mail that comes in from different sources which prevents the same
file being modified on the laptop and the server whilst they are not connected.
Caveats with coda (from my limited experience and view point):
- 25 hour tokens are a pain.
- Poor integration with the Unix user system (have to add users to both Linux
and
coda).
- Challenging to install and setup.
- Consumes lots of ram and disk space.
Overall - well worth it for me and - if you have the time, patience, memory and
disk
space it may solve some of the problems you folks are discussing.
Matt
--
Seth Golub <[EMAIL PROTECTED]> on 09/18/99 09:23:39 PM
To: Steve Robbins <[EMAIL PROTECTED]>
cc: debian-laptop@lists.debian.org
Subject: Re: New to linux on laptops - A few Q's
Steve Robbins <[EMAIL PROTECTED]> writes:
> When I travel, I turn off my home machine, and have the laptop
> masquerade as it, so as to receive email on the laptop. That's fine
> until I return home. Now I have to merge all these mail folders.
I copy everything onto my laptop so that when it becomes the active
mail machine, it's also the master keeper of all mail files. I
manually set which system is in charge of mail, and its files clobber
the ones on the other system when I sync them.
When I just go out for a day or two and leave my home machine on and
pulling my mail down, my laptop isn't the master of my mail, so I Bcc
myself (with fully-qualified, non-local address) to archive outgoing
mail I write while offline.
There are two drawbacks to my setup:
1) When I go out for the day, I may make changes to my mail folders
and spools. When I return, those changes are lost. I do this
because it's critical that I not lose new mail in the spools at
home, and I'm happy being overly cautious in this case.
2) If I pull down mail on my laptop and resync with my desktop
machine without setting my laptop to be the master mail machine, I
will lose mail. Similarly, if after I return and sync I forget to
set my desktop machine to be the mail master, I'll lose mail when
I sync with the laptop. I haven't had any problems yet because
I've been careful enough and don't fetch mail from my laptop
often. The vulnerability could be fixed with some locks and
script changes, but as I'm ditching my desktop machine in a couple
weeks, I won't have to worry about it anymore.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
