diff options
author | xyz <gky44px1999@gmail.com> | 2023-10-23 22:16:29 -0700 |
---|---|---|
committer | xyz <gky44px1999@gmail.com> | 2023-10-23 22:16:29 -0700 |
commit | 28e4f59d9af025e4ca53d4653063162ba0210cc4 (patch) | |
tree | c09abfcb2117a5a860a19dd3d216acd0200414a4 /etc | |
parent | 258b37a79afed83152f315d7e7139a274ca2e318 (diff) |
rm useless
Diffstat (limited to 'etc')
-rw-r--r-- | etc/NetworkManager/NetworkManager.conf | 4 | ||||
-rwxr-xr-x | etc/NetworkManager/dispatcher.d/70-wifi-wired-exclusive | 17 | ||||
-rwxr-xr-x | etc/NetworkManager/dispatcher.d/90-sbar | 5 | ||||
-rw-r--r-- | etc/X11/xorg.conf.d/20-radeon.conf | 5 | ||||
-rw-r--r-- | etc/chrony.conf | 336 | ||||
-rw-r--r-- | etc/systemd/resolved.conf | 34 | ||||
-rw-r--r-- | etc/wildmidi/wildmidi.cfg | 142 |
7 files changed, 0 insertions, 543 deletions
diff --git a/etc/NetworkManager/NetworkManager.conf b/etc/NetworkManager/NetworkManager.conf deleted file mode 100644 index 3e7688b3..00000000 --- a/etc/NetworkManager/NetworkManager.conf +++ /dev/null @@ -1,4 +0,0 @@ -# Configuration file for NetworkManager. -# See "man 5 NetworkManager.conf" for details. -[connection] -connection.mdns=2 diff --git a/etc/NetworkManager/dispatcher.d/70-wifi-wired-exclusive b/etc/NetworkManager/dispatcher.d/70-wifi-wired-exclusive deleted file mode 100755 index 79e18eb2..00000000 --- a/etc/NetworkManager/dispatcher.d/70-wifi-wired-exclusive +++ /dev/null @@ -1,17 +0,0 @@ -#!/bin/sh - -# code modified from: -# `man nmcli-examples` and Copyright 2012 Johannes Buchner <buchner.johannes@gmx.at> Copyright 2012 - 2014 Red Hat, Inc. - -enable_disable_wifi () -{ - if nmcli -t --fields type,state device | grep -q 'ethernet:connected'; then - nmcli radio wifi off - else - nmcli radio wifi on - fi -} - -case "$2" in - up|down) enable_disable_wifi;; -esac diff --git a/etc/NetworkManager/dispatcher.d/90-sbar b/etc/NetworkManager/dispatcher.d/90-sbar deleted file mode 100755 index c45232da..00000000 --- a/etc/NetworkManager/dispatcher.d/90-sbar +++ /dev/null @@ -1,5 +0,0 @@ -#!/bin/sh - -case "$2" in - up|down) kill -RTMIN+2 $(pidof -x sbar);; -esac diff --git a/etc/X11/xorg.conf.d/20-radeon.conf b/etc/X11/xorg.conf.d/20-radeon.conf deleted file mode 100644 index 3facd79d..00000000 --- a/etc/X11/xorg.conf.d/20-radeon.conf +++ /dev/null @@ -1,5 +0,0 @@ -Section "Device" - Identifier "Radeon" - Driver "radeon" - Option "TearFree" "on" -EndSection diff --git a/etc/chrony.conf b/etc/chrony.conf deleted file mode 100644 index 60f37ba5..00000000 --- a/etc/chrony.conf +++ /dev/null @@ -1,336 +0,0 @@ -####################################################################### -# -# This is an example chrony configuration file. You should copy it to -# /etc/chrony.conf after uncommenting and editing the options that you -# want to enable. The more obscure options are not included. Refer -# to the documentation for these. -# -####################################################################### -### COMMENTS -# Any of the following lines are comments (you have a choice of -# comment start character): -# a comment -% a comment -! a comment -; a comment -# -# Below, the '!' form is used for lines that you might want to -# uncomment and edit to make your own chrony.conf file. -# -####################################################################### -####################################################################### -### SPECIFY YOUR NTP SERVERS -# Most computers using chrony will send measurement requests to one or -# more 'NTP servers'. You will probably find that your Internet Service -# Provider or company have one or more NTP servers that you can specify. -# Failing that, there are a lot of public NTP servers. There is a list -# you can access at http://support.ntp.org/bin/view/Servers/WebHome or -# you can use servers from the pool.ntp.org project. - -! server 0.arch.pool.ntp.org iburst -! server 1.arch.pool.ntp.org iburst -! server 3.arch.pool.ntp.org iburst - -# I don't use auto_offline because: what if wifi connected but has no network? this seems happened a lot to me when modem is up but router is down -# I don't use offline because: I want to sync the clock sooner -pool 2.arch.pool.ntp.org iburst - -####################################################################### -### AVOIDING POTENTIALLY BOGUS CHANGES TO YOUR CLOCK -# -# To avoid changes being made to your computer's gain/loss compensation -# when the measurement history is too erratic, you might want to enable -# one of the following lines. The first seems good with servers on the -# Internet, the second seems OK for a LAN environment. - -! maxupdateskew 100 -! maxupdateskew 5 - -# If you want to increase the minimum number of selectable sources -# required to update the system clock in order to make the -# synchronisation more reliable, uncomment (and edit) the following -# line. - -! minsources 2 - -# If your computer has a good stable clock (e.g. it is not a virtual -# machine), you might also want to reduce the maximum assumed drift -# (frequency error) of the clock (the value is specified in ppm). - -! maxdrift 100 - -# By default, chronyd allows synchronisation to an unauthenticated NTP -# source (i.e. specified without the nts and key options) if it agrees with -# a majority of authenticated NTP sources, or if no authenticated source is -# specified. If you don't want chronyd to ever synchronise to an -# unauthenticated NTP source, uncomment the first from the following lines. -# If you don't want to synchronise to an unauthenticated NTP source only -# when an authenticated source is specified, uncomment the second line. -# If you want chronyd to ignore authentication in the source selection, -# uncomment the third line. - -! authselectmode require -! authselectmode prefer -! authselectmode ignore - -####################################################################### -### FILENAMES ETC -# Chrony likes to keep information about your computer's clock in files. -# The 'driftfile' stores the computer's clock gain/loss rate in parts -# per million. When chronyd starts, the system clock can be tuned -# immediately so that it doesn't gain or lose any more time. You -# generally want this, so it is uncommented. - -driftfile /var/lib/chrony/drift - -# If you want to enable NTP authentication with symmetric keys, you will need -# to uncomment the following line and edit the file to set up the keys. - -! keyfile /etc/chrony.keys - -# If you specify an NTP server with the nts option to enable authentication -# with the Network Time Security (NTS) mechanism, or enable server NTS with -# the ntsservercert and ntsserverkey directives below, the following line will -# allow the client/server to save the NTS keys and cookies in order to reduce -# the number of key establishments (NTS-KE sessions). - -ntsdumpdir /var/lib/chrony - -# If chronyd is configured to act as an NTP server and you want to enable NTS -# for its clients, you will need a TLS certificate and private key. Uncomment -# and edit the following lines to specify the locations of the certificate and -# key. - -! ntsservercert /etc/.../foo.example.net.crt -! ntsserverkey /etc/.../foo.example.net.key - -# chronyd can save the measurement history for the servers to files when -# it exits. This is useful in 2 situations: -# -# 1. If you stop chronyd and restart it with the '-r' option (e.g. after -# an upgrade), the old measurements will still be relevant when chronyd -# is restarted. This will reduce the time needed to get accurate -# gain/loss measurements. -# -# 2. On Linux, if you use the RTC support and start chronyd with -# '-r -s' on bootup, measurements from the last boot will still be -# useful (the real time clock is used to 'flywheel' chronyd between -# boots). -# -# Uncomment the following line to use this. - -! dumpdir /var/lib/chrony - -# chronyd writes its process ID to a file. If you try to start a second -# copy of chronyd, it will detect that the process named in the file is -# still running and bail out. If you want to change the path to the PID -# file, uncomment this line and edit it. The default path is shown. - -! pidfile /var/run/chrony/chronyd.pid - -# If the system timezone database is kept up to date and includes the -# right/UTC timezone, chronyd can use it to determine the current -# TAI-UTC offset and when will the next leap second occur. - -leapsectz right/UTC - -####################################################################### -### INITIAL CLOCK CORRECTION -# This option is useful to quickly correct the clock on start if it's -# off by a large amount. The value '1.0' means that if the error is less -# than 1 second, it will be gradually removed by speeding up or slowing -# down your computer's clock until it is correct. If the error is above -# 1 second, an immediate time jump will be applied to correct it. The -# value '3' means the step is allowed only in the first three updates of -# the clock. Some software can get upset if the system clock jumps -# (especially backwards), so be careful! - -makestep 1.0 3 - -####################################################################### -### LEAP SECONDS -# A leap second is an occasional one-second correction of the UTC -# time scale. By default, chronyd tells the kernel to insert/delete -# the leap second, which makes a backward/forward step to correct the -# clock for it. As with the makestep directive, this jump can upset -# some applications. If you prefer chronyd to make a gradual -# correction, causing the clock to be off for a longer time, uncomment -# the following line. - -! leapsecmode slew - -####################################################################### -### LOGGING -# If you want to log information about the time measurements chronyd has -# gathered, you might want to enable the following lines. You probably -# only need this if you really enjoy looking at the logs, you want to -# produce some graphs of your system's timekeeping performance, or you -# need help in debugging a problem. - -! logdir /var/log/chrony -! log measurements statistics tracking - -# If you have real time clock support enabled (see below), you might want -# this line instead: - -! log measurements statistics tracking rtc - -####################################################################### -### ACTING AS AN NTP SERVER -# You might want the computer to be an NTP server for other computers. -# -# By default, chronyd does not allow any clients to access it. You need -# to explicitly enable access using 'allow' and 'deny' directives. -# -# e.g. to enable client access from the 192.168.*.* class B subnet, - -! allow 192.168/16 - -# .. but disallow the 192.168.100.* subnet of that, - -! deny 192.168.100/24 - -# You can have as many allow and deny directives as you need. The order -# is unimportant. - -# If you want to present your computer's time for others to synchronise -# with, even if you don't seem to be synchronised to any NTP servers -# yourself, enable the following line. The value 10 may be varied -# between 1 and 15. You should avoid small values because you will look -# like a real NTP server. The value 10 means that you appear to be 10 -# NTP 'hops' away from an authoritative source (atomic clock, GPS -# receiver, radio clock etc). - -! local stratum 10 - -# Normally, chronyd will keep track of how many times each client -# machine accesses it. The information can be accessed by the 'clients' -# command of chronyc. You can disable this facility by uncommenting the -# following line. This will save a bit of memory if you have many -# clients and it will also disable support for the interleaved mode. - -! noclientlog - -# The clientlog size is limited to 512KB by default. If you have many -# clients, you might want to increase the limit. - -! clientloglimit 4194304 - -# By default, chronyd tries to respond to all valid NTP requests from -# allowed addresses. If you want to limit the response rate for NTP -# clients that are sending requests too frequently, uncomment and edit -# the following line. - -! ratelimit interval 3 burst 8 - -####################################################################### -### REPORTING BIG CLOCK CHANGES -# Perhaps you want to know if chronyd suddenly detects any large error -# in your computer's clock. This might indicate a fault or a problem -# with the server(s) you are using, for example. -# -# The next option causes a message to be written to syslog when chronyd -# has to correct an error above 0.5 seconds (you can use any amount you -# like). - -! logchange 0.5 - -# The next option will send email to the named person when chronyd has -# to correct an error above 0.5 seconds. (If you need to send mail to -# several people, you need to set up a mailing list or sendmail alias -# for them and use the address of that.) - -! mailonchange wibble@foo.example.net 0.5 - -####################################################################### -### COMMAND ACCESS -# The program chronyc is used to show the current operation of chronyd -# and to change parts of its configuration whilst it is running. - -# By default chronyd binds to the loopback interface. Uncomment the -# following lines to allow receiving command packets from remote hosts. - -! bindcmdaddress 0.0.0.0 -! bindcmdaddress :: - -# Normally, chronyd will only allow connections from chronyc on the same -# machine as itself. This is for security. If you have a subnet -# 192.168.*.* and you want to be able to use chronyc from any machine on -# it, you could uncomment the following line. (Edit this to your own -# situation.) - -! cmdallow 192.168/16 - -# You can add as many 'cmdallow' and 'cmddeny' lines as you like. The -# syntax and meaning is the same as for 'allow' and 'deny', except that -# 'cmdallow' and 'cmddeny' control access to the chronyd's command port. - -# Rate limiting can be enabled also for command packets. (Note, -# commands from localhost are never limited.) - -! cmdratelimit interval -4 burst 16 - -####################################################################### -### HARDWARE TIMESTAMPING -# On Linux, if the network interface controller and its driver support -# hardware timestamping, it can significantly improve the accuracy of -# synchronisation. It can be enabled on specified interfaces only, or it -# can be enabled on all interfaces that support it. - -! hwtimestamp eth0 -! hwtimestamp * - -####################################################################### -### REAL TIME CLOCK -# chronyd can characterise the system's real-time clock. This is the -# clock that keeps running when the power is turned off, so that the -# machine knows the approximate time when it boots again. The error at -# a particular epoch and gain/loss rate can be written to a file and -# used later by chronyd when it is started with the '-s' option. -# -# You need to have 'enhanced RTC support' compiled into your Linux -# kernel. (Note, these options apply only to Linux.) - -! rtcfile /var/lib/chrony/rtc - -# Your RTC can be set to keep Universal Coordinated Time (UTC) or local -# time. (Local time means UTC +/- the effect of your timezone.) If you -# use UTC, chronyd will function correctly even if the computer is off -# at the epoch when you enter or leave summer time (aka daylight saving -# time). However, if you dual boot your system with Microsoft Windows, -# that will work better if your RTC maintains local time. You take your -# pick! - -rtconutc - -# By default chronyd assumes that the enhanced RTC device is accessed as -# /dev/rtc. If it's accessed somewhere else on your system (e.g. you're -# using devfs), uncomment and edit the following line. - -! rtcdevice /dev/misc/rtc - -# Alternatively, if not using the -s option, this directive can be used -# to enable a mode in which the RTC is periodically set to the system -# time, with no tracking of its drift. - -rtcsync - -####################################################################### -### REAL TIME SCHEDULER -# This directive tells chronyd to use the real-time FIFO scheduler with the -# specified priority (which must be between 0 and 100). This should result -# in reduced latency. You don't need it unless you really have a requirement -# for extreme clock stability. Works only on Linux. Note that the "-P" -# command-line switch will override this. - -! sched_priority 1 - -####################################################################### -### LOCKING CHRONYD INTO RAM -# This directive tells chronyd to use the mlockall() syscall to lock itself -# into RAM so that it will never be paged out. This should result in reduced -# latency. You don't need it unless you really have a requirement -# for extreme clock stability. Works only on Linux. Note that the "-m" -# command-line switch will also enable this feature. - -! lock_all diff --git a/etc/systemd/resolved.conf b/etc/systemd/resolved.conf deleted file mode 100644 index c7f6fc5a..00000000 --- a/etc/systemd/resolved.conf +++ /dev/null @@ -1,34 +0,0 @@ -# This file is part of systemd. -# -# systemd is free software; you can redistribute it and/or modify it under the -# terms of the GNU Lesser General Public License as published by the Free -# Software Foundation; either version 2.1 of the License, or (at your option) -# any later version. -# -# Entries in this file show the compile time defaults. Local configuration -# should be created by either modifying this file, or by creating "drop-ins" in -# the resolved.conf.d/ subdirectory. The latter is generally recommended. -# Defaults can be restored by simply deleting this file and all drop-ins. -# -# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config. -# -# See resolved.conf(5) for details. - -[Resolve] -# Some examples of DNS servers which may be used for DNS= and FallbackDNS=: -# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com -# Google: 8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google -# Quad9: 9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net -#DNS= -#FallbackDNS=9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google -#Domains= -#DNSSEC=no -#DNSOverTLS=no -MulticastDNS=yes -#LLMNR=yes -#Cache=yes -#CacheFromLocalhost=no -#DNSStubListener=yes -#DNSStubListenerExtra= -#ReadEtcHosts=yes -#ResolveUnicastSingleLabel=no diff --git a/etc/wildmidi/wildmidi.cfg b/etc/wildmidi/wildmidi.cfg deleted file mode 100644 index d0ee73b6..00000000 --- a/etc/wildmidi/wildmidi.cfg +++ /dev/null @@ -1,142 +0,0 @@ -# https://github.com/Mindwerks/wildmidi/blob/master/cfg/wildmidi.cfg -# https://freepats.zenvoid.org/SoundSets/general-midi.html -#dir /usr/share/midi/freepats -dir ~/documents/codecs/freepats/ - -# Automatically generated on Sun Feb 19 19:22:39 EST 2006 -# by http://freepats.opensrc.org/mkcfg.sh.txt - -drumset 0 - - 25 Drum_000/025_Snare_Roll.pat - 26 Drum_000/026_Snap.pat - 27 Drum_000/027_High_Q.pat - 31 Drum_000/031_Sticks.pat - 32 Drum_000/032_Square_Click.pat - 33 Drum_000/033_Metronome_Click.pat - 34 Drum_000/034_Metronome_Bell.pat - 35 Drum_000/035_Kick_1.pat amp=100 - 36 Drum_000/036_Kick_2.pat amp=100 - 37 Drum_000/037_Stick_Rim.pat - 38 Drum_000/038_Snare_1.pat - 39 Drum_000/039_Clap_Hand.pat amp=100 - 40 Drum_000/040_Snare_2.pat - 41 Drum_000/041_Tom_Low_2.pat amp=100 - 42 Drum_000/042_Hi-Hat_Closed.pat - 43 Drum_000/043_Tom_Low_1.pat amp=100 - 44 Drum_000/044_Hi-Hat_Pedal.pat - 45 Drum_000/045_Tom_Mid_2.pat amp=100 - 46 Drum_000/046_Hi-Hat_Open.pat - 47 Drum_000/047_Tom_Mid_1.pat amp=100 - 48 Drum_000/048_Tom_High_2.pat amp=100 - 49 Drum_000/049_Cymbal_Crash_1.pat - 50 Drum_000/050_Tom_High_1.pat amp=100 - 51 Drum_000/051_Cymbal_Ride_1.pat - 52 Drum_000/052_Cymbal_Chinese.pat - 53 Drum_000/053_Cymbal_Ride_Bell.pat amp=100 - 54 Drum_000/054_Tombourine.pat - 55 Drum_000/055_Cymbal_Splash.pat - 56 Drum_000/056_Cow_Bell.pat - 57 Drum_000/057_Cymbal_Crash_2.pat - 58 Drum_000/058_Vibra-Slap.pat - 59 Drum_000/059_Cymbal_Ride_2.pat - 60 Drum_000/060_Bongo_High.pat - 61 Drum_000/061_Bongo_Low.pat - 62 Drum_000/062_Conga_High_1_Mute.pat - 63 Drum_000/063_Conga_High_2_Open.pat - 64 Drum_000/064_Conga_Low.pat - 65 Drum_000/065_Timbale_High.pat - 66 Drum_000/066_Timbale_Low.pat - 67 Drum_000/067_Agogo_High.pat - 68 Drum_000/068_Agogo_Low.pat - 69 Drum_000/069_Cabasa.pat amp=100 - 70 Drum_000/070_Maracas.pat - 71 Drum_000/071_Whistle_1_High_Short.pat - 72 Drum_000/072_Whistle_2_Low_Long.pat - 73 Drum_000/073_Guiro_1_Short.pat - 74 Drum_000/074_Guiro_2_Long.pat - 75 Drum_000/075_Claves.pat amp=100 - 76 Drum_000/076_Wood_Block_1_High.pat - 77 Drum_000/077_Wood_Block_2_Low.pat - 78 Drum_000/078_Cuica_1_Mute.pat amp=100 - 79 Drum_000/079_Cuica_2_Open.pat amp=100 - 80 Drum_000/080_Triangle_1_Mute.pat - 81 Drum_000/081_Triangle_2_Open.pat - 82 Drum_000/082_Shaker.pat - 84 Drum_000/084_Belltree.pat - -bank 0 - - 0 Tone_000/000_Acoustic_Grand_Piano.pat amp=120 pan=center - 1 Tone_000/001_Acoustic_Brite_Piano.pat - 2 Tone_000/002_Electric_Grand_Piano.pat - 4 Tone_000/004_Electric_Piano_1_Rhodes.pat - 5 Tone_000/005_Electric_Piano_2_Chorused_Yamaha_DX.pat - 6 Tone_000/006_Harpsichord.pat - 7 Tone_000/007_Clavinet.pat - 8 Tone_000/008_Celesta.pat - 9 Tone_000/009_Glockenspiel.pat - 13 Tone_000/013_Xylophone.pat - 14 Tone_000/014_Tubular_Bells.pat - 15 Tone_000/015_Dulcimer.pat - 16 Tone_000/016_Hammond_Organ.pat - 19 Tone_000/019_Church_Organ.pat - 21 Tone_000/021_Accordion.pat - 23 Tone_000/023_Tango_Accordion.pat - 24 Tone_000/024_Nylon_Guitar.pat - 25 Tone_000/025_Steel_Guitar.pat - 26 Tone_000/026_Jazz_Guitar.pat - 27 Tone_000/027_Clean_Electric_Guitar.pat - 28 Tone_000/028_Muted_Electric_Guitar.pat - 29 Tone_000/029_Overdriven_Guitar.pat - 30 Tone_000/030_Distortion_Guitar.pat - 32 Tone_000/032_Acoustic_Bass.pat - 33 Tone_000/033_Finger_Bass.pat - 34 Tone_000/034_Pick_Bass.pat - 35 Tone_000/035_Fretless_Bass.pat - 36 Tone_000/036_Slap_Bass_1.pat - 37 Tone_000/037_Slap_Bass_2.pat - 38 Tone_000/038_Synth_Bass_1.pat - 40 Tone_000/040_Violin.pat - 42 Tone_000/042_Cello.pat - 44 Tone_000/044_Tremolo_Strings.pat - 45 Tone_000/045_Pizzicato_Strings.pat - 46 Tone_000/046_Harp.pat - 47 Tone_000/047_Timpani.pat - 48 Tone_000/048_String_Ensemble_1_Marcato.pat - 53 Tone_000/053_Voice_Oohs.pat - 56 Tone_000/056_Trumpet.pat - 57 Tone_000/057_Trombone.pat - 58 Tone_000/058_Tuba.pat - 59 Tone_000/059_Muted_Trumpet.pat - 60 Tone_000/060_French_Horn.pat - 61 Tone_000/061_Brass_Section.pat - 64 Tone_000/064_Soprano_Sax.pat - 65 Tone_000/065_Alto_Sax.pat - 66 Tone_000/066_Tenor_Sax.pat - 67 Tone_000/067_Baritone_Sax.pat - 68 Tone_000/068_Oboe.pat - 69 Tone_000/069_English_Horn.pat - 70 Tone_000/070_Bassoon.pat - 71 Tone_000/071_Clarinet.pat - 72 Tone_000/072_Piccolo.pat - 73 Tone_000/073_Flute.pat - 74 Tone_000/074_Recorder.pat - 75 Tone_000/075_Pan_Flute.pat - 76 Tone_000/076_Bottle_Blow.pat - 79 Tone_000/079_Ocarina.pat - 80 Tone_000/080_Square_Wave.pat - 84 Tone_000/084_Charang.pat - 88 Tone_000/088_New_Age.pat - 94 Tone_000/094_Halo_Pad.pat - 95 Tone_000/095_Sweep_Pad.pat - 98 Tone_000/098_Crystal.pat - 101 Tone_000/101_Goblins--Unicorn.pat - 102 Tone_000/102_Echo_Voice.pat - 104 Tone_000/104_Sitar.pat - 114 Tone_000/114_Steel_Drums.pat - 115 Tone_000/115_Wood_Block.pat - 120 Tone_000/120_Guitar_Fret_Noise.pat - 122 Tone_000/122_Seashore.pat - 125 Tone_000/125_Helicopter.pat - |