ko1ebayev

#!/bin/sh

apt update && apt install xfce4 xdm xfce4-xkb-plugin language-pack-ru -y

sed -i 's/allowed_users=console/allowed_users=anybody/' /etc/X11/Xwrapper.config

echo "xfce4-session" | tee ~/.xsession

systemctl enable xdm.service

ko1ebayev

type StatusChange = (property: string, previousValue: any, value: any) => void;
interface EmpoweredStatus {
    property: string;
    value: any;
    previousValue: any;
}

class EmpoweredFormControl<T extends AbstractControl> {
    private static readonly EMPOWER_KEY = '##empower##';
    private statusChangeHandlers: StatuChange[] = [];

ko1ebayev

# Known systemd bug https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320
# Bug description:  
# systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, 
# causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. 
# That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. 
# The effect is similar to bug 1624071 but for applications doing their own DNS lookups. 
# It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, 
# bypassing validation failures. And it makes failing queries take twice as long.
# /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active.

ko1ebayev

export function trackBy<T>(propertyPath?: keyof T) {
  return function(index: number, item: T) {
    return propertyPath ? get(item, propertyPath, index) : index;
  };
}

export function trackByIdentity<T>(index: number, item: T): T {
  return item;
}