Breeze::OS Kodiak©® is our Linux distribution for x86-based systems, see gallery.
it includes:
The file system used in Breeze::OS©® is a journaling file system (reiserfs). Access to files is administered by the built-in search-engine. A newly added search partition is divided
into the following sections:
Ferret
Where downloaded files are indexed, and stored
when
specified.
Config
Where indices for all system configuration
files are
stored.
System
Where indices for all systems files are stored.
Share
Where indices for packages are stored, and
indexed.
User
Where all user files are indexed, and stored.
Breeze::OS MOTD(s)©® allow you to display company or deparmental info pages to your users. The security manager responsible for content management is the one responsible for managing and updating MOTD(s), The Breeze::OS itself, has by default, system and user interface information as MOTD(s). These system MOTD(s) can be replaced by the security manager.
TheBreeze::OS©® indexing engine uses a /etc/fstab- like file/etc/ifstab. It uses the afore-mentioned configuration file, whenever an indexing of the entire system is desired. The configuration file specifies all the paths that are to be indexed, who the owners of these paths are, and how these paths are supposed to be indexed, (what type of files should be indexed, which ones should be ignored, and if inflating zip/gzip archives should be done before indexing).
When saving a file, the system automatically indexes the newly saved file, and may do a content analysis, with the NLP engine to try to understand the content of the file. Content search is made possible, because of that analysis. See some preliminary results with the following files.
Breeze::OS©® provides several ways of retrieving files:
Breeze::OS©®is straightforward in its ability to allow remote connections. The system relies and is anchored on a search-engine mimicking an Internet search-engine accepting search queries, and protects these connections with our SALT protocol©®.
You can turn-on remote connections by changing your remote connection preferences with the Connections manager. In order to be able to establish a remote connection, you simply log into another machine, which could be your laptop, also running Breeze::OS©®; you then access the login UI-page to access your home computer through your home computer'sBreeze::OS address and port number 8012©®. The connection is established, as long as your home computer's host and domain name can be resolved (dynamic DNS service), as for a real internet website. You then simply issues search request for files as if you were working on your home computer.
Connecting to other systems from your machine is accomplished as above; but you must have an account on the machine you wish to access. The security manager of the remote machine must have provided you with an account with password and optional pass-phrase. You must then supply that information through the loginUI-page to access the remote machine.
The hardware requirements for such a Thin::Client©®server, are obvioulsy more than for the desktop version. The preferred platforms will be, either an Intel Pentium-4, equivalent Athlon, or a 64-bit server, with at least 1G of memory; and the disk space required to store hundreds of gigabytes of files. To allow Thin::Client©® terminals to run applications on the server itself, a faster or multi-processor server will be required, preferably a multi-processor server.
Tsert::Ferret©® willl allow users, whose companies have such a server running, to schedule a daily ferreting run (information retrieval task) on the repository. Tsert::Ferret©® will then produce a content analysis report which contains paragraphs (blurbs) of text, extracted from the returned files, which seem to talk about what the user specified in their ferreting query.
Another future way to remotely connect is through the Tsert::Collab©® component. Tsert::Collab gives the user the ability to setup a collaboration session by sharing a session-id with other users. Once a connection is established with another user, you can then collaborate on an HTML page displayed in an HTML editing window. Out-of-Band messages in the Tsert::Collab©® component arrive as Breeze::OS reminders.
The component manager is used to configure your desktop according to the type of applications you wish to use. Every type of application is listed, and the user selects their application of choice, for each type of component (e.g. office-suite, word-processor, email-client, instant-messenger, personal information manager, music player, etc.) The applications selected in the components manager are displayed in the toolbar, found both in the launcher and the Breeze::OS UI pages.
Access to other files, (system, package or ferreted files), is allowed only if the user making the request has access to the specified files. Content information, see NLP engine.
Subsequent releases of our operating system will use XML, as the document format for all system configuration files, e.g. fstab. All configuration files, such as the files found under the /etc folder will be translated into our XML DTD, for system files.
A fully-integrated developer version of Breeze::OS©®will be released, which incorporates our ITE, updated with Tsert UI pages, development life-cycle and process. All of our development tools will be provided, as part of that release. This version will be able to serve a small team of developers (between 25 and 100 users).
In the future, we will allow the user of our operating system, the ability to automatically upload their document files for translation, through our translation service.
In the future, we will allow the user of our operating system, the ability to automatically upload their source code files for testing, through our software quality assurance service.