Bay/boot/box

From eg

This page describes a crash course in three of the infra trades - for why trades are introduced in three-folds, see synergetics and instructional capital.

Anyone who buys a "computer" or "term:operating system" without first considering how they'll use it is making a serious mistake. The bay trade approach to workbay and work-space-tribe support is to (more or less) design the entire workbay first with all peripherals,

This very complete description of a 2003 offering of the "green bay box" prototype indicates exactly how detailed the descriptions must be, and how specific to the application. The extensive lobbying effort by Civic Efficiency Group dealing with boot image control issues in municipal government provides some useful templates for proposing solutions to larger problems. A truly ergonomic telework environment would fit the green bay box within a green apartment, green office, and yield a favourable total cost of ownership analysis.

The actual descriptions, e.g. of i386 boxes, is no less detailed. The 2004 description provides a template for such descriptions. A boot image as described exactly and in context by infra in 2004 can be delivered from a NOC via DVD or CD, or increasingly on a USB boot.

[edit] Planned extinction

In the long run, the bay/boot/box distinction may become unnecessary. The infra vision proposes to reduce it to slot and a role key card compatible with built-in devices, as in a home theater. This approach would rely exclusively on key continuity management and be compatible with Bitfrost and the OLPC, treating at least Linux boots for OLPC boxes as utterly interchangeable and generic. The key trade concerns in this architecture are difficult and won't be addressed before 2010.

[edit] Relation to other trades

The key trade may also distribute USB keys or keycards or exploit biometric devices to authorize access to a particular bay. Related site security and building security problems are generally undertaken by the ark trade/key trade.

The feed/tag/bit distinctions were proposed to keep data type concerns separate and deal with them from a network manager point of view. Coders implement this via verb/noun/type choices.

[edit] Scope

The the original introduction provides more detail on the relationship with ark/site/key and others.