The Fuchsia OS is entering the testing phase with Google employees.

Google Inc. made changes, indicating the transition of the operating system Fuchsia to the stage of final internal testing 'dogfooding', implying the use of the product in the daily activities of employees before it is released to the general users. At this stage, the product holds is in a state that has already undergone primary testing by special quality assessment teams. Before delivering the product to the masses, a final check is conducted on employees who are not involved in development.

In the client for the update management system Omaha, where Chrome and Chrome OS releases are tested, implemented the fuchsia.cobalt.SystemDataUpdater component and a guideline for transitioning devices to the new 'dogfood-release' branch using the fx utility (analogous to adb for Fuchsia). In the continuous integration system added for building the bootloader for the dogfood branch, and in the Fuchsia platform includes specific metrics to evaluate the testing results.

In the comments on the changes in Fuchsia include there are two links for delivering updates: fuchsia-updates.googleusercontent.com and arm64.dogfood-release.astro.fuchsia.com, where Astro is the codename for the smart display Google Nest Hub, which apparently is used by Google employees as a prototype for testing
Fuchsia instead of the default Cast Platform firmware. The Nest Hub interface is based on the Dragonglass application, which uses the Flutter framework, also supported in Fuchsia.

Recall that within the Fuchsia project, Google is developing a universal operating system capable of running on any type of device, from workstations and smartphones to embedded and consumer electronics. The development takes into account the experience gained from the creation of the Android platform and addresses shortcomings in scaling and security.

The system is based on a microkernel Zircon, based on the project's work 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, an object handling system, and a security model based on capabilities. Drivers are implemented as dynamic libraries running in user space, loaded by the devhost process and managed by the device manager (devmg, Device Manager).

For Fuchsia prepared own graphical interface, written in Dart using the Flutter framework. The project also develops the Peridot user interface framework, the Fargo package manager, and the standard library libc, rendering system Escher, Vulkan driver Magma, composite manager Scenic, file systems MinFS, MemFS, ThinFS (FAT in Go) and Blobfs, as well as the FVM partition manager. To develop applications support for languages C/C++, Dart is provided, while Rust is allowed in system components, Go in the network stack, and Python in the build system. During booting

system manager, which includes a layer appmgr to create the initial application environment, sysmgr for forming the boot environment, and basemgr to configure the user environment and manage system login. For compatibility with Linux in Fuchsia
the Machina library, which allows running Linux programs in a special isolated virtual machine formed with a hypervisor based on the Zircon kernel and Virtio specifications, similar to how it is recommended to Linux applications are organized to run on Chrome OS. To ensure security, an advanced

sandbox isolation , where new processes have no access to kernel objects, cannot allocate memory, and cannot execute code, is offered, and anamespace system , determining available permissions is used for resource access. The platformis a framework for creating components that are programs running in their own sandbox, able to interact with other components via IPC. provides Google has made changes indicating that the operating system

Source: opennet.ru