Few social powers exceed that of permutation. Once a catchy phrase enters common parlance, endless variants soon permute into use. This happened with “Kilroy was here” in World War II, and it's happening now with “All your base are belong to us”. Here's what, other than base, that are now belong to us (or whomever):
Data (and biz plans): www.theregister.co.uk/content/4/18002.html
Data model: discuss.2020hindsight.org/manila/datamodel
Al Qaeda: www.rushmagazine.com
And that's just in the first two pages of a Google search: 1-20 out of 31,600 results.
—Doc Searls (with thanks for the discovery to Don Marti)
What began as a simple move to reduce the workload of the GNU CVS maintainers has turned into an ambitious project to create a complete development hosting facility. In October 2001, the GNU Project announced a plan to rewrite completely the SourceForge software. This rewrite will address several key technical and practical issues.
SourceForge is an integrated collaborative development environment. It presents a web interface as a portal to CVS, FTP and e-mail services. The original SourceForge server, SourceForge.net, currently hosts more than 30,000 projects and 300,000 users.
The GNU Project has been running a modified version of the SourceForge software at savannah.gnu.org since late in the year 2000. Savannah was set up by GNU volunteers to automate and ease the process of GNU project management. Developers of the GNU Project want a service specifically for free software projects, and one independent from the VA Software Corporation.
Concern has been expressed over the centralized nature of the current SourceForge system. Where do the hosted projects go when and if VA Software loses the capital to support SourceForge.net? Where do those 30,000+ projects go if some SSSCA-like bill becomes a reality?
The development team has come up with an obvious answer: decentralization. Projects will be hosted on various sites across a network. All projects will be browseable from any node of the network.
Each machine running the new Savannah system will host any number of read/write and read-only projects. A read/write project will exist locally on that machine. Read-only projects are mirrors of a project hosted elsewhere. In case one of the host machines goes down, locally hosted developers will be able to move to one of the mirrors of their project and set that to be the read/write server for the project. Project definitions are exchanged between distinct servers via an XML-based format. The Savannah service is fault-tolerant. It allows for machines going out of service without loss of data.
The Savannah developers are basing all of the content of the new system on templates. Sections of pages can be pulled from GNU gettext files, based on the language of the reader. gettext is a package for developers, translators and users for creating multilingual applications. This provides for internationalization, a feature sorely lacking in the current SourceForge system.
The developers of the new system have determined to create a system where there is a clearly defined upgrade path between versions of the software. The software will be packaged using Debian's .deb packages, and upgrades will be automated through use of the package system.
The system is based on the GNU phpGroupWare code base. phpGroupWare implements templates needed for internationalization, authentication, database access, an XML-RPC interface and session management. The Savannah team is working closely with the phpGroupWare team to exchange improvements.
Bradley Kuhn, vice president of the Free Software Foundation, wrote:
A collaborative site providing a unified interface for project management is key for free software development. To truly help the cause of software freedom, such sites must be implemented completely with free software. Savannah does this for the GNU Project and will soon do the same for all GPL-compatible free software projects.
Savannah will provide important services to free software developers. It will provide the services of SourceForge.net on a world-spanning network of servers that each speak the individual developer's language. Savannah will have fault tolerance and data recovery. Best of all, the only support that the system needs is for volunteers to provide hosting services and support to their ability. Look for more information on Savannah at savannah.gnu.org.
—Nicholas E. Walker
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide