Language Selection

English French German Italian Portuguese Spanish

SymphonyOS - Act II (Alpha 4)

Filed under

SymphonyOS is proud to announce the release of Alpha 4, as seen on Distrowatch and the Symphony website. Tuxmachines is proud to take a look! I first became aquainted with Symphony back in May with the release of Alpha 3 and was quite impressed at that time with Symphony's unique desktop. As we take a look at this newest release today, we will be concentrating on what's new and improved.

If you'll recall, Symphony is based highly on Knoppix and uses much of its underpinning as well as some tools developed to work on Knoppix. For example, with Alpha 3, hard drive installation was possible using "knoppix-install" on the commandline, but Alpha 4 brings the Kanotix hard drive installation gui tool. This capable tools brings with it a warning that it is still under development and releases itself from responsibility of any and all data loss incurred with using it. I found it to be fairly straighforward and suffered no adverse effects. It did install and complete the job without incident. Some problems encountered include the bootloader step(s). The first being no option to skip the bootloader which is something sorely needed, especially since grub is the only option. The second came when trying to make the boot floppies. This step failed, but no on-screen feedback or second chance was given. All in all a fairly minor complaint given the infancy of both the tool and the os projects. Otherwise the installer completed its task as configured. ...Or so I thought.

The configuration is an exercise in simplicity for the user. It walks the user through partitioning if needed or otherwise designating and formatting partitions, setting up root passwords and an user account with password, as well as where to install the bootloader. However, it took two installs before I was able to boot the system. The first time I chose reisefs as it's usually my favorite, but it wouldn't boot as I reckon the initrd was created using an ext3 system. Reinstalling on ext3 allowed a boot.

