Technology Tales

Dispensing with temptation

Many manufacturers followed Olympus into the compact system camera market. Nikon joined late last year, though Canon hasn't yet entered. Olympus E-PL1 kits with 14-42mm zoom lenses tempted me at around £250. After researching competitors, my shortlist included the Samsung NX-11, Sony NEX-C3, and its higher-end model, the NEX-5N.

What eventually countered the allure of shiny objects was the question as to why I needed such an item. After all, I already possess a Pentax K10D DSLR and a Canon PowerShot G11, and these have been satisfying my photographic needs for a while now. While the DSLR may date from 2007, it is still working well for me and, if it ever needed replacing, I'd be going for another Pentax with the K-5 being a strong contender. The Canon is doing what's asked of it, so the recent launching of the G1 X isn't so tempting either.

The whole dalliance has me wondering about how photographic equipment changeovers come about. After all, it was around a decade ago with the DSLR revolution was in the offing if not in progress. Until then, film photography was predominant, but it looks as if it got as far as it could from a technological point of view when I look back at what happened. The digital photography area was new and untapped, so moving there offered new possibilities and purchases more easily justified. The result is that very few film cameras are being made nowadays. Ironically, it's film photography that now is untrammelled terrain for many, and it is holding its own too in an era when digital photography predominates.

The same sort of newness that came with digital photography also applies to CSC's to a certain extent. From the heritage of half-frame 35 mm film photography, Olympus has fashioned a different type of digital camera: essentially a compact with interchangeable lenses. Was it the fact that I have no CSC that caused me to be tempted, and has it happened to others too? Also, is that what got digital photography going in the first place?

It almost feels as if camera manufacturers have to keep bringing to market new models and new types of camera to stay in business. After all, Minolta had to sell its camera division to Sony when they failed to get going in the DSLR market quickly enough. The same thing might have happened to Pentax too, with the marque passing to first to Hoya, and then to Ricoh after the firm lost its independence.

What doesn't help is the lack of longevity of camera models. The coming of digital photography has exacerbated this situation, with models being launched at a frenetic rate. In the days of film photography, a model could last on the market for a few years and there was once a time when a twenty-year lifetime wouldn't have looked so ridiculous, though there were incremental improvements made over that time too. For instance, a Pentax K1000 wouldn't be the same at the end of its production run as it was at the start, though the model number may be the same. That world is gone.

SLR design has endured for about 50 years, but mirrorless technology now presents unprecedented competition. Even compact cameras offer live through-the-lens viewing. Olympus revived its film heritage by creating the E-P1 with interchangeable lenses. These descendants of the original half-frame 35mm PEN cameras appropriately use smaller micro four thirds sensors. Sony has developed translucent mirror technology that eliminates moving parts found in traditional SLRs. Canon experimented with this in the 1980's with film cameras but abandoned it. Meanwhile, Samsung and Panasonic produce mirrorless SLR-style cameras with live viewing and electronic viewfinders, suggesting full-size equivalents may be coming. Olympus's current teaser campaign has sparked speculation about a possible OM-D release.

In parallel with all this, Sony is making a good impression with their CSC's, the NEX series. These have APS-C sized sensors like many DSLR's and in compact bodies as well. However, the feel very much is that of a compact camera and some have complained of a like of buttons on them, even if the photographic quality is excellent. Samsung have gone for the same sensor size in their NX-11, while they have gone for SLR styling. That may be more suitable for some than having to find settings buried in menus.

We're living in an exciting yet unsettling period of camera technology evolution. Cameras are becoming smaller, and traditional still cameras now shoot videos too, though filmmaking remains a time-intensive hobby that doesn't interest me. Recent legal developments complicate original work, as shown by a successful copyright case based on Photoshop image processing. With countless images being created daily and potential changes allowing intellectual property claims in small claims courts, avoiding infringement becomes harder. Film photography seems appealing in contrast and remains viable despite Kodak's financial struggles. As tastes shift and film becomes novel again, the future is uncertain. Perhaps investing in a DSLR body makes sense before Compact System Cameras completely replace them. Camera technology has become interesting once more.

