Browsing the Web on the Tungsten C

Tags

browsers, ibm, J9, jvm, NetFront, Opera, Opera Mini, palm, PalmOS, TeaShark, WEME, Xiino

I had just about figured that browsing the web using Palm’s Tungsten C was impossible. It comes with a browser, but that was never usable as far as I could tell. I tried numerous other options, and finally found one that worked much better than I had dared to hope.

I tried using Xiino. This browser just looks ugly to start (with decidedly low-resolution graphics), and has completely incomprehensible icons. It wasn’t usable at all; most pages would result in a blank screen. It also uses a proxy server for images (though it doesn’t call it that): the “DataServer” – pds.mobirus.com – no longer exists, which means that you can’t display anything at all unless that setting is cleared. There’s no way to set or unset it; just clear the name entirely.

I tried using Opera Mini. This requires using the old IBM Websphere Everyplace Micro Edition (WEME) – which in reality is the J9 Java Virtual Machine (JVM). The word is that IBM WEME 5.7.1 is much more stable than IBM WEME 5.7.2 (neither of which are supported or available any longer). No matter – Opera Mini v4 (the current) did not work at all, but froze during initial operation; Opera Mini v3 works but crashes reliably and frequently.

I even tried something called TeaShark; that didn’t get past the startup stage (which was buggy at the outset). This wasn’t too surprising since it was running on IBM’s J9 JVM like Opera; word has it that the IBM JVM was crippled on PalmOS in some way.

I love Opera Mini, and used it on my Nokia 6265i (and later the 6165i) – and missed it. However, running it on the J9 JVM gave a completely different experience (I never did try using Sun’s Java Manager – but that was for MIDP 1.0 only) I started thinking to myself: the NetFront browser on my Samsung Caliber is ever so much better…

Then imagine my surprise when I found that there is a NetFront browser for PalmOS. It turns out that the Sony Clie (a PalmOS device) used NetFront for their default browser, and that it would work on a Palm device as well. There are copies of it available on the web, but the one I saw came with something called MaxX to make it work with a different screen resolution than the original browser expected to find (on the Tungsten T I think).

After downloading and installing via HotSync – using Linux (with GNOME’s gpilotd) – the browser crashed when run. However, running on the Tungsten C, MaxX is unneeded; removing it solved the problems entirely.

Running with the NetFront browser has been a delightful (and unexpected) experience. The only problem seems to be a connection-related problem; for some reason, the WiFi connection seems to “age” and loses connectivity even though the device doesn’t think so. Reconnecting seems to fix this.

For more details on using the NetFront browser – and people’s experiences with it – check out this forum thread over at 1src.com.

If you use Google for RSS or for news, try m.google.com in NetFront; it’s the best experience I’ve had yet. You can also use Google’s mobile gateway directly by going to www.google.com/gwt/n and entering the URL that you wish to go to.

Intel’s New Upgradeable CPU: Not a New Idea – But is it a Good One?

Tags

cpu, Intel, processors, upgradeable

There has been some discussion about the new processor from Intel which comes with some features disabled and unlockable only by purchasing an unlock code from Intel. Peter Bright has an excellent write-up on the idea of an upgradeable processor.

If you administer mainframes or enterprise servers, you’ve likely already seen this idea. HP Superdomes, for example, can be purchased with deactivated processors and so forth, then the processors can be turned on temporarily or purchased outright at a later date. IBM Z System also comes with a similar capability – often called something like Capacity on Demand.

The main question is whether the consumer will find this a desirable thing or not; it is possible that the idea will not sell. I find that system “upgrades” are actually done by replacing the system completely.

It is also probably a better idea to increase system memory than it is to upgrade to a faster, more capable processor. More memory means more can be done without going to disk, which is always important as disk is the slowest element.

Rising from the Ashes: OpenIndiana Continues OpenSolaris Open Source Legacy

Tags

Illumos

Several weeks ago, Oracle declared that it would no longer be releasing code to the open source community as it was developed, as well as cutting off communication with the OpenSolaris Governing Board (and thus, the community). The Illumos project was created to continue the kernel development; in the same arena, OpenIndiana now continues the open source ideals with an open version of OpenSolaris under the Illumos Project banner.

Downloads are already available, although it is not yet recommended for production use.

I find the prospects of OpenIndiana exciting; this project is separate from Oracle, who cannot be relied upon for any support of open source. With a serious community behind it, OpenIndiana could very well be a way for shops to run the very capable Solaris environment without having to succumb to a costly support contract before they can afford it. It also allows individuals to run a version of Solaris with current features, quick bug fixes, and more software.

In spite of the general demise of OpenSolaris as a driving force, the times are exciting for the Solaris-based community.

Upgrading a Palm Tungsten C to New ROMs

Tags

Palm Pilot, Palm Tungsten, Splashnews, TealMaster, TealScript, Tungsten C

I had problems with my Tungsten C – with the WiFi not working and the bottom 10 pixels or so of the screen being unresponsive to taps. I had just assumed that this was a sign of hardware failure – after all, the system was used and sold at half the going rate for used Tungsten C models.

