Ubuntu
snapd package

Browsing Brazilian Portuguese translation

  1. Mantic (23.10)
  2. Template “snappy”
  3. Brazilian Portuguese (pt_BR)
Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Brazilian Portuguese guidelines.

These translations are shared with snapd trunk series template snappy.

28 → 37 of 925 results First • • • Last
28.

The fde-setup-request command is used inside the fde-setup hook. It will
return information about what operation for full-disk encryption is
requested and auxiliary data to complete this operation.

The fde-setup hook should do what is requested and then call
"snapctl fde-setup-result" and pass the result data to stdin.

Here is an example for how the fde-setup hook is called initially:
$ snapctl fde-setup-request
{"op":"features"}
$ echo '{"features": []}' | snapctl fde-setup-result

Alternatively the hook could reply with:
$ echo '{"error":"hardware-unsupported"}' | snapctl fde-setup-result

And then it is called again with a request to do the initial key setup:
$ snapctl fde-setup-request
{"op":"initial-setup", "key": "key-to-seal"}
$ echo "{"sealed-key":"$base64_encoded_sealed_key"}" | snapctl fde-setup-result
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in overlord/hookstate/ctlcmd/fde_setup.go:36
29.

The fde-setup-result command sets the result data for a fde-setup hook
reading it from stdin.

For example:
When the fde-setup hook is called with "op":"features:
$ echo '{"features": []}' | snapctl fde-setup-result

When the fde-setup hook is called with "op":"initial-setup":
$ echo "{"sealed-key":"$base64_encoded_sealed_key"}" | snapctl fde-setup-result
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in overlord/hookstate/ctlcmd/fde_setup.go:101
30.

The file-access command returns information about a snap's file system access.

This command is used by the xdg-document-portal service to identify
files that do not need to be proxied to provide access within
confinement.

File paths are interpreted as host file system paths. The tool may
return false negatives (e.g. report that a file path is unreadable,
despite being readable under a different path). It also does not
check if file system permissions would render a file unreadable.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_routine_file_access.go:43
31.

The find command queries the store for available packages.

With the --private flag, which requires the user to be logged-in to the store
(see 'snap help login'), it instead searches for private snaps that the user
has developer access to, either directly or through the store's collaboration
feature.

A green check mark (given color and unicode support) after a publisher name
indicates that the publisher has been verified.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_find.go:40
32.

The forget command deletes a snapshot. This operation can not be
undone.

A snapshot contains archives for the user, system and configuration
data of each snap included in the snapshot.

By default, this command forgets all the data in a snapshot.
Alternatively, you can specify the data of which snaps to forget.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_snapshot.go:66
33.

The get command prints configuration options for the current snap.

$ snapctl get username
frank

If multiple option names are provided, a document is returned:

$ snapctl get username password
{
"username": "frank",
"password": "..."
}

Nested values may be retrieved via a dotted path:

$ snapctl get author.name
frank

Values of interface connection settings may be printed with:

$ snapctl get :myplug usb-vendor
$ snapctl get :myslot path

This will return the named setting from the local interface endpoint,
regardless whether it's a plug or a slot. Returning the setting from the
connected snap's endpoint is also possible by requesting the setting explicitly
with optional --plug and --slot command options:

$ snapctl get :myplug --slot usb-vendor

This requests the "usb-vendor" setting from the slot that is connected to
"myplug".
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in overlord/hookstate/ctlcmd/get.go:52
34.

The get command prints configuration options for the provided snap.

$ snap get snap-name username
frank

If multiple option names are provided, the corresponding values are returned:

$ snap get snap-name username password
Key Value
username frank
password ...

Nested values may be retrieved via a dotted path:

$ snap get snap-name author.name
frank
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_get.go:34
35.

The help command displays information about snap commands.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.

O comando help exibe informações sobre os comandos do snap.
Translated by Henrique Deodato
Reviewed by Tiago Hillebrandt
Located in cmd/snap/cmd_help.go:36
36.

The info command shows detailed information about snaps.

The snaps can be specified by name or by path; names are looked for both in the
store and in the installed snaps; paths can refer to a .snap file, or to a
directory that contains an unpacked snap suitable for 'snap try' (an example
of this would be the 'prime' directory snapcraft produces).
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_info.go:59
37.

The install command installs the named snaps on the system.

To install multiple instances of the same snap, append an underscore and a
unique identifier (for each instance) to a snap's name.

With no further options, the snaps are installed tracking the stable channel,
with strict security confinement. All available channels of a snap are listed in
its 'snap info' output.

When --revision is used, a later refresh will typically undo the revision
override, taking the snap back to the current revision of the channel it's
tracking.

Use --name to set the instance name when installing from snap file.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in cmd/snap/cmd_snap_op.go:52
28 → 37 of 925 results First • • • Last

This translation is managed by Ubuntu Brazilian Portuguese Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Anderson Rodrigo Piram, André Lubawski, Bruno Lopes da Silva, Bruno Straatmann, Caio, Cristofer Portela, Diego Aparecido de Souza Pereira, Edvaldo de Souza Cruz, Elvis da Silva de Menezes, Henrique Deodato, Henrique Matias de Lima, Leonardo Martins, Leticia Martins Bandeira Pascale, Matheus Reich, Northon Souza, Paulo, Rodrigo Henrique, Thiago Monteiro Cruz, Tiago Hillebrandt, Tobias Sirianni Melo, baquelo, liddack, thiago dos santos galdino.