A few thoughts on Ubuntu 12.04 Alpha 1

After an aborted installation in VirtualBox using the direct installation, I got a VM instance of Ubuntu 12.04 in place by installing from a loaded Live CD session. That proceeded without any trouble and downloaded the required updates too. First impressions revealed a polished Unity interface that ran without any crashes. The task of adding VirtualBox's Guest Additions in the usual way was all that was needed to tart up the experience even more. However, there remains a wish list for improvements to the Unity desktop, so here are mine:

• Merging of an application title bar with the desktop's top panel on maximisation: In 11.10, removing the appmenu packages does force menus into application windows and that seems to be destined as a configurable item in Unity at some point; it'd be good to see it in 12.04 though it's not in the first alpha release. The merging of the panel and title bar would be a good thing to have as a user setting too because I am unconvinced by the current behaviour when there is plenty of screen space.
• Rearranging icons on the application launcher: There appears to be no obvious way to do this at the moment and attempting to move them with a mouse only moves the launcher up and down. There is no doubt that this behaviour is a bonus for those working with small screens, but it is a nuisance unless there is another means for achieving the same end.
• Desktop environment switcher on the login screen: This seems to have disappeared for now. Hopefully, this is an oversight that will see correction in later stages of the development of Ubuntu 12.04. This is how I currently get Ubuntu 11.10 to boot into GNOME Shell, so its loss would be a step backwards. Then, a Gubuntu project would become truly necessary, though I have to say that Linux Mint makes such a viable alternative that I wonder how they would get going.

In summary, it does look as if the Unity interface is getting more and more polished. However, there are niggles that I have described above that, I think, need addressing, and I hope that many of them will be addressed in either 12.04 or 12.10. Though usability seems to be improving, I still am left with the impression that it has a way to go yet.

Dealing with variable length warnings in SAS 9.2

A habit of mine is to put a LENGTH or ATTRIB statement between DATA and SET statements in a SAS data step to reset variable lengths. By default, it appears that this triggers truncation warnings in SAS 9.2 or SAS 9.3 when it didn't in previous versions. SAS 9.1.3, for instance, allowed you to have something like the following for shortening a variable length without issuing any messages at all:

data b;
    length x $100;
    set a;
run;

In this case, x could have a length of 200 previously and SAS 9.1.3 wouldn't have complained. Now, SAS 9.2 and 9.3 will issue a warning if the new length is less than the old length. This can be useful to know, but it can be changed using the VARLENCHK system option. Though the default value is WARN, it can be set to ERROR if you really want to ensure that there is no chance of truncation. Then, you get error messages and the program fails where it normally would run with warnings. Setting the value of the option to NOWARN restores the type of behaviour seen in SAS 9.1.3 and versions before that.

The SAS documentation says that the ability to change VARLENCHK can be restricted by an administrator, so you might need to deal with this situation in a more locked down environment. Then, one option would be to do something like the following:

data b;
    drop x;
    rename _x=x;
    set a;
    length _x $100;
    _x=strip(x);
run;

While It's a bit more laborious than setting the VARLENCHK option to NOWARN, the idea is that you create a new variable of the right length and replace the old one with it. That gets rid of warnings or errors in the log and resets the variable length as needed. Of course, you have to ensure that there is no value truncation with either remedy. If any is found, then the dataset specification probably needs updating to accommodate the length of the values in the data. After all, there is no substitute for getting to know your data and doing your own checking should you decide to take matters into your hands.

There is a use for the default behaviour, though. If you use a specification to specify a shell for a dataset, then you will be warned when the shell shortens variable lengths. That allows you to either adjust the dataset or your program. Also, it provides additional information when you get variable length mismatch warnings when concatenating or merging datasets. There was a time when SAS wasn't so communicative in these situations and some investigation was needed to establish which variable was affected. Now, that has changed without leaving the option to work differently if you so do desire. Sometimes, what can seem like an added restriction can have its uses.

Trying out Irish Mobile Broadband

