Chromebooks - Utility and Adaptations

Chromebooks - Utility and Adaptations 

• Availability at Amazon.com
• Ultrathin laptops
• Small form factor
• Limited power consumption
• Lightweight computing
• ARM platforms available 
• Exynos System on a Chip (SoC) in select Chromebooks manufactured by Samsung
• Availability at Amazon.com
• Stocked with Chromium OS
• Chromium OS development
• Web-oriented architecture
• Google Chrome browser
• Google Chrome app store
• Google docs, etc
• Dissimilar to a conventional desktop environment
• Chromium OS is locked into platform
• Alternatives to ChromiumOS?
• With some modifications to the platform, a complete OS installation can be made
• ...in chroot (e.g with Crouton)
• ...in dual boot (e.g with ChrUbuntu)
• ...or "bare metal" 
• Bare metal installation with original BIOS
• 'Developer mode' still enabled 
• OS can be wiped inadvertently
• Legacy BIOS must be accessed for each boot
• Bare metal installation with custom BIOS
• Flashing the Chromebook BIOS - non-trivial
• Hardware modifications then required
• Vendor-specific
• Proceed at own discretion
• Allows for further flexibility in applying the Chromebook as a hardware platform
• Documentation: Installing Bodhi Linux on a Chromebook [Bodhi Linux wiki]
• Option 1: Install for dual boot [Bodhi Linux Wiki]
• Option 2: Bare metal install with upstream  BIOS [Bodhi Linux Wiki]
• Option 3: Bare metal install with custom BIOS
• Not documented at Bodhi Linux Wiki
• Hardware modifications previous to flashing BIOS
• Proceed at own discretion
• Documentation: Coreboot and Chromebook platforms
• Documentation: Compilng Coreboot
• Documentation: flashrom utility
• Documentation: Developer information, Chromebook hardware
• The "Bricked Chromebook" - proceed at own discretion
• Case Study: Samsung Chromebook (Exynos 5250)
• ARM architecture
• Overview, published by  The Chromium Projects
• Hardware teardown, published by iFixIt
• Further resources: Custom firmware images for Chromebooks, pre-compiled
• Proceed at own discretion
• Chrome OS Devices, information at the Arch Linux wiki
• Custom firmware, pre-compiled for Intel Chromebooks
• Custom firmware via Anrold the Bat 
• CARMOS: For ARM architectures
• Camd64OS: For amd64 architectures
• Further wrench-turning may be required.

On Building World - First Pass with FreeBSD 10 amd64/core2

With apology to the reader, though avoiding to develop an outline of a thesis about designs and implementations of operating systems, or either the difficulties before understanding the non-trivial sciences of systems in information processing and communications -- as when the schools are not even teaching from the sciences -- but simply, as a note of some text printed by the FreeBSD 'clang' compiler, this morning, I've noticed some of an error output like the following when building FreeBSD from the releng/10.1 branch., the source code from the FreeBSD repository at GitHub.

/usr/src/secure/lib/libcrypto/amd64/x86_64cpuid.S:17:8: error: register %rdi is only available in 64-bit mode
 movl (%rdi),%eax
       ^~~~

My not being a great aficionado about compiler toolchains, then after that message was produced and the build halted, I discovered the availability of the the stable/10 branch, in the same FreeBSD Project's source code repository. I've now made a local freebsd_10 branch drawing from the same upstream branch, and will proceed to....

make buildworld DESTDIR=/usr/local/myworld

...hoping that perhaps it may build, this time. I'm compiling the FreeBSD source code, with /etc/make.conf containing the following

MACHINE_CPUARCH=amd64
CPUTYPE?=core2
MAKE_SHELL?=sh
CFLAGS+=-msse3
CXXFLAGS+=-msse3
COPTFLAGS?= -O -pipe

Albeit, those were somewhat some arbitrary selections, but it seems to have worked out, so far.

Why would I be enjoining myself to this perhaps seemingly masochistic task, this morning? Initially, I'd thought that it could make a nice result tree for a compiler jail for Poudriere's build automation, such that I might then apply -m null -M /usr/local/myworld for re-using the built objects when applying the poudriere jail command. If the packages could be built against a compiler-optimized core system -- as I'd thought might this morning's make may have produced -- then if that would work out, to apply the compiled world in a process of build automation with Poudriere, then I'd thought, I would consider installing the same /usr/src world onto my host's own root partition, perhaps  then even trying to package it up for installation onto my own amd64 laptop.

