|
9.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_aliases.go:41
|
|
10.
|
|
|
The auto-import command searches available mounted devices looking for
assertions that are signed by trusted authorities, and potentially
performs system changes based on them.
If one or more device paths are provided via --mount, these are temporarily
mounted to be inspected as well. Even in that case the command will still
consider all available mounted devices for inspection.
Assertions to be imported must be made available in the auto-import.assert file
in the root of the filesystem.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The auto-import command searches available mounted devices looking for
assertions that are signed by trusted authorities, and potentially
performs system changes based on them.
If one or more device paths are provided via --mount, these are temporarily
mounted to be inspected as well. Even in that case the command will still
consider all available mounted devices for inspection.
Assertions to be imported must be made available in the auto-import.assert file
in the root of the filesystem.
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_auto_import.go:231
|
|
11.
|
|
|
The buy command buys a snap from the store.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The buy command buys a snap from the store.
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_buy.go:33
|
|
12.
|
|
|
The changes command displays a summary of system changes performed recently.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The changes command displays a summary of system changes performed recently.
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_changes.go:35
|
|
13.
|
|
|
The check-snapshot command verifies the user, system and configuration
data of the snaps included in the specified snapshot.
The check operation runs the same data integrity verification that is
performed when a snapshot is restored.
By default, this command checks all the data in a snapshot.
Alternatively, you can specify the data of which snaps to check, or
for which users, or a combination of these.
If a snap is included in a check-snapshot operation, excluding its
system and configuration data from the check is not currently
possible. This restriction may be lifted in the future.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The check-snapshot command verifies the user, system and configuration
data of the snaps included in the specified snapshot.
The check operation runs the same data integrity verification that is
performed when a snapshot is restored.
By default, this command checks all the data in a snapshot.
Alternatively, you can specify the data of which snaps to check, or
for which users, or a combination of these.
If a snap is included in a check-snapshot operation, excluding its
system and configuration data from the check is not currently
possible. This restriction may be lifted in the future.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
cmd/snap/cmd_snapshot.go:76
|
|
14.
|
|
|
The confinement command will print the confinement mode (strict,
partial or none) the system operates in.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The confinement command will print the confinement mode (strict,
partial or none) the system operates in.
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_confinement.go:31
|
|
15.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_connect.go:37
|
|
16.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
cmd/snap/cmd_connections.go:42
|
|
17.
|
|
|
The console-conf-start command starts synchronization with console-conf
This command is used by console-conf when it starts up. It delays refreshes if
there are none currently ongoing, and exits with a specific error code if there
are ongoing refreshes which console-conf should wait for before prompting the
user to begin configuring the device.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
The console-conf-start command starts synchronization with console-conf
This command is used by console-conf when it starts up. It delays refreshes if
there are none currently ongoing, and exits with a specific error code if there
are ongoing refreshes which console-conf should wait for before prompting the
user to begin configuring the device.
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
cmd/snap/cmd_routine_console_conf.go:40
|
|
18.
|
|
|
The create-cohort command creates a set of cohort keys for a given set of snaps.
A cohort is a view or snapshot of a snap's "channel map" at a given point in
time that fixes the set of revisions for the snap given other constraints
(e.g. channel or architecture). The cohort is then identified by an opaque
per-snap key that works across systems. Installations or refreshes of the snap
using a given cohort key would use a fixed revision for up to 90 days, after
which a new set of revisions would be fixed under that same cohort key and a
new 90 days window started.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The create-cohort command creates a set of cohort keys for a given set of snaps.
A cohort is a view or snapshot of a snap's "channel map" at a given point in
time that fixes the set of revisions for the snap given other constraints
(e.g. channel or architecture). The cohort is then identified by an opaque
per-snap key that works across systems. Installations or refreshes of the snap
using a given cohort key would use a fixed revision for up to 90 days, after
which a new set of revisions would be fixed under that same cohort key and a
new 90 days window started.
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
cmd/snap/cmd_create_cohort.go:30
|