However, upon further research, it turns out that upgrading the ROM was a possible fix. This was ultimately a resounding success. As part of the upgrade, all data was erased.

The upgrade was basically a three step process: 1) make sure the system can be upgraded; 2) prepare the system (which could include removing applications or files); and 3) install the update application and run it. The process includes many more details, but that is the essence of it. I used my Ubuntu Lucid Lynx installation of GNOME Pilot to remove the files, then made sure they were erased on the Tungsten with FileZ.

After running the update, the system is cleared of all applications and data. There were several problems that came up; I wound up clearing the Tungsten of all applications and installing fresh (to remove the cruft from old applications).

One problem was applications that absolutely refused to be deleted. Presumably, this is because there is some hook into the system or otherwise which prevents it from being deleted. Reset the machine while pressing up-arrow key, then release the key after seeing the Palm logo. This starts the system without any extra software hooks. Go into FileZ (or other file manager, such as TealMover) and delete the application – removing the ReadOnly bit if necessary.

Another problem is applications that may need a setup to install, in contrast to the usual installation of a couple of files. SplashNews was one such application. Don’t restore the file; best is to get the original files and reinstall (using the setup applications).

Yet another problem was the TealMaster or TealScript applications (or other similar applications). While the application will work fine, the backed up version of the file does not work. Again, get the original files and install from there. The backed up files are not the correct ones.

After doing all this – I decided to upgrade a few things, the launcher primary among them. I’ve switched (for the moment) from Launcher III to Propel for my launcher; very nice – recommended! Only drawback is Launcher III is free (although web site is gone) and Propel is $15. However, Propel is much more current, so it is more likely to have fewer bugs and more capabilities.

All in all, this upgrade to the Tungsten C ROMs has solved both problems and has resulted in more space due to removing all the unnecessary files. Do it if you have problems with your Tungsten C.

An Ode to English

Tags

English

There are many reasons for writing a blog. For me, there are several: 1) to pass on knowledge of system administration (including technical tips, career tips, industry knowledge, and so on) – while creating a moderate level of permanence; 2) to “thicken” the web, adding links and knowledge; 3) and lastly, for the love of writing.

Over at the blog Jenn in Japan, the author mourns her apparent loss of the finer aspects of English usage and grammar after spending so much time in the Japanese language instead. It is a beautiful read; go on and check it out.

VMware to Buy Novell’s Linux Business?

Tags

java, novell, spring, SpringSource, vmware, Zimbra

This is very interesting indeed. VMware and Novell just announced that VMware would sell SUSE Linux Enterprise Server on VMware’s vSphere product (with full support by VMware) – and now there is a report by the Wall Street Journal that Novell’s Linux business could be bought by VMware. Talks are continuing, but this is intriguing to say the least.

The focus is on SUSE Linux Enterprise Server, but Novell’s Linux “businesses” also include GNOME and Mono; it should be interesting to see what happens next.

Novell has been through some very rough times – first WordPerfect, then Netware, then UNIXware, and now SUSE. When SCO (not The SCO Group!) was split up, what was left was a shell of its former self; I hope that does not happen to Novell.

If VMware buys Novell’s Linux business, then SUSE would join Zimbra and SpringSource in the fold.

Let’s not forget, too, that VMware is owned by the storage company EMC. This could make itself felt in superior support for EMC products in SUSE Linux.

Personally, I feel better about SUSE being in the hands of VMware than I ever did thinking about Sun (and Solaris) in the hands of Oracle. I would also be surprised if some other company got SUSE instead; with the recent cooperation between the two companies VMware is the natural choice.

There was also the rumor that Attachmate would take on some of Novell’s other businesses. Attachmate has been good to the Reflection Suite for X that I like and recommend; perhaps Attachmate could be a good match as well.

User Experiences with System Updates (Fedora)

There has been a lot of discussion about the direction of Fedora, apparently brought on in part by massive updates being pushed to recent Fedora users. I’ve not used Fedora for a long time – for various reasons – but this is good discussion.

Máirín Duffy has a fantastic article (it is a must read!) describing possible user profiles for Fedora Linux, as well as a description of how updates should be done. One thing she mentions that I haven’t seen in Linux before is the idea of an “update bundle”.

Bundled updates are done in many UNIX environments, including HP-UX and Solaris. In my experience with HP-UX, all of the updates are available separately, but there are also patch bundles that are put through strenuous QA together. With all of the patches run through QA as well as the bundle, this leads to better stability for the environment.

Also in HP-UX, each patch is posted with a “patch readiness level” that explains what amount of QA the patch has actually seen so far. Thus, you can load that patch early if you want, or wait until its rating (given in a star rating) rises, indicating less likelihood that the patch will break the system.

Most Linux systems are run through QA as a system, with each package being tested and sent through QA individually.

With all of the discussion that I read, it seems almost like a new spin or distribution is almost necessary which would capture the essence of Fedora with the stability found in Debian Stable or Ubuntu LTS. The camps seem to be split between two sorts of people:

• People who want the latest versions of everything all the time, no matter how many updates are needed.
• People who want a system that is stable and doesn’t change.