Later, I'd thought, I might be able to trust if I've understood how the FreeBSD build process works, well enough that I might then endeavor to build an ARM world -- that, as for applying FreeBSD with BeagleBone Black single-board computers in my own LAN. So far as the LAN design, that much would be trivial, pending the successful installation of a stable, trusted, and uncluttered operating system for the LAN's appliances. I've certainly selected FreeBSD at that -- no more to find interference from NetworkManager about the contents of /etc/resolv.conf -- but, so to speak, the Pokemon ball is just staying welded shut.

Personally, I think that I'm wishing now that the whole build process could be more modularized, in FreeBSD, but not to leverage any kind of an agenda about it. I only wish that I would not have to rebuild the entire FreeBSD local world  if to simply rebuild a component that had failed in the previous build process.

There is one positively simple thing that I've learned, in this morning's effort thus far, namely: That rather than

/bin/fie 2>&1 | tee /some/fum.log

There's a much simpler syntax available with the script shell command:

script /some/fum.log
/bin/fie ...

...such that the script command conveniently receives text printed to both of the standard output and standard error streams, prints the text to the console, then also prints the text to the log file.

So clearly, there are some real reasons for reading the FreeBSD handbook. I believe it's all something to do with knowledge.

Thank you, world wide technical help desk

Not to be too awfully opaque, as a student of an electronics and computing program at a certain institution conventionally denoted as a university, I've been studying some topics of electronics and computing, within and in parallel to, if not furthermore in support to a formal program about the same. In forwarding on my own individual and personal experiences in communications and software applications -- moreover, in focusing on something of a sense of small enterprise, albeit while studying presumably in an audience of corporate enterprise, at the same institution -- personally, I've been trying to focus on "Small data," not reading too much into the "Big data" of any characteristically corporate statistical estimates.

My being of an impression that, in the highly politicized world, I must naturally expect any reader in the general web readership to make a manner of a political character of estimation of my own, simple writing -- that, in and after my own previous experiences with web readership, in online communications -- and though I cannot even possibly estimate the variety of every character of estimation that my own simple writing may be met by, but of course I try to be cautious. As one approach towards being moderately cautious in online communications, I like to not too quickly get around to any specific manner of a point.

This characteristically rambling style that I write with, most often, in online communications -- in  that much -- this "Rambling" is, by all means, a deliberate choice of style. I do hope that my comment, in the following, will not be thought rude in all its plain sense of candor: In a simple sense, if a reader may not wish to "Stick around" until I may get to the point, in any single matter, then I would not wish to trouble the reader to continue with my writing. I do sincerely hope that that may be estimated as fair.

#TLDW ? W as in "Writing", even in writing for a consumerist web, if that's simply how the culture is, these days.

As a writer, I try to take at least a small amount of time before I may even begin to write any single thesis article. Certainly, as a participant in social networking services, in the small-media and whatsoever space-limited forums of any manner of social networking web log or microblog, I may not be able to write out an entire article, in every article I've ever written, if to simply share an observation. Furthermore, in social networking, perhaps I sometimes verge on developing a hasty style of communication, indefinitely. I'm afraid that my writing, sometimes, might be mistaken, ever, in the character of the jib in any single article, but what can I do as a writer, for the ever demanding natures of communications?

Here, sure, I had wanted to simply write an article about Help Desks -- such as to develop a metaphor as of Web as Help Desk, in a sense perhaps seldom heard of, of a range of experiences however far informed of some lengthy personal experiences with networks in free, open communications, namely the Internet Relay Chat (IRC) forums hosted by Freenode. I cannot imagine that most Freenode Help Desk supporters may be inclined to write about the experience, and happily so. Personally, I would not want to verge to far from a plain, capital sense of matters in denoting that some many people working in free/open source software development may have already subscribed, whether formally or informally, to a sort of social contract, such as the Debian Social Contract, It is not to forsake that document, that I personally have taken up a study about FreeBSD, as a component to my studies about electronics and computing, focusing on communications and designs of discrete electronics, with a big heart for all of the mathematics of the same.

FreeBSD, simply, is more truly "Free" to my point of view, contrasted to the GPL.

So, but personally I understand that there's been a veritable social wealth developed in software licensed under terms of the GPL and its numerous variations, including the LGPL and suchforth -- limited in however as to how far that social wealth ever can be practically applied. Today, the Linux kernel itself -- as the kernel of the Android platform -- is already powering the appliances of a large, significant portion of the mobile appliances market, on so many GSM and CDMA radio networks.

