docs/hacks - uncategorized docs

content/blog.md

@@ -4,7 +4,6 @@ toc: false
 ---
 
 {{< cards >}}
-  {{< card link="/posts/mapping-of-physical-usb-ports-to-device-names/" title="Mapping of Physical USB ports to device filename on GNU/Linux" icon="arrow-circle-right"  >}}
   {{< card link="/posts/debian-maintainer/" title="Debian Maintainer Now!! " icon="arrow-circle-right"  >}}
   {{< card link="/posts/contributing-to-debian/" title="Contributing to Debian !!" icon="arrow-circle-right"  >}}
   {{< card link="/posts/software-freedom-camp-2021/" title="Software Freedom Camp 2021" icon="arrow-circle-right"  >}}

content/docs/hacks/_index.md

@@ -0,0 +1,9 @@
+---
+title: Hacks
+type: docs
+next: /docs/hacks/mapping-of-physical-usb-ports-to-device-names/
+sidebar:
+  open: false
+---
+
+If things are uncategorized,it goes to ```Hacks``` :)

content/docs/hacks/customize-qcow2-disk-image.md

@@ -0,0 +1,46 @@
+---
+type: docs
+title: "Customize .qcow2 image"
+---
+
+Tired of Debian Installer ):
+
+On Proxmox VE i had to go through the Debian Installer if i want to spin up a new VM,taking a lot of time and effort.
+
+1. Download the .qcow2 image from cloud.debian.org
+
+https://cloud.debian.org/images/cloud/bookworm/20230910-1499/debian-12-genericcloud-amd64-20230910-1499.qcow2 ,this is a generic cloud image which can be easily imported onto proxmox.
+
+2. Reset the root password on the disk image
+
+```$ virt-customize -a debian-10-genericcloud-amd64.qcow2 --root-password password:debian```
+
+By default the .qcow2 doesn't have any root password,so the disk image has be customized using virt-customize to add root password. 
+
+3. Increase size of .qcow2 disk image.
+By default the size of Debian Generic Cloud is 2GB, using qemu-img we can resize the disk image. 
+
+```
+qemu-img resize image.qcow2 +SIZE 
+```
+
+4. Import the disk image on Proxmox VE.
+
+Copy the image to ```/var/lib/vz/template/qemu/```.
+Create a VM on Proxmox VE without any media (do not attach any physical media) and delete any existing disk on proxmox.
+
+```
+qm importdisk 114 /var/lib/vz/template/qemu/debian-12-genericcloud-amd64-20230910-1499.qcow2 amogha -format qcow2
+```
+
+Execute the above ```qm importdisk``` on the proxmox server where ```114```is the VM id where in your case will be different.
+Refreshing the Proxmox GUI on the browser,attach the ```unused Hard Disk``` under ```Hardware```, also add a cloudInit drive and set ```IP address to dhcp``` to automatically assign IP address for both IPv4 and IPv6.
+
+Under ```Options``` update the boot order and check whether the hard disk which was added to be checklisted and prioritize it to first.
+
+```bash
+Another alternative way is to use Preseed file at boot which automates 
+debian installer,haven't tried that yet.
+
+:wq #for now
+```

content/docs/hacks/mapping-of-physical-usb-ports-to-device-names.md

