The Evolution of the Cloud Revolution ? Part 1 and 2
by Joel Campbell and Amy Zeller Directions Magazine Technology Maturation Created the Cloud When the computing age took off in the 1960s, powerful mainframe computers ran bulk data processes inside large organizations. At that same time, several companies realized they could take advantage of these large-scale systems by selling chunks of processing time to smaller [...]
vincent
11-14-2008 09:11 AM
An industry colleague mentioned to me over the Summer that they had attended a “Cloud Computing” talk where it was mentioned that cloud computing would overtake Complex Event Processing. I didn’t get a good response as to what “overtake” meant in this context - that... (0 Replies)
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
LINK
Open Sources: Voices from the Open Source Revolution
http://www.oreilly.com/catalog/opensources/book/kirkmck.html
Twenty years of Berkeley Unix (AT&T)
From: AT&T
By: Marshall Kirk McKusick
Early History, Early distribution, VAX Unix, DARPA Support, BSD, LAW Suit Etc.
A Complete... (0 Replies)
evolution(1) User Commands evolution(1)NAME
evolution - A personal and workgroup information management solution. An integration of mailer, calendar and addressbook clients. Sun
Microsystems Edition, Version 2.24
SYNOPSIS
evolution [--component=name] [--debug=filename] [--disable-eplugin] [--disable-preview] [--force-shutdown] [--help] [--offline] [--online]
[--usage]
DESCRIPTION
Evolution integrates email, calendar, contacts, and task list management in one application. Evolution provides full support for several
data exchange and communication standards, such as IMAP, POP, SMTP, LDAP, iCalendar, and vCard. Evolution enables tight integration with
Sun ONE Messaging and Calendar Servers and other messaging systems.
OPTIONS
The following options are supported:
-c, --component=name Start Evolution activating the specified component.
--debug=filename Send the debugging output of all components to a file specified by filename. filename is a path to a file. For
example, /tmp/Evolution is a valid value for filename.
--disable-eplugin Disable loading of any plugins.
--disable-preview Disable preview pane of Mail, Contacts and Tasks.
--force-shutdown Forcibly shut down all Evolution components.
-?, --help Display help text.
--offline Start in offline mode.
--online Start in online mode.
--usage Display brief usage text.
gnome-std-options Standard options available for use with most GNOME applications. See gnome-std-options(5) for more information.
EXAMPLES
Example 1: To start Evolution activating the Calendar component
example% evolution -c calendar
EXIT STATUS
The following exit values are returned:
0 Application exited successfully
1 Application exited with failure
FILES
The following files are used by this application:
/usr/bin/evolution Executable script for Evolution application
$HOME/.evolution Directory with per-user configuration files and local storage for Evolution
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWevolution |
+-----------------------------+-----------------------------+
|Interface stability |Volatile |
+-----------------------------+-----------------------------+
SEE ALSO evolution-exchange-setup(1), libebook-1.2(3), libecal-1.2(3), attributes(5), gnome-std-options(5)NOTES
Ever since the upgrade Evolution from 1.4 to 2.x, this product includes source code for the Berkeley Database a product of Oracle Corpora-
tion. Your use of the Berkeley Database software separately from Evolution or authorized derivatives thereof is subject to additional
licensing conditions.
Per-user configuration files and local storage in Evolution 2.x are stored in $HOME/.evolution directory as opposed to $HOME/evolution
directory in Evolution 1.4. If the user had Evolution 1.4 installed on the system before, they are able to upgrade to Evolution 2.8 without
losing configuration and local data. When run for the first time, Evolution 2.x will automatically check for and import all the old config-
uration and local data owned by Evolution 1.4, and convert them to the format readable by Evolution 2.x. Users are also allowed to choose
between preserving the $HOME/evolution directory or not. If users choose to preserve configuration and local data for Evolution 1.4, they
will have to manage Evolution 1.4 and Evolution 2.8 configuration and data separately, after the one-time migration. No automatic syncing
is available for ensuring that changes made to Evolution 2.x are ported to Evolution 1.4, or vice versa.
The addressbook database formats of Evolution 2.x and Evolution 1.4 are different due to the use of different versions of Berkeley DB in
the backend. User cannot simply copy the database file from Evolution 1.4 to Evolution 2.8 in order to do the porting of addressbook.
Written by Jeff Cai, Sun Microsystems Inc., 2008.
SunOS 5.11 28 Jul 2008 evolution(1)
