Benchmark-Perl-Formance-Cargo
view release on metacpan or search on metacpan
share/SpamAssassin/easy_ham/00164.8a0a728a1d5e56631369e5192f0348b6 view on Meta::CPAN
called congnitive dissonance theory
Most businesses keep inconsistent data, documents, tationale
and ideas to support their work activities, it's called real life.
I don't think it matters so much where it's located, i.e.
decentralization. I think that decentralization is the workaround
from technical limitations. The fallout being that the only way
inconsistent information spaces can be maintained is by
protecting them through a set of trust barriers and boundaries.
The local information when combined with the technical
troubles of providing "just enough" forced synchronization
to remote information provide workable data consistenty, i.e.
enforcing local constraints or ignoring global ones when
concerns are more immedidate.
Tolerating temporary, irreconcilable deviations is how
people cope, otherwise you'd be like Nick Gatsby unnecessarily
pre-occupied with a spot of shaving cream on McKee's neck
who thinks that if he can just wipe that spot off that the
whole world would be a little more perfect and everything,
including his pre-occupation with Daisy, would consistently
share/SpamAssassin/easy_ham/00369.f6f9d4cac4af831140abf032d0378365 view on Meta::CPAN
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Sun, 1 Sep 2002 16:59:24 -0700 (PDT)
On Sun, 1 Sep 2002, Bill Stoddard wrote:
> >
> > "Red Hat Linux Advanced Server provides many high end features such as:
> > Support for Asynchronous I/O. Now read I/O no longer needs to stall your
> > application while waiting for completion."
>
> Can you provide a reference? I could find it myself but I'm too lazy.
Well, i saw it on the Compaq Testdrive site, then had to seriously dig on
the redhat site... It's in one of their whitepapers...
http://www.redhat.com/pdf/as/as_rasm.pdf
> > Could it be? After 20 years without this feature UNIX finally
share/SpamAssassin/easy_ham/00411.478dc892fbb1a7970a4442fd6b977c25 view on Meta::CPAN
> -----Original Message-----
> From: fork-admin@xent.com [mailto:fork-admin@xent.com] On Behalf Of
Adam
> L. Beberg
> Sent: Saturday, August 31, 2002 7:35 PM
> To: fork@spamassassin.taint.org
> Subject: Gasp!
>
> "Red Hat Linux Advanced Server provides many high end features such
as:
> Support for Asynchronous I/O. Now read I/O no longer needs to stall
your
> application while waiting for completion."
>
> Could it be? After 20 years without this feature UNIX finally catches
up
> to
> Windows and has I/O that doesnt totally suck for nontrivial apps? No
way!
>
> OK, so they do it with signals or a flag, which is completely ghetto,
share/SpamAssassin/easy_ham/00414.c2dee68136358ceec7d235d03185822b view on Meta::CPAN
Received: from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
with ESMTP id 6F2942940C9; Tue, 3 Sep 2002 15:18:02 -0700 (PDT)
Delivered-To: fork@spamassassin.taint.org
Received: from panacea.canonical.org (ns1.canonical.org [209.115.72.29])
by xent.com (Postfix) with ESMTP id 6B789294099 for <fork@xent.com>;
Tue, 3 Sep 2002 15:17:08 -0700 (PDT)
Received: by panacea.canonical.org (Postfix, from userid 1004) id
D93F83F4EB; Tue, 3 Sep 2002 18:17:30 -0400 (EDT)
From: kragen@pobox.com (Kragen Sitaker)
To: fork@spamassassin.taint.org
Subject: asynchronous I/O (was Re: Gasp!)
Message-Id: <20020903221730.D93F83F4EB@panacea.canonical.org>
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@spamassassin.taint.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
List-Post: <mailto:fork@spamassassin.taint.org>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Tue, 3 Sep 2002 18:17:30 -0400 (EDT)
Of course we've had select() since BSD 4.2 and poll() since System V
or so, and they work reasonably well for asynchronous I/O up to a
hundred or so channels, but suck after that; /dev/poll (available in
Solaris and Linux) is one approach to solving this; Linux has a way to
do essentially the same thing with real-time signals, and has for
years; and FreeBSD has kqueue.
More details about these are at
http://www.citi.umich.edu/projects/linux-scalability/
None of this helps with disk I/O; most programs that need to overlap
disk I/O with computation, on either proprietary Unixes or Linux, just
use multiple threads or processes to handle the disk I/O.
POSIX specifies a mechanism for nonblocking disk I/O that most
proprietary Unixes implement. The Linux kernel hackers are currently
rewriting Linux's entire I/O subsystem essentially from scratch to
work asynchronously, because they can easily build efficient
synchronous I/O primitives from asynchronous ones, but not the other
way around. So now Linux will support this mechanism too.
It probably doesn't need saying for anyone who's read Beberg saying
things like "Memory management is a non-issue for anyone that has any
idea at all how the hardware functions," but he's totally off-base.
People should know by now not to take anything he says seriously, but
apparently some don't, so I'll rebut.
Not surprisingly, the rebuttal requires many more words than the
original stupid errors.
share/SpamAssassin/easy_ham/00414.c2dee68136358ceec7d235d03185822b view on Meta::CPAN
Linux's aio_* routines can notify the process of their completion with
a "signal", a feature missing in Microsoft Windows; a "signal" causes
the immediate execution of a "signal handler" in a process. By
contrast, the Microsoft Windows mechanisms to do similar things (such
as completion ports) do not deliver a notification until the process
polls them.
I don't think signals are a better way to do things in this case
(although I haven't written any RDBMSes myself), but you got the
technical descriptions of the two operating systems exactly backwards.
Most programs that use Linux real-time signals for asynchronous
network I/O, in fact, block the signal in question and poll the signal
queue in a very Windowsish way, using sigtimedwait() or sigwaitinfo().
--
<kragen@pobox.com> Kragen Sitaker <http://www.pobox.com/~kragen/>
Edsger Wybe Dijkstra died in August of 2002. This is a terrible loss after
which the world will never be the same.
http://www.xent.com/pipermail/fork/2002-August/013974.html
share/SpamAssassin/easy_ham/00416.ea1ffcacd8dd84214e745d86a5013115 view on Meta::CPAN
Received: from (127.0.0.1 [127.0.0.1]) by MailEnable Inbound Mail Agent
with ESMTP; Wed, 04 Sep 2002 02:30:43 -08:00
Message-Id: <3D757053.7030006@barrera.org>
From: "Joseph S. Barrera III" <joe@barrera.org>
Organization: Wings over the World
User-Agent: Mutt 5.00.2919.6900 DM (Nigerian Scammer Special Edition)
X-Accept-Language: en-us, en, ja
MIME-Version: 1.0
To: "Adam L. Beberg" <beberg@mithral.com>
Cc: Kragen Sitaker <kragen@pobox.com>, fork@spamassassin.taint.org
Subject: Re: asynchronous I/O (was Re: Gasp!)
References: <Pine.LNX.4.33.0209031924180.13303-100000@watcher.mithral.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@spamassassin.taint.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
List-Post: <mailto:fork@spamassassin.taint.org>
share/SpamAssassin/easy_ham/00417.7ec0b5a250ddfd52a9b46385688f9f9c view on Meta::CPAN
Received: from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
with ESMTP id 7910E2941D0; Tue, 3 Sep 2002 19:23:02 -0700 (PDT)
Delivered-To: fork@spamassassin.taint.org
Received: from mithral.com (watcher.mithral.com [204.153.244.1]) by
xent.com (Postfix) with SMTP id CED692941CF for <fork@xent.com>;
Tue, 3 Sep 2002 19:22:11 -0700 (PDT)
Received: (qmail 13312 invoked by uid 1111); 4 Sep 2002 02:24:24 -0000
From: "Adam L. Beberg" <beberg@mithral.com>
To: Kragen Sitaker <kragen@pobox.com>
Cc: <fork@spamassassin.taint.org>
Subject: Re: asynchronous I/O (was Re: Gasp!)
In-Reply-To: <20020903221730.D93F83F4EB@panacea.canonical.org>
Message-Id: <Pine.LNX.4.33.0209031924180.13303-100000@watcher.mithral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@spamassassin.taint.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
share/SpamAssassin/easy_ham/00417.7ec0b5a250ddfd52a9b46385688f9f9c view on Meta::CPAN
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Tue, 3 Sep 2002 19:24:24 -0700 (PDT)
On Tue, 3 Sep 2002, Kragen Sitaker wrote:
> Of course we've had select() since BSD 4.2 and poll() since System V
> or so, and they work reasonably well for asynchronous I/O up to a
> hundred or so channels, but suck after that; /dev/poll (available in
> Solaris and Linux) is one approach to solving this; Linux has a way to
> do essentially the same thing with real-time signals, and has for
> years; and FreeBSD has kqueue.
>
> More details about these are at
> http://www.citi.umich.edu/projects/linux-scalability/
>
> None of this helps with disk I/O; most programs that need to overlap
> disk I/O with computation, on either proprietary Unixes or Linux, just
> use multiple threads or processes to handle the disk I/O.
>
> POSIX specifies a mechanism for nonblocking disk I/O that most
> proprietary Unixes implement. The Linux kernel hackers are currently
> rewriting Linux's entire I/O subsystem essentially from scratch to
> work asynchronously, because they can easily build efficient
> synchronous I/O primitives from asynchronous ones, but not the other
> way around. So now Linux will support this mechanism too.
>
> It probably doesn't need saying for anyone who's read Beberg saying
> things like "Memory management is a non-issue for anyone that has any
> idea at all how the hardware functions," but he's totally off-base.
> People should know by now not to take anything he says seriously, but
> apparently some don't, so I'll rebut.
>
> Not surprisingly, the rebuttal requires many more words than the
> original stupid errors.
share/SpamAssassin/easy_ham/00417.7ec0b5a250ddfd52a9b46385688f9f9c view on Meta::CPAN
> Linux's aio_* routines can notify the process of their completion with
> a "signal", a feature missing in Microsoft Windows; a "signal" causes
> the immediate execution of a "signal handler" in a process. By
> contrast, the Microsoft Windows mechanisms to do similar things (such
> as completion ports) do not deliver a notification until the process
> polls them.
>
> I don't think signals are a better way to do things in this case
> (although I haven't written any RDBMSes myself), but you got the
> technical descriptions of the two operating systems exactly backwards.
> Most programs that use Linux real-time signals for asynchronous
> network I/O, in fact, block the signal in question and poll the signal
> queue in a very Windowsish way, using sigtimedwait() or sigwaitinfo().
>
> --
> <kragen@pobox.com> Kragen Sitaker <http://www.pobox.com/~kragen/>
> Edsger Wybe Dijkstra died in August of 2002. This is a terrible loss after
> which the world will never be the same.
> http://www.xent.com/pipermail/fork/2002-August/013974.html
>
share/SpamAssassin/easy_ham/00448.18e06f65c923e685fb4f72d90962c217 view on Meta::CPAN
Received: from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
with ESMTP id 429D3294289; Fri, 6 Sep 2002 01:27:05 -0700 (PDT)
Delivered-To: fork@spamassassin.taint.org
Received: from panacea.canonical.org (ns1.canonical.org [209.115.72.29])
by xent.com (Postfix) with ESMTP id 7586129427E for <fork@xent.com>;
Fri, 6 Sep 2002 01:26:11 -0700 (PDT)
Received: by panacea.canonical.org (Postfix, from userid 1004) id
9369B3F4EB; Fri, 6 Sep 2002 04:26:44 -0400 (EDT)
From: kragen@pobox.com (Kragen Sitaker)
To: fork@spamassassin.taint.org
Subject: Re: asynchronous I/O (was Re: Gasp!)
Message-Id: <20020906082644.9369B3F4EB@panacea.canonical.org>
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@spamassassin.taint.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
List-Post: <mailto:fork@spamassassin.taint.org>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
share/SpamAssassin/easy_ham/00477.ae6b0e13cfb834b905857a31327dda32 view on Meta::CPAN
Received: from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
with ESMTP id 21833294287; Fri, 6 Sep 2002 13:16:03 -0700 (PDT)
Delivered-To: fork@spamassassin.taint.org
Received: from localhost.localdomain (pm0-8.sba1.netlojix.net
[207.71.218.8]) by xent.com (Postfix) with ESMTP id 55EC929427E for
<fork@xent.com>; Fri, 6 Sep 2002 13:15:34 -0700 (PDT)
Received: (from dave@localhost) by maltesecat (8.8.7/8.8.7a) id NAA21491;
Fri, 6 Sep 2002 13:25:33 -0700
Message-Id: <200209062025.NAA21491@maltesecat>
To: fork@spamassassin.taint.org
Subject: Re: asynchronous I/O (was Re: Gasp!)
In-Reply-To: Message from fork-request@xent.com of
"Fri, 06 Sep 2002 06:25:37 PDT."
<20020906132537.6311.58517.Mailman@lair.xent.com>
From: Dave Long <dl@silcom.com>
Sender: fork-admin@xent.com
Errors-To: fork-admin@xent.com
X-Beenthere: fork@spamassassin.taint.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:fork-request@xent.com?subject=help>
share/SpamAssassin/easy_ham/00632.5aaf2a16e34b00ee971d17bd4343e61e view on Meta::CPAN
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Wed, 18 Sep 2002 21:21:22 -0400
advice to the lovelorn haiku
serendipity
pilots synchronicity:
turn the next corner.
-----Original Message-----
From: fork-admin@xent.com [mailto:fork-admin@xent.com]On Behalf Of Tom
Sent: Wednesday, September 18, 2002 7:13 PM
To: R. A. Hettinga
Cc: fork@spamassassin.taint.org
Subject: Re: AA Meetings the Hottest Place to Meet Women With Big Bucks
share/SpamAssassin/easy_ham/00648.d3808dc202cff72d0326d74d23eaad17 view on Meta::CPAN
teamwork and interaction without the hassle of travel.
With the rapid growth in popularity of Web meetings, the rationale for this
world-class relationship stems from the growing need for workgroups around
the world to maintain the quality of the team collaboration experience
between online meetings. The issue by those preferring not to travel is how
to continue to collaborate and share information with team members between
meetings rather than depending on intermittent, insecure email and multiple
copies of constantly changing documents.
Inter-meeting collaboration needs an asynchronous medium, independent of
time. In asynchronous mode, a team member can access, read and edit
information relevant to the meeting group at his/her convenience rather than
having to fit into the schedules and timeframes of others. A secured
environment available only to members of a meeting or project is also
essential.
Endeavors' Magi technology converts the Web into a secure platform for
sharing information directly from people's desktops. WebEx meetings can be
recorded and reviewed at any time, documents shared in the meeting can be
actioned in real-time or at a later date, calendars and project schedules
can be updated at any time, and new individuals added to the workgroup at
share/SpamAssassin/easy_ham/00648.d3808dc202cff72d0326d74d23eaad17 view on Meta::CPAN
Bernard Hulme, Tadpole's group chief executive. "The powerful combination
of Endeavors' Magi and WebEx's communications technologies will assist
global work teams to better meet critical business goals and deadlines by
maintaining teamwork momentum within and between Web meetings."
"WebEx is transforming the way businesses use the Web for sales, marketing,
training, support and product design," says David Farrington, vice president
of corporate development at WebEx Communications. "By integrating the
communications capabilities of the WebEx platform with Endeavors' secure
collaboration network, Endeavors has created an offering that provides the
best in synchronous and asynchronous communications."
About Magi
Magi Enterprise 3.0, an award-winning web collaboration system, transforms
today's Web into a highly secure inter- and intra-enterprise collaboration
network of files and web resources. For the first time, enterprises can
implement ad-hoc Virtual Private Networks for collaboration very rapidly and
affordably without disrupting existing applications, networks or work
practices. Magi Enterprise 3.0 does this by effectively transforming
unsecured, "read-only" Web networks into two-way trusted and transparent
collaboration environments, through the use of such features as
share/SpamAssassin/easy_ham/00648.d3808dc202cff72d0326d74d23eaad17 view on Meta::CPAN
For further information, please contact:
Bernard Hulme, Tadpole Technology - via Patcom Media
Hugh Paterson, Patcom Media - Tel 0207 987 4888, Email
hughp@patcom-media.com
Bullets for Editors
WebEx
Web communications services (synchronous): network-based platform for
delivering highly interactive, visually dynamic Web communications. The
WebEx platform supports real-time data, voice and video communications.
WebEx is the only company to design, develop and deploy a global network for
real-time Web communications.
Magi
On and off-line (asynchronous) communication and collaboration: cross
enterprise search and discovery, transparent security and trust (SSL & PKI),
2-way web access to files and applications, permanent cross firewall access,
ad hoc and permanent secure groups, centralized or decentralized control of
access lists and security privileges, centralized caching of information
(never lose anything critical), multi-device access to information (desktop,
laptop, PDA).
share/SpamAssassin/easy_ham/00685.0c2b26b54c5bb9e9072515d58ccc14ea view on Meta::CPAN
List-Post: <mailto:fork@spamassassin.taint.org>
List-Subscribe: <http://xent.com/mailman/listinfo/fork>, <mailto:fork-request@xent.com?subject=subscribe>
List-Id: Friends of Rohit Khare <fork.xent.com>
List-Unsubscribe: <http://xent.com/mailman/listinfo/fork>,
<mailto:fork-request@xent.com?subject=unsubscribe>
List-Archive: <http://xent.com/pipermail/fork/>
Date: Sat, 21 Sep 2002 09:53:58 -0400
Hello Chris,
Oh I don't know, Time-lag synchrocity?
Or mutual shared experience over time?
:)
Its like 930 am..I can't function yet. Lord knows its 630 where you
are.
I say this should be a FoRK Posit.
share/SpamAssassin/easy_ham_2/00087.809e03adf935435f9e493a3ffdfd9e85 view on Meta::CPAN
An NIS/NFS server which will also run Samba to allow the VMware clients
access to its filesystems.
How can I set things up so that all the VMware clients (all running 'doze
98, possibly being upgraded in future to W2K) authenticate against the NIS
server's Samba ? I have read the Samab documentation in large quantities
down through the years but as I've never wanted to do anything like this, I
never paid much attention to all the stuff about domain controllers etc.
which I presume is what I will need to have running here.
I would also like, if at all possible, to have synchronisation of passwords
between the NIS domain and the NIS server's Samba with minimal manual
intervention.
Ideas, accompanied by annotated Samba configration files :-) , gratefully
received.
Niall
share/SpamAssassin/easy_ham_2/00438.a4e08ec27cc4d6d5dd27d43178d3bc17 view on Meta::CPAN
is that BRU will do it.
On balance, I'd personally _still_ go with a DDS4 drive using either DDS3
or DDS4 media, mostly because once you've survived life with one
oddball, less-standard tape format, you're not in a hurry to repeat the
experience. But ADR does seem at a quick glance to be well designed,
and might be a good bet after all. As they say in the gaming industry,
"Ya pays your money, and ya takes your chances."
--
"Is it not the beauty of an asynchronous form of discussion that one can go and
make cups of tea, floss the cat, fluff the geraniums, open the kitchen window
and scream out it with operatic force, volume, and decorum, and then return to
the vexed glowing letters calmer of mind and soul?" -- The Cube, forum3000.org
--
Irish Linux Users' Group: ilug@linux.ie
http://www.linux.ie/mailman/listinfo/ilug for (un)subscription information.
List maintainer: listmaster@linux.ie
share/SpamAssassin/easy_ham_2/00693.2183b91fb14b93bdfaab337b915c98bb view on Meta::CPAN
input. [But] once it is decided, people don't get to vote with their feet.
We try to make a quantum leap here in terms of our ability to improve
pulling together all the pieces. Our customers want us to do
that. Simplifying concepts by unifying them. The customers don't say
they want us to do that, but when we do do that, they go, 'Ahhh, I get
it. That makes sense.'
I don't want to go to six more meetings where people say, 'Is your
workflow strategy BizTalk?' ... Or 'What's your Office workflow
strategy?' Or 'Why is synchronization in some ways better for e-mail and
Outlook than it is for file folders and Web pages?'
To get that sort of synchronization sometimes -- to get that high-level
road map to work -- you have to build something we don't have today. So
we have been talking about unifying storage. And so the best way to get
all this stuff to work is to get them all to work just one way. Then you
just keep tuning one set of parameters instead of having a thousand
flowers blooming.
> In your Fusion keynote today, you talked about who your competitors
> are, and it was the usual suspects. But one you didn't mention is
> yourself. You are competing against the last generation of your technology.
share/SpamAssassin/easy_ham_2/00694.a56619f593077d85ce28a4fafe547ab7 view on Meta::CPAN
By Anthony Cataldo
May 28, 2002
SAN JOSE, Calif. -- A group of engineers in Calabasas Hills, CA wants to
turn the microprocessor world on its head by doing the unthinkable:
tossing out the clock and letting the signals move about unencumbered.
For those designers, inspired by research conducted at nearby Caltech,
clocks are for wimps.
The Fulcrum Microsystems Inc. design team isn't the first to propose an
asynchronous processor, but president and chief executive officer Robert
Nunn wants to be the first to take a clockless, fire-breathing processor
mainstream. "We really deal with an asynchronous world," he said. "We
only make it synchronous for our own convenience."
This is the kind of stuff that many in the processor industry would
consider lunatic fringe, too weird for conservative embedded-systems
designers. But the young processor company and more than a dozen others
like it are anchored in the mainstream courtesy of the MIPS
instruction-set architecture. More and more, MIPS is becoming the choice
for maverick processor design teams seeking a place at the high end by
fielding unorthodox devices. And if Motorola and IBM in the PowerPC camp
aren't careful, they could see their performance leadership in the
high-end embedded-processor market snatched away by some of these upstarts.
share/SpamAssassin/easy_ham_2/00694.a56619f593077d85ce28a4fafe547ab7 view on Meta::CPAN
Caltech who founded Fulcrum Microsystems in 2000. "There is a pervasive
philosophy at Caltech that no problem is unsolvable," Cummings
says. "There's a focus on scientific ingenuity that is thrilling to be
around. Caltech has so many entrepreneurs because the school doesn't
make it about business or focus on how much money they'll get out of
it. Caltech is a catalyst, moving technology from the university out
into industry, and students are thrilled to be a part of it."
Before starting Fulcrum, Cummings and Lines worked for six years with
Caltech computer-science professor Alain Martin on an
asynchronous-circuit design for semiconductor chips. They ventured into
commercialization while still in the throes of their doctoral program.
That they could afford to do that points to another, more practical
aspect to Caltech's approach. Other universities typically require
entrepreneurs to pay up-front application and licensing fees for the use
of technology patents. But Caltech believes that such payments stifle
entrepreneurship, since young companies usually have little cash to
spare. Instead, the school typically takes equity stakes in startups,
and it defers collection of patent payments until fledgling companies
are financially secure.
share/SpamAssassin/easy_ham_2/01018.cb98ac59fae50ab0823aba7483d37d50 view on Meta::CPAN
The unit has an 10.4 inch 800 x 600 High Luminance SVGA resistive touch screen display that can be used either in portrait or landscape mode, 128 MB RAM (expandable to 512MB), a 10 GB hard disk drive, two USB ports, an open type II PCMCIA slot, an in...
--------------------------------------------------------------------------------------------------------------------------------------------
Fujitsu Stylistic 3500 and LT-P600:
The Fujitsu Stylistic 3500 and LT-P600 products are available in several configurations depending on disk, screen, memory capacity and wireless options. The prices range from $3559 to $3859 and offer the choice of Windows 2000 or Windows 98. The scre...
--------------------------------------------------------------------------------------------------------------------------------------------
ViewSonic ViewPad 100 Super PDA - SAME DAY SHIPPING AVAILABLE
The ViewPad 100 Super PDA enables you to access important applications and data from virtually anywhere. Not only is information easy to get (with options added to the included PC Card and CompactFlash slots), but it's also easy to keep organized by ...
The price for the Microsoft Windows CE 3.0 based ViewSonic ViewPad 100 is $1225. The cradle is an additional $129. The unit features a PCMCIA slot and a CF slot which enable you to insert either a 802.11b WLAN card or a cellular based WAN card (not i...
Internet Explorer 4.0 with Java Virtual Machine and Macromedia Flash support are included, as are viewers for many types of files, PTab Spreadsheet software (Microsoft Excel compatible), Citrix ICA 6.0 and Microsoft RDP 5.0, Microsoft Inbox, Microsof...
The unit features Microsoft ActiveSync, handwriting recognition software, and a virtual keyboard.
The unit has an 10 inch 800 x 600 High Luminance SVGA resistive touch screen display that can be used either in portrait or landscape mode, 128 MB RAM and 32MB Flash, one USB port, an open type II PCMCIA slot and an open type II CompactFlash slot . I...
--------------------------------------------------------------------------------------------------------------------------------------------
share/SpamAssassin/easy_ham_2/01317.7fc86413a091430c3104b041a6525131 view on Meta::CPAN
[055] - Open Remote Collaboration Tool 1.0.1
by Thomas Amsler (http://freshmeat.net/users/amsler/)
Tuesday, July 30th 2002 18:06
Communications :: Chat
Education
Internet
About: OpenRCT is a multidisciplinary effort to enhance collaboration
between people who are not co-located in time and space. It is a platform
independent multimedia tool that supports synchronous and/or asynchronous
communication.
License: GNU General Public License (GPL)
URL: http://freshmeat.net/projects/openrct/
- % - % - % - % -
[056] - OpenCL 0.8.7
by Jack Lloyd (http://freshmeat.net/users/randombit/)
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
Enjoy,
-- Benjamin
Changes since 2.9.1:
* Added a preference maxthreads that can be used to limit the number
of simultaneous file transfers.
* Added a backupdir preference, which controls where backup files
are stored.
* Basic support added for OSX. In particular, Unison now recognizes
when one of the hosts being synchronized is running OSX and
switches to a case-insensitive treatment of filenames (i.e., 'foo'
and 'FOO' are considered to be the same file). (OSX is not yet
fully working, however: in particular, files with resource forks
will not be synchronized correctly.)
* The same hash used to form the archive name is now also added to
the names of the temp files created during file transfer. The
reason for this is that, during update detection, we are going to
silently delete any old temp files that we find along the way, and
we want to prevent ourselves from deleting temp files belonging to
other instances of Unison that may be running in parallel, e.g.
synchronizing with a different host. Thanks to Ruslan Ermilov for
this suggestion.
* Several small user interface improvements
* Documentation
+ FAQ and bug reporting instructions have been split out as
separate HTML pages, accessible directly from the unison web
page.
+ Additions to FAQ, in particular suggestions about performance
tuning.
* Makefile
+ Makefile.OCaml now sets UISTYLE=text or UISTYLE=gtk
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
Changes since 2.8.1:
* Changing profile works again under Windows
* File movement optimization: Unison now tries to use local copy
instead of transfer for moved or copied files. It is controled by
a boolean option ``xferbycopying''.
* Network statistics window (transfer rate, amount of data
transferred). [NB: not available in Windows-Cygwin version.]
* symlinks work under the cygwin version (which is dynamically
linked).
* Fixed potential deadlock when synchronizing between Windows and
Unix
* Small improvements:
+ If neither the
tt USERPROFILE nor the
tt HOME environment variables are set, then Unison will put
its temporary commit log (called
tt DANGER.README) into the directory named by the
tt UNISON environment variable, if any; otherwise it will use
tt C:.
+ alternative set of values for fastcheck: yes = true; no =
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
characters in filenames on Windows systems in the GTK UI.
(This code is currently untested---if you're one of the
people that had reported problems with display of non-ascii
filenames, we'd appreciate knowing if this actually fixes
things.)
+ `-prefer/-force newer' works properly now. (The bug was
reported by Sebastian Urbaniak and Sean Fulton.)
* User interface and Unison behavior:
+ Renamed `Proceed' to `Go' in the graphical UI.
+ Added exit status for the textual user interface.
+ Paths that are not synchronized because of conflicts or
errors during update detection are now noted in the log file.
+ [END] messages in log now use a briefer format
+ Changed the text UI startup sequence so that
tt ./unison -ui text will use the default profile instead of
failing.
+ Made some improvements to the error messages.
+ Added some debugging messages to remote.ml.
Changes since 2.7.7:
* Incorporated, once again, a multi-threaded transport sub-system.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
* New functionality: centralized backups and merging
+ This version incorporates two pieces of major new
functionality, implemented by Sylvain Roy during a summer
internship at Penn: a centralized backup facility that keeps
a full backup of (selected files in) each replica, and a
merging feature that allows Unison to invoke an external
file-merging tool to resolve conflicting changes to
individual files.
+ Centralized backups:
o Unison now maintains full backups of the
last-synchronized versions of (some of) the files in
each replica; these function both as backups in the
usual sense and as the ``common version'' when invoking
external merge programs.
o The backed up files are stored in a directory
/.unison/backup on each host. (The name of this
directory can be changed by setting the environment
variable UNISONBACKUPDIR.)
o The predicate backup controls which files are actually
backed up: giving the preference 'backup = Path *'
causes backing up of all files.
o Files are added to the backup directory whenever unison
updates its archive. This means that
# When unison reconstructs its archive from scratch
(e.g., because of an upgrade, or because the
archive files have been manually deleted), all
files will be backed up.
# Otherwise, each file will be backed up the first
time unison propagates an update for it.
o The preference backupversions controls how many previous
versions of each file are kept. The default is 2 (i.e.,
the last synchronized version plus one backup).
o For backward compatibility, the backups preference is
also still supported, but backup is now preferred.
o It is OK to manually delete files from the backup
directory (or to throw away the directory itself).
Before unison uses any of these files for anything
important, it checks that its fingerprint matches the
one that it expects.
+ Merging:
o Both user interfaces offer a new 'merge' command,
invoked by pressing 'm' (with a changed file selected).
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
experts only. See the ``Archive Files'' section of the manual for
more information.)
* Graphical user-interface:
+ A new command is provided in the Synchronization menu for
switching to a new profile without restarting Unison from
scratch.
+ The GUI also supports one-key shortcuts for commonly used
profiles. If a profile contains a preference of the form 'key
= n', where n is a single digit, then pressing this key will
cause Unison to immediately switch to this profile and begin
synchronization again from scratch. (Any actions that may
have been selected for a set of changes currently being
displayed will be discarded.)
+ Each profile may include a preference 'label = <string>'
giving a descriptive string that described the options
selected in this profile. The string is listed along with the
profile name in the profile selection dialog, and displayed
in the top-right corner of the main Unison window.
* Minor:
+ Fixed a bug that would sometimes cause the 'diff' display to
order the files backwards relative to the main user
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
+ On Unix systems, the graphical version of Unison will check
the DISPLAY variable and, if it is not set, automatically
fall back to the textual user interface.
+ Synchronization paths (path preferences) are now matched
against the ignore preferences. So if a path is both
specified in a path preference and ignored, it will be
skipped.
+ Numerous other bugfixes and small improvements.
Changes since 2.6.1:
* The synchronization of modification times has been disabled for
directories.
* Preference files may now include lines of the form include <name>,
which will cause name.prf to be read at that point.
* The synchronization of permission between Windows and Unix now
works properly.
* A binding CYGWIN=binmode in now added to the environment so that
the Cygwin port of OpenSSH works properly in a non-Cygwin context.
* The servercmd and addversionno preferences can now be used
together: -addversionno appends an appropriate -NNN to the server
command, which is found by using the value of the -servercmd
preference if there is one, or else just unison.
* Both '-pref=val' and '-pref val' are now allowed for boolean
values. (The former can be used to set a preference to false.)
* Lot of small bugs fixed.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
* The log preference is now set to true by default, since the log
file seems useful for most users.
* Several miscellaneous bugfixes (most involving symlinks).
Changes since 2.5.25:
* INCOMPATIBLE CHANGE: Archive format has changed (again).
* Several significant bugs introduced in 2.5.25 have been fixed.
Changes since 2.5.1:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New functionality:
+ Unison now synchronizes file modtimes, user-ids, and
group-ids.
These new features are controlled by a set of new
preferences, all of which are currently false by default.
o When the times preference is set to true, file
modification times are propaged. (Because the
representations of time may not have the same
granularity on both replicas, Unison may not always be
able to make the modtimes precisely equal, but it will
get them as close as the operating systems involved
allow.)
o When the owner preference is set to true, file ownership
information is synchronized.
o When the group preference is set to true, group
information is synchronized.
o When the numericIds preference is set to true, owner and
group information is synchronized numerically. By
default, owner and group numbers are converted to names
on each replica and these names are synchronized. (The
special user id 0 and the special group 0 are never
mapped via user/group names even if this preference is
not set.)
+ Added an integer-valued preference perms that can be used to
control the propagation of permission bits. The value of this
preference is a mask indicating which permission bits should
be synchronized. It is set by default to 0o1777: all bits but
the set-uid and set-gid bits are synchronised (synchronizing
theses latter bits can be a security hazard). If you want to
synchronize all bits, you can set the value of this
preference to -1.
+ Added a log preference (default false), which makes Unison
keep a complete record of the changes it makes to the
replicas. By default, this record is written to a file called
unison.log in the user's home directory (the value of the
HOME environment variable). If you want it someplace else,
set the logfile preference to the full pathname you want
Unison to use.
+ Added an ignorenot preference that maintains a set of
patterns for paths that should definitely not be ignored,
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
+ Removed the trace and silent preferences. They did not seem
very useful, and there were too many preferences for
controlling output in various ways.
+ The text UI now displays just the default command (the one
that will be used if the user just types <return>) instead of
all available commands. Typing ? will print the full list of
possibilities.
+ The function that finds the canonical hostname of the local
host (which is used, for example, in calculating the name of
the archive file used to remember which files have been
synchronized) normally uses the gethostname operating system
call. However, if the environment variable
UNISONLOCALHOSTNAME is set, its value will now be used
instead. This makes it easier to use Unison in situations
where a machine's name changes frequently (e.g., because it
is a laptop and gets moved around a lot).
+ File owner and group are now displayed in the ``detail
window'' at the bottom of the screen, when unison is
configured to synchronize them.
* For hackers:
+ Updated to Jacques Garrigue's new version of lablgtk, which
means we can throw away our local patched version.
If you're compiling the GTK version of unison from sources,
you'll need to update your copy of lablgtk to the developers
release, available from
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
(Warning: installing lablgtk under Windows is currently a bit
challenging.)
+ The TODO.txt file (in the source distribution) has been
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
linux). We will not be distributing binaries for these
architectures ourselves (at least for a while) but if someone
would like to make them available, we'll be glad to provide a
link to them.
* Bug fixes:
+ Pattern matching (e.g. for ignore) is now case-insensitive
when Unison is in case-insensitive mode (i.e., when one of
the replicas is on a windows machine).
+ Some people had trouble with mysterious failures during
propagation of updates, where files would be falsely reported
as having changed during synchronization. This should be
fixed.
+ Numerous smaller fixes.
Changes since 2.4.1:
* Added a number of 'sorting modes' for the user interface. By
default, conflicting changes are displayed at the top, and the
rest of the entries are sorted in alphabetical order. This
behavior can be changed in the following ways:
+ Setting the sortnewfirst preference to true causes newly
created files to be displayed before changed files.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
a path descriptor in the same format as 'ignore' and 'follow'
patterns, causes paths matching this pattern to be displayed
first.
+ Similarly, giving the preference sortlast=<pattern> causes
paths matching this pattern to be displayed last.
The sorting preferences are described in more detail in the user
manual. The sortnewfirst and sortbysize flags can also be accessed
from the 'Sort' menu in the grpahical user interface.
* Added two new preferences that can be used to change unison's
fundamental behavior to make it more like a mirroring tool instead
of a synchronizer.
+ Giving the preference prefer with argument <root> (by adding
-prefer <root> to the command line or prefer=<root>) to your
profile) means that, if there is a conflict, the contents of
<root> should be propagated to the other replica (with no
questions asked). Non-conflicting changes are treated as
usual.
+ Giving the preference force with argument <root> will make
unison resolve all differences in favor of the given root,
even if it was the other replica that was changed.
These options should be used with care! (More information is
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
differently when the user has overridded Unison's default
recommendation (====> instead of ---->). This matches the
behavior of the graphical interface, which displays such
arrows in a different color.
+ Carriage returns (Control-M's) are ignored at the ends of
lines in profiles, for Windows compatibility.
+ All preferences are now fully documented in the user manual.
Changes since 2.3.12:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New/improved functionality:
+ A new preference -sortbysize controls the order in which
changes are displayed to the user: when it is set to true,
the smallest changed files are displayed first. (The default
setting is false.)
+ A new preference -sortnewfirst causes newly created files to
be listed before other updates in the user interface.
+ We now allow the ssh protocol to specify a port.
+ Incompatible change: The unison: protocol is deprecated, and
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
values are 1 and 2. (Default is empty, which will make unison
use whatever version of ssh is installed as the default 'ssh'
command.)
+ The situation when the permissions of a file was updated the
same on both side is now handled correctly (we used to report
a spurious conflict)
* Improvements for the Windows version:
+ The fact that filenames are treated case-insensitively under
Windows should now be handled correctly. The exact behavior
is described in the cross-platform section of the manual.
+ It should be possible to synchronize with Windows shares,
e.g., //host/drive/path.
+ Workarounds to the bug in syncing root directories in
Windows. The most difficult thing to fix is an ocaml bug:
Unix.opendir fails on c: in some versions of Windows.
* Improvements to the GTK user interface (the Tk interface is no
longer being maintained):
+ The UI now displays actions differently (in blue) when they
have been explicitly changed by the user from Unison's
default recommendation.
+ More colorful appearance.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
to install the headers and libraries (which are not installed by
default).
* Added a new -addversionno switch, which causes unison to use
unison-<currentversionnumber> instead of just unison as the remote
server command. This allows multiple versions of unison to coexist
conveniently on the same server: whichever version is run on the
client, the same version will be selected on the server.
Changes since 1.219:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version fixes several annoying bugs, including:
+ Some cases where propagation of file permissions was not
working.
+ umask is now ignored when creating directories
+ directories are create writable, so that a read-only
directory and its contents can be propagated.
+ Handling of warnings generated by the server.
+ Synchronizing a path whose parent is not a directory on both
sides is now flagged as erroneous.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
files.
* The semantics of Path and Name regular expressions now correspond
better.
* Some minor improvements to the text UI (e.g. a command for going
back to previous items)
* The organization of the export directory has changed --- should be
easier to find / download things now.
Changes since 1.200:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version has not been tested extensively on Windows.
* Major internal changes designed to make unison safer to run at the
same time as the replicas are being changed by the user.
* Internal performance improvements.
Changes since 1.190:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* A number of internal functions have been changed to reduce the
amount of memory allocation, especially during the first
synchronization. This should help power users with very big
replicas.
* Reimplementation of low-level remote procedure call stuff, in
preparation for adding rsync-like smart file transfer in a later
release.
* Miscellaneous bug fixes.
Changes since 1.180:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* Fixed some small bugs in the interpretation of ignore patterns.
* Fixed some problems that were preventing the Windows version from
working correctly when click-started.
* Fixes to treatment of file permissions under Windows, which were
causing spurious reports of different permissions when
synchronizing between windows and unix systems.
* Fixed one more non-tail-recursive list processing function, which
was causing stack overflows when synchronizing very large
replicas.
Changes since 1.169:
* The text user interface now provides commands for ignoring files.
* We found and fixed some more non-tail-recursive list processing
functions. Some power users have reported success with very large
replicas.
* INCOMPATIBLE CHANGE: Files ending in .tmp are no longer ignored
automatically. If you want to ignore such files, put an
appropriate ignore pattern in your profile.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
matches exactly the path <path>.
Standard ``globbing'' conventions can be used in <name> and
<path>:
+ a ? matches any single character except /
+ a * matches any sequence of characters not including /
+ [xyz] matches any character from the set {x, y, z }
+ {a,bb,ccc} matches any one of a, bb, or ccc.
See the user manual for some examples.
Changes since 1.146:
* Some users were reporting stack overflows when synchronizing huge
directories. We found and fixed some non-tail-recursive list
processing functions, which we hope will solve the problem. Please
give it a try and let us know.
* Major additions to the documentation.
Changes since 1.142:
* Major internal tidying and many small bugfixes.
* Major additions to the user manual.
* Unison can now be started with no arguments -- it will prompt
automatically for the name of a profile file containing the roots
to be synchronized. This makes it possible to start the graphical
UI from a desktop icon.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.139:
* The precompiled windows binary in the last release was compiled
with an old OCaml compiler, causing propagation of permissions not
to work (and perhaps leading to some other strange behaviors we've
heard reports about). This has been corrected. If you're using
precompiled binaries on Windows, please upgrade.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
Changes in Version 2.9.20
Changes since 2.9.1:
* Added a preference maxthreads that can be used to limit the number
of simultaneous file transfers.
* Added a backupdir preference, which controls where backup files
are stored.
* Basic support added for OSX. In particular, Unison now recognizes
when one of the hosts being synchronized is running OSX and
switches to a case-insensitive treatment of filenames (i.e., 'foo'
and 'FOO' are considered to be the same file). (OSX is not yet
fully working, however: in particular, files with resource forks
will not be synchronized correctly.)
* The same hash used to form the archive name is now also added to
the names of the temp files created during file transfer. The
reason for this is that, during update detection, we are going to
silently delete any old temp files that we find along the way, and
we want to prevent ourselves from deleting temp files belonging to
other instances of Unison that may be running in parallel, e.g.
synchronizing with a different host. Thanks to Ruslan Ermilov for
this suggestion.
* Several small user interface improvements
* Documentation
+ FAQ and bug reporting instructions have been split out as
separate HTML pages, accessible directly from the unison web
page.
+ Additions to FAQ, in particular suggestions about performance
tuning.
* Makefile
+ Makefile.OCaml now sets UISTYLE=text or UISTYLE=gtk
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
Changes since 2.8.1:
* Changing profile works again under Windows
* File movement optimization: Unison now tries to use local copy
instead of transfer for moved or copied files. It is controled by
a boolean option ``xferbycopying''.
* Network statistics window (transfer rate, amount of data
transferred). [NB: not available in Windows-Cygwin version.]
* symlinks work under the cygwin version (which is dynamically
linked).
* Fixed potential deadlock when synchronizing between Windows and
Unix
* Small improvements:
+ If neither the
tt USERPROFILE nor the
tt HOME environment variables are set, then Unison will put
its temporary commit log (called
tt DANGER.README) into the directory named by the
tt UNISON environment variable, if any; otherwise it will use
tt C:.
+ alternative set of values for fastcheck: yes = true; no =
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
characters in filenames on Windows systems in the GTK UI.
(This code is currently untested---if you're one of the
people that had reported problems with display of non-ascii
filenames, we'd appreciate knowing if this actually fixes
things.)
+ `-prefer/-force newer' works properly now. (The bug was
reported by Sebastian Urbaniak and Sean Fulton.)
* User interface and Unison behavior:
+ Renamed `Proceed' to `Go' in the graphical UI.
+ Added exit status for the textual user interface.
+ Paths that are not synchronized because of conflicts or
errors during update detection are now noted in the log file.
+ [END] messages in log now use a briefer format
+ Changed the text UI startup sequence so that
tt ./unison -ui text will use the default profile instead of
failing.
+ Made some improvements to the error messages.
+ Added some debugging messages to remote.ml.
Changes since 2.7.7:
* Incorporated, once again, a multi-threaded transport sub-system.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
* New functionality: centralized backups and merging
+ This version incorporates two pieces of major new
functionality, implemented by Sylvain Roy during a summer
internship at Penn: a centralized backup facility that keeps
a full backup of (selected files in) each replica, and a
merging feature that allows Unison to invoke an external
file-merging tool to resolve conflicting changes to
individual files.
+ Centralized backups:
o Unison now maintains full backups of the
last-synchronized versions of (some of) the files in
each replica; these function both as backups in the
usual sense and as the ``common version'' when invoking
external merge programs.
o The backed up files are stored in a directory
/.unison/backup on each host. (The name of this
directory can be changed by setting the environment
variable UNISONBACKUPDIR.)
o The predicate backup controls which files are actually
backed up: giving the preference 'backup = Path *'
causes backing up of all files.
o Files are added to the backup directory whenever unison
updates its archive. This means that
# When unison reconstructs its archive from scratch
(e.g., because of an upgrade, or because the
archive files have been manually deleted), all
files will be backed up.
# Otherwise, each file will be backed up the first
time unison propagates an update for it.
o The preference backupversions controls how many previous
versions of each file are kept. The default is 2 (i.e.,
the last synchronized version plus one backup).
o For backward compatibility, the backups preference is
also still supported, but backup is now preferred.
o It is OK to manually delete files from the backup
directory (or to throw away the directory itself).
Before unison uses any of these files for anything
important, it checks that its fingerprint matches the
one that it expects.
+ Merging:
o Both user interfaces offer a new 'merge' command,
invoked by pressing 'm' (with a changed file selected).
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
experts only. See the ``Archive Files'' section of the manual for
more information.)
* Graphical user-interface:
+ A new command is provided in the Synchronization menu for
switching to a new profile without restarting Unison from
scratch.
+ The GUI also supports one-key shortcuts for commonly used
profiles. If a profile contains a preference of the form 'key
= n', where n is a single digit, then pressing this key will
cause Unison to immediately switch to this profile and begin
synchronization again from scratch. (Any actions that may
have been selected for a set of changes currently being
displayed will be discarded.)
+ Each profile may include a preference 'label = <string>'
giving a descriptive string that described the options
selected in this profile. The string is listed along with the
profile name in the profile selection dialog, and displayed
in the top-right corner of the main Unison window.
* Minor:
+ Fixed a bug that would sometimes cause the 'diff' display to
order the files backwards relative to the main user
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
+ On Unix systems, the graphical version of Unison will check
the DISPLAY variable and, if it is not set, automatically
fall back to the textual user interface.
+ Synchronization paths (path preferences) are now matched
against the ignore preferences. So if a path is both
specified in a path preference and ignored, it will be
skipped.
+ Numerous other bugfixes and small improvements.
Changes since 2.6.1:
* The synchronization of modification times has been disabled for
directories.
* Preference files may now include lines of the form include <name>,
which will cause name.prf to be read at that point.
* The synchronization of permission between Windows and Unix now
works properly.
* A binding CYGWIN=binmode in now added to the environment so that
the Cygwin port of OpenSSH works properly in a non-Cygwin context.
* The servercmd and addversionno preferences can now be used
together: -addversionno appends an appropriate -NNN to the server
command, which is found by using the value of the -servercmd
preference if there is one, or else just unison.
* Both '-pref=val' and '-pref val' are now allowed for boolean
values. (The former can be used to set a preference to false.)
* Lot of small bugs fixed.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
* The log preference is now set to true by default, since the log
file seems useful for most users.
* Several miscellaneous bugfixes (most involving symlinks).
Changes since 2.5.25:
* INCOMPATIBLE CHANGE: Archive format has changed (again).
* Several significant bugs introduced in 2.5.25 have been fixed.
Changes since 2.5.1:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New functionality:
+ Unison now synchronizes file modtimes, user-ids, and
group-ids.
These new features are controlled by a set of new
preferences, all of which are currently false by default.
o When the times preference is set to true, file
modification times are propaged. (Because the
representations of time may not have the same
granularity on both replicas, Unison may not always be
able to make the modtimes precisely equal, but it will
get them as close as the operating systems involved
allow.)
o When the owner preference is set to true, file ownership
information is synchronized.
o When the group preference is set to true, group
information is synchronized.
o When the numericIds preference is set to true, owner and
group information is synchronized numerically. By
default, owner and group numbers are converted to names
on each replica and these names are synchronized. (The
special user id 0 and the special group 0 are never
mapped via user/group names even if this preference is
not set.)
+ Added an integer-valued preference perms that can be used to
control the propagation of permission bits. The value of this
preference is a mask indicating which permission bits should
be synchronized. It is set by default to 0o1777: all bits but
the set-uid and set-gid bits are synchronised (synchronizing
theses latter bits can be a security hazard). If you want to
synchronize all bits, you can set the value of this
preference to -1.
+ Added a log preference (default false), which makes Unison
keep a complete record of the changes it makes to the
replicas. By default, this record is written to a file called
unison.log in the user's home directory (the value of the
HOME environment variable). If you want it someplace else,
set the logfile preference to the full pathname you want
Unison to use.
+ Added an ignorenot preference that maintains a set of
patterns for paths that should definitely not be ignored,
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
+ Removed the trace and silent preferences. They did not seem
very useful, and there were too many preferences for
controlling output in various ways.
+ The text UI now displays just the default command (the one
that will be used if the user just types <return>) instead of
all available commands. Typing ? will print the full list of
possibilities.
+ The function that finds the canonical hostname of the local
host (which is used, for example, in calculating the name of
the archive file used to remember which files have been
synchronized) normally uses the gethostname operating system
call. However, if the environment variable
UNISONLOCALHOSTNAME is set, its value will now be used
instead. This makes it easier to use Unison in situations
where a machine's name changes frequently (e.g., because it
is a laptop and gets moved around a lot).
+ File owner and group are now displayed in the ``detail
window'' at the bottom of the screen, when unison is
configured to synchronize them.
* For hackers:
+ Updated to Jacques Garrigue's new version of lablgtk, which
means we can throw away our local patched version.
If you're compiling the GTK version of unison from sources,
you'll need to update your copy of lablgtk to the developers
release, available from
http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
(Warning: installing lablgtk under Windows is currently a bit
challenging.)
+ The TODO.txt file (in the source distribution) has been
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
linux). We will not be distributing binaries for these
architectures ourselves (at least for a while) but if someone
would like to make them available, we'll be glad to provide a
link to them.
* Bug fixes:
+ Pattern matching (e.g. for ignore) is now case-insensitive
when Unison is in case-insensitive mode (i.e., when one of
the replicas is on a windows machine).
+ Some people had trouble with mysterious failures during
propagation of updates, where files would be falsely reported
as having changed during synchronization. This should be
fixed.
+ Numerous smaller fixes.
Changes since 2.4.1:
* Added a number of 'sorting modes' for the user interface. By
default, conflicting changes are displayed at the top, and the
rest of the entries are sorted in alphabetical order. This
behavior can be changed in the following ways:
+ Setting the sortnewfirst preference to true causes newly
created files to be displayed before changed files.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
a path descriptor in the same format as 'ignore' and 'follow'
patterns, causes paths matching this pattern to be displayed
first.
+ Similarly, giving the preference sortlast=<pattern> causes
paths matching this pattern to be displayed last.
The sorting preferences are described in more detail in the user
manual. The sortnewfirst and sortbysize flags can also be accessed
from the 'Sort' menu in the grpahical user interface.
* Added two new preferences that can be used to change unison's
fundamental behavior to make it more like a mirroring tool instead
of a synchronizer.
+ Giving the preference prefer with argument <root> (by adding
-prefer <root> to the command line or prefer=<root>) to your
profile) means that, if there is a conflict, the contents of
<root> should be propagated to the other replica (with no
questions asked). Non-conflicting changes are treated as
usual.
+ Giving the preference force with argument <root> will make
unison resolve all differences in favor of the given root,
even if it was the other replica that was changed.
These options should be used with care! (More information is
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
differently when the user has overridded Unison's default
recommendation (====> instead of ---->). This matches the
behavior of the graphical interface, which displays such
arrows in a different color.
+ Carriage returns (Control-M's) are ignored at the ends of
lines in profiles, for Windows compatibility.
+ All preferences are now fully documented in the user manual.
Changes since 2.3.12:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* New/improved functionality:
+ A new preference -sortbysize controls the order in which
changes are displayed to the user: when it is set to true,
the smallest changed files are displayed first. (The default
setting is false.)
+ A new preference -sortnewfirst causes newly created files to
be listed before other updates in the user interface.
+ We now allow the ssh protocol to specify a port.
+ Incompatible change: The unison: protocol is deprecated, and
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
values are 1 and 2. (Default is empty, which will make unison
use whatever version of ssh is installed as the default 'ssh'
command.)
+ The situation when the permissions of a file was updated the
same on both side is now handled correctly (we used to report
a spurious conflict)
* Improvements for the Windows version:
+ The fact that filenames are treated case-insensitively under
Windows should now be handled correctly. The exact behavior
is described in the cross-platform section of the manual.
+ It should be possible to synchronize with Windows shares,
e.g., //host/drive/path.
+ Workarounds to the bug in syncing root directories in
Windows. The most difficult thing to fix is an ocaml bug:
Unix.opendir fails on c: in some versions of Windows.
* Improvements to the GTK user interface (the Tk interface is no
longer being maintained):
+ The UI now displays actions differently (in blue) when they
have been explicitly changed by the user from Unison's
default recommendation.
+ More colorful appearance.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
to install the headers and libraries (which are not installed by
default).
* Added a new -addversionno switch, which causes unison to use
unison-<currentversionnumber> instead of just unison as the remote
server command. This allows multiple versions of unison to coexist
conveniently on the same server: whichever version is run on the
client, the same version will be selected on the server.
Changes since 1.219:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version fixes several annoying bugs, including:
+ Some cases where propagation of file permissions was not
working.
+ umask is now ignored when creating directories
+ directories are create writable, so that a read-only
directory and its contents can be propagated.
+ Handling of warnings generated by the server.
+ Synchronizing a path whose parent is not a directory on both
sides is now flagged as erroneous.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
files.
* The semantics of Path and Name regular expressions now correspond
better.
* Some minor improvements to the text UI (e.g. a command for going
back to previous items)
* The organization of the export directory has changed --- should be
easier to find / download things now.
Changes since 1.200:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* This version has not been tested extensively on Windows.
* Major internal changes designed to make unison safer to run at the
same time as the replicas are being changed by the user.
* Internal performance improvements.
Changes since 1.190:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* A number of internal functions have been changed to reduce the
amount of memory allocation, especially during the first
synchronization. This should help power users with very big
replicas.
* Reimplementation of low-level remote procedure call stuff, in
preparation for adding rsync-like smart file transfer in a later
release.
* Miscellaneous bug fixes.
Changes since 1.180:
* INCOMPATIBLE CHANGE: Archive format has changed. Make sure you
synchronize your replicas before upgrading, to avoid spurious
conflicts. The first sync after upgrading will be slow.
* Fixed some small bugs in the interpretation of ignore patterns.
* Fixed some problems that were preventing the Windows version from
working correctly when click-started.
* Fixes to treatment of file permissions under Windows, which were
causing spurious reports of different permissions when
synchronizing between windows and unix systems.
* Fixed one more non-tail-recursive list processing function, which
was causing stack overflows when synchronizing very large
replicas.
Changes since 1.169:
* The text user interface now provides commands for ignoring files.
* We found and fixed some more non-tail-recursive list processing
functions. Some power users have reported success with very large
replicas.
* INCOMPATIBLE CHANGE: Files ending in .tmp are no longer ignored
automatically. If you want to ignore such files, put an
appropriate ignore pattern in your profile.
share/SpamAssassin/easy_ham_2/01380.e3fad5af747d3a110008f94a046bf31b view on Meta::CPAN
matches exactly the path <path>.
Standard ``globbing'' conventions can be used in <name> and
<path>:
+ a ? matches any single character except /
+ a * matches any sequence of characters not including /
+ [xyz] matches any character from the set {x, y, z }
+ {a,bb,ccc} matches any one of a, bb, or ccc.
See the user manual for some examples.
Changes since 1.146:
* Some users were reporting stack overflows when synchronizing huge
directories. We found and fixed some non-tail-recursive list
processing functions, which we hope will solve the problem. Please
give it a try and let us know.
* Major additions to the documentation.
Changes since 1.142:
* Major internal tidying and many small bugfixes.
* Major additions to the user manual.
* Unison can now be started with no arguments -- it will prompt
automatically for the name of a profile file containing the roots
to be synchronized. This makes it possible to start the graphical
UI from a desktop icon.
* Fixed a small bug where the text UI on NT was raising a 'no such
signal' exception.
Changes since 1.139:
* The precompiled windows binary in the last release was compiled
with an old OCaml compiler, causing propagation of permissions not
to work (and perhaps leading to some other strange behaviors we've
heard reports about). This has been corrected. If you're using
precompiled binaries on Windows, please upgrade.
( run in 1.877 second using v1.01-cache-2.11-cpan-0d8aa00de5b )