I recently had a hard drive crash on box at work. The important files were on a software raid 5 array, but the root filesystem (with the majority of the OS) were on a separate IDE hard drive.
Only the IDE drive crashed, but I needed to remount the raid array. Here are the commands needed to reconstruct & remount a raid array with a Gentoo live cd:
Most of you know that you need to save your iptables changes using service iptables save before rebooting on Redhat, or else you’lllose all your rules. I brought up the setting IPTABLES_SAVE_ON_STOP to “yes” in /etc/sysconfig/iptables-config. There’s some pretty cool settings in there . Read on for details.
Continue reading ‘/etc/sysconfig/iptables-config in RHEL/CentOS’ »
If you want an easy way to keep commands out of your ~/.bash_history, do the following:
put this in your .bashrc:
export HISTCONTROL=ignorespace
then in a new bash session when you type in a command, if you put a space before it, it doesn’t appear in your history.
$echo hello #in history
$ echo hello #not in history
After testing this on a couple of emerges I am quite confident it works AS LONG AS YOU HAVE ENOUGH RAM – enough is 768M or more, although may be okay on 512M with a minimal desktop or X-less server. Tested on three machines with (768M, 1G, and 3G of RAM). The emerge of xorg-server went from 1.5 hours to about 20 minutes on an athlon-xp, for example.
Portage uses /var/tmp/portage (by default) as it’s working directory, everything is built in there before it gets merged to /. So, why not stick /var/tmp/portage in RAM? It’s a tmp directory after all, saves all that I/O bottleneck…
Interested? Okay, here’s what you have to do…
Continue reading ‘Speed up Emerge by compiling in RAM with tmpfs’ »
A co-worker of mine did this and shared with me, so i thought I’d continue spreading it around. If you have multiple gnu screen sessions going at once, wouldn’t it be nice to visually tell them apart without spending time to read the session name of each or trying to see what was going on within each?
The best way would be to color code the caption and hardlinestatus lines and be able to easily select a “color” per screen session and that’s what he and I did. Using C-g, we/you can easily cycle through various “themes”. This could also be useful if you wanted to cycle through mutiple hardstatus lines that displayed different information too if that’s the route you’d like to go. Anyways here it goes.
In Arch if you have the vga=793 (or whatever size) on your kernel line in /boot/grub/menu.list, you may have the Arch Logo at the top of your screen during boot. On vanilla or unmodified kernels, you’ll get a Tux logo. You get one logo per processor.
Example:
Click for Larger
Some don’t like it, and it’s pretty easy to get rid of. Simply do the following:
In /boot/grub/menu.list change
title Arch Linux root (hd0,2) kernel /boot/vmlinuz26 root=/dev/sda3 ro vga=773 initrd /boot/kernel26.img totitle Arch Linux root (hd0,2) kernel /boot/vmlinuz26 root=/dev/sda3 ro vga=773 logo.nologo initrd /boot/kernel26.img
Like your large monitor but tire of getting everything to just fit on the screen? I got tired of it a while back and switched to wmii, but now I have been trying out xmonad, another tiling window manager.
A tiling window manager arranges your windows in a grid. This maximizes window sizes and prevents any window from obscuring another. In other words, unless you have transparency going on, or switch to a viewing area with no windows open; you won’t see your desktop. Here’s a screenshot courtesy of pbrisbin.
Click for Larger
So, you have just installed Debian GNU/Linux. Good for you! But, what now? All you have is a black screen in front of you with no mouse pointer or application menu or anything! What gives?!
What you need now is to install a Desktop Environment. Don’t fret, it’s actually pretty easy.
Continue reading ‘Install X Window System and a Desktop Environment in Debian’ »
When you use a socks proxy with firefox (with SSH for instance) the dns lookups are done via your default gateway. Which makes the whole thing pointless if you’re trying to be private. This setting makes the dns lookups go out over the tunnel where they can’t be sniffed.
1. go to about:config
2. search for network.proxy.socks_remote_dns
3. Set to true, which will have the proxy server perform DNS lookups.
