A quote from this article on ZDnet made me think of Gnome 3 as it relates to my use of it.
The biggest problem with Windows 8 is that it wasn’t born out of a need or demand.
I don’t have a need for it. After moving on from Fedora I switched to Red Hat Enterprise Linux as my regular desktop. Yes, there were a few applications that were missing, but those were usually applications not related to getting my job done or daily productivity. Red Hat Enterprise Linux really does everything I need to do and is based on Gnome 2.
Maybe there were architectural or maintenance reasons for creating and developing Gnome 3 after Gnome 2. I don’t know. I do remember talking to one of the Gnome developers at the time who said it was going to usher in a new paradigm of what using a computer and an operating system meant.
I don’t see it. To me the iPad and Apple’s mobile operating system have been much bigger and useful paradigm shifts. Perhaps Android too, though I haven’t had a chance to try it.
No matter how many times I’ve tried Gnome 3, it just doesn’t click with me. The notion that I should have to install a tweak tool and go to a website to install any number of plugins beyond the base install to reach a solid working desktop, just doesn’t compute for me. It’s time consuming and frustrating and doesn’t meet my expectation of what a good user experience is supposed to provide.
My most recent experience was with a new Lenovo x220. The default fonts and screen were just two small out of the box–definitely smaller compared to Gnome 2 and other Fedora 17 desktop environments (I tried three of them). I’ll raise my hand as one of the people who asked Paul Frields for help changing the font size because I couldn’t figure out how to do it. It’s cool a search box gets you to the right place, but doesn’t that miss the point of a good user experience for basic settings?
Maybe I’m getting too old or maybe I’ve lost the passion and interest I used to have for configuring Linux. I just want to install an operating system and use it–not install it and then spend a number of days tweaking and searching for answers it so it’s productive and useful.
It seems Linus Torvalds feels the same way.
Photo credit Laura Scott
If you want to run the Windows 8 Beta on RHEL 6 you need the `virtio-win` package installed. You can get it by subscribing to the “Supplementary” RHN channel.
Silly me. I thought I could just download the Windows 8 Beta and install it on a virtual machine with RHEL 6. Instead I kept getting an error message about a missing DVD driver. Since I wasn’t sure if this was a Windows problem or a `virt-manager` problem I filed bug #809160. From that I learned about virtio-win.
Windows 8 DVD driver error
Install `virtio-win` and restart `virt-manager` and everything should work as expected. Note, you must be subscribed to the `supplementary` RHN channel where this package is located.
$ su -c 'yum install virtio-win'
If you think trying to find the power off button on Gnome3 is frustrating, Windows 8 takes things to new unintuitive heights.
I believe that you need similar packages for Fedora, though I am not sure if they are provided by yum or what you have to do. Has anyone installed the Windows 8 Beta on Fedora and if so, did you have to do anything special with `virt-manager` to make it work?
My current diagramming program of choice is yEd. It definitely has it’s quirks, but I haven’t found anything this powerful that is free.
I’ve been running it for a long time on Red Hat Enterprise Linux 6 (64 bit) and recently did re-installs of Fedora 17 and RHEL 6 because I got a new notebook–more on that in another post. I got some weird errors trying to install it using the sh script. I’m not sure how I was able to previously install it, but apparently my old system had some of the prerequisite packages to make it work without me knowing it.
All the details of the problem are at http://yed.yworks.com/support/qa/17 and is specific to 64bit systems. The short answer is that you’re best off downloading a zip of the jar file and running it from a command line.
1) Download the Java zip version yEd
2) Unzip the file
$ unzip yEd-3.9.2.zip
3) Run it
$ java -jar ./yed-3.9.2/yed.jar
Did anyone else find a way to make the sh installer work?
The other day I set out to write a post on getting a WordPress instance running on OpenShift. I got sidelined in the confusion of determining the best place to install `rhc` tools from.
I’m trying to be more deliberate about using OpenShift and blogging about about my experiences along the way. I myself, prefer more detailed, step-by-step guides and that is what I plan to writer here.
Stay with upstream for now
The best place to currently get rhc tools is from the openshift.redhat.com repo. I’m told this is because they change a lot and the versions in Fedora don’t get updated as often because of the updates approval process (that’s not a knock on the Fedora process–OpenShift follows Fedora’s process and policies just like everyone else and updates Fedora as time permits).
rhc tools is available in Fedora 14 through 17 and known as `rubygem-rhc.` Setting aside the technical or policy reason why the package name is this way, it always bugs me when a trip to Google is required to determine the package named to`yum install` something this simple. It’s definitely not as obscure as 7zip.
Install rhc tools
Below is the essence of what you need to do. Alternatively you can follow OpenShift’s getting started instructions which felt less efficient to me.
1) Set up the yum repo. As root,
# cd /etc/yum.repos.d
# wget https://openshift.redhat.com/app/repo/openshift.repo
If you prefer to configure the OpenShift repo by hand, as root, put the following in a separate file (with a name ending in .repo, for example openshift.repo) in /etc/yum.repos.d:
2) Install rhc tools
$ su -c 'yum install rhc'
UPDATE: A new page has been added to the OpenShift Developer center clarifying this process for each operating system. It’s better than my steps above.
I have no technical backing for this suggestion except that I’ve seen it work on two different operating systems with the Google Chrome web browser.
Accessing my self-hosted WordPress blog to add posts and do site maintenance, page loads were taking FOREVER. The media uploader was hanging too. I thought it was a plugin hogging resources so I disabled a bunch of them and it still didn’t really help.
Finally I cleared the browser cache and cookies and now everything is back to normal speed.
Ideas anyone? I’m running plugins only provided by wordpress.org and the latest version of WordPress and everything else.