The scheme we propose is built around the variety of concepts of btrfs and Linux file system name-spacing. btrfs at this point already has a large number of features that fit neatly in our concept, and the maintainers are busy working on a couple of others we want to eventually make use of.
[…]
app:<vendorid>:<runtime>:<architecture>:<version> — This encapsulates an application bundle. It contains a tree that at runtime is mounted to /opt/<vendorid>, and contains all the application's resources. The <vendorid> could be a string like org.libreoffice.LibreOffice, the <runtime> refers to one the vendor id of one specific runtime the application is built for, for example org.gnome.GNOME3_20:3.20.1. The <architecture> and <version> refer to the architecture the application is built for, and of course its version. Example: app:org.libreoffice.LibreOffice:GNOME3_20:x86_64:133
[…]
- We want a unified scheme, how we can install and update OS images, user apps, runtimes and frameworks.
- We want a unified scheme how you can relatively freely mix OS images, apps, runtimes and frameworks on the same system.
- We want a fully trusted system, where cryptographic verification of all executed code can be done, all the way to the firmware, as standard feature of the system.
- We want to allow app vendors to write their programs against very specific frameworks, under the knowledge that they will end up being executed with the exact same set of libraries chosen.
- We want to allow parallel installation of multiple OSes and versions of them, multiple runtimes in multiple versions, as well as multiple frameworks in multiple versions. And of course, multiple apps in multiple versions.
- We want everything double buffered (or actually n-fold buffered), to ensure we can reliably update/rollback versions, in particular to safely do automatic updates.
- We want a system where updating a runtime, OS, framework, or OS container is as simple as adding in a new snapshot and restarting the runtime/OS/framework/OS container.
- We want a system where we can easily instantiate a number of OS instances from a single vendor tree, with zero difference for doing this on order to be able to boot it on bare metal/VM or as a container.
- We want to enable Linux to have an open scheme that people can use to build app markets and similar schemes, not restricted to a specific vendor.
[…]
The future is going to be awesome!
←
1
2
3
4
5
6
→
Ответ на:
комментарий
от goingUp
Ответ на:
комментарий
от shatsky
Ответ на:
комментарий
от tailgunner
Ответ на:
комментарий
от F457
Ответ на:
комментарий
от vurdalak
Ответ на:
комментарий
от tailgunner
Ответ на:
комментарий
от F457
Ответ на:
комментарий
от tailgunner
Ответ на:
комментарий
от F457
Ответ на:
комментарий
от tailgunner
Ответ на:
комментарий
от F457
Ответ на:
комментарий
от tailgunner
Ответ на:
комментарий
от F457
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
Похожие темы
- Форум Как переводится Project Treble? (2018)
- Форум [LKML] FatELF - аргументы за и против (2009)
- Форум Centos 7 - не устанавливается пакет libcurl-devel (2019)
- Форум Сыр падает в бубунте (2012)
- Форум error MSB3644. Че оно от меня хочет??? (2019)
- Новости Не открывайте вашу почту с картинками (2004)
- Форум Calligra 2.4 Released (2012)
- Форум [:|||:][ды´рище] [samba] [линакс] Security problem with Samba on Linux - affects 3.5.0, 3.4.6 and 3.3.11 (2010)
- Форум LongHorn уже сделали и его даже можно скачать... (2005)
- Форум Перлокапец? (2008)