mkdir -p './NetworkManager/system-connections'
mkdir -p './X11/xinit/xinitrc.d'
mkdir -p './X11/xkb'
+mkdir -p './acpi/events'
mkdir -p './apm/event.d'
mkdir -p './apparmor.d/force-complain'
mkdir -p './apt/auth.conf.d'
maybe chmod 0755 'X11/xsm'
maybe chmod 0644 'X11/xsm/system.xsm'
maybe chmod 0755 'acpi'
-maybe chmod 0755 'acpi/asus-keyboard-backlight.sh'
-maybe chmod 0755 'acpi/asus-wireless.sh'
maybe chmod 0755 'acpi/events'
-maybe chmod 0644 'acpi/events/asus-keyboard-backlight-down'
-maybe chmod 0644 'acpi/events/asus-keyboard-backlight-up'
-maybe chmod 0644 'acpi/events/asus-wireless-off'
-maybe chmod 0644 'acpi/events/asus-wireless-on'
-maybe chmod 0644 'acpi/events/ibm-wireless'
-maybe chmod 0644 'acpi/events/lenovo-undock'
-maybe chmod 0644 'acpi/events/thinkpad-cmos'
-maybe chmod 0644 'acpi/events/tosh-wireless'
-maybe chmod 0755 'acpi/ibm-wireless.sh'
-maybe chmod 0755 'acpi/tosh-wireless.sh'
-maybe chmod 0755 'acpi/undock.sh'
maybe chmod 0644 'adduser.conf'
maybe chmod 0644 'adduser.conf.update-old'
maybe chmod 0644 'aliases'
maybe chmod 0755 'debuginfod'
maybe chmod 0644 'debuginfod/elfutils.urls'
maybe chmod 0755 'default'
-maybe chmod 0644 'default/acpi-support'
maybe chmod 0644 'default/acpid'
maybe chmod 0644 'default/add-apt-key'
maybe chmod 0644 'default/alsa'
+++ /dev/null
-#!/bin/sh
-
-# this directory is a symlink on my machine:
-KEYS_DIR=/sys/class/leds/asus\:\:kbd_backlight
-
-test -d $KEYS_DIR || exit 0
-
-MIN=0
-MAX=$(cat $KEYS_DIR/max_brightness)
-VAL=$(cat $KEYS_DIR/brightness)
-
-if [ "$1" = down ]; then
- VAL=$((VAL-1))
-else
- VAL=$((VAL+1))
-fi
-
-if [ "$VAL" -lt $MIN ]; then
- VAL=$MIN
-elif [ "$VAL" -gt $MAX ]; then
- VAL=$MAX
-fi
-
-echo $VAL > $KEYS_DIR/brightness
+++ /dev/null
-#!/bin/sh
-# Find and toggle wireless devices on Asus laptops
-
-test -f /usr/share/acpi-support/state-funcs || exit 0
-
-. /usr/share/acpi-support/state-funcs
-
-toggleAllWirelessStates
+++ /dev/null
-# /etc/acpi/events/asus-keyboard-backlight-down
-# This is called when the user presses the key brightness
-# down button and calls /etc/acpi/asus-keyboard-backlight.sh for
-# further processing.
-
-event=hotkey ATKD 000000c5
-action=/etc/acpi/asus-keyboard-backlight.sh down
+++ /dev/null
-# /etc/acpi/events/asus-keyboard-backlight-up
-# This is called when the user presses the key brightness
-# up button and calls /etc/acpi/asus-keyboard-backlight.sh for
-# further processing.
-
-event=hotkey ATKD 000000c4
-action=/etc/acpi/asus-keyboard-backlight.sh up
+++ /dev/null
-event=hotkey (ATKD|HOTK) 0000005e
-action=/etc/acpi/asus-wireless.sh off
-
+++ /dev/null
-event=hotkey (ATKD|HOTK) 0000005f
-action=/etc/acpi/asus-wireless.sh on
-
+++ /dev/null
-# /etc/acpi/events/ibmwireless
-# This is called when the user presses the wireless button and calls
-# /etc/acpi/wireless.sh for further processing.
-
-event=ibm/hotkey HKEY 00000080 00001005
-action=/etc/acpi/ibm-wireless.sh
-
+++ /dev/null
-event=ibm/hotkey HKEY 00000080 00001009
-action=/etc/acpi/undock.sh
+++ /dev/null
-# /etc/acpi/events/thinkpad-cmos
-# This is called when ever an ACPI interupt comes in; we
-# use it to perform a (more intelligent) event-driven form
-# of polling for Thinkpad hotkey status.
-
-event=METHOD CMOS|UCMS|CMS 00000000 00000000
-action=/usr/sbin/thinkpad-keys --update
+++ /dev/null
-# /etc/acpi/events/tosh-wireless
-# This is called when the user presses the wireless button and calls
-# /etc/acpi/wireless.sh for further processing.
-
-event=hkey VAL[DZ] 00000001 00000142
-action=/etc/acpi/tosh-wireless.sh
+++ /dev/null
-#!/bin/sh
-
-test -f /usr/share/acpi-support/state-funcs || exit 0
-
-# Find and toggle wireless of bluetooth devices on ThinkPads
-
-. /usr/share/acpi-support/state-funcs
-
-rfkill list | sed -n -e'/tpacpi_bluetooth_sw/,/^[0-9]/p' | grep -q 'Soft blocked: yes'
-bluetooth_state=$?
-
-# Note that this always alters the state of the wireless!
-toggleAllWirelessStates;
-
-# Sequence is Both on, Both off, Wireless only, Bluetooth only
-if ! isAnyWirelessPoweredOn; then
- # Wireless was turned off
- if [ "$bluetooth_state" = 0 ]; then
- rfkill unblock bluetooth
- else
- rfkill block bluetooth
- fi
-fi
+++ /dev/null
-#!/bin/sh
-
-test -f /usr/share/acpi-support/key-constants || exit 0
-
-. /usr/share/acpi-support/state-funcs
-
-if isAnyWirelessPoweredOn; then
- if [ -x /usr/bin/toshset ]; then
- if `toshset -bluetooth | grep -q attached`; then
- toshset -bluetooth off
- toggleAllWirelessStates
- else
- toshset -bluetooth on
- fi
- else
- toggleAllWirelessStates
- fi
-else
- toggleAllWirelessStates
-fi
+++ /dev/null
-#!/bin/sh
-
-test -f /usr/share/acpi-support/key-constants || exit 0
-
-for device in /sys/devices/platform/dock.*; do
- [ -e "$device/type" ] || continue
- [ x$(cat "$device/type") = xdock_station ] || continue
- echo 1 > "$device/undock"
-done
+++ /dev/null
-#
-# Configuration file for the acpi-support package
-#
-#
-# The acpi-support package is intended as "glue" to make special functions of
-# laptops work. Specifically, it translates special function keys for some
-# laptop models into actions or generic function key presses.
-#
-
-
-#
-# Suspend/hibernate method
-# ------------------------
-#
-# When gnome-power-manager or klaptopdaemon are running, acpi-support will
-# translate the suspend and hibernate keys of laptops into special "suspend"
-# and "hibernate" keys that these daemons handle.
-#
-# Only in situations where there is no gnome-power-manager or klaptopdaemon
-# running, acpi-support needs to perform suspend/hibernate in some other way.
-# There are several options for this. The options are:
-#
-# dbus-pm:
-# Perform suspend and hibernate actions via a DBUS request to the power
-# management daemon. This works for power management daemons that we don't
-# know of. (For gnome-power-manager and klaptopdaemon this will do nothing,
-# since those will be detected when they are running, and triggered using
-# a virtual keypress.)
-#
-# dbus-hal:
-# Perform suspend and hibernate actions via a DBUS request directly to HAL,
-# bypassing any running power management daemons.
-#
-# pm-utils:
-# Use pm-suspend and pm-hibernate to suspend and hibernate. (The dbus method
-# normally results in this as well, but calls through dbus. Use this option
-# only if you don't have dbus installed.)
-#
-# hibernate:
-# Use the hibernate package to suspend and hibernate.
-#
-# acpi-support:
-# Use the legacy built-in suspend/hibernate support. (DEPRECATED)
-#
-# none:
-# Do not attempt to suspend/hibernate. Set SUSPEND_METHODS="none" to
-# disable suspend/hibernate handling in acpi-support.
-#
-# If you specify dbus or pm-utils, the result will normally be the same as when
-# you suspend from your desktop environment. If you specify "hibernate" or
-# "acpi-support", be aware that this probably does not match what your desktop
-# environment would do (unless you have managed to configure something so that
-# the DBUS power management interfaces call the hibernate package).
-#
-#
-# Please specify a space separated list of options. The recommended value is
-# "dbus pm-utils"
-#
-SUSPEND_METHODS="dbus-pm dbus-hal pm-utils"
-
-
-
-#
-# LEGACY BUILT IN SUSPEND SUPPORT (DEPRECATED)
-# --------------------------------------------
-#
-# These options only work for the "acpi-support" suspend method. This is NOT
-# recommended, but is retained for backward compatibility reasons.
-#
-
-# Comment the next line to disable ACPI suspend to RAM
-ACPI_SLEEP=true
-
-# Comment the next line to disable suspend to disk
-ACPI_HIBERNATE=true
-
-# Change the following to "standby" to use ACPI S1 sleep, rather than S3.
-# This will save less power, but may work on more machines
-ACPI_SLEEP_MODE=mem
-
-# Add modules to this list to have them removed before suspend and reloaded
-# on resume. An example would be MODULES="em8300 yenta_socket"
-#
-# Note that network cards and USB controllers will automatically be unloaded
-# unless they're listed in MODULES_WHITELIST
-MODULES=""
-
-# Add modules to this list to leave them in the kernel over suspend/resume
-MODULES_WHITELIST=""
-
-# Should we save and restore state using the VESA BIOS Extensions?
-SAVE_VBE_STATE=true
-
-# The file that we use to save the vbestate
-VBESTATE=/var/lib/acpi-support/vbestate
-
-# Should we attempt to warm-boot the video hardware on resume?
-POST_VIDEO=true
-
-# Save and restore video state?
-# SAVE_VIDEO_PCI_STATE=true
-
-# Should we switch the screen off with DPMS on suspend?
-USE_DPMS=true
-
-# Use Radeontool to switch the screen off? Seems to be needed on some machines
-# RADEON_LIGHT=true
-
-# Uncomment the next line to switch away from X and back again after resume.
-# This is needed for some hardware, but should be unnecessary on most.
-# DOUBLE_CONSOLE_SWITCH=true
-
-# Set the following to "platform" if you want to use ACPI to shut down
-# your machine on hibernation
-HIBERNATE_MODE=shutdown
-
-# Comment this out to disable screen locking on resume
-LOCK_SCREEN=true
-
-# Uncomment this line to have DMA disabled before suspend and reenabled
-# afterwards
-# DISABLE_DMA=true
-
-# Uncomment this line to attempt to reset the drive on resume. This seems
-# to be needed for some Sonys
-# RESET_DRIVE=true
-
-# Add services to this list to stop them before suspend and restart them in
-# the resume process.
-STOP_SERVICES=""
-
-# Restart Infra Red services on resume - off by default as it crashes some
-# machines
-RESTART_IRDA=false
-
-# Add to this list network interfaces that you don't want to be stopped
-# during suspend (in fact any network interface whose name starts with
-# a prefix given in this list is skipped)
-SKIP_INTERFACES="dummy qemu"
-
-# Note: to enable "laptop mode" (to spin down your hard drive for longer
-# periods of time), install the laptop-mode-tools package and configure
-# it in /etc/laptop-mode/laptop-mode.conf.
projects / config / bruni / etc-mint-new1.git / commitdiff