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)
BLAZE-INIT(1) BlazeBlogger Documentation BLAZE-INIT(1)NAME
blaze-init - creates or recovers a BlazeBlogger repository
SYNOPSIS
blaze-init [-fqV] [-b directory]
blaze-init -h|-v
DESCRIPTION
blaze-init either creates a fresh new BlazeBlogger repository, or recovers an existing one in case it is corrupted. Optionally, it can also
revert a configuration and default templates to their original state, leaving all user data (that is, both blog posts and pages) intact.
OPTIONS -b directory, --blogdir directory
Allows you to specify a directory in which the BlazeBlogger repository is to be blaced. The default option is a current working
directory.
-f, --force
Reverts existing configuration, theme, and language files to their initial state. By default, these files are kept intact.
-q, --quiet
Disables displaying of unnecessary messages.
-V, --verbose
Enables displaying of all messages, including a list of created files.
-h, --help
Displays usage information and exits.
-v, --version
Displays version information and exits.
EXAMPLE USAGE
Create a new blog in a current directory:
~]$ blaze-init
Created a BlazeBlogger repository in .blaze.
Create a new blog in ~/public_html:
~]$ blaze-init -b ~/public_html
Created a BlazeBlogger repository in /home/joe/public_html/.blaze.
Revert a configuration file and default templates to their initial state:
~]$ blaze-init -f
Recovered a BlazeBlogger repository in .blaze.
Or if you want to see what files have been reverted:
~]$ blaze-init -fV
Created .blaze/config
Created .blaze/theme/default.html
Created .blaze/style/default.css
Created .blaze/lang/en_US
Recovered a BlazeBlogger repository in .blaze.
SEE ALSO blaze-config(1), blaze-add(1)BUGS
To report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit
the discussion group at <http://groups.google.com/group/blazeblogger/>.
COPYRIGHT
Copyright (C) 2008-2011 Jaromir Hradilek
This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Version 1.2.0 2012-03-05 BLAZE-INIT(1)