Personally, I'd happily leave it to the cellular phone service providers, that those aren't the only digital radio protocols around, in the universe. It's not to threaten their market share, that I observe as so -- AX.25 and so on, golly. Personally, I'm not sure if T-Mobile would even begin to consider the possibilities -- that, beyond the formal, consumer media markets -- beyond the consumer media, rather towards M2M communications, in a context of the "Internet of Things" (IoT) and the conceptual leadership of circuit element designs developed by companies such as Freescale, a division of Motorola. If pressed to a wager, I'd wager that  they -- Motorola -- may know a lot about communications in a digital domain.

Personally, I do sincerely hope that such a simple observation as that may not need to be prefaced with 20 pages of thesis article. Motorola is a company I would personally trust about their content with regards to IoT designs.

Does the reader necessarily trust me, to my observation as such? Should I worry, at that? I understand, there is a concept of Trust, in the world. I think, it is a concept that cannot all be measured in static bits. If the reader may wish to verify my simple statement, in the previous, I'm certain there's a veritable academic wealth of content published about IoT. Personally, I can recall the novelty of something so -- I would say -- odd as a battery-powered IoT bicycle lock. Innovative, somehow? but why would I want to latch my bicycle onto a battery powered device? Is it to  make it seem any more like a classier transport, but I think it is classy enough already? Sure, it'll never be as classy a Goodyear. Myself, I prefer to use non-battery-operated locks. However convenient my car's little electronic lock system might seem, I think there are some things that perhaps don't need to be driven by a microcontroller -- a matter of personal preference in bicycle locks, perhaps?

Here I go rambling, again, hm?  Personally, I've never been good at making succinct, pointed introductions in any media -- especially, if the proverbial rear wheel of my proverbial literary bicycle keeps hopping into a corporate rut, as here today -- the "Hacker rut," if I may denote that so succinctly. It's not anywhere I consider I should either want or need to be, though there's ever at least seemed to be a hint towards anything of a sense of a warmer gravity to things, around free/open source software -- a warmer sense than "Zombie cold," so to speak -- until post-2010. What happened, I don't know, and I'm not one try to to guess.

So, in and among all things under the sun, there's an operating system kernel named FreeBSD.

To the single point of this article? Thank you, world wide technical help desk.

Onto ... Graph Theory in Applications of Ontology

Though with apology to the indeterminate readership, I don't have a convenient bibliography to present about it, offhand, personally I've been studying some concepts in ontology, for a small number of years -- all, in informal study. I've really not ever managed to develop an academic transcript adequate for transfer to any manner of an Ivy League school or anything like. I suppose, personally I'm still trying to understand what academia means, to me, as academia being such that I consider to be a necessary part of life. I would not wish to make any long sort of an anecdote as to denote why I consider that I'm of such a view, perhaps it's a bit of a meta-semantic sidebar anyway, towards the present article.

Presently, I've begun to develop a thesis concept with regards to how ontologies may be applied in a sense of personal or academic knowledge management -- nothing quite so technically aspiring as the Nepomuk ontologies, though I suppose it could "Aim" towards that, at some time, as when there would be any applications to speak of that could utilize Nepomuk's facilities for adding an ontological layer onto personal information management (PIM). Presently, I'm trying to focus more about a concept of concept -- in a manner of a literary sense of concept -- such as may presented meta-semantically in extensions of the SKOS ontology.

Considering an ontology, in a generic sense, as a form of a reference medium, orthogonally, one may endeavor to view an ontology as it being essentially a literary kind of reference medium. However an ontology -- whether in RDF, OWL as extending of RDF, KIF, Common Logic, or other format -- however stored or transmitted in its essential structures, an ontology typically contains a lot of essentially textual information. In a sense of RDF, an ontology may contain textual information in forms of short texts about resources -- texts that are likewise resources, such that may be furthermore reified as resources, within any single RDF graph medium. Perhaps it may ever be recognized as a nice susbset of application media, the set of ontological graphs altogether.

Presently, I would like to denote a simple thesis statement that I've been able to etch out the raw stuff of own knowledge, this evening: In a practical application of ontologies, focusing namely on the Web Ontology Language (OWL), one may define two categories of OWL ontology for practical applications:

