Uncategorized Archive

Forwarding multicast on Ubiquiti

Posted October 30, 2017 By Landis V

May be relevant to some things I’d like to try.

https://community.ubnt.com/t5/EdgeMAX/mDNS-bonjour-forwarding/td-p/414093

Be the first to comment

DIY HDPE Blocks

Posted October 24, 2017 By Landis V

Had a post a while back with a link to a Garage Journal forum thread where a guy did some great tool organization by milling HDPE blocks. Some info on DIY HDPE blocks.
http://www.instructables.com/id/HDPE-Blocks-From-Plastic-Bottles/

And machines for working with plastic (shredding, extruding, casting, etc.).
https://preciousplastic.com/en/machines.html

Also read some things about using HDPE as a filament for 3D printing.  Not as easy as PLA or ABS, but sounds like it is do-able.

Be the first to comment

IR remote controls revisited

Posted July 22, 2017 By Landis V

I posted a while back about building a device to use as a universal remote control, where I could program commands that were relevant to devices in my living room, and have since been thinking about taking further actions towards integrating them with Alexa. I have a Harmony Hub, but the whole scene thing just doesn’t do what I really want – or does so in a kludgy fashion – most of the time. I’ve run across a few things in the past few days that might be useful in furthering the concept. The webmote link in my previous post may also be a viable option, since I’ve picked up some Arduinos and a tinker kit since I posted that – hoping it contains an IR receiver.

Right now, just need to get some tabs closed out, so posting a few of the relevant links I’ve run across so I can revisit them later.
Irdroid USB Infrared Transmitter, around $30
Irdroid-RPi Transceiver, around $20
irkit open source IR transceiver

Be the first to comment

VM System With VGA Pass-Through

Posted March 31, 2015 By Landis V

Hardware hangup note for Ctrl+C to get past.
http://www.reddit.com/r/debian/comments/25h49k/debain_wheezy_network_installation_freezes_after/

Configured LVM environment with /home, /usr/, and /var on spinning platter drive.

Configured an IP reservation on my DHCP server, though I may change this to a true static address at some point.

Instructions for linux-headers and virtualbox setup:  https://wiki.debian.org/VirtualBox

Downloaded the extension pack with wget http://download.virtualbox.org/virtualbox/4.1.36/Oracle_VM_VirtualBox_Extension_Pack-4.1.36-97684.vbox-extpack (NOTE:  you will need to download the appropriate version for your installed VirtualBox version.  Run vboxmanage -v and compare the output version to the versions available at https://www.virtualbox.org/wiki/Downloads; it apears you will need to match at least Major.Minor version numbers) and installed using instructions at https://www.virtualbox.org/manual/ch08.html#vboxmanage-extpack.

