INSTALATION

1. Create the folders needed(just in case their not present)

$ mkdir -p ~/.local/{bin,share/applications}

2. Download the script & make it executable

$ cd ~/.local/bin
$ wget http://remmina-unity-launcher.googlecode.com/files/remmina-unity.sh
$ chmod u+x remmina-unity.sh

3. Run it

$ ./remmina-unity.sh

4. f the remmina launcher is Locked to the Unity Bar, unlock it.
5. Start remmina (<super>+”remmina”+<enter>) and it’s right click menu will have the shiny saved sessions list.
6. Now you can lock it back, but you’ll need to unlock/lock it on every list update (see issue 1)

source

sudo add-apt-repository ppa:ingalex/super-boot-manager

sudo apt-get update && sudo apt-get install super-boot-manager

source

Add:

+OptRenegotiate

source

HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal DWORD key with a value of 1.

source

try this or:
cat /proc/sys/net/ipv6/conf/all/disable_ipv6
0 means it’s enabled and 1 – disabled.

/etc/sysctl.conf:
#disable ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

sysctl -p

source

http://www.omgubuntu.co.uk/2011/05/five-beautifully-simple-conky-themes/

remaster_ubuntu.sh

apt-get install squashfs-tools genisoimage

Usage

All the following commands MUST be run as root (sudo).

• remaster_ubuntu.sh extract /path/to/original/ubuntu.iso /path/to/working/area
  This will extract the contents of the ISO into 2 subdirectories of path/to/working/area/ (should be empty initially):

  extract-cd/: the files needed to boot (isolinux config, kernel, initramfs, etc.), but not the root FS
  edit/: the root file system (complete with /etc, /usr, etc.)

• remaster_ubuntu.sh chroot /path/to/working/area
  This will start a root bash shell inside the root file system. Takes care of mounting /dev, /proc, /sys. In that shell, you can aptitude purge/install, edit /etc files, create users, even start X applications (xauth is configured), etc. But do NOT edit anything in /dev, as this will affect your host (the host’s /dev is mounted inside the chroot: anything changed in the chroot’s /dev is also changed in the host’s /dev !): avoid doing rm in /dev at this point ! Beware also that issuing some aptitude install commands might start /etc/init.d daemons which will run inside the chroot, even after you exited from it: you might have to kill these manually so that they don’t interfere with the host
  Note: This operation will also copy the host’s apt config into the working area, so that the same repositories can be used. The original ubuntu apt config will be restored when the regen command is issued

• remaster_ubuntu.sh regen /path/to/working/area SOME_NAME /path/to/dest/my.iso
  Generate a new ISO file from the extract-cd/ and edit/ dirs of the working area. The SOME_NAME param is just a dummy tag for the ISO image. The original apt configuration will be restored before the image is generated. You will still be able to use the chroot operation after a regen.

• remaster_ubuntu.sh release /path/to/working/area
  You will probably never need to use this operation manually. It is essentially an internal command used by the regen operation. But it might be important to use manually if you plan to remove /path/to/working/area (eg. rm -rf) after you chroot’ed to it at least once. This command makes sure the host will not be impacted by the removal of the working area (eg. it will unmount the /dev mount in the chroot). After this command, it is safe to remove completely the working area. You will still be able to use the chroot operation after a release

The extract and regen operations will be verbose and stop at the first error that occurs. You can of course run the extract operation just once, and run the chroot or regen operations thousands of times on the same working area. You can also run several chroot sessions in parallel. But be sure NOT to run a chroot operation while a regen is in progress.

source

packer -S oxygen-gtk3-git

$ ln -s /usr/share/themes/oxygen-gtk/gtk-3.0 ~/.config/gtk-3.0

source

On the primary node :
———————–

1.#pvcreate <new row diskfiel>

2.#vgextend vgname <new block device file>

3.export the map file in preview mode
#vgexport -v -p -s -m /tmp/vgname.map <vgname>

4.copy the map file to the adoptive node

On the adoptive node.
——————–
1.Note the minor number of the VG which ur goung to remove.
#ll /dev/vgname/group

2. remove the VG from the node.
#vgexport <vgname>

3.create the VG directory and group file
#mkdir /dev/vgname
#mknod /dev/vgname/group c 64 <minor number, eg 0×090000 in the below eg. “get it from the ll command” >
eg:
# ll /dev/vg10/group
crw-r–r– 1 root sys 64 0×090000 Mar 14 23:21 /dev/vg99/group

4.import the volume group.
#vgimport -v -s -m /tmp/vgname.map vgname

5. Activate the vgname in read only mode to verify and then deactivate it once is ie verified.

#vgchange -a r vgname

#vgdisplay -v vgname # u can see the new disk

#vgchange -a n vgname

source

/opt/omni/lbin/.util

Within there is a line:

/bin/df -P -t psfs -t ext2 [snipped]

All you need to do so that Data Protector can recognise the ext4 filesystem is added a little snippet near the other filesystems:

‘-t ext4′

source