• Structural Ontologies, containing definitions of OWL Class, Object Property, Datatype Property, XSD Datatypes, and Annotation Properties for applications
• Instance Ontologies, as applications of structural ontologies, such that would be applied in definition of OWL Indvidual type resources, in extending of structural ontologies.

Though I would not wish to seem excessively proprietary about it, personally I've begun to develop a corresponding thesis about a small set of structural ontologies, such that may be applied in tracing of information conveyed in jouranilsm, and might likewise be of some use for applications perhaps in at least an ad hoc manner of field archaeology. In a trivial sense, it may be decandted to a matter of: Persons, Places, Events and References, in a bibliographical sense. The Events concept might seem to be the pivotal concept, at that -- in however an event may be in any sense singularly defined, as in a  context of any single literary work.

There's a fifth concept that I would like to add to that small list, this evening, if one may endeavor to develop at least an ad hoc sense of structural geneaology. It's a concept that I've yet to find any single ontology for, however -- essentially, orthogonal to an Events ontology, if there may be any single ontology for literary endeavors about constructed objects. I do know of a small few of resources I could revisit online, as to do conduct more research about that concept, perhaps this evening. I'm afraid that it might be a bit of a disorganized list, if I'd try to itemize that set of resources, immediately. It's also a task wholly orthogonal to the thesis topic that I'd hoped I might be able to begin to write down, presently -- and although the latter may be a bit of a vague idea anyway, but it's such that I'd like to continue to whittle about, literally, towards further developing an idea for application of a small set of structural ontologies and instance ontologies in ... in no exacting usage case, as yet.

Personally, I'm not certain of how far a concept of proprietary knowledge may or may not extend into formal academia. Towards my further sense of disdain at that sense of ambiguity, even if I am researching of these topics, informally -- not being a student of any single, formal course about ontology, at present -- I consider that I should certainly try to respect any number of formal academic models, even in my own research and writing -- at least inasmuch as I  might understand such models, candidly.

What, then, do I mean by proprietary knowledge?  In as much of an exacting sense as in which I can try to define what I mean, in that phrase: I mean, any knowledge legally and necessarily protected under terms like with regards to literal intellectual property. Not as if to indulge in writing any lengthy sidebar with regards to any sense of  commercial intelligences or small business, but if I would denote intelligence as a noun, I consider that I should as well denote how it is a noun that I consider has a natural, plural form. At that, though, I think it goes far towards psychology, and personally I'm not well read about that domain of academia.  It would be quite a sidebar to begin, this evening, to define what I may mean to denote by that simple term, in an exacting sense.

So, but in being aware of some concepts of proprietary knowledge, and in avoiding any particularly revolutionarily characteristic sort of views about any concepts of propriety, I know there are things that I know, such that -- for online discourse, and not only -- that I advise myself, implicitly, to not even denote I know. Perhaps it's a bit of an odd thing, but "That's life," as I understand it -- never 110% transparent. I feel that that's such that I should denote, distinctly, before any further discussion of ontologies. Orthogonal to that oblique disclaimer, I know there are things that I don't know, too -- if there may ever be any single count of known things, probably more things in the second category than in the "Immediate knowledge" category. I think it's as well to not be too deterministic about knowledge -- moreover that science, as a human effort, indicates that no person's knowledge is ever absolute and complete.

Perhaps its simply that I wanted to note, this evening, that there is a thesis concept, vaguely "Here," and that I know there's probably more of a bibliography about it, mroe than what I have ever found, as such. Perhaps, either, I'm simply trying to circumscribe an arc around a notable gap with regards to any profound and immediate illustration of a thesis concept, in software, such as may entail an application of any number of concepts in ontology.

In my not being direct, in this article, I'm certainly not trying to avoid mentioning any manner of a pink elephant in the room, with regards to applications of ontologies. Orthogonally, I don't personally happen to follow the logic of the Manning/Snowden/Assange conspiracy, though I have certainly read of it. 

Inasmuch as considering that a study of academia may entail, implicitly, a study of a veritable plethora of knowledge, namely human knowledge --inasmuch as even to present the ultimate, existentially challenging question, What is knowledge? -- perhaps, though, what I should be concerned about with a perspective about software, perhaps it  may be more towards a practical question of presentation, How well may knowledge be presented?

Not to cut corners in this informal thesis, I understand that there's a design as for a human-computer interface (HCI) toolkit, the Common Lisp Interface Manager (CLIM). As an HCI toolkit, perhaps the design of CLIM, so far as to CLIM 2, has been focused about graphical displays and keyboard interactions, but certainly that's in keeping with the sort of HCI environment that we may be most familiar with, as sighted computer users at personal computers.

