Monday, May 7, 2018

feeding giraffes at the zoo



Visit to feed the giraffes and other critters on 4/21/2018.

Barb feeding her turn.














gif movie feeding the critter

https://gph.is/2FSUfx2

wifey










-30-

Friday, May 4, 2018

Developer mode on Samsung Galaxy Note 4 (and possibly others)


Rather than having the developer option switch on the "About Device" and having a simple switch for it, they have hidden it on the Build Number info.

Multi tapping it three times will reveal the Developer options bar on the phone.   The video below illustrates it.

Other info pages erroneously state that the older mode applies to the Note 4, but it does not.

video

-30-

Tuesday, April 24, 2018

Error 53, or not available error on Windows 10


Microsoft in their infinite wisdom have horribly broken SMB1 functionality on Windows 10.  No simple way to turn it back on, nor any explanation of why it is broken.

When you try to connect to a share via the protocol \\192.168.1.1\share you get an error not available, or an error 53.

The page below is an extended explanation of the justification, FWIW.  If there was a comprehensible error or change there would be less sarcasm and criticism here,  but just removing an insecure and broken protocol that they invented which was wrong and not putting in a way to recover when a release upgrade is made is just nuts.

When you upgrade to the 1709 creator release, or so, you will see this happen with your shares that have SMB1 and no SMB2 version support.  FWIW, I believe the latest and approved SMB is 4. 

https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709

Knowledge base workaround to re-enable it or get it back

https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server

seems to be in the same spot you enable and install the Ubuntu shell support

Windows server



Server Manager - Dashboard method

Windows 8 and 10

Add-Remove Programs client method

-30-

Saturday, April 21, 2018

Bluetooth serial Raspberry Pi 3


set up raspberry pi 3 bluetooth to allow serial connection once paired.

https://hacks.mozilla.org/2017/02/headless-raspberry-pi-configuration-over-bluetooth/

Basic part of above which covers setting up bluetooth connection.  No pass code, all parings accepted.

rfcomm connects and presents a shell session on connection w/o password, so more can be done to secure this.

You’ll create this file in the /home/pi directory, like so:

$ sudo nano /home/pi/btserial.sh
 
Add the following lines to the script:

#!/bin/bash -e

#Edit the display name of the RaspberryPi so you can distinguish
#your unit from others in the Bluetooth console
#(very useful in a class setting)

echo PRETTY_HOSTNAME=raspberrypi > /etc/machine-info

# Edit /lib/systemd/system/bluetooth.service to enable BT services
sudo sed -i: 's|^Exec.*toothd$| \
ExecStart=/usr/lib/bluetooth/bluetoothd -C \
ExecStartPost=/usr/bin/sdptool add SP \
ExecStartPost=/bin/hciconfig hci0 piscan \
|g' /lib/systemd/system/bluetooth.service

# create /etc/systemd/system/rfcomm.service to enable 
# the Bluetooth serial port from systemctl
sudo cat <<EOF | sudo tee /etc/systemd/system/rfcomm.service > /dev/null
[Unit]
Description=RFCOMM service
After=bluetooth.service
Requires=bluetooth.service

[Service]
ExecStart=/usr/bin/rfcomm watch hci0 1 getty rfcomm0 115200 vt100 -a pi

[Install]
WantedBy=multi-user.target
EOF

# enable the new rfcomm service
sudo systemctl enable rfcomm

# start the rfcomm service
sudo systemctl restart rfcomm
 
Save the file, and then make it executable by updating its permissions like so:

$ chmod 755 /home/pi/btserial.sh
 
Now you have the basics of the script required to turn on the Bluetooth service and configure it.  But to do this 100% headless, you’ll need to run this new script on startup. Let’s edit /etc/rc.local to launch this script automatically.

$ sudo nano /etc/rc.local
 
Add the following lines after the initial comments:

#Launch bluetooth service startup script /home/pi/btserial.sh
sudo /home/pi/btserial.sh &
 
Save the rc.local script, unmount the image, and write it to an SD Card using your favorite tool (mine is ApplePiBaker).
Now you are ready to go.  Plug in power to the Rpi and give it 30 seconds or so to startup. Then unplug it, and plug it in again and let it boot up a second time.  Restarting the Bluetooth service doesn’t work correctly, so we need to reboot.
-30-