yarapavan

Keybase proof

I hereby claim:

• I am yarapavan on github.
• I am pavanyara (https://keybase.io/pavanyara) on keybase.
• I have a public key ASCJtRaanIoF534oaamIw7LrYtdrQzG0V2stYtBmOAmZvgo

To claim this, I am signing this object:

yarapavan

Keybase proof

I hereby claim:

• I am yarapavan on github.
• I am pavanyara (https://keybase.io/pavanyara) on keybase.
• I have a public key ASCTtjOIP74_WEXbYs9Qj7KWHkhA5rn54ftx5QOaijLGigo

To claim this, I am signing this object:

yarapavan

adb devices
adb shell
# enter shell prompt


pm uninstall -k --user 0 com.google.android.googlequicksearchbox

pm uninstall -k --user 0 com.xiaomi.mipicks

pm uninstall -k --user 0 com.android.browser

yarapavan

AWS new instance type which are full HVM, utilizes NVMe interface for accessing the EBS volume, instead of paravirtual driver on HVM AMI.

With the following instances, EBS volumes are exposed as NVMe block devices: C5, C5d, i3.metal, M5, and M5d. The device names are /dev/nvme0n1, /dev/nvme1n1, and so on. The device names that you specify in a block device mapping are renamed using NVMe device names (/dev/nvme[0-26]n1).

Please type sudo lsblk to get the device listing e.g. when I have created another volume and attached as /dev/sdb, it is being shown as nvme1n1.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:1 0 30G 0 disk
nvme0n1p1 259:2 0 1M 0 part

yarapavan

     

    *_SOME USEFUL  WEBSITES  ONLINE EDUCATIONAL SUPPORT_*

    www.khanacademy.org
    www.academicearths.org
    www.coursera.com
    www.edx.org

yarapavan

BEGIN MESSAGE.
L70woFBuTaP11QN TCWefR6zIXLyrKu b0F45yGOgZwnf1H xAYaasPsv5ql5nR
fnPiGLVpFk7aMgT OgrX2PLSbk7TCKq 6Xr2MZHgg6V7AWU xicGOkb0xyAXXdp
0ICW9AgdWOT5JOs vtQFmPZNuMpkQmU SrTYzeUaKhOJ0Nn Ib3pWjEOHtkA0Iw
gNWLa0fXHUfHdxj JXUpiXKiUk4wLNo 2FTsu29HFxl.
END MESSAGE.