CLIM presents something of a simple, basic, practical model for HCI implementation in graphical display/textual keyboard/on-screen pointer environments. Also, CLIM has some features catered for print-based representation of graphical objects, as towards a sense of print as media.

Personally, candidly,, perhaps I have not always been a great fan of the interface for the CLIM obect model, in Common Lisp. I'm a little put off that it doesn't seem, to me, that it completely utilizes the Metaobject Protocol (MOP), though I know MOP is not an ANSI-standard fare in the Common Lisp Object System (CLOS) anyway. I simply think there must be a more effective way to program interfaces with CLIM, of maybe that's simply too naive of an idea.

As it being an object model however, I'd say CLIM is pretty square.

So, now I'll just jump right to the point of applying CLIM and Franz Allegrograph -- taking a short break from this thesis article, presently

Franz, Inc. publishes a VMDK edition of their semantic information systems platform, AllegroGraph. Presently, the VMDK edition includes AllegroGraph pre-installed in a 64-bit Ubuntu 14.04 OS, the Trusty Tarpaulin edition of the Debian-based Ubuntu GNU/Linux operating system. The VMDK can be installed to a virtual appliance in VirtualBox, or any number of other desktop-based virtualization systems. In a nutshell, it provides a quick start-and-go interface for working with Franz AllegroGraph.

As far as how to configure VirtualBox networking for accessing the VMDK from outside of the VMDK's software space ... that will not be presented with details, in this article. The VirtualBox manual includes the complete details of that. This article will assume that the VirtualBox virtual guest appliance is configured with VirtualBox NAT networking, with a host interface having the IP address 172.16.42.1

Moreover, this article assumes AllegoGraph is configured in agraph.cfg, with at least the following configuration directives:

Hostname 10.0.2.15
Port 10035

Thirdly, this article will assume that the VirtualBox NAT networking is configured for port forwarding in the VirtualBox interface between the virutal host OS and the virtual guest OS, simply to the effect:

172.16.42.1:10035 <=> 10.0.2.15:10035

With such a configuration installed, a developer may apply any of the AllegroGraph clients, in developing on the virutal host OS -- with apology, developing no lengthy side-thesis about software defined networking (SDN), here, or either, about integrated development environment (IDE) platforms applicable for Common Lisp software development. In a practical sense, certainly such configuration properties can be managed via software, but even in so much of automation, it probably would help to understand at least a little bit about TCP/IP networking. Within the virtual host OS, the networking and port forwarding properties can be managed via the VBoxManage shell command. Within the virutal guest OS, as in this example, the configuration properties can be managed via both of the files, /etc/network/interfaces and /home/franz/ag/lib/agraph.cfg

So, with such a configuration installed, there are the AllegroGraph clients, and a bit more of TCP/IP networking. Beyond a context of VirtualBox host-only networking, a framework for SSH port forwarding could be applied, on top of the VirtualBox port forwarding.

Presently, this thesis article will jump, by a certain distance, to develop some concepts about object models. The development of that aspect of this thesis article must naturally entail a presentation about some concepts developed in CLIM. This article will now assume an outline format, towards an overview about CLIM.

CLIM - An Overview

• Interaction
• Menus
• Key bindings
• Modeline
• Presentation
• Presentation types
• Presentation methods
• Device Interface
• CLIM port
• CLX port
• GTK Cairo port
• ...
• HCI structures in CLIM applications
• CLIM Graft and Sheet objects
• CLIM Frame objects
• The application frame class
• ...
• CLIM Pane objects
• The application pane class
• ...
• Objects displayed on a CLIM pane
• Geometric objects via CLIM drawing forms
• Text via CLIM drawing forms
• Presentations
• ...
• CLIM and Common Lisp
• Streams in CLIM
• ...
• CLIM and X.org
• XLib
• CLX
• Adding support for XFree86 shared memory extension 
• TBD
• Input methods
• Integration with window managers
• Integration with desktop environments
• ...
• CLIM and text media
• ...
• ...
• Climacs
• ...
• CLIM and CORBA
• TBD - Thesis not yet developed

Secondly, this article will now develop an outline focusing on Franz AllegroGraph as an RDF information service.

Towards developing a CLIM layer for AllegroGraph - Notes / Outline

