TOPIC: UBUNTU
Windows Home Server: an interesting proposition?
29th January 2008
If I was still running Windows as my main OS, the idea of storing my files on a separate computer acting as a server would appeal to me. After all, I rapidly developed the habit of partitioning my hard disk so that my data files were separated from the rough and tumble lives of operating system and software files. Later, I took it further by placing system files and data files on separate hard drives, an arrangement that smoothed my move to Linux. Separation of computers would further secure things, and that's why Windows Home Server caught my eye when it was released. The recent spate of glitches with the thing might have changed my mind, but my move to Ubuntu makes that irrelevant now. In any event, I suppose that I could have gone with Network-Attached Storage or an external hard rive. I do possess the latter, and a backup is being stored on it as I write this, and the former still remains an option but for the fact that I am happy with how things stand. In any event, the conventional networking model would be yet another potential choice. While I was going to say more about Windows Home Server, I think I'll leave that to others, so here's a library of links for your perusal.
Running Photoshop Elements 5 using WINE on Ubuntu and openSUSE
23rd January 2008
When you buy a piece of software and get accustomed to its ways of working, it is natural to want to continue using it. That applied to a number of applications when I moved over to Linux in the latter half of last year, and one of these was Adobe's Photoshop Elements 5.0, a purchase made earlier in the year. My way forward was to hang on to Windows by way of VMware. However, Elements fails to edit or save files in the Linux file system accessed through VMware's shared folders feature. I have yet to work out what's happening, but the idea of using a more conventional networking arrangement has come to mind.
Another idea that intrigued me was the idea of using WINE, the Windows API emulator for Linux. You can get it in the Ubuntu and openSUSE software repositories, but the WINE website has more to say on the subject. That's only the first stage, though, as you might see from WINE's Wiki page on Photoshop and its like. However, their advice is a spot incomplete, so I'll make it more explicit here. You need to run Winetricks from its online home as follows:
wget kegel.com/wine/winetricks; sh winetricks fakeie6
wget kegel.com/wine/winetricks; sh winetricks mdac28
wget kegel.com/wine/winetricks; sh winetricks jet40
The first line flicks a switch to fool Microsoft components to install thinking that they are installing into a Windows system with IE on board. Without this, the rest will not happen. The second installs Microsoft's native ODBC drivers; Elements will not function at all without these if my experience is any guide. The last step is to add JET support so that Elements' Organiser can get going. With all of these in place, having a working Photoshop Elements instance under Linux should be a goer. Apart from the odd crash, things seem to be working OK on Ubuntu and openSUSE seems hospitable too. Further experimentation may reveal more.
Update: The WINE Wiki has now been updated (and links back here!). As per dank's comment, the above lines can be condensed into what you see below:
wget kegel.com/wine/winetricks; sh winetricks fakeie6 mdac28 jet40
Succumbing to Temptation: Ubuntu Studio
12th December 2007
Because the fancy artwork that comes with Ubuntu Studio does look appealing, I got lured into converting my vanilla Ubuntu 7.10 into something a bit more avant-garde. The theme's all very dark (you can have a peek here; file size is 1.1 MB) but it has a very appealing look, even if the merging of the application title bar and top desktop panel due to their having the same colour and texture is a little disconcerting. My momentary lapse of discipline also got me adding a whole array of audio, graphics and movie applications that I may never use; it's good to have them if I ever fancy a fiddle, but removal is not off the agenda either. The other thing that came with the package was an alternate kernel that looks as if it might be of the real time variety, at least if the "rt" in its package name is to be believed. The main reason for mentioning that is that VMware has ceased working, so I need to snag the correct kernel source code to get things going again. Let's hope that it's a successful venture...
Update: After a spot of poking, Synaptic offered up the required kernel header files and VMware was reinstated with only a modicum of effort. All's well that ends well.
Setting up automatic Firefox updates on Ubuntu with Ubuntuzilla
1st December 2007
No sooner had we received Firefox 2.0.0.10 than they have already started talking about 2.0.0.11. Apparently, the latest update broke support for a tag that I have never used: canvas. This is stuff that makes you wonder about their quality control.
Because the 2.0.0.10 was a security update, Ubuntu volunteered it to me without any effort on my part. However, I am using Ubuntuzilla, so I didn't get the update coming through to my browsing world without further intervention. Launching Firefox using the gksu command allowed me to update the thing like I have been doing on Windows: Help > Check for Updates... Now, I have got a more permanent check set up, thanks to my issuing the following command:
ubuntuzilla.py -a installupdater -p firefox
A different Firefox II: cross-platform font display issues
18th November 2007
One of the things that I have been sorting out on this blog is how the fonts appear in Firefox running on Ubuntu. Even with the same fonts and the same browser, serif fonts were being displayed smaller and appeared more fuzzy in Linux than on Windows. And that's even with the font sharpening that comes with turning on Ubuntu's visual effects. So, there was a spot of swapping between Ubuntu and Windows (running on VMware) while I was increasing font sizes to improve legibility on the Linux side without things going all Blue Peter on Windows. Along the way, I added a mention of the Ubuntu font ae_AlArabiya in the CSS to further spruce up things. In my earlier web building efforts, I was having to make serif fonts bigger because of those serifs. From the on-screen legibility point of view, there's a lot to be said for sans serif fonts and I may yet alter this blog's theme to use them instead, but I'll ponder the idea a bit more before taking the plunge.
A different Firefox…
17th November 2007
On Ubuntu, I made a move to using Ubuntuzilla's deployment of Firefox. Because Firefox's Gecko engine is used by other parts of Ubuntu, any Firefox updates issued by Mozilla don't come through straight away. The idea of using Ubuntuzilla is that you get Mozilla's latest, be it Firefox, Thunderbird or Seamonkey, without having an impact on the rest of the Linux installation; while Ubuntu's Firefox is left in place, you are now presented with the vanilla Firefox for all your web surfing needs. Visually, there's not much change but for the built-in Firefox application fonts coming through in the new instance, a strange sight when you see Ubuntu's more subtle alternatives everywhere else. I tried the new tack to see if picked up RealPlayer in place of Xine, but that sadly has not been the case. Nevertheless, I now have 2.0.0.9 and the latest improvements this side of version 3.
Navigating multiple workspaces: A Linux and UNIX advantage over Windows?
16th November 2007
One of the nice things about the world of Linux and UNIX is the availability of multiple workspaces. In Window, you only ever get one, and the likes of me can easily fill up that task bar. So the idea of parcelling off different applications to different screens is useful from a housekeeping point of view so long as icons only appear in the task bar for the open workspace; Ubuntu respects this but openSUSE doesn't, a possible source of irritation.
However, a case can be made that UNIX/Linux needs workspaces more than Windows because of the multi-window interfaces of some of the software applications. The trouble with each of these sub-windows is that an entry appears in the task bar for each of this, rapidly creating a mess. And it can also be an issue working out which window closes the lot.
Examples of the above that come to my mind include GIMP, XSane and SAS. The Windows version of the latter's DMS is confined to a single application window while the UNIX incarnation is composed of a window each for individual components like program editor, log, output, etc. Typing "bye" in the command line of the program editor is enough to dispatch the GUI. With GIMP, Ctrl+Q will close it down in any window, apart from the "Tip of the Day" one that pops up when GIMP is started. The same sort of behaviour also seems to dispatch XSane too.
Switching from one workspace to another is as easy as clicking the relevant icon in the task bar in all the UNIX variants that I have used. Switching an application from one workspace to another has another common thread: finding the required entry in the application window menu.
On Ubuntu, I have seen other ways of working with workspaces. In the interface with visual effects turned off, hovering over the workspace icons in the task bar allows you to move from one to another with the wheel of your mouse. Moving an application between workspaces can be done as simply as dragging boxes from one task bar icon to another. Turning on the visual effects changes things, though. It might appear that the original functionality still works, but that seems not to be the case: a matter for Canonical to resolve, perhaps?
The visual effects do provide other ways around this, though. Keeping all your application windows minimised means that you can run through workspaces themselves with your wheel mouse. Moving applications between workspaces becomes as simple as grabbing the title bar and pulling the window left or right until it changes workspace. Be careful that you do the job fully, though, or you could have an application sitting astride two workspaces. It would appear that ideas from the sharing of a desktop across multiple monitors have percolated through to workspace behaviour.
Aside (regarding Ubuntu visual effects): I don't know who came up with the idea of having windows wobble when they're being moved around, but it certainly is unusual, as is seeing what happens when you try prising a docked window from its mooring (particularly when you're pulling it up from the bottom task bar). The sharper font display and bevelled screen furniture make more sense to me, though; they certainly make a UI more appealing and modern.
BBC Radio Player and Linux
13th November 2007
It's been a while since I mentioned anything that might be aurally related, and then this rears its head. The Xine plugin beloved by the instance of Firefox on my Ubuntu box simply refuses to play ball with the BBC's Listen Again feature; 6Music shows are what I am trying to catch later. RealPlayer is on the system, but Firefox simply refuses to locate it. On its own, it plays live radio from the BBC and Ireland's Today FM but, unless I need to do some digging, that's not much use for the Listen Again service. It may be some hard-wiring done by Canonical as part of their packaging of Firefox: might be related to their preference for Free Software. If I can be bothered, I might replace it with the usual version to see if RealPlayer can be picked up: I do seem to remember reading somewhere that this was a possibility...
Yes, I could use one of my Windows VM's, but I have found another way courtesy of openSUSE 10.3. No, I haven't changed Linux distro, yet the reason that openSUSE has made a sudden appearance on this blog in recent times has got to do with my acquiring a copy of the latest issue of Linux Magazine. It came emblazoned with a DVD containing both 32-bit and 64-bit variants of openSUSE's latest version and, wanting to have a look at how KDE appears these days, I knocked up a VM and installed the 32-bit variant thereupon.
Unexpectedly, that has afforded a Linux solution to my BBC Radio Player conundrum. openSUSE's Firefox instance can find RealPlayer once you have it installed. That process involves a spot more work than if it was Free Software: you need to add an extra software repository to YaST (openSUSE's configuration utility). The breadcrumb trail is YaST -> Software -> Software Repositories and hitting the Add button fires up a wizard that needs the following settings to set things up as needed:
Protocol: http
Server Name: download.opensuse.org
Directory on server: /distribution/10.3/repo/non-oss/suse/
Authentication: anonymous
Once the new repository was set up (I named it Non-OSS), I found the RPM and YaST took care of the rest. So, what started out as an exercise in curiosity has now found a use. While network traffic may cause playback to stutter, I have what I want without once starting up Windows. Sorting out Ubuntu may happen, but it is a lesser priority and I don't want to disrupt my computing environment in any event.
Choices, choices…
10th November 2007
While choice is a great thing, too much of it can be confusing, and the world of Linux is a one very full of decisions. The first of these centres around the distro to use when taking the plunge; you quickly find that there can be quite a lot to it. In fact, it is a little like buying your first SLR/DSLR or your first car: you only really know what you are doing after your first one. Putting it another way, you only know how to get a house built after you have done just that.
With that in mind, it is probably best to play a little on the fringes of the Linux world before committing yourself. It used to be that you had two main choices for your dabbling:
- using a spare PC
- dual booting with Windows by either partitioning a hard drive or dedicating one for your Linux needs.
In these times, innovations such as Live CD distributions and virtualisation technology keep you away from such measures. In fact, I would suggest starting with the former and progressing to the latter for more detailed perusal; it's always easy to wipe and restore virtual machines anyway, so you can evaluate several distros at the same time if you have the hard drive space. It also a great way to decide which desktop environment you like. Otherwise, terms like KDE, GNOME, XFCE, etc. might not mean much.
The mention of desktop environments brings me to software choices because they do drive what software is available to you. For instance, the Outlook lookalike that is Evolution is more likely to appear where GNOME is installed than where you have KDE. The opposite applies to the music player Amarok. Nevertheless, you do find certain stalwarts making a regular appearance; Firefox, OpenOffice and the GIMP all fall into this category.
The nice thing about Linux is that distros more often than not contain all the software that you are likely to need. However, that doesn't mean that it is all on the disk and that you have to select what you need during the installation. Though there might have been a time when it might have felt like that, my recent experience has been that a minimum installation is set in place that does all the basics for you to easily add the extras later on an as needed basis. I have also found that online updates are a strong feature too.
Picking up what you need when you need it has major advantages, the big one being that Linux grows with you. You can add items like Apache, PHP and MySQL when you know what they are and why you need them. It's a long way from picking applications of which you know very little at installation time and with the suspicion that any future installation might land you in dependency hell while performing compilation of application source code; the temptation to install everything that you saw was a strong one. The "learn before you use" approach favoured by how things are done nowadays is an excellent one.
Even if life is easier in the Linux camp these days, there is no harm in sketching out your software needs. Any distribution should be able to fulfil most if not all of them. As it happened, the only third party application that I have needed to install on Ubuntu without recourse to Synaptic was VMware Workstation, and that procedure thankfully turned out to be pretty painless.
A fallback installation routine?
9th November 2007
In a previous sustained spell of Linux meddling, the following installation routine was one that I encountered rather too often when RPM's didn't do what I required of them (having a SUSE distro in a world dominated by a Red Hat standard didn't make things any easier...):
tar xzvf progname.tar.gz; cd progname
The first part of the command extracts from a tarball compressed using gzip and the second one changes into the new directory created by the extraction. For files compressed with bzip use:
tar xjvf progname.tar.bz2; cd progname
The command below configures, compiles and installs the package, running the last part of the command in its own shell.
./configure; make; su -c make install
Yes, the procedure is a bit convoluted, but it would have been fine if it always worked. My experience was that the process was a far from foolproof one. For instance, an unsatisfied dependency is all that is needed to stop you in your tracks. Attempting to install a GNOME application on a KDE-based system is as good a way to encounter this result as any. Other horrid errors also played havoc with hopeful plans from time to time.
It shouldn't surprise you to find that I will be staying away from the compilation/installation business with my main Ubuntu system. Synaptic Package Manager and its satisfactory dependency resolution fulfil my needs well and there is the Update Manager too; I'll be leaving it for Canonical to do the testing and make the decisions regarding what is ready for my PC as they maintain their software repositories. My past tinkering often created a mess, and I'll be leaving that sort of experimentation for the safe confines of a virtual machine from now on...