Monthly Archives: January 2014


The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesnt work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.

If you are using Ubuntu:

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset”

removing vg and lvm after physical drive has been removed


/dev/vm_backups/backup read failed after 0 of 4096 at 995903864832: Input/output error
/dev/vm_backups/backup read failed after 0 of 4096 at 995903922176: Input/output error
/dev/vm_backups/backup read failed after 0 of 4096 at 0: Input/output error
/dev/vm_backups/backup read failed after 0 of 4096 at 4096: Input/output error

dmsetup remove vm_backups-backup


vgreduce –removemissing

Satisfy Any vs Satisfy All

The Satisfy directive controls how Authentication directives (used for password protection) and access directives (e.g. Allow/Deny) interact with each other. You can instruct your Apache server to allow requests if either authentication or access requirements are met. Or you can insist that all criteria are met before allowing the request.

run chrome as root on Fedora

Its not safe, but sometimes useful:

vi /usr/bin/google-chrome

export LD_LIBRARY_PATH export CHROME_VERSION_EXTRA=”stable” # We don’t want bug-buddy intercepting our crashes. export GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME exec -a “$0” “$HERE/chrome” “$@” –user-data-dir