ZFS and Linux unfortunately collide. M. Tim Jones has a paper on IBM developerWorks called Run ZFS on Linux.
ZFS and Linux unfortunately collide. M. Tim Jones has a paper on IBM developerWorks called Run ZFS on Linux.
While watching the SLLUG May presentation on SALT by Thomas S. Hatch, I was intrigued by his reference to ØMQ (ZeroMQ). This is a fascinating “intelligent” networking library, but some of the philosophy I found interesting. In the guide it says, for example:
Programming is a science dressed up as art, because most of us don’t understand the physics of software, and it’s rarely if ever taught. The physics of software is not algorithms, data structures, languages and abstractions. These are just tools we make, use, throw away. The real physics of software is the physics of people.
This clicked with me right away. Languages require almost no effort to pick up. Algorithms, etc. are useful toys selected by how well they match the current problem space. The most useful class that I took in university was Computer Theory, the mathematical underpinnings of software, but again it’s a tool.
From the beginning of my software crafting, I intuitively knew that software was about people. Early on I would tell people who approached me, “Write what you think you want, then write what would like in a dream world where anything is possible.” The first list is normally the list constrained by preconceptions of what can and cannot be done. The second list is usually what the client really wants. It’s a great way to trigger discussion on what the real problem space is. And, frequently, many of those items are actually quite feasible.
Code has to talk to code. Code has to be chatty, sociable, well-connected. Code has to run like the human brain, trillions of individual neurons firing off messages to each other, a massively parallel network with no central control, no single point of failure, yet able to solve immensely difficult problems.
I’m sill not convinced about the human brain analogy (a different topic), but I am convinced from my experience that this much is true. Code must talk to code, easily, impromptu, and in unexpected ways… but this hides the greater reality. It is people that drive the whole process. It must be easy for people to arrange the code chatter, and to change it at will to fit the changing needs and desires of individual humans.
While the implementation may show its age, the original Unix model of tiny specialized programs that can be easily threaded together has stood the test of time quite well. The old tools of sed, grep, find, etc. are bits of code that talk to code in a primitive way. Dated they may be, but Un*x and its relatives are the backbone of the Internet.
If you’ve done any work with threads, protocols, or networks, you’ll realize this is pretty much impossible. … Even connecting a few programs across a few sockets is plain nasty, when you start to handle real life situations. Trillions? The cost would be unimaginable. …
Today we face another software crisis, … Only the largest, richest firms can afford to create connected applications. There is a cloud, but it’s proprietary. Our data, our knowledge is disappearing from our personal computers into clouds that we cannot access, cannot compete with. Who owns our social networks? …
[W]hile the Internet offers the potential of massively connected code, the reality is that this is out of reach for most of us, and so, large interesting problems … remain unsolved because there is no way to connect the code, and thus no way to connect the brains that could work together to solve these problems.
Having worked on projects that have tackled pieces of the puzzle, this resonates with me also. Individuals, when left to their own devices to do clever things, can solve this. We have to not buy into the notion that traditional monolithic portals are The One True Way. It’s a seductive ancient paradigm, but software was made for Man. Man was not made for software.
Photography is not hard in an academic sense. The fundamentals are rooted in physics, but the principles are few and simple. Photography is applying those principles as a means to bring creative ideas inside of one’s head into being.
What makes photography hard is what makes every other artistic medium hard. One has to conceive of an idea, and master the skills to manipulate light and machinery needed to bring that idea into existence.
Furthermore, tools such as cameras, strobes, filters, software, etc. are merely resources for the use of the creator. They do not make one a creator, nor do they endow the skills required to fully use the resources. A novice will take terrible snapshots whether he has a cell phone or a $3,000 camera because he has the mind of a novice.
Becoming a photographer requires one to expand one’s understanding and ability to match the creative mind. This process, in turn, expands the creative mind further. This requires a new expansion of understanding and ability. And thus the cycle continues.
Line upon line, precept upon precept.
Chiaroscuro (key-ar-oh-skoo-roh) is a classic technique for giving visual depth to a two-dimensional image.
Mikko Reinikainen has on his Flikr page a wonderful, concise description that sums up this technique, using a 30º grid spot to illustrate.
Namahage are demons who terrorize lazy children. In the Oga peninsula, on New Year’s Eve, villagers dress up as namahage and drum. Would be a great performance to see live
Quick tutorial on using the graduated filters in LightRoom by David Terry.
Another local photographer posted a short YouTube video of the great photographer Ansel Adams speaking on visualization. The following are my comments on the subject.
As an artist in other media, I must go through the visualization stage. My pencil or brush can’t create an image by pressing a button. There are no short cuts.
Light-writing (photo-graphy) is a two-edged sword because it’s easy to push the button. It doesn’t take a lot of deliberate forethought to create beautiful, well-crafted shots. We can get very good at this with practice. People may pay a lot for our skills.
But as an art, we must go through the same deliberate process as using ink, pencil, or paint. Cameras do not allow us to turn off our brains, to short-cut the creative process of visualizing and working towards bringing that vision into fruition.
I find it true that light-writing this can be notoriously difficult. We have to manipulate intangible physical objects (photons). Because the camera stage can be so difficult, I think there’s a barrier that can make people reluctant to cross. The seduction, the Dark Side, if you will, is to be deceived that just because we can push a button and an image magically appears, we’re suddenly an artist without having to visualize and work the tools of the trade to make that idea reality.
As for tools, with light-writing, we have to start with the camera. If we’re creating what was not recorded, we’re not engaged in light-writing but moving to mixed media. This is not to suggest that it’s bad per se. (Also note that I include necessary post as photography (curves, WB, etc.). We finish the creative process in post (LR, PS, etc.)).
I have no problem acknowledging that a lot of what I do doesn’t go through the full process. Much of it is to hone my craft, and make some cash doing it.
On the other hand, I find it a rather interesting anecdote that when people seek me or my work out, it’s always the shots that I’ve gone through the full creative process on. I had the idea, I worked the process, and those works grab people somehow.
Even in the studio yesterday, most of the shots were on the fly because of the action going down, but again, the one shot that got immediate comments, every time, was the one I thought through and created deliberately.
It’s not a scientific answer, purely anecdote, but I do find it interesting.
I’ve really enjoyed Viscosity for Mac since last year. It’s an inexpensive, drop-dead simple VPN client that works with OpenVPN-enabled firewalls such as SmoothWall. However, Spark Labs didn’t have a Windows version. I spent quite a bit of time trying to find a simple OpenVPN client for non-techie users, but wasn’t satisfied with what I could find.
Spark Labs released their Windows version of Viscosity. I sat down to figure out how to install the OpenVPN certificates.(If you want to try Viscosity, they have a 30-day trial.)
I will only cover connecting to a OpenVPN client similar to SmoothWall (using PKCS 12 files).
Download the installer from the Viscosity download page. Accept all of the defaults. There is an option to create a desktop icon, if you want.
Depending on your OS, the installer may require a .NET piece to be downloaded from Microsoft. Click on Yes and the installer will take care of it for you.
You may see a warning that Viscosity doesn’t have an official happy face from Microsoft. Click on Continue Anyway.
When the install is complete, allow the installer to run Viscosity so we can proceed to setting it up for use.
You’ll see a one-time Welcome to Viscosity screen. Close it to continue.
At this point, Viscosity will be running in your task bar (usually in the lower right-hand corner of your screen). The default icon is a lock in front of a circle:
Click on the icon and select Preferences….
There are couple of defaults in the Preferences window which I personally like to tweak. These are optional.
There are two steps here. One is the creation of the VPN certificates, and the other is installing the certificates into Viscosity.
I will use SmoothWall as an example simply because it’s a firewall I have ready access to. Refer to your documentation on how to do it on your firewall. SmoothWall has an option called Download Client Package (zip) which provides a single convenient .zip file that contains the two files we need.
Copy the file to the machine you’re installing Viscosity on and extract them (assuming a zip file). Certificates are installed using the + button in the lower left corner of the Connections tab.
Navigate to where you put the files. You’ll choose the file that ends in .ovpn. It should import cleanly and show on the Connections tab. Now we need to click on the Edit button.
If you do not like the default name, feel free to change it on the General tab.
On the Authentication tab, change the authentication method to SSL/TLS Client (PKCS 12). Click on the upper Select button. (If it shows a file, click Clear.)
Choose the PKCS 12 file. SmoothWall uses the exention .p12. Finally, click Save.
The VPN connection should be ready at this point. Close the window.
Now that the connection is set up, you can click on the tool bar and choose the new connection. Ensure, of course, that you’re outside of the firewall first.
While Viscosity is connecting, you may see a message that A network cable is unplugged. This is normal and can be ignored.
If you’re having problems, click on the Details… menu item before connecting.
This window has three tabs which are a little hard to discern, in my opinion. The third one shows the progress of the connection, and may (or may not) provide useful information.
I’m sorry I cannot help diagnose your particular system. For further assistance see the Spark Labs’ support page.
I don’t have any connection to the company. I’ve just been really happy with the product.
This is a collection of various Zimbra tweaks.
When a user wants to log in with a web browser, I want to force HTTPS to be used. All connections to http://mail.domain.com are redirected to https://mail.domain.com.
$ zmtlsctl redirect $ zmcontrol stop $ zmcontrol start
Reference: CLI zmtlsctl to Set Web Server Mode
Zimbra is very picky about the time zone string. The complete list is at the very bottom of Time Zones in ZCS.
zmprov mc default zimbraPrefTimeZoneId '(GMT-07.00) Mountain Time (US & Canada)'Reference: Time Zones in ZCS