Created a separate logical volume on my SSD drive.  Dedicated it to the Win10 guest (see https://wiki.archlinux.org/index.php/VirtualBox#Create_a_VM_configuration_to_boot_from_the_physical_drive).

Created a VM from the CLI.  Had to actually go into the BIOS and enable AMD-V on my Gigabyte 78LMT-USB3 as it was disabled.  Could not get the version of VirtualBox included with the Debian distribution to give anything except the “Your PC needs to restart” 0x0000005D error, even when trying to force the NX bit using info for setting CMPXCHG16B as found at http://www.makeuseof.com/tag/try-windows-10-youre-running-linux/.  Ultimately ended up loosely following instructions from http://www.admin-magazine.com/Articles/Server-Virtualization-with-VirtualBox but substituting “wheezy contrib” for “lucid contrib” early in the instructions, and substituting 4.3 for 4.1, then running a “modifyvm” and setting ostype to Windows81_64.  Once this was done, I was able to start the install process.  Yay.

Had to modify the e1000g0 adapter config from http://www.perkin.org.uk/posts/create-virtualbox-vm-from-the-command-line.html to instead be “eth0” since I’m on a linux box (also had to remove it before re-adding, got an error when even attempting to start the machine).

Mouse pointer was batty, like it was scaled.  Ended up downloading the appropriate VirtualBox guest additions to the host machine, mounting them in the DVD drive, selecting the AMD64 file, bringing up properties and setting to compatibility mode Windows 8 (can’t seem to locate where I found this), and was able to install.  Pointer synced, system is on the web.

Second Steps – Debian LXC Guest for KDE

Debian 7.8

#From https://wiki.debian.org/LXC - loosely

apt-get install lxc
apt-get install bridge-utils libvirt-bin debootstrap

# Failed with:
# Failed to fetch http://security.debian.org/pool/updates/main/libx/libxml2/libxml2-utils_2.8.0+dfsg1-7+wheezy3_amd64.deb 404 Not Found [IP: 128.31.0.63 80]
# E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

apt-get
apt-get install bridge-utils libvirt-bin debootstrap

# Successful this time

echo -e "cgroup\t/sys/fs/cgroup\tcgroup\tdefaults\t0\t0" >>/etc/fstab
mount /sys/fs/cgroup
mount

# Confirmed that cgroup is mounted

lxc-checkconfig

# All show enabled
# Check out http://www.turnkeylinux.org/blog/announcing-turnkey-lxc, maybe add
# Turnkey template for some other functionality on this box
# Switched tracks and decided to try out Docker
# From http://docs.docker.com/installation/debian/#debian-wheezystable-7x-64-bit

echo "deb http://http.debian.net/debian wheezy-backports main" >> /etc/apt/sources.list
apt-get update
apt-get install -t wheezy-backports linux-image-amd64
reboot

# SSH'ed back into machine, verify new kernel

uname -a
wget https://get.docker.com/
chmod +x index.html
gpasswd -a my-account docker
service docker restart

# Service apparently did not restart, so had to start it again manually

service docker start

# Now as non-root
# Determined the following from http://www.syncano.com/getting-started-docker/

docker pull ubuntu:14.10
docker images

# Lists the newly pulled image; attempted to run it.
docker run -t ubuntu:14.10

# At this point, continuously encountered an error similar to the following:
# FATA[0034] Error response from daemon: Cannot start container (container UUID here): [8] System error: write /sys/fs/cgroup/docker/(container UUID here)/cgroup.procs: no space left on device
# There is definitely space left on the device, I do not appear to be lacking inodes as others seem to have encountered similarly, and permissions look OK.
# Started to install strace to troubleshoot further... but I need to get an accounting system back online.
# Switched to a VirtualBox KDE environment plan.  I guess I can always kill it later :)

lvm lvcreate -L 10g -n kmm
wget http://peppermintos.com/iso/Peppermint-5-20140623-amd64.iso
vboxmanage createvm --name kmm --register
vboxmanage modifyvm kmm --memory 1024 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth0
VBoxManage internalcommands createrawvmdk -filename ~/VirtualBox\ VMs/kmm/kmmSSD.vmdk -rawdisk /dev/amdfx/kmm
vboxmanage storagectl kmm --name "SATA Controller" --add sata
vboxmanage storageattach kmm --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium ~/VirtualBox\ VMs/kmm/kmmSSD.vmdk
vboxmanage storageattach kmm --storagectl "SATA Controller" --port 1 --device 0 --type dvddrive --medium ./Peppermint-5-20140623-amd64.iso
vboxmanage modifyvm kmm --ostype Ubuntu_64 --vrde on --vrdeport 22888
vboxmanage startvm kmm --type headless

# Able to RDP in and started Peppermint install process.
Be the first to comment

RRNR quote

Posted March 1, 2015 By Landis V

The great lesson for democracies to learn is for the majority to give the minority a full, free opportunity to present their side of the case, and then for the minority, having failed to win a majority to their views, gracefully to submit and to recognize the action as that of the entire organization, and to cheerfully assist in carrying it out, until they can secure its repeal.

Be the first to comment

Blackberry Scones | Baking Bites

Posted June 22, 2014 By Landis V

http://bakingbites.com/2012/01/blackberry-scones/

These look awesome for a campsite breakfast.  I suspect you could pre-make the dough and just keep it cool for maybe a day or two, then knead in the berries and cook at the campsite.

Be the first to comment

Creating a new VirtualBox VM on the command line

Posted March 1, 2014 By Landis V

I finally removed a computer that I’ve had running for quite a while, configuring another “intermittently operational” system to run all the time.  I’d like to have the old system run as a VirtualBox VM on the new system.  My VirtualBox VMs are running headless as services using VboxVMService.  Further, one of my VirtualBox VMs runs an Ubuntu guest which itself runs Linux Containers guests for some small, lightweight hosts on my network.

I’ve got a couple of existing LXC guests that do some monitoring for me using Nagios, run a Gitlab instance, and a couple of others that I no longer need and will probably remove.  I’d also like to set up a couple of new hosts to run a small, simple webserver for my home network “homepage” with links to things I commonly use and a Puppet system to manage my configurations a little bit more efficiently (especially credentials if I look to expand the number of Linux hosts on my network; I’d like the logins to be maintained automatically, and very preferably to be key based).

My straight Nagios monitoring takes a bit more thought to maintain than I’d like, given the number of things on my mind at any given time, so that’s one of the first things I’d like to simplify.  However, from the point of view of simplicity, creating a dead simple web host (though I’d like to eventually integrate some DNS service discovery…) is the simplest.

I spun up a new, basic LXC with Apache, RCS, and a few Perl modules to load Foswiki onto for a basic intranet home page.

Finally attempting to spin a new VM from the command line… fails

VBoxVMService does not allow you to run the VirtualBox GUI at the same time, as I understand it.  As such, I assume that I will need to create any new native (non-LXC) guests I require from the command line.  This Oracle reference describes how to configure the VM instances from the CLI using the ‘vboxmanage’ command.  However, upon issuing a ‘vboxmanage list ostypes’ command, I discovered that even the CLI version appears to be dependent upon the same COM configuration that prevents the GUI from running.  So, I configured as stated at http://sourceforge.net/p/vboxvmservice/wiki/Runing%20VirtualBox%20GUI%20together%20with%20VBoxVmService/.  This didn’t take immediately, so I restarted.

Numerous hassles

I had a lot of problems being able to get back into VirtualBox to work on setting up a VM to replace the machine I took down, generally appearing to be related to permissions.  I’d run across a batch file that someone had written that supposedly sets the permissions appropriately to allow you to switch back and forth between the VirtualBox GUI and VBoxVMService, but it didn’t seem to be very effective.  I was finally successful after uninstalling VirtualBox, deleting the VirtualBox directory, reinstalling, then going into DCOMConfig and setting permissions back to defaults (everything on Security tab as “Use Defaults” and the Identity tab as “Launching User”).  That let me get back in and do some things.

Using a physical/raw disk in a VM

I referenced these instructions to configure the disk I had pulled from my old system as a raw disk for the VM.  A couple of notes on items that proved handy:

  • The command wmic diskdrive list brief under Windows 7 helps to identify the correct PhysicalDrive setting to use in creating the VMDK.
  • User Account Control under Windows 7 is a turd for configuring the physical disk as a VMDK.  I was able to get around this by going into User Accounts -> Change User Account Control Settings and slid the bar all the way to the bottom – i.e., don’t prompt me for anything (I didn’t reboot as the system told me I had to).  I was then able to create the VMDK under my local account, which has administrative privileges (previously I had received the error “VBoxManage.exe: error: Cannot open the raw disk ‘\\.\PhysicalDrive1’: VERR_ACCESS_DENIED
    VBoxManage.exe: error: The raw disk vmdk file was not created” under my own account and “VBoxManage.exe: error: Failed to create the VirtualBox object!
    VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) – Server execution failed (extended info not available)
    VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running orfailed to start” under a “runas administrator” command window.

This was a great idea until I determined that I couldn’t (or at least there wasn’t a method I could find) grant my user account raw/physical disk access under Windows 7 Home.  I can run VirtualBox as an administrator and launch the machine, booting from the physical drive, and everything works.  Unfortunately I’d prefer not to run as an administrator, so I will probably need to work on converting the physical disk to an image.  My goal is ultimately to get everything copied off of that drive anyway and eliminate the machine; I had just thought this might be a shortcut to save a step or two.

Be the first to comment