Statically typed programming language that uses a new concept of variable ownership and reference tracking. Largely explain in \autoref{context::rust}.
},
first = {\glsentrylong{Rust}}
}
\newglossaryentry{proglang}{
name = {programming language},
description = {
A well-defined language used to write software. Hundreds of language exists, each with focus on different aspects like comfort for humans, size, speed, safety, etc.
entitiy that holds a specific set of process attributes and can be set per process
},
}
\newglossaryentry{lxcap}{
name = Linux Capability,
description = {
entitiy that holds a specific set of process attributes and can be set per process, mainly to establish a relationship between processes and \gls{OS} resources
},
plural = Linux Capabilities,
}
\newglossaryentry{lxvfs}{
name = Linux VFS,
description = {
Virtual Filesystem Switch, a filesystem abstraction layer in \gls{Linux}.
},
}
\newglossaryentry{BSD}{
name = BSD,
description = {
TODO
}
}
\newglossaryentry{computer}{
name = Computer,
description = {
is a programmable machine that receives input,
stores and manipulates data, and provides
output in a useful format
}
}
\newglossaryentry{app}{
name=software-application,
description={
TODO
}
}
\newglossaryentry{pm}{
name=package manager,
description={
TODO
}
}
\newglossaryentry{sac}{
name=Software Application Container,
description={
The broad term for the technology used to build, package, distribute and run an application program in isolation from the underlying and co-existing systems, wherein the level or technique of isolation can be different depending on the \gls{sacr}.
The term is nuanced from \gls{appc} defined by the \gls{appcorg}.
The \gls{appcorg} is a community driven effort to create an open, standardized specification for developers and users of \gls{sac} technology.
Such independent standards are required to form interoperability between \gls{sac} implementations made by independent parties.
Some implementations will be subject to more detailed examination in Part \ref{part:research}.
}
}
\newglossaryentry{saci}{
name=Software Application Container Image,
description={
An archive file that contains all of the necessary binaries that are needed to execute an application and a manifest file that that contains metadata about the application. Alternatively to containing all the required binary files, the manifest file can declare dependencies to other application container images, which must then be available at runtime to execute the contained application.
}
}
\newglossaryentry{sacr}{
name=Software Application Container Runtime,
description={
An application program (suite) that understands how to run the software inside an \gls{saci}.
}
}
\newglossaryentry{LXC}{
name=LXC,
description={
TODO
}
}
\newglossaryentry{Docker}{
name=Docker,
description={
A very popular \gls{sac} platform and application suite, providing functionality to build and deploy Docker specific \glspl{saci}.
}
}
\newglossaryentry{systemd-nspawn}{
name=systemd-nspawn,
description={
TODO
}
}
\newglossaryentry{rkt}{
name=rkt,
description={
TODO
}
}
\newglossaryentry{appcorg}{
name=App Container Organisation,
description={
Organisation for the App Container specification, including the schema and associated tooling.
}
}
\newglossaryentry{appc}{
name=App Container,
description={
Specific variant of an \gls{sac} defined by the \gls{appcorg}.