Over the course of a year, I end up visiting Ireland a few times, so I decided to invest in a Meteor PAYG broadband stick to see how I'd get on with it. For €20, you can get a 30-day pass with 7.5 GB downloading capacity, a more generous offer than you'd get with some UK mobile networks (T-Mobile really comes to mind here). Signal strength was strong wherever I tried it too with 3G being available so long as you are in the right place with EDGE being the lowest that I got otherwise. Download speeds are good too so it turned out to be a good investment of €30 to get the Huawei E173 USB dongle (I had a T-Mobile one of these before that no longer works, so I am keeping an eye on reliability with this one; though the design seems a little different, I am getting OK so far) and €20 of credit that comes with it. After all, anything's better than the punitive roaming rates that UK providers charge.

Yet another useful Windows shortcut

During the week, I needed to go to a client to upgrade the laptop that they'd given me for doing work for them. The cause was their migration from Windows XP to Windows 7. Office 2010 also came with the new set-up, and they replaced the machines with new ones too. As part of doing this, they carried out upgrade training and this is when I got to learn a thing or two.

While I may have been using Windows 7 since the beta releases first were made available, I am under no illusions that I know all there is to be known about the operating system. Included among the things of which I wasn't aware was a shortcut key combination for controlling display output from the HP laptop that I'd been given. This is the Windows key + P. This brings up a dialogue screen from which you can select the combination that you need and that includes extending the display across two different screens, such as that of the laptop and an external monitor. Going into the display properties will fine tune things such as what is the main display and the placement of the desktops; there's no point in having Windows thinking that the external screen is to your left when in fact it is on the right.

Another interesting shortcut is the Windows key + TAB. This affects the Aero application view and repeating the combination cycles through the open applications, or you can use a mouse wheel to achieve the same end. With ALT + TAB and the taskbar still about, this might appear more of a curiosity, but some may still find it handy, so I've shared it here too.

All in all, it's best never to think that you know enough about something because there's always something new to be learned, and it's always the smallest of things that proves to be the most helpful. With every release of Windows, that always seems to be the case and Windows 8 should not be any different, even if all the talk is about its Metro interface. A beta release is due in the spring of 2012, so we'll have a chance to find out then. You never can stop learning about this computing business.

A little more freedom

A few weeks ago, I decided to address the fact that my Toshiba laptop have next to useless battery life. The arrival of an issue of PC Pro that included a review of lower cost laptops was another spur for looking on the web to see what was in stock at nearby chain stores. In the end, I plumped for an HP Pavilion dm4 from a branch of Argos. In fact, they seem to have a wider range of laptops than PC World!

The Pavilion dm4 seems to come in two editions and I opted for the heavier of these, though it still is lighter than my Toshiba Equium as I found on a recent trip away from home. Its battery life is a revelation for someone who never has got anything better than three hours from a netbook. Having more than five hours certainly makes it suitable for those longer train journeys away from home, and I have seen remaining battery life being quoted as exceeding seven hours from time to time, though I wouldn't depend on that.

Of course, having longer battery life would be pointless if the machine didn't do what else was asked of it. It comes with the 64-bit of Windows 7 and this taught me that this edition of the operating system also runs 32-bit software, a reassuring discovering. There's a trial version of Office 2010 on there too and, having a licence key for the Home and Student edition, I fully activated it. Otherwise, I added a few extras to make myself at home, such as Dropbox and VirtuaWin (for virtual desktops as I would in Linux). While I was playing with the idea of adding Ubuntu using Wubi, I am not planning to set up dual booting of Windows and Linux like I have on the Toshiba. Little developments like this can wait.

Regarding the hardware, the CPU is an Intel Core i3 affair and there's 4 MB of memory on board. The 14" screen makes for a more compact machine without making it too diminutive. The keyboard is of the scrabble-key variety and works well too, as does the trackpad. There's a fingerprint scanner for logging in and out without using a password, but I haven't got to check how this works so far. It all zips along without any delays, and that's all that anyone can ask of a computer.

There is one eccentricity in my eyes though: it appears that the functions need to be used in combination with the Fn key for them to work like they would on a desktop machine. That makes functions like changing the brightness of the screen, adjusting the sound of the speakers and turning the Wi-Fi on and off more accessible. My Asus Eee PC netbook and the Toshiba Equium both have things the other way around, so I found this set of affairs unusual, but it's just a point to remember rather than being a nuisance.