• Presentation Types
• Triple Store / DB
• Triple
• subject, predicate, object
• graph
• triple ID
• Resource
• Unique Part Identifier (UPI) strings
• Class
• RDF Schema
• OWL
• Annotation properties
• rdfs:label
• skos:altLabel
• skos:prefLabel
• skos:hiddenLabel
• Graph Display
• Graph 'link' properties
• e.g. SKOS broader / narrower properties
• Graph layout
• Radial graph
• Hyperbolic graph
• Tree graph
• Resources may appear multiple times in a tree graph hierarchy
• Resource aliasing for individual presentation in tree graph
• Graph Management
• Graph Management Actions (Default)
• Open graph service connection (i.e. connect to graph server)
• Create graph DB
• Delete graph DB
• Rename (?) graph DB
• Close graph service connection (i.e. disconnect from graph server)
• Graph Management Panes
• List of "registered" graph DBs
• Registry by way of application of ... something compatible with CORBA object services (TBD) (Persistent naming, etc)
• TBD: Implementing an access control layer onto AllegroGraph triple stores
• Fundamental service interface model
• Implementation as an adapter
• Graph service: AllegroGraph
• Display management: CLIM
• Integration with CORBA
• TBD - more towards providing a triples-graph service for other graph/SPARQL servers in Common Lisp or Java
• Usage Cases
• TBD

Lastly, this article  will endeavor to develop a platform-agnostic view about RDF media and CLIM -- again, presented here in an outline format.

Broader Context: CLIM + Semantic Web (A Generic Model)

• RDF Resources // URI Referencing
• See also: ODM
• Generic  model for collections of RDF tuples
• Concept: tuples-index
• Registration of RDF namespace per triples-index
• Classification of ontologies
• Application: Per-ontology presentation method selection
• Examples // Use Cases
• Presentation methods for SKOS Concept classes
• Presentation methods for RTM Topic classes
• Selection criteria for classification in resource => presentation type assignment
• RDF namespace of resource's RDF URI
• Type of entity (RDS class, OWL class, RDF property, OWL object property, OWL datatype property, OWL annotation property, XSD type)
• Properties defined to entity
• Requires a full-graph search initially
• List of properties may be updated on graph change
• Concern: Concurrency
• RDFS/OWL Classes & CLIM Presentation Types
• RDFS/OWL classes available only in connection to any single tuples-index
• Presentation types may be defined as in association to an individual RDF namespace
• Presentation types may be defined as in association to an individual tuples-index
• Presentation types may be defined in individual source trees
• Such source trees may be referenced as in an index or transformation of the URI of any single ontology namespace (?)
• ? Internal table for registration of presentation types for reference via presentation methods
• Concept: Presentation of tuples
• Classic presentation mode: subject, predicate, object
• Presentation of each of a subject, predicate, object will be affected by presentation method defined for each individual resource referenced in that field of each tuple
• Concept: Presentation of reified tuples
• Append 'button' area for activating presentation layer for reification data
• Project: Object model for SPARQL
• CLIM layer
• Concept: Table view (onto SPARQL)
• per each column
• An RDF/OWL property
• Column displays resource denoted in that property
• A column heading
• per each table
• SPARQL query (as an object)
• "Key" column[s]
• applicable for sorting in table display
• Concept: Graph view (onto SPARQL)
• Concept: Metadata view (onto any single set of specifications/standards/conventions in a context of linked open data )
• Arbitrary
• Usage cases (blue sky?)
• Bibliographical display and editing [application]
• "FOAFpedia" app
• Integration platform (app) for collation of bibliographical information
• Bibliographical information for "Good Jedi"
• Is not LinkedIn
• Is not Encyclopedia Britannica, etc
• Bibliographical information for "Dark side of the moon"
• Is not INTERPOL's single registry or analogous national registries
• Topic maps
• Alternate to "Mind maps"
• Concerns
• Implementation in CLIM
• Integration with file media
• Integration with desktop/mobile computing systems
• Resource graph as a central data service on each platform
• Resource graphs on desktop platforms
• Nepomuk
• TBD
• Resource graphs on mobile platforms
• See also: androjena
• Resource graphs on enterprise server platforms
• (?)
• Service model
• Interface model
• Resource=>application dispatching on Android platform - i.e "Open with..."
• See also: 
• Java Content Repository (JCR) (2.0)
• JSR-283
• Implementations (Java)
• Modeshape
• Apache Jackrabbit
• DOM L3 Load & Save
• Towards a streams model for CORBA
• Integration with web media
• See also
• Vincent, Cristopher R. W3P: A Portable Presentation System for the World-Wide Web
• Presentation: Article
• Presentation: Slides
• HTTP Services - Common Lisp
• CL-HTTP at NTT-Data
• Hunchentoot
• Concept: HTTP as an application-layer service
• OSI seven layer model
• TCP sockets
• Trivial request/response cycle
• Response codes
• HTTP 1.1 - See also
• In Proceedings: The Eighth International  World Wide Web Conference (1999)
• Krishnamurthy et. al. Key Differences between HTTP/1.0 and HTTP/1.1   
• Kaplan and Oldham. Managing TCP Connections under Persistent HTTP
• HTTP proxying
• WebDAV
• Concept: HTTP as a CORBA object service
• Web resource as object
• Accessible via HTTP/HTTPS
• Identified with a request URI
• Related: Request method (GET, POST, etc)
• May require persistent state data for access
• Persistent client identity data (cookies)
• Writable via WebDAV
• CORBA
• ODM

