|
44.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
In Ubuntu: |
|
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_list.go:36
|
|
45.
|
|
|
The login command authenticates the user to snapd and the snap store, and saves
credentials into the ~/.snap/auth.json file. Further communication with snapd
will then be made using those credentials.
It's not necessary to log in to interact with snapd. Doing so, however, enables
interactions without sudo, as well as some some developer-oriented features as
detailed in the help for the find, install and refresh commands.
An account can be set up at https://login.ubuntu.com
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The login command authenticates the user to snapd and the snap store, and saves
credentials into the ~/.snap/auth.json file. Further communication with snapd
will then be made using those credentials.
It's not necessary to log in to interact with snapd. Doing so, however, enables
interactions without sudo, as well as some some developer-oriented features as
detailed in the help for the find, install and refresh commands.
An account can be set up at https://login.ubuntu.com
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
cmd/snap/cmd_login.go:42
|
|
46.
|
|
|
The logout command logs the current user out of snapd and the store.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
In Ubuntu: |
|
The logout command logs the current user out of snapd and the store.
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_logout.go:34
|
|
47.
|
|
|
The logs command fetches logs of the given services and displays them in
chronological order.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
In Ubuntu: |
|
The logs command fetches logs of the given services and displays them in
chronological order.
|
|
|
Suggested by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_services.go:58
|
|
48.
|
|
|
The managed command will print true or false informing whether
snapd has registered users.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The managed command will print true or false informing whether
snapd has registered users.
|
|
Translated and reviewed by
Anthony Harrington
|
|
|
|
Located in
cmd/snap/cmd_managed.go:31
|
|
49.
|
|
|
|
|
|
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_model.go:35
|
|
50.
|
|
|
The model command returns the active model assertion information for this
device.
By default, the model identification information is presented in a structured,
yaml-like format, but this can be changed to json by using the --json flag.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The model command returns the active model assertion information for this
device.
By default, the model identification information is presented in a structured,
yaml-like format, but this can be changed to json by using the --json flag.
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
overlord/hookstate/ctlcmd/model.go:44
|
|
51.
|
|
|
The mount command mounts the given source onto the given destination path,
provided that the snap has a plug for the mount-control interface which allows
this operation.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The mount command mounts the given source onto the given destination path,
provided that the snap has a plug for the mount-control interface which allows
this operation.
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
overlord/hookstate/ctlcmd/mount.go:40
|
|
52.
|
|
|
|
|
|
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_warnings.go:60
|
|
53.
|
|
|
The pack command packs the given snap-dir as a snap and writes the result to
target-dir. If target-dir is omitted, the result is written to current
directory. If both source-dir and target-dir are omitted, the pack command packs
the current directory.
The default file name for a snap can be derived entirely from its snap.yaml, but
in some situations it's simpler for a script to feed the filename in. In those
cases, --filename can be given to override the default. If this filename is
not absolute it will be taken as relative to target-dir.
When used with --check-skeleton, pack only checks whether snap-dir contains
valid snap metadata and raises an error otherwise. Application commands listed
in snap metadata file, but appearing with incorrect permission bits result in an
error. Commands that are missing from snap-dir are listed in diagnostic
messages.
When used with --append-integrity-data, pack will append dm-verity data at the end
of the snap to be used with snapd's snap integrity verification mechanism.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
The pack command packs the given snap-dir as a snap and writes the result to
target-dir. If target-dir is omitted, the result is written to current
directory. If both source-dir and target-dir are omitted, the pack command packs
the current directory.
The default file name for a snap can be derived entirely from its snap.yaml, but
in some situations it's simpler for a script to feed the filename in. In those
cases, --filename can be given to override the default. If this filename is
not absolute it will be taken as relative to target-dir.
When used with --check-skeleton, pack only checks whether snap-dir contains
valid snap metadata and raises an error otherwise. Application commands listed
in snap metadata file, but appearing with incorrect permission bits result in an
error. Commands that are missing from snap-dir are listed in diagnostic
messages.
When used with --append-integrity-data, pack will append dm-verity data at the end
of the snap to be used with snapd's snap integrity verification mechanism.
|
|
Translated and reviewed by
Andi Chandler
|
|
|
|
Located in
cmd/snap/cmd_pack.go:49
|