@@ -0,0 +1,113 @@
+---
+type: docs
+title: "Mapping of Physical USB ports to Device Name on GNU/Linux"
+next: /docs/
+---
+
+## How to Map Physical USB ports to Device Names on GNU/Linux
+```bash{filename="lsusb command"}
+$ lsusb
+Bus 002 Device 004: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
+Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 003 Device 123: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
+Bus 003 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub             
+
+$ lsusb -t
+/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
+    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/7p, 5000M
+/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
+    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
+/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
+/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
+    |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
+        |__ Port 2: Dev 123, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
+/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
+    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
+        |__ Port 3: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
+/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
+    |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
+
+```
+
+"lsusb" is a utility of "usbutils" in GNU/Linux to display information about the USB Buses and the USB's attached to the buses.The output of the command displays the VendorID:ProductID and to which bus it is attached,the "Kingston Technology DataTraveler" bearing the VendorID:ProductID (0951:1666) attached to bus 003, the lsusb command with option "-t" provides a tree like output in a hierarchial structure.
+
+"lsblk" is a tree-like structure to identify devices and their partitions,and also displays device name (/dev/sd* if its a hard disk,/dev/nvme0n1 in case of SSD),size of the drive/partition,  whether it is a disk/partition and the device's mountpoints,here the /dev/sda* is the hard disk and sda1/2/5 are the partitions of the hard disk and /dev/sdb is the Kingston USB drive connected.
+
+```bash
+$ lsblk
+NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
+sda      8:0    0 119.2G  0 disk 
+├─sda1   8:1    0 118.3G  0 part /
+├─sda2   8:2    0     1K  0 part 
+└─sda5   8:5    0   976M  0 part [SWAP]
+sdb      8:16   1  28.9G  0 disk 
+sr0     11:0    1  1024M  0 rom  
+```
+
+```Suppose if there are multiple USB sticks attached to mutiple physical USB ports how to know which device names is mapped to which USB port ?```
+
+If there are multiple USB's attached how do we get to know USB drive's device file and to which port that USB is connected ?
+
+The answer is by /dev/disk/* 
+Everything in GNU/Linux is either a file or a directory,so even the disk are represented as files in GNU/Linux.
+```bash
+$  ls -ltrh /dev/disk/
+total 0
+drwxr-xr-x 2 root root 100 Aug 28 12:28 by-partuuid
+drwxr-xr-x 2 root root 100 Aug 29 09:49 by-uuid
+drwxr-xr-x 2 root root 260 Aug 29 09:49 by-path
+drwxr-xr-x 2 root root  60 Aug 29 09:49 by-label
+drwxr-xr-x 2 root root 160 Aug 29 09:49 by-id
+drwxr-xr-x 2 root root 260 Aug 29 09:49 by-diskseq
+```
+
+The USB disks can be identified by the Partition UUID, UUID of the disk, by path, by label of the disk and also by disk sequence.
+
+### By UUID(Universally Unique Identifier)
+```bash{filename="by uuid"}
+$ cat /etc/fstab 
+UUID=3341b336-0c26-4079-b3aa-faca8e2dd8b6 /               ext4    errors=remount-ro 0       1
+UUID=53b53d97-b5e4-43fe-b560-2a01f119b6cf none            swap    sw              0       0
+/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
+
+$ ls -ltrh /dev/disk/by-uuid/
+total 0
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 3341b336-0c26-4079-b3aa-faca8e2dd8b6 -> ../../sda1
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 53b53d97-b5e4-43fe-b560-2a01f119b6cf -> ../../sda5
+lrwxrwxrwx 1 root root  9 Aug 29 09:49 2010-10-06-11-43-04-00 -> ../../sdb
+```
+The device /dev/disk/by-uuid/3341b336-0c26-4079-b3aa-faca8e2dd8b6 is simply a symbolic link to actual an device,the reason being this is device name may change depending whether disk is attached or not,whereas these links will point to the same drive,so henceforth safer to use.
+
+
+
+### By-Label
+```bash{filename="by-label"}
+$ ls -ltrh /dev/disk/by-label/
+total 0
+lrwxrwxrwx 1 root root 9 Aug 29 09:49 VINAY-USB -> ../../sdb
+```
+Labels are easy, it avoids confusion in identifying disk, instead of remembering /dev/sda device file names.
+
+### By-Path
+```bash{filename="by-path"}
+$ ls -ltrh /dev/disk/by-path/
+total 0
+lrwxrwxrwx 1 root root  9 Aug 22 10:40 pci-0000:00:1f.2-ata-2.0 -> ../../sda
+lrwxrwxrwx 1 root root  9 Aug 22 10:40 pci-0000:00:1f.2-ata-2 -> ../../sda
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2-part2 -> ../../sda2
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2.0-part2 -> ../../sda2
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2-part1 -> ../../sda1
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2.0-part1 -> ../../sda1
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2-part5 -> ../../sda5
+lrwxrwxrwx 1 root root 10 Aug 22 10:40 pci-0000:00:1f.2-ata-2.0-part5 -> ../../sda5
+lrwxrwxrwx 1 root root  9 Aug 22 10:40 pci-0000:00:1f.2-ata-3.0 -> ../../sr0
+lrwxrwxrwx 1 root root  9 Aug 22 10:40 pci-0000:00:1f.2-ata-3 -> ../../sr0
+lrwxrwxrwx 1 root root  9 Aug 29 09:49 pci-0000:00:14.0-usb-0:4.2:1.0-scsi-0:0:0:0 -> ../../sdb
+```
+Here /dev/sdb is the USB device attached and "pci-0000:00:14.0-usb-0:4.2:1.0-scsi-0:0:0:0" file which represents the USB device describes that the USB device is connected from PCI bus to SCSI adapter."by-path" is the pci path of the disk device. this device file name is created depending on the shortest physical path to the device.
+"/dev/sda" the first SCSI drive on the first SCSI bus,/dev/sdb is the second SCSI drive and /dev/sdc is the third SCSI drive and so on.
+
+```
+:wq
+```
+

content/docs/interception-vimproved.md

@@ -1,6 +1,6 @@
 ---
 title: Interception Vimproved
-next: /docs/selfhosting/nextcloud
+next: /docs/openldap
 ---
 
 

content/docs/openldap.md

@@ -1,6 +1,7 @@
 ---
 title: OpenLDAP 
-prev: /docs/selfhosting/nextcloud
+next: /docs/selfhosting/nextcloud
+prev: /docs/interception-vimproved
 ---
 
 ### Directory Service
@@ -336,6 +337,8 @@ userPassword:: am9obg==
 
 #### Modifying existing entries
 
+1. Using ```ldapmodify``` to update entries. 
+
 Now to modify an already added record we use ldapmodify and the attributes that are to be modified are put into a separate file,here ```john-modify.ldif``` and to demonstrate here an OU ```Support```
 is added to the existing entry,along with ```People``` OU.
 
@@ -373,9 +376,54 @@ createTimestamp: 20230928112421Z
 entryCSN: 20230928120656.291224Z#000000#000#000000
 modifiersName: cn=admin,dc=vinay,dc=com
 modifyTimestamp: 20230928120656Z
+```
+
+2.Using ```ldapvi``` to update LDAP entries with a text editor.
+
+```bash{filename="ldapvi example"}
+$  ldapvi -d --host vinay.im 
+```
+```ldapvi```  is a ldap client using which we can search,modify and delete entries which is easier than ```ldapmodify```  instead of adding the updated records in a separate ```ldif``` file.
+ldapvi prompts to open text editor to modify entries,just similar to text editor.
+
+The above command will bind anonmously to hostname, here the hostname is ```vinay.im```.After making necessary changes in the entry save from the text editor.
+```
+# ldapvi -d --host nextcloud.vinay.com
+      3 entries read                                                                                                                                                                        
+add: 0, rename: 0, modify: 1, delete: 0
+Action? [yYqQvVebB*rsf+?] b
+
+
+--- Login
+
+--- Login
+
+--- Login
+Type M-h for help on key bindings.
+
+Filter or DN: cn=admin,dc=vinay,dc=im
+
+    Password: *****
+
+Bound as cn=admin,dc=vinay,dc=im.
+add: 0, rename: 0, modify: 1, delete: 0
+Action? [yYqQvVebB*rsf+?] y
+Done.
+```
+after saving and exiting from text editor, an interactive bash prompt ``` [yYqQvVebB*rsf+?]``` 
+
+```y``` to commit changes.
+
+```e``` to edit changes.
+
+```v``` to view changes as LDIF change records.
+
+```b``` to show login and rebind - we are trying to auth from admin and save the changes to LDAP entries.
+
 
 ```
 [Reference serverfault] https://serverfault.com/questions/290296/ldapadd-ldapmodify-clarifications-needed-about-these-commands
+
 #### Verifying the ```slapd.conf``` Configuration file
 
 ```bash
@@ -387,6 +435,8 @@ config file testing succeeded
 
 ```-v``` : enable verbose mode.
 
+
+
 #### Conventions in OpenLDAP
 
 dn - Distinguished Name  

content/posts/mapping-of-physical-usb-ports-to-device-names.md

@@ -5,6 +5,7 @@ weight: 10
 description: "Mapping of Physical USB ports to Device Names (/dev/sda) on GNU/Linux"
 tags: ["usb", "linux", "gnu/linux" , "gnu"]
 type: post
+draft: true
 ---
 
 ## How to Map Physical USB ports to Device Names on GNU/Linux