How to run Ubuntu 18 on SSD and Windows 10 on HDD using dual boot

Get two pen drives and make one of them the recovery disk for windows.
Just search for recovery disk on windows and it will help you create
one, might take 2 hours.
Now your backup plan is ready in case things go south.

Download ISO from ubuntu site and burn it over the other pen drive using rufus
Change boot order in windows bios to boot from pen drive first and
move HDD after that.

Restart pc and let it boot from usb and select the install option
Navigate to the page where it asks you if you want to install along
windows or erase or select something else

You need to select something else, assuming your SSD is 256 gig and
your RAM is 8 gig.
Now identify your ssd in the disk section and make two partitions

e. g /dev/sdb5 230 GB / on WD256DIAXX


SWAP primary at the end 16 GB
ext4 primary at the front left over 230~ gb

MOST important make sure boot loader (option at the bottom) is set to
the master hdd where windows MBR resides so that
GRUB is updated correctly, if you mess up this option ubuntu won't be
added to GRUB.

Now just do next next and it will install and reboot later, it will work fine
Ubuntu will work out of ssd with a grub entry and windows will work
from grub /dev/sda

It worked for me !

Login to docker vm without password default vm

ssh -i /path to id_rsa in .docker/machine folder docker@ ip of the vm

good to have it bridged so that ip is available in host.

Log into Minikube via putty

Get the ppk file via puttygen , import the id_rsa files in minikube/machines folder and import

via the conversion tab on putty gen, save the ppk and use it on the putty ssh options.

make sure you select the SHa1-rsa(2048 bits) while saving ppk else it won't work.

on_picture_save event motion.conf raspberry pi

If you are tying to fire an FTp or shell/java/python command on the on_picture_save event, and its  highly likely

that it is not firing, reason could be that motion user is not able to run  your command at all. 

Do a switch user to pi and try to run that command manually and see if their are any permission issues.

Do a chmod/chown of the file/dir your command is interacting with, check the absolute/relative paths your command

is executing, also do a grep on the /var/log/*.log for errors on your command name, check the motion log file on.

/tmp/motion/motion.log 

enable the debug log inside the motion.conf file by changing the level to 8 

also if you are running motion on jessie and upgraded from wheezy , these kind of problem will occur.