linux-modder

There's another reason too: 
Khaytsus> mikedep333: I, personally, am tired of your spamming your blog.
mikedep333> Khaytsus, you have persuaded me to blog less often.
Khaytsus> Spam less often too.  That'd be great.
mikedep333> K, I will send the commands to my botnet
* Khaytsus shakes

linux-modder

HexChat 2.11.0

GTK+ interface ........ : yes
Text interface ........ : no
Theme manager ......... : no

OpenSSL support ....... : yes
D-Bus support ......... : yes
libnotify support ..... : yes
libcanberra support ... : yes

linux-modder

##	assumes a b43 brcm43xx or bcma or broadcom-wl driver onboard
 
 
## 	installing inxi is highly helpful for this and many other things so lets install now:
 
sudo apt-get install inxi 
 
## or 
 
sudo yum/yast/zypper  install inxi 

linux-modder

########
For the purpose of this purpose of this tutorial NO RAID / Luks / EFI are in play ( I have separate Gist that address these cases)

For all LVM tutorials I assume a default GPT partition table is laid on the target drive however with a few changes can be done on a MBR / MSDOS install as long as the drive is <2Tb at which point MBR is no longer an option.

Default layout referenced in this write up is a follows ---the following sample output is the starting point i will explain how 
to create it as well.

[linuxdev@linuxdevel ~]$ lsblk
NAME                                       MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT

linux-modder

#########
For the purpose of this tutorial -- NO RAID / EFI are in play ( I have separate Gist that address these cases)
 
For all LVM tutorials I assume a default GPT partition table is laid on the target drive however with a few changes can be done on a MBR / MSDOS install as long as the drive is <2 Tb at which point MBR is no longer an option.


Default layout referenced in this write-up is a follows ---the following sample output is the starting point i will explain how 
to create it as well. with the luks crypt being an LVM inside sda3. 
 
[linuxdev@linuxdevel ~]$ lsblk

linux-modder

###From another gist member 


USING ecryptfs-recover-private TO RECOVER ENCRYPTED HOME IN MINT 17 CINNAMON
--------------------------------------
 
This has saved more than twice when somehow I found myself...without a backup ?!
 
My setup had encrypted and encrypted home.  If you only encrypted home then I believe you can start at:
 

linux-modder

######     This tutorial is a merge of http://wiki.gentoo.org/wiki/EFI_Gentoo_End_to_End_Install/Preparing_the_LUKS    #######
######                    LVM_Filesystem_and_Boot_USB_Key and my previous tutorials on the subject                     #######

For the purpose of this tutorial -- NO RAID / EFI are in play ( I have separate Gist that address these cases)
 
For all LVM tutorials I assume a default GPT partition table is laid on the target drive however with a few changes can be done on a MBR / MSDOS install as long as the drive is <2 Tb at which point MBR is no longer an option.
 
 
Default layout referenced in this write-up is a follows ---the following sample output is the starting point i will explain how 
to create it as well. with the luks crypt being an LVM inside sda3. 

linux-modder

gist-paste /etc/fstab
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- gist (LoadError)
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/bin/gist-paste:7:in `<main>'

linux-modder

An error occurred while installing the items
session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.android.ide.eclipse.adt 23.0.4.1468518, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
Could not acquire the framework manipulator service.
Could not acquire the framework manipulator service.

linux-modder

~/testCloud :python testCloud.py --atomic http://mirror.umd.edu/fedora/linux/releases/21/Cloud/Images/x86_64/Fedora-Cloud-Atomic-20141203-21.x86_64.qcow2
Traceback (most recent call last):
  File "testCloud.py", line 21, in <module>
    import config
  File "/home/server/testCloud/config.py", line 10
    password:passwOrd
            ^
SyntaxError: invalid syntax