* create modline setting with cvt for desired resolution

* add new modline with xrandr --newmode

* add mode to output with xrandr --addmode

* set output and dimension with xrandr --output and --mode

The needed steps are done in

/etc/X11/Xsession.d/45custom_xrandr-settings

# $ cvt 1280 1024 60
# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
# Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 \
# -hsync +vsync
# $ xrandr
# Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
# HDMI-1 disconnected (normal left inverted right x axis y axis)
# VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
#    1024x768       60.0* 
#    800x600        60.3     56.2  
#    848x480        60.0  
#    640x480        59.9
xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 \
-hsync +vsync
xrandr --addmode VGA-1 1280x1024_60.00
# $ xrandr
# Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
# HDMI-1 disconnected (normal left inverted right x axis y axis)
# VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
#    1024x768       60.0* 
#    800x600        60.3     56.2  
#    848x480        60.0  
#    640x480        59.9  
#    1280x1024_60.00   59.9
xrandr --output VGA-1 --mode 1280x1024_60.00

[ view entry ] ( 1395 views )   |  print article

---

Server

needed packages: mgetty, pppd

start and stop mgetty on plugin of usbmodem (0572:1329 Conexant Systems (Rockwell), Inc.)

/etc/init/mgetty.conf

# mgetty - dialin daemon

description     "mgetty daemon"

start on tty-device-added KERNEL=ttyACM0
stop on tty-device-removed KERNEL=ttyACM0

respawn
exec /sbin/mgetty -s 115200 -D /dev/ttyACM0

/etc/mgetty/login.config

/AutoPPP/ - a_ppp /usr/sbin/pppd auth +chap -pap name dialinserver remotename dialer debug

I use chap instead of pap because of plain password used by pap.

/etc/ppp/chap-secrets

dialer dialinserver password *

/etc/ppp/options.ttyACM0

10.0.0.1:10.0.0.2

Client

needed packages: pppd

/etc/ppp/peers/dialinserver

noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/dialinserver"
debug
/dev/ttyS0
115200
defaultroute
noipdefault
name dialer
remotename dialinserver

/etc/chatscripts/dialinserver

ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE'
ABORT 'NO ANSWER' ABORT DELAYED
'' ATZ
OK-AT-OK "ATDTnumber"
CONNECT \d\c

/etc/ppp/chap-secrets

dialer dialinserver password *

Connect with "pon dialinserver" and disconnect with "poff dialinserver"

[ view entry ] ( 1064 views )   |  print article

---

sudo apt-get install kexec-tools

change LOAD_KEXEC to true in /etc/default/kexec

[ view entry ] ( 834 views )   |  print article

---

I got a funny viennese dialect keyboard, but after start using it i missed a key '<,>,|'

So i searched for a way to remap 'AltGr + y' to '|', 'AltGr + ,' to '<' and 'AltGr + .' to '>'

Console

evaluate the key to change with

#> sudo showkey -s

press the key

here y is 0x2c = 44
here , is 0x33 = 51
here . is 0x34 = 52

test remap with

echo "altgr keycode 44 = bar" | loadkeys

bar is a symbolic name i found at German-Howto

Finally i extended /etc/rc.local with

LOADKEYS=$(which loadkeys)
if [ -x $LOADKEYS ]; then
  cat << EOT | $LOADKEYS
altgr keycode 44 = bar
altgr keycode 51 = less
altgr keycode 52 = greater
EOT
  unset LOADKEYS
fi

Xorg

evaluate the key to change with

#> xev

press the key

here y is keycode 52
here , is keycode 59
here . is keycode 60

test remap with

xmodmap -e "keycode 52 = y Y y Y bar"

dump keys with

#> xmodmap -pke > ~/.Xmodmap

remove all lines except lines starting with desired keycodes to change.

my ~/.Xmodmap now looks like

keycode  52 = y Y y Y bar U203A guillemotright
keycode  59 = comma semicolon comma semicolon less multiply periodcentered
keycode  60 = period colon period colon greater division U2026

[ view entry ] ( 2487 views )   |  print article

---