Though HP may have had its wobbles regarding its future in the PC making business, the Pavilion feels well put together and very solidly built. The premium paid over the others on my shortlist seems to have been worth it. If HP does go down the premium laptop route as has been reported recently, this is the kind of quality that they would need to deliver to just higher prices. Saying that, is this the time to do such a thing with other devices challenging the PC's place in consumer computing? It would be a shame to lose the likes of the Pavilion dm4 from the market to an act of folly.

A new repository for GNOME 3 Extensions

Not before time, the GNOME project has set up a central website for GNOME Shell extensions. It seems to be in the hands of extension developers to make GNOME 3 more palatable to those who find it not to their taste in its default configuration. If you are using Firefox, installation is as easy as clicking the ON/OFF icon for a particular plugin on its web page and then selecting install in the dialogue box that pops up. Of all the browsers that you can use on GNOME, it seems to be Firefox that is the only one that has this ability at the moment.

Though the website may have the alpha legend on there at present, it works well enough so far, so I have had no hesitation in using it for those extensions that are of interest to me. This is an interesting development that deserves to stay, especially when it detects that a plugin is incompatible with your version of GNOME.

Currently, I use GNOME 3.2, and it pops up a useful menu for deactivating extensions when the desktop fails to load. That's a welcome development because I have had extensions crashing GNOME 3.0 on me and running the GNOME Tweak Tool on the fallback desktop often was the only alternative. GNOME 3 seems to be growing up nicely.

Getting Gnome Shell going for Fedora 16 running in VirtualBox

There are a number of complaints out there about how hard it is to get GNOME Shell running for a Fedora 16 installation in a VirtualBox virtual machine. As with earlier versions of Fedora, preparation remains a matter of having make, gcc and kernel-devel (kernel headers, in other words). While I have got away with just those, adding dkms (dynamic kernel module support) to the list might be no bad idea either. To get all of those instated, it is a matter of running the following command as root or using sudo:

yum -y install make gcc kernel-devel dkms

The -y switch ensures that any Y/N prompts that usually appear are suppressed and that the installation is completed. Just leave it out if you are inclined to get second thoughts. Another item that has been needed with a previous release of Fedora is libgomp, but I haven't had to add this for Fedora 16 if I recall correctly.

Once those are in place, it is time to install the VirtualBox Guest Additions.  Going to Devices > Install Guest Additions... mounts a virtual CD that can be used for the installation of the various drivers that are needed. To do the installation, first go to where the installer is located using the following command:

cd /media/VBOXADDITIONS_4.1.6_74713/

Note that this location will change according to the release and build numbers of VirtualBox, yet the process essentially will be the same aside from this. Once in there, issue the following command as root or using sudo:

./VBoxLinuxAdditions.run

Hopefully, this will complete without errors now with the precursor software that has been added beforehand. However, there is one more thing that needs doing, or you will get the GNOME 3 fallback desktop instead. It pertains to SELinux, an old adversary of mine that got in the way when I was setting up a web server on a machine running Fedora. It doesn't recognise the new VirtualBox drivers as it should, so the following command needs executing as root or using sudo:

restorecon -R -v /opt

Doing this restores the SELinux contexts for the /opt directories within which the VirtualBox software directories are found. The -R switch tells it to act recursively and -v makes it verbose. When it has done its work, hopefully successfully, it is time to reboot the virtual machine, and you should have a GNOME Shell desktop interface when you log in.

An in situ upgrade to Linux Mint 12

Though it isn't the recommended approach, I have ended up upgrading to Linux Mint 12 from Linux Mint 11 using an in situ route. Having attempted this before with a VirtualBox hosted installation, I am well aware of the possibility of things going wrong. Then, a full re-installation was needed to remedy the situation. With that in mind, I made a number of backups in the case of an emergency fresh installation of the latest release of Linux Mint. Apache and VirtualBox configuration files together with MySQL backups were put where they could be retrieved should that be required. The same applied to the list of installed packages on my system. So far, I haven't needed to use these, but there is no point in taking too many chances.

