Fuchsia OS enters testing phase on Google employees

Google company made changes, indicating the transition of the operating system Fuchsia to the stage of final internal testing "dog food“, implying the use of the product in the daily activities of employees, before bringing it to ordinary users. At this stage, the product is in a condition that has already passed basic testing by dedicated quality assessment teams. Before delivering the product to the general public, they additionally conduct a final check on their employees who are not involved in the development.

In the client to the update delivery management system Omaha, which tests Chrome and Chrome OS releases, added the fuchsia.cobalt.SystemDataUpdater component and provided instructions for transferring devices to the new “dogfood-release” branch using the utility fx (similar to adb for Fuchsia). Into a continuous integration system added bootloader builds for the dogfood branch, and to the Fuchsia platform included separate metrics for evaluating test results.

In the comments to the changes in Fuchsia mentioned two links to deliver updates fuchsia-updates.googleusercontent.com and arm64.dogfood-release.astro.fuchsia.com, in the second link Astro is the smart screen codename Google Nest Hub, which seems to be used by Google employees as a prototype for testing
Fuchsia instead of the stock Cast Platform firmware. The Nest Hub interface is based on the Dragonglass app, which uses the Flutter framework, which is also supported by Fuchsia.

Recall that within the framework of the Fuchsia project, Google is developing a universal operating system that can run on any type of device, from workstations and smartphones to embedded and consumer equipment. The development is based on the experience of creating the Android platform and takes into account the shortcomings in the field of scaling and security.

The system is based on a microkernel Zirconbased on the developments of the project LK, extended for use on various classes of devices, including smartphones and personal computers. Zircon extends LK with support for processes and shared libraries, user level, object handling system, and capability-based security model. Drivers implemented in the form of dynamic libraries running in user space, loaded by the devhost process and managed by the device manager (devmg, Device Manager).

For Fuchsia prepared by own GUI, written in Dart using the Flutter framework. The project also develops the framework for building user interfaces Peridot, the Fargo package manager, the standard library libc, rendering system Escher, Vulkan driver Magma, composite manager Scenic, MinFS, MemFS, ThinFS (FAT in Go) and Blobfs file systems, and the FVM partition manager. For application development is provided support for C / C ++, Dart, Rust is also allowed in system components, in the Go network stack, and in the Python language build system.

Fuchsia OS enters testing phase on Google employees

Loading in progress used system manager including
appmgr to create an initial software environment, sysmgr to create a boot environment, and basemgr to set up a user environment and organize login. For Linux compatibility in Fuchsia offered Machina library, which allows you to run Linux programs in a special isolated virtual machine, formed using a hypervisor based on the Zircon kernel and Virtio specifications, similar to how is organized running Linux applications in Chrome OS.

An advanced system is offered for security sandbox-isolation, in which new processes do not have access to kernel objects, cannot allocate memory, and cannot run code, and a system is used to access resources namespacesA that defines the available permissions. Platform provides a framework for creating components, which are programs that run in their sandbox that can interact with other components via IPC.

Source: opennet.ru

Add a comment