Tuesday, January 16, 2018
Saturday, November 26, 2016
It took me too long to find all these pieces and figure this out so I thought I would share it to make it easier for the next person. I needed to have packer create an AMI that includes an additional filesystem that is already formatted and mounted on system boot. At first I tried using ami_block_device_mappings, but the new ebs volumes were not re-created when an instance was launched. Then I found launch_block_device_mappings which causes an additional snapshot to be saved with the additional volume information.
In the amazon-ebs builder, I included a launch_block_device_mappings section with the details about the additional volume:
"builders": [Then I added a shell provisioner (it was the second one in the list) to format the filesystem and add it to /etc/fstab:
"provisioners": [You may notice that the device names are different between the builder and provisioner. The builder uses the AWS name for it (/dev/sde), while the provisioner commands are run on the linux box and must user the device names that linux uses (/dev/xvde). I haven't looked in to this much but my guess is that it is just a matter of how the linux device driver wants to name the device.
"sudo mkfs.ext4 /dev/xvde",
"sudo mkdir -p /var/www",
"echo '/dev/xvde /var/www ext4 defaults 1 2' | sudo dd of=/etc/fstab",
"sudo mount /var/www"
Thursday, December 31, 2015
To view an individual channel I use a URL like this:
In VLC I select "Open Network Stream" and plug in the URL and viola...
Wednesday, August 29, 2012
Today that has all changed after updating to google-musicmanager-beta-220.127.116.1122-0. When Music Manger asked me to log in I took a chance and tried using my "normal" Google password. To my surprise a window appeared asking me for my verification code. After entering the code I was in... no more looking up that application specific password to log in! I also tried stopping and restarting it and it logged back in without asking me for my password again... it finally remembers me!
Thanks Google for showing a little bit of love to us Linux nerds!
Saturday, August 4, 2012
Wednesday, February 13, 2008
I found the answer in Kavinda Munasinghe's Blog, and in two Google documents (here) and (here).
As I understand it Jabber/XMPP uses DNS entries to find the servers needed to talk to another domain. For example, if you want to talk to firstname.lastname@example.org, your Jabber server will use DNS to look up service (SRV) records for the jabber/xmpp service in the example.com domain. Here is an excerpt from the ejabberd documentation regarding the SRV records:
Putting it all togehter, the records needed for a Google Apps domain (example.com) are:
There are 3 SRV records that can be created for a Jabberd installation:_jabber._tcp.
-> . :5269
-> . :5269
-> . :5222
The first and second of these specify the host and the port for server-to-server (s2s) communications. There are two listings for this because the new XMPP protocol, regarding SRV records, is replacing the older Jabber standards. The third listing above specifies host and port for unencrypted client communications (c2s).
_xmpp-server._tcp.example.com. IN SRV 5 0 5269 xmpp-server.l.google.com.
_xmpp-server._tcp.example.com. IN SRV 20 0 5269 xmpp-server1.l.google.com.
_xmpp-server._tcp.example.com. IN SRV 20 0 5269 xmpp-server2.l.google.com.
_xmpp-server._tcp.example.com. IN SRV 20 0 5269 xmpp-server3.l.google.com.
_xmpp-server._tcp.example.com. IN SRV 20 0 5269 xmpp-server4.l.google.com.
_jabber._tcp.example.com. IN SRV 5 0 5269 xmpp-server.l.google.com.
_jabber._tcp.example.com. IN SRV 20 0 5269 xmpp-server1.l.google.com.
_jabber._tcp.example.com. IN SRV 20 0 5269 xmpp-server2.l.google.com.
_jabber._tcp.example.com. IN SRV 20 0 5269 xmpp-server3.l.google.com.
_jabber._tcp.example.com. IN SRV 20 0 5269 xmpp-server4.l.google.com.
_xmpp-client._tcp.example.com IN SRV 5 0 5222 talk.l.google.com
_xmpp-client._tcp.example.com IN SRV 20 0 5222 talk1.l.google.com
_xmpp-client._tcp.example.com IN SRV 20 0 5222 talk2.l.google.com
_xmpp-client._tcp.example.com IN SRV 20 0 5222 talk3.l.google.com
_xmpp-client._tcp.example.com IN SRV 20 0 5222 talk4.l.google.com