X-Git-Url: http://git.grml.org/?a=blobdiff_plain;f=grml_tips;h=529b28941b054577058a9197d4e1c84d11c90ef6;hb=df7659aa275933f06f6c20bbb6e0e4dcf350ce8e;hp=21ff86c6e1d2436cabc884ebde564a81178caabd;hpb=0f7d60b21a1cd14b32a84069fa942ad64ab40e8a;p=grml-tips.git diff --git a/grml_tips b/grml_tips index 21ff86c..529b289 100644 --- a/grml_tips +++ b/grml_tips @@ -704,9 +704,9 @@ Write back the guessed table: Develop, test and use exploit code with the Metasploit Framework: cd /tmp -wget http://www.metasploit.com/tools/framework-2.7-snapshot.tar.gz -unp framework-2.7-snapshot.tar.gz -cd framework* +wget http://framework-mirrors.metasploit.com/msf/downloader/framework-3.0.tar.gz +unp framework-3.0.tar.gz +cd framework-3.0 ./msfcli -- Useful documentation: @@ -1756,12 +1756,16 @@ Start X and lock console via exiting: % startx 2>~/.xsession-errors &| exit -- -Which process is writing to disk? +Which process is writing to disk and/or causes the disk to spin up? + +First of all use lsof to check what's going on. Does not help? -> # echo 1 > /proc/sys/vm/block_dump -Warning: you must disable syslogd before you do this, or you must -make sure that kernel output is not logged. +The command sets a sysctl to cause the kernel to log all disk +writes. Please notice that there is a lot of data. So please +disable syslogd/syslog-ng before you do this, or you must make +sure that kernel output is not logged. When you're done, disable block dump using: # echo 0 > /proc/sys/vm/block_dump @@ -1769,6 +1773,10 @@ When you're done, disable block dump using: Alternative: laptop-mode-tools provides a tool named lm-profiler (laptop mode profiler) which handles block_dump on its own. + +See: $KERNEL-SOURCE/Documentation/laptop-mode.txt + +Also take a look at event-viewer(8) which is part of grml-debugtools. -- Install initrd via initramfs-tools for currently running kernel: @@ -2069,10 +2077,13 @@ xfs without vol_id: # xfs_admin -l /dev/sda1 reiserfs without vol_id: -# debugreiserfs /dev/sda1 | grep UUID +# debugreiserfs /dev/sda1 | grep -i label + +jfs without vol_id: +# jfs_tune -l /dev/sda1 | grep -i label reiser4 without vol_id: -# debugfs.reiser4 /dev/sda1 | grep uuid +# debugfs.reiser4 /dev/sda1 | grep -i label -- Check filesystem's UUID: @@ -2080,16 +2091,41 @@ generic way: # vol_id -u /dev/sda1 ext2/3 without vol_id: -# dumpe2fs /dev/sda1 | grep UUID +# dumpe2fs /dev/sda1 | grep -i UUID xfs without vol_id: # xfs_admin -u /dev/sda1 reiserfs without vol_id: -# debugreiserfs /dev/sda1 | grep LABEL +# debugreiserfs /dev/sda1 | grep -i UUID reiser4 without vol_id: -# debugfs.reiser4 /dev/sda1 | grep label +# debugfs.reiser4 /dev/sda1 | grep -i UUID +-- +Change a filesystem's LABEL: + +swap: +# mkswap -L $LABEL /dev/sda1 + +ext2/ext3: +# e2label /dev/sda1 $LABEL +# tune2fs -L $LABEL /dev/sda1 + +reiserfs: +# reiserfstune -l $LABEL /dev/sda1 + +jfs: +# jfs_tune -L $LABEL /dev/sda1 + +xfs: +# xfs_admin -L $LABEL /dev/sda1 + +fat/vfat: +# echo 'drive i: file="/dev/sda1"' >> ~/.mtoolsrc +# mlabel -s i:$LABEL + +ntfs: +# ntfslabel $LABEL /dev/sda1 -- Disable pdiffs feature of APT: @@ -2380,17 +2416,6 @@ EOF Start dnsmasq finally: # Restart dnsmasq -- -Find out which process(es) cause the disk to spin up: - -# echo 1 > /proc/sys/vm/block_dump - -The command sets a sysctl to cause the kernel to log all disk -writes. Please notice that there is a lot of data. - -See: $KERNEL-SOURCE/Documentation/laptop-mode.txt - -Also take a look at event-viewer(8). --- Display stats about memory allocations performed by a program: Usage example for 'ls': @@ -2475,7 +2500,11 @@ Configuration options relevant on harddisk installation: # tzconfig which adjusts /etc/timezone and /etc/localtime according - to the provided information. + to the provided information. Running: + + # dpkg-reconfigure tzdata + + might be useful as well. * /etc/default/rcS: set variable UTC according to your needs, whether your system clock is set to UTC (UTC='yes') or @@ -2497,7 +2526,7 @@ Configuration options relevant on harddisk installation: * If you change the time (using 'date --set ...', ntpdate,...) it is worth setting also the hardware clock to the correct time: - # hwclock --hctosys [--utc] + # hwclock --systohc [--utc] Remember to add the --utc -option if the hardware clock is set to UTC! @@ -2521,3 +2550,8 @@ Further information: http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html http://wiki.debian.org/TimeZoneChanges -- +Recorder shellscript session using script: + +% script -t 2>~/upgrade.time -a ~/upgrade.script +% scriptreplay ~/upgrade.time ~/upgrade.script +--