4:21
  "   ˆl–ß=¿J	µ2ÛR‚ œP-\lâ˜´oÂ970ÁÀ Ê    #!/usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT: 'cloud-init==24.4','console_scripts','cloud-init'
import re
import sys

# for compatibility with easy_install; see #2198
__requires__ = 'cloud-init==24.4'

try:
    from importlib.metadata import distribution
except ImportError:
    try:
        from importlib_metadata import distribution
    except ImportError:
        from pkg_resources import load_entry_point


def importlib_load_entry_point(spec, group, name):
    dist_name, _, _ = spec.partition('==')
    matches = (
        entry_point
        for entry_point in distribution(dist_name).entry_points
        if entry_point.group == group and entry_point.name == name
    )
    return next(matches).load()


globals().setdefault('load_entry_point', importlib_load_entry_point)


if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(load_entry_point('cloud-init==24.4', 'console_scripts', 'cloud-init')())
     �_’I|¥‰ÓMjqØ‚¦ð¬÷ÂÁ      File not found.
  9   	ˆl–äY>”ªe¶¥@à�¸ÓÊbÑ¿Ä633a–Ým_J*j"Tâ€jã ¸!)‹FÿÃ y    	#!/usr/bin/env perl
# This helper script makes it easy to use a passwd or group file to map
# values in a LOCAL transfer.  For instance, if you mount a backup that
# does not have the same passwd setup as the local machine, you can do
# a copy FROM the backup area as follows and get the differing ID values
# mapped just like a remote transfer FROM the backed-up machine would do:
#
# rsync -av --usermap=`mapfrom /mnt/backup/etc/passwd` \
#           --groupmap=`mapfrom /mnt/backup/etc/group` \
#           /mnt/backup/some/src/ /some/dest/

while (<>) {
    push @_, "$2:$1" if /^(\w+):[^:]+:(\d+)/;
}
print join(',', @_), "\n";
  "   ˆl–äY>”je¶…8 Cq§nµ1hßÆƒmà9¿Ä ®    a
    ´ià  ã                   @   s€   d Z ddlZddlZddlZdgZG dd„ dƒZdd„ ZzddlZW n eyZ   dZ	Y n"0 e 
eƒ j¡ e dd	„ ¡ d
Z	dS )a1  Word completion for GNU readline.

The completer completes keywords, built-ins and globals in a selectable
namespace (which defaults to __main__); when completing NAME.NAME..., it
evaluates (!) the expression up to the last dot and completes its attributes.

It's very cool to do "import sys" type "sys.", hit the completion key (twice),
and see the list of names defined by the sys module!

Tip: to use the tab key as the completion key, call

    readline.parse_and_bind("tab: complete")

Notes:

- Exceptions raised by the completer function are *ignored* (and generally cause
  the completion to fail).  This is a feature -- since readline sets the tty
  device in raw (or cbreak) mode, printing a traceback wouldn't work well
  without some complicated hoopla to save, reset and restore the tty state.

- The evaluation of the NAME.NAME... form may cause arbitrary application
  defined code to be executed if an object with a __getattr__ hook is found.
  Since it is the responsibility of the application (or the user) to enable this
  feature, I consider this an acceptable risk.  More complicated expressions
  (e.g. function calls or indexing operations) are *not* evaluated.

- When the original stdin is not a tty device, GNU readline is never
  used, and this module (and the readline module) are silently inactive.

é    NÚ	Completerc                   @   s6   e Zd Zddd„Zdd„ Zdd„ Zdd	„ Zd
d„ ZdS )r   Nc                 C   s6   |rt |tƒstdƒ‚|du r&d| _nd| _|| _dS )aá  Create a new completer for the command line.

        Completer([namespace]) -> completer instance.

        If unspecified, the default namespace where completions are performed
        is __main__ (technically, __main__.__dict__). Namespaces should be
        given as dictionaries.

        Completer instances should be used as the completion mechanism of
        readline via the set_completer() call:

        readline.set_completer(Completer(my_namespace).complete)
        znamespace must be a dictionaryNé   r   )Ú
isinstanceÚdi