Towards a set of concepts for a separate focus article:

• Prolific mobile computing
• Mobile operating systems utilizing the Linux kernel
• Android platform
• Manufacturer-specific applicaitons
• Firefox OS
• Apple iOS
• BlackBerry
• See also: QNX
• Prolific laptop computing
• Google Chromebook
• Also based on the Linux kernel
• Microsoft Windows laptops
• ...
• Ubuntu laptops
• HP TouchSmart laptops
• FreeBSD desktop distributions
• ????
• Computing in Small Office/Home Office (SOHO)  Environments
• Software Defined Networking (SDN) as scalable online service platform
• Amazon Web Services (AWS)
• OpenShift Origin
• Digital Ocean
• ...
• System on Chip (SoC) platforms and single-board computing platforms
• Texas Instruments AM35xx Sitara SoC
• BeagleBone Black
• Allwin A20 SoC
• Cubieboard 3 (Cubietruck)
• Broadcom BCM2835 SoC
• Raspberry Pi
• Alternate design concept: Computer on module (CoM)
• Juxtaposed to SoC as a design concept
• Commercially, another delivery platform for manufacturer's microcircuit designs
• e.g. Gumstix
• Company profile at Texas Instruments
• See also: Gumstix Gepetto

OOP4SCADA // Thesis Concept (Own Thesis) : SCADA systems for localized monitoring and automation of agricultural infrastructure systems

This  content is licensed to the reader, by the author, under terms of the CC BY-SA 3.0 Unported  content license

Thesis - Overview Concepts

• Agricultural irrigation systems
• Soil kinds
• Root distribution
• Plant (biotic) lifecycle
• Pressurized irrigation systems
• Irrigation flow processes
• Pressurized systems: Filtering
• Pressurized systems: Pressure  monitoring
• Irrigation flow timing (on/off durations)
• Irrigation Systems Power Supplies

Thesis - Naive Theory: Arduino + BBB

• Arduino for agricultural irrigation - flow control & monitoring
• Irrigation
• Motor control
• PWM
• Motor type
• Irrigation flow
• Flow Rate Sensors
• Alarm for underflow /underflow rate at any discrete time
• Overflow: May indicate irrigation line or valve rupture
• Underflow: May indicate irrigation line or valve obstruction
• Monitoring system would have to be preprogrammed for 'acceptable' flow rates over time
• Reporting system may utilize SDN, mobile push
• Time-duration analysis
• Agriculture
• Remote reporting
• What signal proto?
• See also: BBB
• Arduino for solar
• BeagleBone Black (BBB)
• TI AM35XX Sitara MCU
• ARM Cortex architecture
• PRU-ICSS x2 
• I2C
• Microprogramming
• Board Interfaces
• Ethernet
• USB host
• USB client//OTG
• I2C (IO Headers)
• SPI (IO Headers)
• MicroSD
• Board resources
• eMMC
• Pushbuttons
• ...
• BBB enclosures for outdoor applications
• Environmental concern: Operating temperature
• Direct solar energy
• Ambient temperature inside and outside of enclosure
• Environmental concern: Humidity in functional enclosure
• Preciptation types - estimates varying over region and time
• Fog
• Rain
• Snow
• Functional concern: Power supply (solar?)
• Functional concern: Network data transmittal
• BBB & Solar
• See also: Instructables; Arduino; PWM; Electrodynamics (inverter efficiency)
• BBB & RF
• Usage cases
• Remote supervisory reporting, remote mechanical systems control, OOP4SCADA//AGGIE
• Remote systems configuration and update OOP4SCADA//DIST
• Limitations
• Signal band, signal power, and modulation
• Refer to regional guidelines for signal broadcast standards and limitations
• US: FCC
• TxRx Power
• Regional availability of celluar phone towers as limiting factor for M2M hardware applications
• See also
• AX.25
• ...
• Convenient modeling tools for systems design and systems maintenance
• Garden plots / field plots
• Drip systems models
• Parts by manufacturer
• STEP product data interchange
• Control panel
• Alarms
• Flow reporting
• Flow reprogramming
• Shop (maint) panel
• Parts lists
• Invoices