The first step in an in-situ Linux Mint upgrade is to edit /etc/apt/sources.list. In the repository location definitions, any reference to katya (11) was changed to lisa (for 12) and the same applied to any appearance of natty (Ubuntu 11.04) which needed to become oneiric (Ubuntu 11.10). With that done, it was time to issue the following command:

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade

Once that had completed, it was time to add the new additions that come with Linux Mint 12 to my system using a combination of apt-get, aptitude and Synaptic; the process took a few cycles. GNOME already was in place from prior experimentation, so there was no need to add this anew. However, I need to instate MGSE to gain the default Linux Mint customisations of GNOME 3. Along with that, I decided to add MATE, the fork of GNOME 2. That necessitated the removal of two old libraries (libgcr0 and libgpp11, if I recall correctly, which will tell you what is causing any conflict) using Synaptic. With MGSE and MATE in place, it was time to install LightDM and its Unity greeter to get the Linux Mint login screen. Using GDM wasn't giving a very smooth visual experience and Ubuntu, the basis of Linux Mint, uses LightDM anyway. Even using the GTK greeter with LightDM produced a clunky login box in front of a garish screen. Configuration tweaks could have improved on this, but it appears that using LightDM and Unity greeter is what gives the intended setup and experience.

With all of this complete, the system seemed to be running fine until the occasional desktop freeze occurred with Banshee running. Blaming that, I changed to Rhythmbox instead, though that helped only marginally. While this might be blamed on how I upgraded my system, things seemed to have steadied themselves in the week since then. As a test, I had the music player going for a few hours and there was no problem. With the call for testing of an update to MATE a few days ago, it now looks as if there may have been bugs in the original release of Linux Mint 12. Daily updates have added new versions of MGSE and MATE, so that may have something to do with the increase in stability. Even so, I haven't discounted the possibility of needing to do a fresh installation of Linux Mint 12 just yet. However, if things continue as they are, then it won't be needed and that's an upheaval avoided should things go that way. That's why in situ upgrades are attractive, though rolling distros like Arch Linux (these words are being written on a system running this) and LMDE are more so.

Adding Software to Arch Linux from the AUR

There are packages absent from the Arch Linux repositories that could come in useful. When you are after one of these, then it's time to search the Arch User Repository (AUR). In here, I have found the likes of Microsoft Core Fonts, Adobe Reader and Dropbox. While there may be others, these examples are what comes to mind as I write this. In time, it may be that packages make if from the AUR into the Arch community repository, but you have to use the former if you cannot wait.

Just search the AUR for what you want and download the compressed tarball (tar.gz file) from the webpage where you find it. Then, I recommend extracting it to /tmp where clearance at boot time means that you don't need to do it yourself. Then, go into the appropriate subfolder in /tmp (acroread for Adobe Reader, for instance) and issue the following command:

makepkg

This will attempt to create a package file where you are working for installation by pacman. If dependencies are absent, you will be told and these may need another AUR search in some cases, though most are included in the repositories. Once dependencies, have been sorted, just issue the makepkg command again to create the xz file that pacman needs to perform the installation. To do so, issue the following command from the same directory either as root or by using sudo if your user account has such privileges:

pacman -U *.xz

There is usually just one xz archive in a package folder, so I have been taking the easy route of not looking up the name all the time. Of course, you can do that for safety if you like.

With pacman not looking at the AUR, you have to do more work to get upgrades to happen should you want to avoid without having to repeat the above process all the time. There is a package in the AUR called yaourt that needs package-query from the same place as well. Before any of these, yajl needs to be installed from one of the default repositories. Once yaourt is in place, then the following does the updates for you:

yaourt -Syu --aur

Again, it might be best to run this as root or using sudo though that gives messages from makepkg about not running it as a privileged user. However, I reckon that those might need to be ignored. When I tried it, the Citrix update failed, though the Dropbox one succeeded. This experience might be worth bearing in mind. Saying that, I have found installing and updating software from the AUR not to be too onerous a process so far. Anything that gives a little more freedom only can be a good thing.