Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity

December 2, 2014

Emacs and Org Mode:…

Filed under: Editor — Patrick Durusau @ 10:58 am

Emacs and Org Mode: What People are Saying by Nick Higham.

From the post:

For a couple of years I’ve been collecting tweets about Emacs and Org mode. With the Twitter app’s new ability to provide code to embed tweets I decided to create a post listing the collection. If you are not an existing user of Emacs or Org mode these tweets should give you a feel for whether you might want to explore further. If you are already a convert then many of the sentiments expressed here will be familiar. Note that the links and hashtags below are clickable. (Like all of this Blog, this post was written in Org mode.)

Of interest to non-Emacs users.

I hear but don’t understand the objections to markup (XML/SGML) so the need to create plain text is lost on me.

Emacs as an editor is different question. I am currently using Emacs to edit approximately 4800 pages of OCR output. Its regex features are essential.

But if you are going to create plain text, Emacs is the way to go.

I first saw this in a tweet by Christophe Lalanne.

Announcing Apache Hadoop 2.6.0

Filed under: Hadoop,MapReduce — Patrick Durusau @ 10:32 am

Announcing Apache Hadoop 2.6.0 by Arun Murthy.

From the post:

It gives me great pleasure to announce that the Apache Hadoop community has released Apache Hadoop 2.6.0 !

In particular, we are excited about three major pieces in this release: heterogeneous storage in HDFS with SSD & Memory tiers, support for long-running services in YARN and rolling upgrades—the ability to upgrade your cluster software and restart upgraded nodes without taking the cluster down or losing work in progress. With YARN as its architectural center, Hadoop continues to attract new engines to run within the data platform, as organizations want to efficiently store their data in a single repository and interact with it simultaneously in different ways.

Many thanks to all of the contributors and committers who collaborated on this version and resolved a total of nearly 900 JIRA issues across four areas:

  • Hadoop Common: 231 JIRAs resolved
  • Hadoop HDFS: 305 JIRAs resolved
  • Hadoop YARN: 290 JIRAs resolved
  • Hadoop MapReduce: 70 JIRAs resolved

Highlights for Apache Hadoop 2.6.0

Here are some details about the most important features. For the complete list of features, improvements and bug fixes, see the sidebar and the release notes.

The post includes a nifty PNG file that lists the major issues with what I think were intended to be links to JIRA issues. Unfortunately the links point to the PNG file. I suspect a missing map directive. I posted a comment on same and hopefully it will be fixed soon.

In the meantime, enjoy the new release of Hadoop! (And thank the many contributors to the project this holiday season!)

BrightstarDB 1.8.0 Released

Filed under: .Net,BrightstarDB — Patrick Durusau @ 9:30 am

BrightstarDB 1.8.0 Released

From the post:

I am pleased to announce release 1.8.0 of BrightstarDB is now available from all the usual places:

This update fixes some bugs and addresses performance issues reported by the community. Thanks to all those who took the trouble to report and to provide patches / suggested workarounds.

Key new features in this release are:

  • EntityFramework now supports GUID properties.
  • EntityFramework now has an [Ignore] attribute which can be used to decorate interface properties that are not to be implemented by the generated EF class.
  • Added a constructor option to generated EF entity classes that allows property initialisation in the constructor.
  • Added some basic logging support for Android and iOS PCL builds.
  • It is now possible to iterate the distinct predicates of a data object using the GetPropertyTypes method.

Significant fixes in this release are:

  • Fix for Polaris crash when attempting to process a query containing a syntax error.
  • Fixed NuGet packaging to remove an obsolete reference to Windows Phone 8. WP8 (and 8.1) are still both supported but as PCL profiles.
  • Performance fix for full cache scenarios.

The store format remains compatible with previous releases. This is a recommended update for all BrighstarDB users.

Docker Image Now Available

With this release we are now also providing a Docker image to run a BrightstarDB server in a Docker container. This makes it really easy to get a BrightstarDB service up and running on a cloud VM infrastructure such as Azure or AWS. The docker image is available on Docker Hub. For more information please read our notes in the
BrightstarDB/Docker repository on GitHub where you will also find the Dockerfile and configuration files used to build the image.

