Language Selection

English French German Italian Portuguese Spanish

GoblinX Releases G:Noblin 3.0.beta01

Filed under
Linux

"The GoblinX Project is proud to announce the third beta of the next stable release. The G:Noblin is the GoblinX Gnome and GTK/GTK2 based distribution. The edition is ideal for those users whose are fan of the Gnome desktop environment. This distribution is an old desire of GoblinX users.

The G:Noblin edition include GNOME 2.24.3 and several improvements and modifications in the core of the system. The method of save changes are different in this edition. Now all changes are saved in different directories when the Netbook interface is used or a non english language. Also we added a second check for swap partition when blkid fails to find it, we changed the default graphical boot to use GDM for english and also all other languages and added some other improvements.

The G:Noblin brings to you two kinds of desktop environment inside the same ISO (cdrom). The first is the default Gnome desktop and the second is a special prepared interface for Netbooks, using the Ubuntu Netbook Remix model and some ideas provided by Foresight."

Announcement: http://www.goblinx.com.br/en/?p=888

More in Tux Machines

Mozilla, Firefox, and FirefoxOS

  • B2G OS and Gecko Annoucement from Ari Jaaksi & David Bryant
    In the spring and summer of 2016 the Connected Devices team dug deeper into opportunities for Firefox OS. They concluded that Firefox OS TV was a project to be run by our commercial partner and not a project to be led by Mozilla. Further, Firefox OS was determined to not be sufficiently useful for ongoing Connected Devices work to justify the effort to maintain it. This meant that development of the Firefox OS stack was no longer a part of Connected Devices, or Mozilla at all. Firefox OS 2.6 would be the last release from Mozilla. Today we are announcing the next phase in that evolution. While work at Mozilla on Firefox OS has ceased, we very much need to continue to evolve the underlying code that comprises Gecko, our web platform engine, as part of the ongoing development of Firefox. In order to evolve quickly and enable substantial new architectural changes in Gecko, Mozilla’s Platform Engineering organization needs to remove all B2G-related code from mozilla-central. This certainly has consequences for B2G OS. For the community to continue working on B2G OS they will have to maintain a code base that includes a full version of Gecko, so will need to fork Gecko and proceed with development on their own, separate branch.
  • Firefox 53 Will Drop Support for Windows XP and Windows Vista
    Software companies are one by one giving up on Windows XP support for their products, and now it appears that it’s Mozilla’s turn to switch the focus to newer versions of Windows. Firefox 53 will be the first version of the browser which will no longer support Windows XP and Windows Vista, so users who haven’t yet upgraded to Windows 7 or newer will have to either stick with Firefox 52 or move to a different browser.
  • Boot 2 Gecko Being Stripped From Mozilla's Codebase
    At the end of 2015 Mozilla effectively put an end to Firefox OS / Boot 2 Gecko by concluding things weren't working out for Mozilla Corp and their commercial partners to ship Firefox OS smartphones. All commercial development around it has since stopped and they are now preparing to strip B2G from the mozilla-central code-base. The news to report on now is that Ari Jaaksi and David Bryant have announced, "Today we are announcing the next phase in that evolution. While work at Mozilla on Firefox OS has ceased, we very much need to continue to evolve the underlying code that comprises Gecko, our web platform engine, as part of the ongoing development of Firefox. In order to evolve quickly and enable substantial new architectural changes in Gecko, Mozilla’s Platform Engineering organization needs to remove all B2G-related code from mozilla-central. This certainly has consequences for B2G OS. For the community to continue working on B2G OS they will have to maintain a code base that includes a full version of Gecko, so will need to fork Gecko and proceed with development on their own, separate branch."

Blockchain Going Mainstream

FOSS in Networking

  • OPNFV Colorado platform bolsters open source NFV efforts
    The Linux Foundation’s Open Platform for NFV project claims its third platform release targets accelerating development of NFV apps and services The telecom market’s continued move towards integrating network functions virtualization received a boost as the Linux Foundation’s Open Platform for NFV project released its latest Colorado platform release, the third from the open source-based organization.
  • Open-source NFV Project delivers third platform release
    The OPNFV Project, an open source project that facilitates the development and evolution of Network Functions Virtualization (NFV) components across various open source ecosystems through integration, deployment, and testing today announced the availability of OPNFV Colorado, the project’s third platform release.
  • Inocybe Technologies Launches Community Version of their Open Networking Platform
  • Open Source Getting on My Nerves
    Open source people are generally not dirt dishers, however. Take Phil Robb of OpenDaylight , where he is senior technical director. Robb was on that MANO panel in Denver, and he spoke to me shortly afterward in an interview on ODL's new Boron software release. I specifically asked him about the "messy MANO situation" right now. His response was frustratingly calm. "I would equate the MANO space with where the controller space was three years ago," he says. "One of the great things about open source is that real code is going to be up, going to be used, stuff will work or it will fall over. But we'll fail fast and move on." (See Carriers Driving ODL's Boron Release.) So having multiple versions in process isn't a bad thing, Robb says, because it might be that one approach works better for a set of use cases than another. What the industry will come around to "sooner rather than later" is that one approach likely addresses the broadest set of use cases and will be more widely adopted, while others address niches and either are used alongside the major approach or incorporated into it.

Open Access on the Rise