How to delete a command from the bash history / Hide an command from the bash history
Hide an command from the bash history:
Start a terminal and try
wget user:passwd@ftp.example.com/secret.tar.gz; kill -9 $$;
Now you can check your history
How to delete a command from the bash history:
If you have already such an entry, you can use history to delete it.
history # [...] # 849 uname -a # 850 wget user:passwd@ftp.example.com/secret.tar.gz # 851 ping blog.devnu11.net # [...]
Now you can delete your history with history -d 850 this line.
history -d 850
And see...
history # [...] # 849 uname -a # 850 history # 851 ping blog.devnu11.net # [...]
SLES11, SLES10 SP3, grml64 on HP DL360-G6
Wozu gibt es zertifizierte Hardware(listen), wenns dann doch nicht geht ?
Ein HP DL360-G6 mit einer NetXtreme BCM5709 Netzwerkkarte soll unter SLES10 (SP3) und SLES11 (GM) funktionieren (Quelle: HP und Novell). Aber irgendwie gehts dann doch nicht
Selbst mit dem HP ProLiant Support Pack (Version 8.30) ging es nicht. Auch die md5sum vom bnx2.ko Modul, die HP angibt, stimmt.
Als letzter Versuch war dann noch grml64 2009.10 (x86_64 & i386) dran, nur leider ging es hier auch nicht. Alle melden nur "Firmware not running. Aborting..." Super! Ich muss leider zugeben, ich konnte auch nicht alles testen z.B. Firmware patchen konnte ich nicht, da es nur eine Leihgabe aus einem anderen Fachbereich war.
Mal sehen wann ich wieder eine in die Finger bekomme....
Don’t try this at home – root shell Russian roulette
Don't try this at home!
[ $[$RANDOM%6] = 0 ] || rm -rf /;
Unless you really know what you are doing.
ZTE MF637 unter Ubuntu
Um den ZTE MF637 oder auch T-Mobile W'n'W Stick Fusion unter Ubuntu zum laufen zubekommen, braucht man den Stick (leider) nur einmal auf einem Windows installieren - sprich die Treiber, und sich dann via Hyperterminal auf den Diagnose Port zuverbinden und folgendes Kommando ausführen:
AT+ZCDRUN=8
Damit wird der Autostart vom Stick, also das virtuelle CD-ROM am Anfang, deaktiviert !
Geht mit 9.08, 9.10 usw.
DD-WRT PPPoE Passthrough (on WRT54G)
For a PPPoE Passthrough on DD-WRT, enable jffs and do the following steps on a *nix-based system
cd /tmp; wget http://kamikaze.openwrt.org/8.09.1/brcm-2.4/packages/rp-pppoe-relay_3.10-1_mipsel.ipk; tar zxf rp-pppoe-relay_3.10-1_mipsel.ipk; tar zxf data.tar.gz; scp usr/sbin/pppoe-relay root@:/tmp/
Start the relay agent on the router
/tmp/pppoe-relay -S vlan1 -C br0
Now you can start your pppoe client on your notebook.
Tested with a WRT54G and DD-WRT v23 !
Benchmarking Tape drives
Generally it is much better to create a ramdisk for this benchmark:
# mount -t tmpfs -o size=10G tmpfs /tmp/ramdisk;
or
# dd if=/dev/zero of=/dev/ram bs=1M count=10000;
# mkfs.ext3 /dev/ram;
# mount /dev/ram /tmp/ramdisk -o loop;
Normally your harddisk is to slow for a LTO3/4 or a Jaguar2/3 drive
- Create a 5G or 10G file
# dd if=/dev/urandom of=/tmp/ramdisk/urandom bs=1M count=5000; - Now load the tape and start the backup
# tar -cl -f- /tmp/ramdisk/urandom 2>/dev/null | mbuffer -L -s 256k -m 5G -P 85 > /dev/nstX;
For Jaguar2/3 (IBM) tapedrives you can reach up to 150mb/s over a 2GBit FC HBA - Now rewind the tape and restore
# mt -f /dev/nstX rewind
# < /dev/nstX mbuffer -L -s 256k -m 5G -p 25 | tar -x -f- 2>/dev/null;
Now check which is the best blocksize (-s 256k) for your drive. This must be the same for backup AND restore!
My results for a 2Gbit FC HBA, Jaguar2/3 drive and FC disk(s) on SLES10 SP2:
HDD -> Tape -> HDD (5G Cache, BS 256k): W 139mb/s peak 75mb/s avg R 137mb/s peak 84mb/s avg
RAM -> Tape -> RAM (1G Cache, BS 256k): W 139mb/s peak 126mb/s avg R 155mb/s peak 140mb/s avg
HDD -> Tape -> HDD (5G Cache, BS 512k): W 149mb/s peak 70mb/s avg R 137mb/s peak 84mb/s avg
RAM -> Tape -> RAM (1G Cache, BS 512k): W 149mb/s peak 131mb/s avg R 155mb/s peak 140mb/s avg
BS <256 or >512 jammed the drive.
For IBM tape drives exists the lin_tape driver which is only necessary for multipathing (or support from IBM *unverified* )
Xen virtualization with Intel-VT
Hej,
for a training i needed some pcs with a virtualization technology preferably from Intel (VT). The easiest way is to buy some pc components and to build thereof a pc. After my last selfmade pc i'm a little bit impaired on that score. So i needed a pre-build pc with a intel cpu, gigabit lan and if it possible: small-sized. So is started my research with my best friend google
After a while i found the transtec SENYO 610.
In the small configuration they have a
- Intel Celeron 585 (2.16 Ghz) / C2D T6500 (2.1 Ghz)
- 1 GB DDR2 RAM (up to 4GB RAM)
- 160GB 5400rpm (up to 500GB)
- Gigalan, Bluetooth
inside. But according to the Intel website both cpus didn't support the Intel VT
So i needed the big one and they have the following configuration
- C2D T8300 / C2D T9500
- 1 GB DDR2 RAM (up to 4GB RAM)
- 160GB 5400rpm (up to 500GB)
- Gigalan, Bluetooth, Wlan
So i order the big one with a C2D T8300, 4GB Ram and a 160GB (7200rpm) harddisk. Now i'm waiting for the postman
XEN: clocksource/0 Time went backwards
Everybody know about these sweet line(s):
clocksource/0: Time went backwards: delta=-5802595381342 shadow=440273248432 offset=11586903
To prevent this, add this line to your sysctl.conf
xen.independent_wallclock=1Next is, to add
extra="clocksource=jiffies"
to the config of your XEN domain (like /srv/xen/build.conf).
After all this, you can reboot the vm's or to get it working for your current kernel config type this in each vm:
sysctl -p echo "jiffies" > /sys/devices/system/clocksource/clocksource0/current_clocksource
At the moment i only know this from debian-based systems.
Building DD-WRT Firmware….Part One
Yeah...1 o'clock and i'm not able to sleep....
...and what happend when i'm not able to sleep ? I'm trying something new - yes, okay Christian would say i'm hacking ^^
20 minutes after i started the svn checkout from the dd-wrt source, i've read that the source is approximately 20GB huge - wtf ?
svn co svn://svn.dd-wrt.com/DD-WRT .
So now i try it next day...oh wait in a couple of hours
