Connecting to UVic's eduroam wireless network using Ubuntu 18.04
Security: WPA2 Enterprise
Authentication: PEAP
CA Certificate: /etc/ssl/certs/GlobalSign_Root_CA_-_R3.pem
PEAP Version: Automatic
Inner Authentication: MSCHAPv2
Username: netlink@uvic.ca
Note that the cert above may be a symlink to
/usr/share/ca-certificates/mozilla/GlobalSign_Root_CA_-_R3.crt
Whatever file you point to, the md5sum of the cert that works is
221eb05e63024bb1b6420f8606d0c092
Registered for the MS Insider program and downloaded an ISO for Windows 10. Built a VM for testing, especially the new browser engine -- works fine with Agas. The VM won't scale the screen, though.
The data I pushed out of MS SQL is kind of cruft-ey. I'm using some sed commands to clean up:
sed -i '/^-- /d' CGWP_data.sql
sed -i '/^LOCK TABLES/d' CGWP_data.sql
sed -i '/^\/\*\!/d' CGWP_data.sql
sed -i '/^UNLOCK TABLES/d' CGWP_data.sql
sed -i '/^[[:space:]]*$/d' CGWP_data.sql
csplit CGWP_data.sql '/^INSERT INTO/'
the csplit doesn't work properly though. I'll look in to it another day.
I've added a cron.daily script that will run zsync and pull down the most recent ISOs that we're likely to want around HCMC - specifically, it will grab the Trusty desktop, server, and Gnome-shell ISOs and store them in the ${SERVER_URL}/hcmc/iso directory.
It looks like this:
#!/bin/bash zsync -qo /var/www/hcmc/iso/ubuntu-14.04-desktop-amd64.iso http://ubuntu-releases.mirror.nexicom.net/trusty/ubuntu-14.04-desktop-amd64.iso.zsync zsync -qo /var/www/hcmc/iso/ubuntu-14.04-server-amd64.iso http://ubuntu-releases.mirror.nexicom.net/trusty/ubuntu-14.04-server-amd64.iso.zsync zsync -qo /var/www/hcmc/iso/ubuntu-gnome-14.04-desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/trusty/release/ubuntu-gnome-14.04-desktop-amd64.iso.zsync zsync -qo /var/www/hcmc/iso/daily-desktop-amd64.iso http://cdimage.ubuntu.com/daily-live/current/utopic-desktop-amd64.iso.zsync rm -rf /var/www/hcmc/iso/*.zs-old
--args: q is for quiet, o is for output file. In this case it includes an explicit path to the output file
I knew I was taking a chance as the repo is for RHEL 6 and the machine is RHEL 5, but I figured "it's php, what can go wrong?" This is what went wrong:
owncloud-6.0.1-5.1.noarch from isv_ownCloud_community has depsolving problems
--> Missing Dependency: php-pear-Net-Curl is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
php53-common-5.3.3-22.el5_10.x86_64 from rhel-x86_64-server-5 has depsolving problems
--> php53-common conflicts with php-common
owncloud-6.0.1-5.1.noarch from isv_ownCloud_community has depsolving problems
--> Missing Dependency: php-pear-MDB2-Driver-mysqli is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
owncloud-6.0.1-5.1.noarch from isv_ownCloud_community has depsolving problems
--> Missing Dependency: php-pear-MDB2-Driver-mysqli is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
owncloud-6.0.1-5.1.noarch from isv_ownCloud_community has depsolving problems
--> Missing Dependency: php-pear-Net-Curl is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
Error: Missing Dependency: php-pear-Net-Curl is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
Error: php53-common conflicts with php-common
Error: Missing Dependency: php-pear-MDB2-Driver-mysqli is needed by package owncloud-6.0.1-5.1.noarch (isv_ownCloud_community)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
Owncloud install is now on hold...
I've spent a couple of days trying and failing over the weekend to build an Ubuntu 12.04 VM which was able to build and run Android apps using the Titanium Appcelerator IDE. The requirements are very confusing and the whole system is quite fragile. At home I was working with a 64-bit VM, but I've now given up on that idea because ia32-libs seems to be required and that's no longer provided by Ubuntu. I've now built a 32-bit VM, and after much hassle I've got things building for Android and running on the Android emulator. The basic rules:
When you first run Titanium, let it do the updates it identifies; then restart it to confirm that it succeeded and doesn't ask you again (several times I've been caught in a loop where it installs, but thinks it hasn't, so tries again every time you start it up). Then install the platform SDKs. I succeeded in installing Android and Tizen, but Blackberry keeps failing.
Did a test setup this morning for using the large-screen TV station for Skype video-conferencing, using my cheapo camera, one of the Apex condenser mics and one of the Art mic pres. This is the setup and settings that worked best:
This proves to be more complicated than you might think. I assumed you could copy a vm (its folder with config file and settings, and its HD vdi file) to a new machine and just run it. No no no, that would be too easy, at least in the case of Windows vms. What you have to do is to clone the vm on the original machine, then copy the clone to a new machine (make sure you never run it on the original machine before moving it). Then when you first run it on the new machine, you'll have to re-activate it (choose the least intrusive option when asked; it works OK), and then it'll run OK.
Other things I've learned in the process of migrating machines from one Linux host to another: my new machine did not have Intel VTx virtualization options turned on in the bios, so I had to do that. I also had to reconfigure a couple of my non-Windows vms after moving them, because they were originally set up as generic "Linux", but were actually CentOS 64-bit, and on the new machine they wouldn't run unless configured in the vm settings as "Red Hat 64-bit".
I haven't yet moved the really crucial Windows 7 vm. I'll report back after trying that.