Actually SUSE Linux began deployment at ESA in 2012 and has been continuing until now, the distro is used by 450 teams in the European Space Operations Centre at ESA, this includes being used by Mission Control Systems who are responsible for simulation and control of aircraft and satellites outside the atmosphere and further still.
Until now, as with most new versions of software, new code for a new version of OpenSUSE had been bottled up for group testing at a beta or milestone stage.
In the OpenSUSE world, this milestone stage had taken place in something called the "Factory".
The milestone approach is now being abandoned.
The goal is to get more users and contributors involved in development and testing phase, speeding up fixes and improving quality.
In the past 4 months during this years Google Summer of Code (GSoC), a global program that offers student developers stipends to write code for open source software projects, Christian Bruckmayer collaborated with other students and mentors to code a dashboard for the Open Source Event Manager (OSEM). In this series of three posts Christian will tell you about his project and what he has learned from this experience.
OpenSUSE "Factory" up to now has referred to the development version of the openSUSE Linux distribution while being announced by SUSE today is that it's also going to serve as an independent distribution under a rolling-release development model.
OpenSUSE Factory will still serve where openSUSE development takes place, but it's also going to aim for being a distribution on its own as a "tested and stable fresh-daily bleeding-edge distribution."
The SUSE method for live kernel patching, kGraft, is being proposed for possible inclusion into the linux-next branch in hopes it will be merged into an upcoming Linux kernel release cycle.
The kGraft patches for live kernel patching continue to be revised and reviewed but at the same time there's still Kpatch that's been developed by Red Hat with some different design principles for updating the running kernel in real-time. To date there's been no general consensus on the superior solution nor any agreement to try to merge Kpatch and kGraft.
There are so many Linux distributions in the world that sometimes it's difficult to keep track of each and every one of them. Despite what people might think about Linux distros, the truth is that most of them are actually uninteresting and of sub-par quality.
People are used to the quality of systems like Ubuntu, Debian, Linux Mint, or openSUSE, but not all distros have been created equal. In fact, users wouldn't install such distros because they simply lack a team with the manpower to make the operating system interesting.
In order to install Linux from a bootable USB stick I need to be able to get to the Boot Selection menu, but on Acer systems with UEFI firmware, this is a bit tricky. The Boot Menu key (F12) is disabled by default, so I first have to boot to the BIOS Setup Utility, by pressing F2 during the power on or reboot cycle. Then in the Main setup screen there is an option to enable "F12 Boot Menu".
That's one trick down, but there's another one which might be required. Depending on what version of Linux you want to install, and perhaps how you feel about Secure Boot, you might want/need to disable that. In the BIOS Setup Utility, on the Boot menu there is an option to disable Secure Boot - but I can't get to it: moving the cursor down just skips over it!
I can change boot mode from UEFI to 'Legacy BIOS', but that isn't what I want to do. I learned (the hard way) with my previous Acer Aspire One, that I have to go to the Security menu and set a "Supervisor Password" before it will let me disable Secure Boot mode. I'm sure this makes sense to someone, but whoever that is, it isn't me.
In this case I am going to start by installing Linux with Secure Boot still enabled, so I don't really have to do this, but I went ahead and set a supervisor password anyway, because I will eventually want to turn off Secure Boot anyway.