Resetting the device Transferring data between devices (Ref.https://support.apple.com/en-ca/HT204350) Proper backup and restore functionality Instant connectivity to peripherals like Game controllers, wireless headsets. (i.e Popups when peripherals like Airpods, ear buds, Xbox, etc are brought near the PC) FancyZones (Ref.https://learn.microsoft.com/en-us/windows/powertoys/fancyzones)

In the previous article, we announced the development of Vanilla OS 2.0 to change the base from Ubuntu to Debian. We've documented the changes we've done since that post, and the challenges. The first thing we did was to create a copy of Debian Sid's repositories to make our own modifications and freeze them. We used Aptly to generate a mirror that includes the main and non-free components to guarantee that users have access to proprietary drivers in a single repository. We've thoroughly tested the repositories to make sure that they work properly and was able to handle under heavy load. We also worked on OEM changes in the first setup and the installer. We moved user-related configurations, such as user creation, from the installer to the first setup, to let the user handle user creation. This means that manufacturers won't need to create new credentials for the user anymore. Another important change was to create GNOME sessions dedicated to the installer and the first setup. They are mandated and restricted GNOME environment, preventing the user from exiting the system with unconfigured states. One of the big challenges with Vanilla OS 2.0 was to rebase the system on an OCI image structure with distinst, a choice we made to improve reproducibility and reliability. The images are built by a remote infrastructure and distributed to the user as OCI images. The first problem we encountered was incompatibility with our previous model: squashfs. We reconsidered this decision and created our own tool called Albius to address this issue.