If you don’t know BrightstarDB:

Why BrightstarDB?

BrightstarDB is a unique and powerful data storage technology for the .NET platform. It combines flexibility, scalability and performance while allowing applications to be created using tools developers are familiar with.

An Associative Model

All databases adopt some fundamental world view about how data is stored. Relational databases use tables, and document stores use documents. BrightstarDB has adopted a very flexible, associative data model based on the W3C RDF data model. (From: Why BrightstarDB?)

If you still don’t recognize BrightstarDB, perhaps the names Kal Ahmed and Graham Moore will ring a bell.

Still nothing?

I guess you will just have to read the documentation and play with BrightstarDB!

Enjoy!

December 1, 2014

New NSA Drone!

Filed under: Cryptography,NSA — Patrick Durusau @ 4:58 pm

I don’t pay much attention to the musical chairs game in Washington so I wasn’t aware that the NSA acquired a new drone last April. Code name: Adm. Michael Rogers.

Just in case you need a photograph for identification purposes:

Michael Rogers

Doesn’t look like he gets outside very often does it? Being a cryptographer, what else did you expect?

But that’s makes Rogers a dangerous leader of the NSA.

Consider the latest testimony by Rogers to Congress:

Certain nations are regularly performing electronic “reconnaissance,” Rogers warned, in an effort to be well placed within utility systems in the event that the networks relied on by chemical facilities, water treatment plants and other critical infrastructure components are ordered to be taken offline by a foreign government.

All of that leads me to believe it is only a matter of when, not if, we are going to see something dramatic,” the NSA chief said.

Leading figures within the American intelligence community and Congress have long warned of potentially catastrophic repercussions if such networks should happen to be penetrated and pulverized by foreign actors with malicious intent, but Rogers’ remarks this week are among the most dire ever from not just individual well placed within the administration, but a person arguably most qualified to testify as much. (From China & others can cripple US power grid, NSA admits for the first time)

Well, except that water treatment plants and chemical facilities aren’t part of any seamless network. Minor detail I know but just because some contractor wants to protect us from a non-existent threat with cost-plus contracting, isn’t a reason to credit their reports.

If the Admiral wants to obsess about something, how about the regional power stations that are too big to be housed and are subject to attack with one person anti-tank weapons that could take such stations out for months. (Each is a custom build so there aren’t spare parts if oil cooling goes out and critical parts melt into slag.) No Internet or hacking required. And major parts of the United States could go dark for the entire time needed for repairs. Does that sound like a potential threat?

Compare that to the Admiral’s fantasy about cyber defense:

The U.S. Cyber Command has three primary missions, Adm. Rogers said. Along with defending DOD networks, the Cyber Command is “generating the cyber mission force, the men and women who are going to be addressing the department’s cyber needs, from the defensive to the offensive.” Lastly, Rogers said he is preparing the emerging DOD cyber force to defend U.S. critical infrastructure.

DOD’s cyber force has been given the responsibility to defend, for example, critical power and other utility, telecommunications and transportation networks—which he said are vulnerable to attacks from China and “one or two other” countries. He said a major attack was likely in the next decade.

The cyber chief estimated that DOD is about halfway toward its goal of organizing a cyber capability to defend U.S. networks. (From: NSA chief details ‘real’ threats to US networks, infrastructure)

Quick points to remember:

The civilian population comes dead last, assuming a threat exists at all.

Attack is “likely” within the next decade. (Courteous of our adversaries to wait for us to tool up to repel the attack.)

The DOD is halfway towards a cyber capacity to defend non-existent U.S. water, chemical plants, etc., networks?

The advantage of being halfway to defend networks that don’t exist isn’t clear. But, the DOD is also said to be halfway to being subject to auditing. Maybe those programs are on the same track?

All news outlets should be calling BS on testimony such as that by Adm. Rogers. Creating disinformation about security issues distorts the policy process and makes for fat contractors and a poorly served civilian population.

Not to mention making security issue topic maps more laborious to construct by re-weeding out false threats such as those being pandered by Adm. Rogers.

« Newer Posts

Powered by WordPress