However, the desktop would not load. I only got a big white screen. Tried as I might I couldn't coax that desktop into starting. As a result (my story is really late posting and) I wasn't able to get any synaptic screenshots (it wouldn't open on the livecd for me), but I can say that apt-get from the commandline was working fine.

Which leads (or bowls right passed) the other major improvement to SymphonyOS - the addition of apt/synaptic package management. I think everyone at least likes synaptic. I've yet to read any bad press on it. No matter if you're a source based, rpm-based, or deb-based distro lover, everyone likes apt/synaptic. I think this was a good (if not obvious) choice for Symphony.

Another new addition is the use of Beagle for local searches. I didn't realize that's what it was when I was using it, I just noticed it was a nice looking seach window that matched the whole of the desktop experience quite well.

Other improvements include desktop links (icons) to sound and net configuration tools, .desktop file support, and just an all over polish and spit shine. The theme is still an attractive blue and the corner icons/targets seem smaller and more discreet. Also new is this cool looking clock at the top center of screen. For a full list of improvements, one can visit SymphonyOS' Alpha 4 page.

Some of the links (icons) were still inoperative, but most did their job. The rox filemanagement was nice looking even if it couldn't open the jpeg thumbnails, instead giving the error kview not found. The fonts were gorgeous throughout even in firefox.

Overall Alpha 4 is an exciting development release. It shows wonderful improvement and future promise. Although a few problems were encountered, it performed very well for an alpha/development product. It just makes one even more anxious for a production quality release (no pressure, no pressure!) Big Grin

Speaking of the future, Ryan has given fans a glimpse. One change planned for Beta 1 includes a componentized Linux, that he explains will allow "compatibility with Progeny, Linspire, and Xandros along with other members of the consortium as well as with the core Debian." Another is Dashboard Compatibility, which he says will "make Symphony's desklet system compatible with Apple's Dashboard system. This means that if we succeed, dashboard widgets will be able to run inside Symphony OS." And yet another will be Multimedia. Ryans states, "we want beta 1 to let you play movies, organize photos, listen to music and internet radio all without going through the kind of effort usually required on Linux."

I've put a few Screenshots up in the Gallery, and SymphonyOS has some on their site. Also, for reference is my original story on SymphonyOS, which gives a fairly good introduction to this wonderfully revolutionary Linux distribution.

More in Tux Machines

Linux 4.8.4

I'm announcing the release of the 4.8.4 kernel. And yeah, sorry about the quicker releases, I'll be away tomorrow and as they seem to have passed all of the normal testing, I figured it would be better to get them out earlier instead of later. And I like releasing stuff on this date every year... All users of the 4.8 kernel series must upgrade. The updated 4.8.y git tree can be found at: git:// linux-4.8.y and can be browsed at the normal git web browser: Read more Also: Linux 4.7.10 Linux 4.4.27

New Releases: Budgie, Solus, SalentOS, and Slackel

  • Open-Source Budgie Desktop Sees New Release
    The pet parakeet of the Linux world, Budgie has a new release available for download. in this post we lookout what's new and tell you how you can get it.
  • Solus Linux Making Performance Gains With Its BLAS Configuration
    - Those making use of the promising Solus Linux distribution will soon find their BLAS-based workloads are faster. Solus developer Peter O'Connor tweeted this week that he's found some issues with the BLAS linking on the distribution and he's made fixes for Solus. He also mentioned that he uncovered these BLAS issues by using our Phoronix Test Suite benchmarking software.
  • SalentOS “Luppìu” 1.0 released!
    With great pleasure the team announces the release of SalentOS “Luppìu” 1.0.
  • Slackel "Live kde" 4.14.21
    This release is available in both 32-bit and 64-bit architectures, while the 64-bit iso supports booting on UEFI systems. The 64-bit iso images support booting on UEFI systems. The 32-bit iso images support both i686 PAE SMP and i486, non-PAE capable systems. Iso images are isohybrid.

Security News

  • Free tool protects PCs from master boot record attacks [Ed: UEFI has repeatedly been found to be both a detriment to security and enabler of Microsoft lock-in]
    Cisco's Talos team has developed an open-source tool that can protect the master boot record of Windows computers from modification by ransomware and other malicious attacks. The tool, called MBRFilter, functions as a signed system driver and puts the disk's sector 0 into a read-only state. It is available for both 32-bit and 64-bit Windows versions and its source code has been published on GitHub. The master boot record (MBR) consists of executable code that's stored in the first sector (sector 0) of a hard disk drive and launches the operating system's boot loader. The MBR also contains information about the disk's partitions and their file systems. Since the MBR code is executed before the OS itself, it can be abused by malware programs to increase their persistence and gain a head start before antivirus programs. Malware programs that infect the MBR to hide from antivirus programs have historically been known as bootkits -- boot-level rootkits. Microsoft attempted to solve the bootkit problem by implementing cryptographic verification of the bootloader in Windows 8 and later. This feature is known as Secure Boot and is based on the Unified Extensible Firmware Interface (UEFI) -- the modern BIOS.
  • DDOS Attack On Internet Infrastructure
    I hope somebody's paying attention. There's been another big DDOS attack, this time against the infrastructure of the Internet. It began at 7:10 a.m. EDT today against Dyn, a major DNS host, and was brought under control at 9:36 a.m. According to Gizmodo, which was the first to report the story, at least 40 sites were made unreachable to users on the US East Coast. Many of the sites affected are among the most trafficed on the web, and included CNN, Twitter, PayPal, Pinterest and Reddit to name a few. The developer community was also touched, as GitHub was also made unreachable. This event comes on the heels of a record breaking 620 Gbps DDOS attack about a month ago that brought down security expert Brian Krebs' website, KrebsonSecurity. In that attack, Krebs determined the attack had been launched by botnets that primarily utilized compromised IoT devices, and was seen by some as ushering in a new era of Internet security woes.
  • This Is Why Half the Internet Shut Down Today [Update: It’s Getting Worse]
    Twitter, Spotify and Reddit, and a huge swath of other websites were down or screwed up this morning. This was happening as hackers unleashed a large distributed denial of service (DDoS) attack on the servers of Dyn, a major DNS host. It’s probably safe to assume that the two situations are related.
  • Major DNS provider Dyn hit with DDoS attack
    Attacks against DNS provider Dyn continued into Friday afternoon. Shortly before noon, the company said it began "monitoring and mitigating a DDoS attack" against its Dyn Managed DNS infrastructure. The attack may also have impacted Managed DNS advanced service "with possible delays in monitoring."
  • What We Know About Friday’s Massive East Coast Internet Outage
    Friday morning is prime time for some casual news reading, tweeting, and general Internet browsing, but you may have had some trouble accessing your usual sites and services this morning and throughout the day, from Spotify and Reddit to the New York Times and even good ol’ For that, you can thank a distributed denial of service attack (DDoS) that took down a big chunk of the Internet for most of the Eastern seaboard. This morning’s attack started around 7 am ET and was aimed at Dyn, an Internet infrastructure company headquartered in New Hampshire. That first bout was resolved after about two hours; a second attack began just before noon. Dyn reported a third wave of attacks a little after 4 pm ET. In all cases, traffic to Dyn’s Internet directory servers throughout the US—primarily on the East Coast but later on the opposite end of the country as well—was stopped by a flood of malicious requests from tens of millions of IP addresses disrupting the system. Late in the day, Dyn described the events as a “very sophisticated and complex attack.” Still ongoing, the situation is a definite reminder of the fragility of the web, and the power of the forces that aim to disrupt it.
  • Either IoT will be secure or the internet will be crippled forever
    First things first a disclaimer. I neither like nor trust the National Security Agency (NSA). I believe them to be mainly engaged in economic spying for the corporate American empire. Glenn Greenwald has clearly proven that in his book No Place to Hide. At the NSA, profit and power come first and I have no fucking clue as to how high they prioritize national security. Having said that, the NSA should hack the Internet of (insecure) Things (IoT) to death. I know Homeland Security and the FBI are investigating where the DDoS of doomsday proportions is coming from and the commentariat is already screaming RUSSIA! But it is really no secret what is enabling this clusterfuck. It’s the Mirai botnet. If you buy a “smart camera” from the Chinese company Hangzhou XiongMai Technologies and do not change the default password, it will be part of a botnet five minutes after you connect it to the internet. We were promised a future where we would have flying cars but we’re living in a future where camera’s, light-bulbs, doorbells and fridges can get you in serious trouble because your home appliances are breaking the law.
  • IoT at the Network Edge
    Fog computing, also known as fog networking, is a decentralized computing infrastructure. Computing resources and application services are distributed in logical, efficient places at any points along the connection from the data source (endpoint) to the cloud. The concept is to process data locally and then use the network for communicating with other resources for further processing and analysis. Data could be sent to a data center or a cloud service. A worthwhile reference published by Cisco is the white paper, "Fog Computing and the Internet of Things: Extend the Cloud to Where the Things Are."
  • Canonical now offers live kernel patching for Ubuntu 16.04 LTS users
    Canonical has announced its ‘Livepatch Service’ which any user can enable on their current installations to eliminate the need for rebooting their machine after installing an update for the Linux kernel. With the release of Linux 4.0, users have been able to update their kernel packages without rebooting, however, Ubuntu will be the first distribution to offer this feature for free.
  • ​The Dirty Cow Linux bug: A silly name for a serious problem
    Dirty Cow is a silly name, but it's a serious Linux kernel problem. According to the Red Hat bug report, "a race condition was found in the way the Linux kernel's memory subsystem handled the copy-on-write (COW) breakage of private read-only memory mappings. An unprivileged local user could use this flaw to gain write access to otherwise read-only memory mappings and thus increase their privileges on the system."
  • Ancient Privilege Escalation Bug Haunts Linux
  • October 21, 2016 Is Dirty COW a serious concern for Linux?
  • There is a Dirty Cow in Linux
  • Red Hat Discovers Dirty COW Archaic Linux Kernel Flaw Exploited In The Wild
  • Linux kernel bug being exploited in the wild
  • Update Linux now: Critical privilege escalation security flaw gives hackers full root access
  • Linux kernel bug: DirtyCOW “easyroot” hole and what you need to know
  • 'Most serious' Linux privilege-escalation bug ever discovered
  • New 'Dirty Cow' vulnerability threatens Linux systems
  • Serious Dirty Cow Linux Vulnerability Under Attack
  • Easy-to-exploit rooting flaw puts Linux PCs at risk
  • Linux just patched a vulnerability it's had for 9 years
  • Dirty COW Linux vulnerability has existed for nine years
  • 'Dirty Cow' Linux Vulnerability Found
  • 'Dirty Cow' Linux Vulnerability Found After Nine Years
  • FakeFile Trojan Opens Backdoors on Linux Computers, Except openSUSE
    Malware authors are taking aim at Linux computers, more precisely desktops and not servers, with a new trojan named FakeFile, currently distributed in live attacks. Russian antivirus vendor Dr.Web discovered this new trojan in October. The company's malware analysts say the trojan is spread in the form of an archived PDF, Microsoft Office, or OpenOffice file.

today's howtos