If the current leadership is unwilling to accommodate those that want stability and reliability, then they will go somewhere else to find it. This would be a dramatic loss to the Fedora community in my opinion.

Native ZFS for Linux Coming (and Other ZFS News)

Tags

Behlendorf, file systems, KQ Infotech, Lawrence Livermore, LLNL, zfs

Two different projects are in full swing developing a native port of the ZFS file system to Linux. Currently, the only available ZFS for Linux is based on FUSE (running file systems in user space, not kernel space). Running with FUSE means a significant penalty in speed.

One ZFS project is being done at Lawrence Livermore National Laboratory and is driven by Brian Behlendorf; the other project is being done by KQ Infotech. OSNews had a good article about the LLNL project.

Phoronix is reporting that KQ Infotech announced they would be releasing source code in September. Unfortunately, the project apparently only supports 64-bit Linux, and does not support data de-duplication and other newer features.

The writer is also unimpressed by ZFS overall; there is mention of BtrFS as being better. What is truly interesting is that both file systems are now are under the Oracle umbrella – BtrFS since the beginning, and ZFS as part of the Sun acquisition.

On top of this, Oracle and NetApp have resolved the lawsuit over ZFS, removing the clouds that had hung over ZFS.

These are interesting times for ZFS. If you don’t understand what the fuss is all about, Paul Rubens has a quick overview, and Sun’s ZFS team has an excellent slide presentation on ZFS. There are more ZFS resources available from the OpenSolaris ZFS Community.

Administrator Experiences with VMware and SUSE Linux

Tags

ESXI, novell, SLES, suse, vmware, vSphere

Recently, VMware announced a partnership with Novell in which they would support Novel SUSE Linux Enterprise Server (SLES) directly on VMware vSphere. Neil over at VirtuallyNil wrote about his experiences with SLES and VMware ESXI. Unfortunately, he had some problems with VMware’s additions to SLES.

To enhance the experience with virtual machines, virtual environment managers add tools to the guest environments – and VMware is no different. For SLES there are tools available that permit advanced operations directly from the virtual machine manager. With ESXI, these are available for SLES 10 and SLES 11 – but not SLES 11 SP1.

This means that you either build your own SLES 11 SP1 tools or you cannot upgrade your SLES 11 to the most recent patch level. This is unfortunate.

I have experienced this before with an application that required a particular version of Red Hat Linux (7.1 if I remember rightly) even though that version of Red Hat was no longer supported by Red Hat itself.

Also, Neil points out two other sites that have images of people’s direct experiences with the new VMware-supported SLES. One first look comes from vcritical.com (a blog by Eric Gray, a VMware employee); the other comes from Jase McCarty at Jase’s Place.

How Systems Fail (and Principles of Prevention)

Tags

bp, bp oil spill, errors, failure prevention, failures, Virginia

A system failure does not always have a single, identifiable (and preventable) cause. In fact, often it does not.

The BP oil spill provides an excellent case study of this situation: the spill has numerous contributing causes, most of which seem minor or unlikely in isolation, but which taken together resulted in catastrophe.

What general principles can we apply to prevent such cascade failures? One should already be familiar: Test, test, test fail-over systems before they are needed. Without testing, there is no guarantee that things will work as expected. In the BP oil spill, several failsafe systems did not properly engage as expected. In the recent IT disaster in Virginia, a storage system did not fail over when needed, resulting in a down-time of several days for a significant portion of state resources.

Another principle is: Sift and winnow alarms to the truly necessary. Pay attention to alarms and other indicators, and to purge alarms and notifications that are irrelevant or unnecessary. In the oil spill, one of the causes was that the indications that there was an immediate problem were masked by other occurrences at the time. Too many alarms and too much information can hide problems and lead to administrators ignoring problems that require intervention.

To improve alarms, and prevent unnecessary alarms, use time based alarms, i.e., alarms that account for change over time. Products such as SGI’s Performance CoPilot (PCP), HP’s Performance Agent (included with some versions of HP-UX), and the System Event Correlator (SEC) all help. With alarms that work over a time-span, momentary brief peaks will not result in alarms, but chronic problems will.

Another item that can improve alarm response is systemic alarms: that is, monitoring that accounts for multiple systems or processes, and combines it all into an appropriate setting. Is the web site running smoothly? Are all systems reporting logs to the central server? Are all virtual environments running?

One of the earliest problems that lead to the oil spill was a lack of oversight of the contractors involved in building the well. Each assumed that the others would do the right thing. In system administration, we assume that other systems are functioning correctly. To prevent failure, we should assume that other systems and processes could fail, and verify for ourselves that the systems we are responsible for will not fail in any case. What systems are you dependent on? Power? Cooling? Serial concentrator? Operations staff? Backup staff?

Part of the problem in the Virginia failure was that the state did not oversee the external vendor well. With proper oversight (and demands), the state IT staff could have forced the storage vendor to test the fail-over processes, and could have implemented a backup plan in case the fail-over did not take place as expected.

By studying other’s fail patterns and experiences, we can help to minimize our own.