These are scripts to backup system's and build an image for an usb stick or kvm for testing:

rescue.tar.gz

The only thing to configure is the backup-script:

All your partition's must have an UUID.

With "uuidgen | xargs mkswap /dev/sda1 -U" and "uuidgen | xargs tune2fs /dev/sda1 -U" you can generate one.


This is an example of a backup of a system with two partitions:

#!/bin/sh

cat >root_exclude <<EOF
/lost+found/*
/tmp/*
EOF

cat >var_exclude <<EOF
./tmp/*
./run/*
./lock/*
./log/messages*
./lost+found/*
EOF

sudo tar -cSp --one-file-system --numeric-owner --atime-preserve \
         --exclude-from=root_exclude -f $(hostname).root.tar /

sudo tar -cjSp --one-file-system --numeric-owner --atime-preserve \
         --exclude-from=var_exclude -f $(hostname).var.tar.bz2 --directory /var .

uuid() { sudo blkid -o value -s UUID /dev/$1; }
fstype() { sudo blkid -o value -s TYPE /dev/$1; }
inodesize() { sudo tune2fs -l /dev/$1 | grep "Inode size" | sed -e 's/[^0-9]//g'; }
raiduuid() { sudo sed -n "s/^.*$1.*UUID=\(.*\)/\1/p" /etc/mdadm/mdadm.conf; }
partitioninfo() { echo "$(echo $1|sed -e 's/[^0-9]//g') $(uuid $1) $(fstype $1)"; }

cat >$(hostname).cfg <<EOF
DISK_PARTITIONS=",1024,S;,10000,L,*;,,L"
ARCHIVES="$(partitioninfo sda2) $(hostname).root.tar.bz2
$(partitioninfo sda3) $(hostname).var.tar.bz2"
SWAP="1 $(uuid sda1)"
GRUB=1
GRUB1_PARTITION=1
GRUB1_INODESIZE=$(inodesize sda2)
EOF

* for each tar an exlude-file can be defined
* files are named HOSTNAME.root.tar.bz2, HOSTNAME.var.tar.bz2 and HOSTNAME.cfg
* this backup needs a small config-file (HOSTNAME.cfg)

DISK_PARTITIONS is used by sfdisk and has to be definded in its INPUT FORMAT
ARCHIVES takes a config line for each partition with an optional tar archive at the end
SWAP starts with the number of the partition and the uuid of it
GRUB needs the version of grub
GRUB1_PARTITION is only needed for grub 1 and is the boot partition (counting starts with 0)
GRUB1_INODESIZE is needed because older grub1 can not boot with a filesystem of different inode size

For a raid1 system with only one filesystem the config looks like

DISK_PARTITIONS=",8000,S;,,L,* ,8000,S;,,L,*"
RAID_UUIDS="$(raiduuid md0) $(raiduuid md1)"
ARCHIVES="$(partitioninfo md1) $(hostname).root.tar.bz2"
SWAP="0 $(uuid md0)"
GRUB=1
GRUB1_PARTITION=1
GRUB1_INODESIZE=$(inodesize md1)

After running the backup script HOSTNAME.root.tar.bz2, HOSTNAME.var.tar.bz2 and HOSTNAME.cfg are build.
Now you can run ./rescue-build.sh or copy these files to your backup server (where you put the files from other systems) and run there ./rescue-build.sh. Now you got a directory called image with all your archives, your running kernel and a configured initrd (initramfs).
With ./rescue-create-stick.sh /dev/STICKDEVICE your stick to restore is prepared (Warning all data on the stick is erased!).

With kvm you can test the restore process:

Therefore run sudo ./rescue-create-kmv-image.sh.
The build image can be mounted with sudo ./rescue-kvm-mount.sh to ./mnt and unmounted with sudo ./rescue-kvm-umount.sh.
Test the image with rescue-kvm-restore.sh and test the restored image with ./rescue-kvm-test.sh.



[ view entry ] ( 1500 views )   |  print article

---

<<First <Back | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | Next> Last>>

- Page Generated in 0.0496 seconds | Site Views: 3398