Notes - Bibliography and Reference - Android Platform

Android Apps - Bibliography Databases

• Eratosthenes
• RefMe
• EasyBib
• Pearson Writer app

Android Apps - Writing - Web Logs - Blogger

• Blogger app
• Blogaway app

Android Apps - Writing - Social Networking

• Tweetcaster Pro
• Google+ app
• Facebook app
• Tapatalk app

Android Apps - Writing - Office Documents

• Documents to Go
• Google Docs
• Hancom Office 2004
• AndrOpenOffice

Android Apps - eBooks - eBook Readers

• Adobe Acrobat app
• MoonReader+
• CoolReader
• Kindle app
• Kindle app for Samsung Mobile
• Kobo app
• Nook app

Android Apps - Academic Resources - Content Portals

• OpenStax CNX
• [No off. Mendeley app]
• [No off. ResearchGate app]
• Archivist app
• ACM Digital Library app

Android Apps - Distributed Learning Networks - School Portals

• DeVry app
• UDemy app
• Coursera app
• APUS app

<untitled article>

Overview

9P is a network application protocol [CatV] and a correlated filesystem concept [9P], originally developed in Plan 9 from Bell Labs (Plan 9) – as concerning a correlated concept of "Everything via file streams", seen in Plan 9 [Wikipedia], also in Linux [SysFS] and FreeBSD [devfs] and more specifically, in the original Proc filesystem (procfs) of Plan 9 [procfs].

Implementations of the 9P Filesystem Concept

NinePea is a 9P implementation developed for/around an Arduino application of the AVR ATMega 1280 microcontroller. [NinePea][Arduino Mega]

…

Interfacing 9P for Distributed Object Systems

Though 9P itself is not a CORBA model, yet hypothetically, in selecting any number of functional interfaces developed in 9P implementations, those same functional interfaces may be published onto an appliance network, qs via a CORBA Portable Object Adapter (POA) [CORBA Infrastructure], such as is provided with the ACE ORB (TAO). [TAO POA] {TBD: Towards an introspective methodology for transformation of C functional interfaces into platfom-neutral definitions of primitive types and object classes, onto CORBA IDL. See also: [Metaprogramming]}

Towards an application of {any single {emebedded computing platform} {{constructed} with {resources} sufficient to implement a {networking stack and a corresponding implementation of CORBA GIOP}, such as IIOP [CORBA Infrastructure]}}, a CORBA IDL model of 9P may be applied for a CORBA based appliance control and appliance sensor data logging model — perhaps, reminiscent of the Goofy Giggles application* developed at Indiana University (2007) [Pisupati2007]

…

Works Referenced

[CatV] 9P The Simple Distributed Filesystem from Bell Labs. Available at 9p.cat-v.org

[9P] intro - introduction to the Plan 9 File Protocol, 9P. Available at man.cat-v.org

[Wikipedia] Plan 9 from Bell Labs. Wikipedia. Available at en.wikipedia.org

[SysFS]  {Linux kernel docs onto SysFS}

[devfs] Pritchard, Mike. devfs -- device file system. FreeBSD File Formats Manual. 2012. Available at freebsd.org

[procfs] proc - running processes. Available at man.cat-v.org

[Arduino Mega] Arduino Mega. Available at arduino.cc

[CORBA Infrastructure]

[TAO POA]

[Pisupati2007] Bhanu Pisupati. A Virtual Filesystem Framework to Support Embedded Software Development. Indiana University. 2007. Available at www.cs.indiana.edu

Cross-References - Correlated Resources

[Pisupati2007] is also referenced at the Google Play bookstore

Endnotes

* Thus, the initial keynote that began the author's research, in developing this single web log article.