Language Selection

English French German Italian Portuguese Spanish

Alternative GUIs: SymphonyOS

Filed under
Linux

Notes:

  • This is the first of two articles; the second one will take a look at GoblinX.
  • SymphonyOS was originally reviewed on this site in May, 2006, and again in December, 2006. Since then, SymphonyOS suffered through some financial problems, but seems to be alive and well today.

We're all familiar with the "big two" desktops for Linux — KDE and GNOME. Of course, there are many more to choose from. If you asked a group of Linux users, "Which one is best?", the ensuing debate would likely take on religious overtones. Some would even argue that a desktop like KDE is too hard for newbies to use.

One of the things that can be difficult for Windows users to understand is how Linux users have a choice of graphical user interfaces (GUIs). Even though Windows itself used to be a graphical shell running on top of DOS, until the advent of Windows NT and beyond, Windows users just get one choice of GUI.

It's a safe bet that most Linux users don't stray too far away from those "big two," KDE and GNOME. So it's especially interesting to look at some innovative alternatives.

SymphonyOS

SymphonyOS is a departure from the normal desktop interface. Since the distro is still in beta, it's not ready for mass consumption by any stretch. I wanted to take a look at the just-released version 2007.06. The reason I used version 2006-12 for this overview is that the hard disk installer in version 2007.06 simply didn't work. (Installing 2006-12 wasn't exactly easy, either — more on that below.) Hopefully they'll iron out the bugs, because users new to Linux might well appreciate SymphonyOS' simplicity.

The SymphonyOS desktop (named "mezzo") seems to be a marriage of the fvwm window manager with Mozilla's scriptable layout engine, Gecko. On the desktop, there are areas with links in them (known as "desklets" and "launchers"). When clicked, the links can bring up Web pages or programs. In the four corners of the desktop, there are hotspots that bring up what are referred to as "menus," which are actually full-page views of four specific functional areas: Computer (settings); Files; Programs; and Trash. In the top center of the main page, there's a hotspot containing the clock, that also works as the way to refresh the desktop after the desktop background image has been changed through SymphonyOS' Desktop Manager.

SymphonyOS comes as a live Linux CD, and uses ROX-Filer as its default file manager, and also includes Firefox; Thunderbird; Gaim (for instant messaging); and the VLC media player (the latter didn't work until it was reinstalled).


SymphonyOS login screen

Once logged in, the user is presented with the main screen, which has an area for favorite programs on the left, an area for favorite directories on the right, a bunch of news feeds, and a Google search box. On the whole, it has the feel of Web page, but one that gives you access to programs and directories as well.

  

The Desktop Manager allows you (in theory, at least) to change the contents of the desklets and launchers, as well as to change the desktop's background image.

   

The Desktop Manager

When you click on the hotspot in the upper left-hand corner, it brings you to the "Computer" page, offering you access to your partitions, various settings, and "tasks" such as shutting down the computer.

   

The Computer menu

The hotspot in the lower left-hand corner brings up the "Programs" page, with launchers for favorite programs; all programs; and tasks (such as installing software).

   

The Programs menu

The hotspots in the upper right-hand corner and lower right-hand corner bring up the "Files" page and the "Trash" page, respectively. At this point, they don't seem to do a lot. (Perhaps you'll be able to "drag-and-drop" in future editions.)

   

The Files menu and Trash menu

I'm looking forward to SymphonyOS' continued success and development. It's an innovative and novel concept.

On a personal level, it passed the "wife test" — she praised its ease-of-use. (Since I've been trying to get her to allow me to put Linux on her computer, but only (so far) managed to get her hooked on playing Shisen-Sho (a game that comes with KDE) on my computer, this may eventually be the distro for her.)

One could also easily imagine a SymphonyOS-like desktop operating completely within a web browser. The trend seems to be pointing that way already. It's not hard to imagine the day you'll be able to start up a Web browser on a Windows-based computer in a library someplace, and have something very similar to SymphonyOS come up with your files and settings, ready to go.

Boring Technical Stuff

This version of SymphonyOS (2006-12) is based on Debian Etch. The new version (2007.06) is Ubuntu-based. Either way, it would seem that you could install other desktops (like GNOME) if you wanted to. Note how it offers "Mezzo" as a choice among login sessions in the following gdm ("GNOME Display Manager") screenshot.

As noted above, the installer for version 2007.06 simply didn't work.

There were multiple problems with installing version 2006-12. It didn't install GRUB, like it said it would — not a big deal, since an openSUSE installation already controls GRUB on my test box — but it also didn't install a kernel to boot from ("vmlinuz") or an initial RAM disk ("initrd") in /boot. I had to copy those off the live CD. The next problem was that the "initrd.gz" I copied over went with the live CD (which, for 2006-12, is based on the Slax subsystem), not with the actual installation, so it went looking for the live CD and its loadable modules upon boot. Fortunately, that didn't ultimately stop it from booting. Once installed, it was easy enough to create a compatible "initrd" by installing and using normal Debian-based tools.

Another problem I encountered was that the live CD (of version 2006-12) didn't properly configure my display's resolution or sync rates. I had to use the vi editor to configure /etc/X11/xorg.conf. Yikes! (However, the newest version did.)

Finally, here's something to ponder: Will the developers of this system create tools to change desktop elements that are as easy-to-use as the OS itself, or will the desktop user need to turn to someone with a knowlege of scripting in order to make changes? Arthur C. Clarke is quoted as saying, "Any sufficiently advanced technology is indistinguishable from magic." How well will SymphonyOS succeed at making its magic accessible to the end user?


Purchase a 2007-06 CD from On-Disk.com.



StumbleUpon

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Great review

It's nice to see the very latest and greatest of Mezzo, especially after SymphonyOS threw out and begged for a lifeline in their Web site. With a solid Ubuntu base, they could have a lot to offer. Where's Ulteo BTW?

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30